Database Develop

Easy 'sysrw' and 'sysro' scripts for remounting system in Android! (S-OFF only!)

Tired of typing out that long "mount" command for remount system as read/write in Android?
NOTE: This is for S-OFF only!
Before you start, run this command in adb:
Code:
ls /system/bin/bash
If you get "bash: no such file or directory", run this command
Code:
ln -s /system/bin/sh /system/bin/bash
A new command prompt means the command completed successfully.
Now ensure bash is there:
Code:
ls /system/bin/bash
If it finds "bash", then continue on!
Here are two easy ways to stop the typing and make your life easier!
If you like using adb:
1. Download this zip, extract, and push the "sysrw" and "sysro" files to /system/xbin
2. Then run chmod 755 /system/xbin/sysrw and chmod 755 /system/xbin/sysro
Now, all you have to do is shell in and type "sysrw" to remount as read/write, or "sysro" to remount back to read-only!
If you don't like using adb:
1. Download Scripter from the market, QR:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Open Scripter, and tap on "Scan script" and scan these two QR codes:
sysrw:
sysro:
You can run them to make sure they work.
3. Long press on each one and save as "system read/write" and "system read-only" to know which one does which. (If you forget, the one with the command remount,rw is read/write, and the one with remount,ro is read-only)
That's it! Just open Scripter and tap on each to run them when you need to remount system!

Cool, you beat me to it. I was going to post something similar. Another option to keep in mind if you are using adb is the command:
Code:
adb remount
Run that command before anything else and it will remount your partitions as rw. Then you can push anything you want to /system.

This makes developing within the phone much easier and more fun.
What I did before these scripts was when I opened my Terminal Emulator on my phone, I had the mount -r blah.. as an initial command. Worked nicely for a while. I like this better because I can set it back as read only with ease.
Thanks.

Awesome, thank you!

This is the same as going into root explorer and clicking mount R/W for read/write, correct?

Is this supposed to make the build.prop file rw? Because when I run the script, the file still says -r-.
I'm not seeing a change to the /system folder when running the script. The permissions in Astro say dr- before I run the script and don't change after I run it.

mozetti said:
Is this supposed to make the build.prop file rw? Because when I run the script, the file still says -r-.
I'm not seeing a change to the /system folder when running the script. The permissions in Astro say dr- before I run the script and don't change after I run it.
Click to expand...
Click to collapse
This has nothing to do with changing file permissions--it shouldn't permanently change anything. Running this script is like kinda giving Ubuntu elevated privileges -- you are authorizing read-write access for yourself to make changes to /system, temporarily. It ends when you run the other script, reboot, or kill the terminal session you started (I assume).

rynosaur said:
This has nothing to do with changing file permissions--it shouldn't permanently change anything. Running this script is like kinda giving Ubuntu elevated privileges -- you are authorizing read-write access for yourself to make changes to /system, temporarily. It ends when you run the other script, reboot, or kill the terminal session you started (I assume).
Click to expand...
Click to collapse
Ok, so if I run this script then should I be able to open build.prop with Astro (long-hold, open as text, using file editor), make changes, and then save the file?
Because if that's the case, it's not working. I'm not a Linux pro, but I run Ubuntu on my desktop. I'm pretty sure that if you mount /system as read-write (which this script is supposed to do), then the permissions that show in Astro for the /system folder shouldn't b dr-, correct?

mozetti said:
Ok, so if I run this script then should I be able to open build.prop with Astro (long-hold, open as text, using file editor), make changes, and then save the file?
Because if that's the case, it's not working. I'm not a Linux pro, but I run Ubuntu on my desktop. I'm pretty sure that if you mount /system as read-write (which this script is supposed to do), then the permissions that show in Astro for the /system folder shouldn't b dr-, correct?
Click to expand...
Click to collapse
AFAIK, Astro does not do root privileges, you need Root Explorer to do what you trying to do. Perhaps someone else will chime in who knows how to give multiple processes r/w. The way I would do that without Root Explorer is to open the build.prop in a text editor, make changes, then write it to /data, then in terminal emulator, remount /system, and then move the file to system with build.prop.new, rename the original something like build.prop.old, then rename new to build prop.

rynosaur said:
AFAIK, Astro does not do root privileges, you need Root Explorer to do what you trying to do. Perhaps someone else will chime in who knows how to give multiple processes r/w. The way I would do that without Root Explorer is to open the build.prop in a text editor, make changes, then write it to /data, then in terminal emulator, remount /system, and then move the file to system with build.prop.new, rename the original something like build.prop.old, then rename new to build prop.
Click to expand...
Click to collapse
Ok, thanks. I'm not ready to pay for root explorer because I'm not sure how much I'm going to need it. I'll give your method a shot.

mozetti said:
Ok, thanks. I'm not ready to pay for root explorer because I'm not sure how much I'm going to need it. I'll give your method a shot.
Click to expand...
Click to collapse
In your position, I'd use adb, actually. It's pretty easy to push/pull in adb rather than all that copying and renaming

kentoe said:
This is the same as going into root explorer and clicking mount R/W for read/write, correct?
Click to expand...
Click to collapse
Yes, it's for people who don't want to spend the money or who like the command line.
mozetti said:
Is this supposed to make the build.prop file rw? Because when I run the script, the file still says -r-.
I'm not seeing a change to the /system folder when running the script. The permissions in Astro say dr- before I run the script and don't change after I run it.
Click to expand...
Click to collapse
No, this doesn't let you edit specific files on system, it just lets you add or delete files while in Android. If you want to change build.prop, you need to pull it, edit it, and push it back and reboot. Before, we had to do this in recovery mode, now you can do it in Android by making system read/write with these scripts.

mozetti said:
Ok, thanks. I'm not ready to pay for root explorer because I'm not sure how much I'm going to need it. I'll give your method a shot.
Click to expand...
Click to collapse
I think Android Mate has root file explorer. It's free as well. Try that.

ihtfp69 said:
I think Android Mate has root file explorer. It's free as well. Try that.
Click to expand...
Click to collapse
Thanks, installing it now.
**EDIT** Just in case anyone else is following this, Android Mate didn't work. It requested and received ROOT privileges but when I try to paste a file into /system, it doesn't work. It gives me a message that says it copied the file, but the file doesn't actually get put into the folder. **/EDIT**

ihtfp69 said:
Cool, you beat me to it. I was going to post something similar. Another option to keep in mind if you are using adb is the command:
Code:
adb remount
Run that command before anything else and it will remount your partitions as rw. Then you can push anything you want to /system.
Click to expand...
Click to collapse
remember that "adb remount" only works if the default.prop has the "ro.secure=0" in the boot.img(ramdisk), most most kernels are using the anykernel method, which uses the existing ramdisk. so unless you or the ROM cook change the ramdisk it will be set to "ro.secure=1"
CW recovery uses its own default.prop with the setting changed.

I think these scripts are something Adrynalyne has had in his ROMs since he put out the "One ROM to Rule Them All".
*shrug* Cool that you got a simpler/portable way instead of pulling them out of Adryn's roms

these work great, very handy thanks!

Droid 3 Root Issues

Ok so i followed the instructions to root my D3 twice and i have gotten the proper results, after the second reboot when i adb to my device i am given the root prompt.
That is about it though. I have installed superuser, tried to install jrummy16 busybox installer so i could get titanium working, but neither of the apps can find superuser or get root access.
Any ideas. Sorry for not putting this in the OG Thread but figured that would get real big real quick, thought it might be easier to start a separate thread for issues with the exploit.

need to find and push the su binary to the phone first. Superuser won't work without it.

Alright i got it working.
Anyone know of a good resource for how to kill all of the bloatware?

Is it safe to use titianium to remove the VZ apps, as in uninstall not just freeze

Titanium backup
Sent from my DROID3 using Tapatalk

at this point, i've just been freezing things. I'm waiting till we get a better list of what we can safely remove without breaking things.

Feels good man!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

lordgodgeneral said:
need to find and push the su binary to the phone first. Superuser won't work without it.
Click to expand...
Click to collapse
Can anyone add this stuff to the guide? I know most of the stuff is logical for some of you, but I've never rooted a device or used android. (edit: and planning on getting a droid 3 soon)
Also how to delete bloatware and install/use ADB

DoubleYouPee said:
Can anyone add this stuff to the guide? I know most of the stuff is logical for some of you, but I've never rooted a device or used android.
Also how to delete stuff and install/use ADB
Click to expand...
Click to collapse
Here's exactly how I did it... all steps stolen from the thread in the developers forum:
1) Make sure you've installed the android-sdk from Google on your computer. (http://developer.android.com/sdk/index.html)
2) Connect phone to computer. In terminal or a dos prompt, navigate to the directory where you installed the sdk and where adb is located.
(example location)
and type the following:
Code:
adb shell
mv /data/local/12m /data/local/12m.bak
ln -s /data /data/local/12m
3) Power off and power back on your Droid 3.
4) Drop back to shell/prompt and back to adb location. Type the following commands:
Code:
adb shell
rm /data/local/12m
mv /data/local/12m.bak /data/local/12m
mv /data/local.prop /data/local.prop.bak
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
5) Restart the phone again. You now have root.
6) Get a copy of su (http://www.megaupload.com/?d=82FH3AGI) and extract it to the same directory as adb on your computer. Type the following:
Code:
adb remount
adb push su /system/bin
adb shell chmod 6755 /system/bin/su
7) Install superuser from the android market.
Done!

Thanks! And then you delete apps with superuser?

I'm having trouble with:
Code:
adb push su /system/bin
It keeps returning:
Code:
cannot stat 'su' : No such file or directory
I have su (from the above link) in the same directory as adb...
*EDIT*
I have root within adb. So I definitely did everything before this right.

Did you extract su from the zip and put in the same directory as adb?

Yep.
10char

similar problem here. adb shell recognizes me as [email protected]_solana so im assuming its rooted..but when i try "adb remount" and press enter it says adb not found. i extracted the su file to my adb directory. Any ideas?

If you get an error like I did (top of 2nd page), try this:
Code:
C:\AndroidSDK\platform-tools\adb push C:\AndroidSDK\platform-tools\su \system\bin\su
That worked for me.

I hope this is helpful to any one that is having a hard time.
I found a one touch root video like 5 mins ago on youtube.
This is not my viedo all credits go to thedriodpeople the ones that made the video.
http://www.youtube.com/watch?v=RpGcuhoUp0k

k finally got the remount to succeed...now its say "chmod 6755: not found" after i enter "adb shell chmod 6755 /system/bin/su"

nevermind, simply retyped the same command and seemed to work on the third try mysteriously. working now

Hosed up my contacts after root and un-install --Help please--
---Solved---
So, I pulled a noob move and uninstalled a number of apps using titanium backup without understanding the repercussions of each. After uninstalling a few at a time, I would reboot my device and everything seemed fine. Little did I know, after uninstalling most, if not all, of the bloat I am unable to click a contact's picture to bring up the submenu and select call or text or whatever.
I didn't write down a list of items that I uninstalled and I should have frozen the apps prior to uninstall. I'm not a complete idiot and stayed away from obvious apps that shouldn't be uninstalled and what I thought was ALL motroblur stuff.
Long story short, I get a "com.motorola.contacts" stopped unexpectedly error(force close prompt) after trying to view a contact. I can look through all of the dialer menus showing contacts and recent calls and whatnot but I can't view a specific contact in detail. The searching I've done seems like there are a number of apps that use com.motorola.contacts and I believe I still have all of them installed but apparently not since there isn't a ton of detail on the latest motoblur that the D3 runs.
Does anyone have an idea of what apps use this process on the D3?
Thanks.
EDIT Javier78 ended up providing a solution to this issue.
http://forum.xda-developers.com/showpost.php?p=16998796&postcount=5
Quick fix and I was on my way again.

I dont think we know what all uses that process.
Sounds like your are going to have to do a factory restore, give it sometime eventually we will have a list of what is safe to remove and what isnt

Ubuntu on Galaxy Tab (WIP)

I tried loading Ubuntu using one of the market Ubuntu installers on the 4.0.3 install and convinced my self the kernel did not have loop support. Now I'm not so sure. I tried again with 4.0.4 and realized that the kernel had support, but the mount and umount tools did not. But busybox's commands support loop!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'll update as I figure out more, but the basic drill was:
Download "Complete Linux Installer (NEW)" from Market. You don't really have to do this, it just is a "guide" and has a nice launcher which (so far) does not work because we need some hacks. You could probably download the image off sourceforge and be as well off, but I was trying to get this to work. You download a 3.5MB zip file and then use a zip program (ES choked on it but Astro did ok) to extract ubunutu.img into /sdcard/ubuntu
Since the launcher crashed, I went here http://forum.xda-developers.com/showthread.php?t=962023&page=2
I followed the script by hand in an adb terminal. I suppose you could use a local terminal too. I didn't do the redirects and things I knew I didn't need. All worked except for the pts which I am still investigating. (oops a typo). Also this line:
Code:
busybox mount -o bind /sdcard/external_sd /data/local/mnt/external_sd > /dev/null 2>&1
Should be (for us):
Code:
busybox mount -o bind /mnt/extSdCard /data/local/mnt/external_sd > /dev/null 2>&1
The script will ask you the size (1280x800 although probably should use 1280 x 720 or something to handle the bar at the bottom of the screen.
Then you pick LXDE or Gnome. I picked LXDE.
Off you go. You can connect with an X server, a VNC client, or keep using the shell. Awesome!
I'll update if I fix the pts.
UPDATE: My bad. A typo on the pts line. That script actually works fine as-is except for the difference in the sdcard.
Now need to find a good onscreen keyboard although a real keyboard should work pretty well. The ones I have tried have trouble sending <ENTER> and want to dismiss the keyboard instead.
A few other notes. The init from the app has some output, so you need to NOT redirect the chroot. Also, has to run as root for the chroot to work (unless I have wonked some permission).
There are a few other issues with the image I used.
1) Need to update emacs23 for it to work (from a Ubuntu terminal: apt-get update; apt-get install emacs emacs23)
2) /etc/bash.bashrc needs to have the sudo hinting taken out or you get annoying error messages
3) The scripts attached do not clean up all processes. This may not be a problem if we can get the launcher to work, I'm not sure if it cleans up better or not.
I will post my modified/customized scripts in just a minute. The directory structure is such that /system is all on the android side and everything in /data/local/mnt should be at the ROOT of the Ubuntu files (that is, put them in while running Ubuntu or at least mount Ubuntu and then put everything in the mounted place).
I pulled these off my sdcard so you will need to patch the permissions for the scripts:
For example:
chmod 755 /system/xbin/ubuntu
Here are the files in tar format (use tar xzvf ubuntu-files.z.tar to extract):
View attachment ubuntu-files.z.tar Version 2, 15 July 2012 (fixed bad path in loop mount)
Once you have everything installed, start a terminal and execute:
su -c ubuntu
I have tried making a BTEP shortcut but with no luck yet.
Enjoy!
There is a thread about this including the image links etc (thanks to zacthepack for pointing me to it, now I've got to read it ;-) ).
http://forum.xda-developers.com/showthread.php?t=1585009
P.S. Of the VNC apps I tried that were free Jump (https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5wNXN5cy5hbmRyb2lkLmp1bXAiXQ..) seemed to work the best. The free version only lets you have one connection.
PocketCloud wasn't bad but you can't get the onscreen mouse all the way to the bottom (it tries to shrink it, but I think it doesn't know about the "permanent" ICS bar down there. If you have a real keyboard/mouse then the AndroidVNC team version works well, but it is a pain to use without a keyboard.

Please post your scripts.
Whats with backtrack? Any idea if the gtab2 support the system with all his funtions?

exebreez said:
Please post your scripts.
Whats with backtrack? Any idea if the gtab2 support the system with all his funtions?
Click to expand...
Click to collapse
There you go. Don't know a thing about backtrack other than I saw it was an option.

wd5gnr said:
There you go. Don't know a thing about backtrack other than I saw it was an option.
Click to expand...
Click to collapse
Had a small bug in the ubuntu script that didn't show up until I rebooted. Updated to v2.

Hello wd5gnr,
Would it be possible that a newbie like me can get a step by step for getting this done?
I have a P5113 with CyanogenMod 9 working great and I would really like to have Ubuntu with Gnome if possible.
Thanks in advance!
Best regards,
galcv2

galcv2 said:
Hello wd5gnr,
Would it be possible that a newbie like me can get a step by step for getting this done?
I have a P5113 with CyanogenMod 9 working great and I would really like to have Ubuntu with Gnome if possible.
Thanks in advance!
Best regards,
galcv2
Click to expand...
Click to collapse
Maybe this weekend. I can tell you that the performance especially with Gnome leaves something to be desired.
You might have better luck with this approach: http://forum.xda-developers.com/showthread.php?t=1782383

THANK YOU!

General [SOLVED] Can't copy Titanium Backup files to PC!!!

How can i copy TitaniumBackup folder to PC?
With my others Galaxy phones i always could copy through MTP but with my G998B/DS i can't.
I've used all the methods i found on the internet, such as:
Copy through MTP;
Compress TitaniumBackup's folder into a .zip file;
And through the ADB command
Code:
adb pull "/sdcard/TitaniumBackup" "D:\BACKUP"
Through MTP and compressing the folder i only get the .PROPERTIES files and through ADB i get this error message:
adb: error: failed to copy '/sdcard/TitaniumBackup/com.google.android.apps.photos-20210403-172138.tar.gz' to 'D:\BACKUP\TitaniumBackup\com.google.android.apps.photos-20210403-172138.tar.gz': remote open failed: Permission denied
If anyone can help me I would appreciate it.
SOLUTION: I entered in TWRP and i've been able to copy the folder.​

anyone know how to resolve this? i don't have TWRP so i can't use that work around.

fizmixa said:
anyone know how to resolve this? i don't have TWRP so i can't use that work around.
Click to expand...
Click to collapse
Do you get the same error as below?
MasterHack10 said:
adb: error: failed to copy '/sdcard/TitaniumBackup/com.google.android.apps.photos-20210403-172138.tar.gz' to 'D:\BACKUP\TitaniumBackup\com.google.android.apps.photos-20210403-172138.tar.gz': remote open failed: Permission denied
Click to expand...
Click to collapse
Maybe the "Permission denied" error is triggered by windows itself since you try to copy into the root of drive D. Maybe running your terminal (e.g. PowerShell) as admin will resolve your issue.
Else, @fizmixa , you could still manually boot (but not flash) twrp using fastboot, if your device isn't a Samsung device (I don't know if you can achieve this with Samsung).

Same here...Still couldn't find a solution.

I had the same problem. Looks like it's permission related. I fixed the problem by booting into TWRP -> Advanced -> File Manager, navigating to /sdcard/TitaniumBackup, clicking the blue folder with the tick and then selecting the chmod755 option.
@fizmixa, try and download Terminal Emulator for Android from the Play store and run:
Code:
chmod 755 /sdcard/TitaniumBackup/

It is about owner permission. Tar.gz files has a different owner from .properties. I don't have TWRP recovery because I use Android Emulator. How can I solve this problem?

Same issue here. Is this an Android 11 issue?

I'm struggling with the same issue .. No TWRP with me yet. So any clue how to get these files out of the device ?

JazonX said:
I'm struggling with the same issue .. No TWRP with me yet. So any clue how to get these files out of the device ?
Click to expand...
Click to collapse
They're protected due to security changes in newer versions of Android. I had the same issue on my last device, unable to pull /sdcard/android or /sdcard/TitaniumBackup using ADB for example.
You can try the SmartSwitch Windows app to take a backup of your phone?
Just a word of warning, I used SmartSwitch yesterday and although the backup was successful the call log backup zip was corrupt and couldn't be restored.

skymera said:
They're protected due to security changes in newer versions of Android. I had the same issue on my last device, unable to pull /sdcard/android or /sdcard/TitaniumBackup using ADB for example.
You can try the SmartSwitch Windows app to take a backup of your phone?
Just a word of warning, I used SmartSwitch yesterday and although the backup was successful the call log backup zip was corrupt and couldn't be restored.
Click to expand...
Click to collapse
Hey, I just managed to sort it out.
Go to Titanium Backup, Preferences, Backup location - and click the below selected option;
Select the external backup storage option, and allow access to it.
It was weird how this caused the PC copying / internal copying to fail .. This sorted the problem for good.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

JazonX said:
Hey, I just managed to sort it out.
Go to Titanium Backup, Preferences, Backup location - and click the below selected option;
Select the external backup storage option, and allow access to it.
It was weird how this caused the PC copying / internal copying to fail .. This sorted the problem for good.
Click to expand...
Click to collapse
I'm not rooting my S21U but this is good to know for the future, tks.

I'm also having this problem with Android 11 on Pixel 5a, adb: error: failed to copy ...: remote open failed: Permission denied
There isn't a TWRP for this device yet so I can't try that solution. I tried JazonX's idea but it hasn't helped. The problem seems to be that the tar.gz files are owned by media_rw user instead of u0_a252 like the other files. I tried using 'adb shell', "su -" and then "chmod 755 /sdcard/TitaniumBackup/" but it doesn't actually change any of the permissions. Also tried commands such as "chown u0_a252 *.tar.gz" but it doesn't actually change anything. I tried to write to TB support too but no response yet. Any other ideas?

Aha! I found a solution! use "adb shell" then "su -" then navigate to "cd /data/media/0/TitaniumBackup". Now commands like "chown u0_a252 *" actually work and I was able to get full backup of /sdcard/TitaniumBackup with "adb pull". Crazy Android file system!

scarlion said:
Aha! I found a solution! use "adb shell" then "su -" then navigate to "cd /data/media/0/TitaniumBackup". Now commands like "chown u0_a252 *" actually work and I was able to get full backup of /sdcard/TitaniumBackup with "adb pull". Crazy Android file system!
Click to expand...
Click to collapse
Wow! It worked for me! Thanks very much

scarlion said:
Aha! I found a solution! use "adb shell" then "su -" then navigate to "cd /data/media/0/TitaniumBackup". Now commands like "chown u0_a252 *" actually work and I was able to get full backup of /sdcard/TitaniumBackup with "adb pull". Crazy Android file system!
Click to expand...
Click to collapse
Did you do this via windows command prompt or within a terminal program on the android device?
As I can't seem to get it to work on Windows CMD
Code:
C:\platform-tools>adb shell
redfin:/ $ su -
redfin:/ # cd /storage/emulated/0/TitaniumBackup
1|redfin:/storage/emulated/0/TitaniumBackup # chown u0_a252 *
redfin:/storage/emulated/0/TitaniumBackup # adb pull "/storage/emulated/0/TitaniumBackup" "D:\Temp"
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup # adb pull /storage/emulated/0/TitaniumBackup
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup #

pennywaltz said:
Code:
redfin:/storage/emulated/0/TitaniumBackup # adb pull "/storage/emulated/0/TitaniumBackup" "D:\Temp"
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup # adb pull /storage/emulated/0/TitaniumBackup
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup #
Click to expand...
Click to collapse
I think you have to exit the "adb shell" for further adb commands to work, as "adb" is in your C:\platform-tools directory

scarlion said:
I think you have to exit the "adb shell" for further adb commands to work, as "adb" is in your C:\platform-tools directory
Click to expand...
Click to collapse
I'm having the same problem on my Pixel 5 ("redfin"). It has nothing to do with adb. Without adb running at all, I can go to a terminal emulator on the device and run the following commands ...
Code:
redfin:/ $ su -
redfin:/ # cd /sdcard/TitaniumBackup
redfin:/sdcard/TitaniumBackup # chown u0_a362 *
No error is reported. However, after doing this, all the files previously owned by rw_media are still owned by rw_media. In other words, for those files, the chown command is effectively a no-op, even after an su to root.
Google strikes again with its "We think we're much smarter than you, and we're going to 'protect' you from yourself, whether you like it or not!" attitude.

HippoMan said:
Google strikes again with its "We think we're much smarter than you, and we're going to 'protect' you from yourself, whether you like it or not!" attitude.
Click to expand...
Click to collapse
I know right, it's pretty annoying... but even with root, I think you have to specifically modify the data from the /data/media/0 directory instead, i.e.:
redfin:/ $ su -
redfin:/ # cd /data/media/0/TitaniumBackup
redfin:/data/media/0/TitaniumBackup # chown u0_a362 *
Does that work?

scarlion said:
I know right, it's pretty annoying... but even with root, I think you have to specifically modify the data from the /data/media/0 directory instead, i.e.:
redfin:/ $ su -
redfin:/ # cd /data/media/0/TitaniumBackup
redfin:/data/media/0/TitaniumBackup # chown u0_a362 *
Does that work?
Click to expand...
Click to collapse
Yep, that worked for me! Thanks! It seems they have put some stupid userland file system which mirrors files from /data:
/dev/fuse on /storage/emulated type fuse (rw,lazytime,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other)

Probably A Simple Question

Hi I am trying to learn Linux better so I can dump my android boot.img. I was able to figure out the unpackbootimg tool and the dump part, but I am caught up on something that will probably be simple for you guys, how do I access the Documents folder in CLI?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I couldn't figure it out so I typed a . to see if the unpack tool would get past the segmentation fault and it did, but idk where it put the kernel and ramdisk.. so if someone could help me at all I'd appreciate it.
Edit I remembered the sudo nautilus command and was able to locate the root directory and find my kernel and ramdisk
But if someone is able to help me with the exact pathing to Documents that would help me a lot

Well I figured it out before anyone woke up I guess XD
Spoiler: show
The trouble is that is too long for what I was trying to do and since the . period works for root like it does android I just built in the root folder. Is this bad? I am trying to make the steps easy for other users to recreate.
bootimg.zip
drive.google.com
For instance, if user takes these tools and unzips them. The instructions go like this:
Add your boot.img to the bootimg folder
Open terminal, run this code:
sudo nautilus
paste bootimg in the root folder
Open the bootimg folder. Right click and open terminal.
Run this code to install 32 bit binary support:
sudo apt-get install gcc-multilib -y
Then Run this code to extract the kernel and ramdisk from boot.img
sudo ./unpackbootimg -i boot.img -o /bootimg/bootmod
The kernel and ramdisk files will be in bootmod
Ref:
How to extract boot.img?
I am trying to see the content in a boot.img file from an Android image. I googled and found this article to extract system.img, but it doesn't work for boot.img. When trying to do this for boot.i...
unix.stackexchange.com
Spoiler: visual

TBH I am going to use a tool that Miss Renate shared for windows since it will be easier to walk others through.
BUT Just So I stand a better chance of having my one linux question I have left, answered, I will re-ask here so no one has to read through my mess.
Is it bad to build a toolset in the root directory on linux, or What Exactly is the root file system on linux in comparison to a windows system?
Why do windows users not have that or is that like the hidden files and folders on windows? Like this example?
Spoiler: SHOW
the slightly faded hidden folders like app
I appreciate anyone that can answer the question in this context. I am trying to understand file systems specifically, and since I take things to literally, it really makes it hard to just google this.
Plus google is more of a rabbit hole these days without dorks and dorks involve time.. maybe someone can just explain it in a way that makes sense. Thank you...

So two months later and I figured out how to answer my original question.
Adding a "~" to the beginning of a home folder name will allow you to access the Documents, Downloads, and other Home folders without having to type in the entirety of the home path (/home/x0110/Downloads)
cd ~/Downloads
mkdir ~/Documents/Blahblahblah
"~" allows you to execute commands outside of the folder too
example:
mkdir ~/android/system_dump/
cd ~/android/system_dump/
unzip ~/Downloads/lineage-17.1-20220202-nightly-mdarcy-signed.zip
The code above was able to change into the android/system_dump folder and then take the contents of the lineage zip in downloads and paste it into system_dump.
I don't quite understand much of anything well enough to answer the root file system question but will come back to it when it is understood if no one else does

jenneh said:
So two months later and I figured out how to answer my original question.
Adding a "~" to the beginning of a home folder name will allow you to access the Documents, Downloads, and other Home folders without having to type in the entirety of the home path (/home/x0110/Downloads)
cd ~/Downloads
mkdir ~/Documents/Blahblahblah
"~" allows you to execute commands outside of the folder too
example:
mkdir ~/android/system_dump/
cd ~/android/system_dump/
unzip ~/Downloads/lineage-17.1-20220202-nightly-mdarcy-signed.zip
The code above was able to change into the android/system_dump folder and then take the contents of the lineage zip in downloads and paste it into system_dump.
I don't quite understand much of anything well enough to answer the root file system question but will come back to it when it is understood if no one else does
Click to expand...
Click to collapse
you can use cd Downloads as long as the "Downloads" folder at your HOME Directory
and any folder of that like a Music, Documents
I am using Ubuntu 22.04.02 with X11 Desktop Environment