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

[TUTORIAL] Keeping root after upgrade from v10x to v20x

↓ A new root method! ↓
There is now a new root method, that does not require downgrade!
http://forum.xda-developers.com/showthread.php?t=2180688
↑ Read this thread first! ↑
Prerequisites
A rooted LG O4X HD with a v10 firmware. (SuperSU preferred - personally tested)
Device adb drivers installed (so that a phone is detected as an ADB device when in B&R Recovery mode), adb itself is included in the archive
You need an installed Busybox! (/system/bin preferred, or need to edit bat file)
Warning: Do NOT do factory reset between step 1 and step 3! Otherwise /data/rootkit will be deleted, and you will have to start over.
Important note for linux users: bat files are for Windows. If you are using linux, i assume that it will be easy for you to open bat files and do commands by hand.
Step 0
Backup all your settings, and data from internal storage (!), cause factory reset (wipe) will be required.
You can try using LG's backup tool or Titanium Backup or anything else.
Also I'd strongly recommend removing SIM card and SD card from the phone.
Step 1
Make sure USB debugging is enabled (Settings -> Dev Options -> Debugging)
Connect your phone to your PC.
Execute file step0.bat and ensure that you grant su priv to ADB shell (2000).
Now execute file step1.bat - it:
- creates folder /data/rootkit
- copies busybox from /system/bin to /data/rootkit
- copies su from /system/xbin to /data/rootkit
- copies Superuser.apk from /system/app to /data/rootkit
- ensures owner and group of 0 for those files
- chmods files to required attributes (06755 for su, 0644 for apk, 0777 for busybox)
Result should be something like this: Note: In v2 i modified step1, so it tries to copy busybusybox from bin and xbin - one of them will fail, thats normal.
{
"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"
}
Step 2
Upgrade your firmware to v20a. For example: http://forum.xda-developers.com/showthread.php?t=2069723
DO NOT DO FACTORY RESET! OR YOU WILL DELETE /data/rootkit FOLDER! DO STEP 3 FIRST!
Step 3
After successful upgrade shut down your phone.
Now, with USB connected (!!), hold volume up and power, and keep holding it at least until you hear windows "new device" sound.
You must see something like this:
Now execute file step3.bat - it:
- remounts system as writeable
- copies su to /system/xbin/
- copies superuser to /system/app/
- sets permissions on those files
Step 4
Now you can hold power button to reboot or just run step4.bat to reboot instantly.
Make sure that root is working, before doing factory reset!
Now you are STRONGLY recommended to do factory reset - or many things will mess up, such as lock screen settings or storage.
AGAIN warning, that factory reset WILL wipe internal storage, look at step 0
If you did all things correct, root will be kept (because it is on ro system partition now)
Step 5
Enjoy.
Note
If you are already at v20a and you want root, you can:
1) Wait for official release, with really unlocked BL - then it will be possible to install CWM -> get root
2) Wait until I make some interaction with B&R daemon in recovery
3) Wait for someone to find easier method
4) If you dont want to wait, you can go back to v10x (warning: all data will be wiped!), root phone, and do the procedure.
Any comments, notes, criticism or anything else very welcome!
Edit: In version 2 it tries to copy busybox from /system/bin and /system/xbin, thanks to AlderCass for pointing out

Nice work friend :good:

I don't have adb on my pc, is there a way to simply download the drivers? I ask because my current pc doesn't have the internet
Sent from my LG-P880 using Tapatalk 2

@non4 said:
I don't have adb on my pc, is there a way to simply download the drivers? I ask because my current pc doesn't have the internet
Sent from my LG-P880 using Tapatalk 2
Click to expand...
Click to collapse
adb is included in the archive... i will see what i can do about drivers.
try to connect phone to your PC with debugging on and do "adb devices" from the folder with unpacked adb
if it sees your device - then good

@SkyDev
great findings, nice to see ideas expand to something useful.
did you also went all way and tried to install a changed/modified boot.img and add it to the LNX partition in /dev/block/mmcblk0p2 or /dev/block/platform/sdhci-tegra.3/by-name/LNX , it might just be our bootloader do work as unlocked and we can write unsigned boot / recovery img
edit;
i believe you can easily test it from recovery and su in here. even if you get security error on "boot", i think recovery can still be booted and you can recover the backup of the mmcblk0p2 partition (men always do backups)

Utterly fantastic work, and I'm sure this discovery will be the first huge step in truly unlocking this device. Congratulations!
Sent from my LG-P880 using xda app-developers app

skydev said:
adb is included in the archive... i will see what i can do about drivers.
try to connect phone to your PC with debugging on and do "adb devices" from the folder with unpacked adb
if it sees your device - then good
Click to expand...
Click to collapse
Isn't adb a pain to install? At least it was back in the day when I rooted my desire z with froyo thanks for the good work I will try get this to work on my own
Sent from my LG-P880 using Tapatalk 2

Dexter_nlb said:
@SkyDev
great findings, nice to see ideas expand to something useful.
did you also went all way and tried to install a changed/modified boot.img and add it to the LNX partition in /dev/block/mmcblk0p2 or /dev/block/platform/sdhci-tegra.3/by-name/LNX , it might just be our bootloader do work as unlocked and we can write unsigned boot / recovery img
edit;
i believe you can easily test it from recovery and su in here. even if you get security error on "boot", i think recovery can still be booted and you can recover the backup of the mmcblk0p2 partition (men always do backups)
Click to expand...
Click to collapse
Well, when now root is easily obtainable, you can do it
I think you are more experienced in all those things, i am low-levelly playing with phones only for 3-4 days so far.
I just dont want to trash stuff to the extent that reflash would be required.
Anyway i worked on the method almost 10 hours instead of sleeping at night, so now i think i going to go take some "Deep sleep" /10:46/
Anyway, i am noting again: if anyone also has disassembly skills, then you really should try to disassemble and analyze brd (backup and recovery daemon) - it runs at recovery with root rights, listens for commands on udp port, and probably can be used for "perfect root" (root without reflashing, and maybe even any LG device)

for people having issues using adb, you can download "terminal" from play , and do the same steps except do not start from a windows shell with adb
you just open the terminal.
secondly all files needed, should be tar'd instead, so the busbox more easily can unpack all files with proper rights instantly to the dest folder.
ie.
# cd /data ; tar xf /data/local/tmp/rootkit.tar
assuming rootkit folder is extracted and all files already was properly set with rights in linux when tar'ing the folder.
so conclusion
you do 3 steps to do this.
1. download rootkit.tar
2. open terminal on phone
3. cd to /data and extract(tar xf) rootkit.tar from where you put it when downloaded
this is all without adb used.
but you need adb in the end to run the bat file

Dexter_nlb said:
for people having issues using adb, you can download "terminal" from play , and do the same steps except do not start from a windows shell with adb
you just open the terminal.
secondly all files needed, should be tar'd instead, so the busbox more easily can unpack all files with proper rights instantly to the dest folder.
ie.
# cd /data ; tar xf /data/local/tmp/rootkit.tar
assuming rootkit folder is extracted and all files already was properly set with rights in linux when tar'ing the folder.
so conclusion
you do 3 steps to do this.
1. download rootkit.tar
2. open terminal on phone
3. cd to /data and extract(tar xf) rootkit.tar from where you put it when downloaded
this is all without adb used.
but you need adb in the end to run the bat file
Click to expand...
Click to collapse
Well, adb will be required anyway, and i want to keep freedom of choosing the su binary and Superuser.apk file.
The only requirement: su must grant root if called from recovery (when Superuser.apk is not accessible)
Also, why mess with terminal? You can easily misspell command, and they are long and important (because executed as root)
But idea with tar is good, maybe it will be required to do it this way, from B&R way.

I'm trying this method now and I noticed that a command in step1 fails on my system.
I changed:
adb shell su -c cp /system/bin/busybox /data/rootkit/
to
adb shell su -c cp /system/xbin/busybox /data/rootkit/

postacik said:
I'm trying this method now and I noticed that a command in step1 fails on my system.
I changed:
adb shell su -c cp /system/bin/busybox /data/rootkit/
to
adb shell su -c cp /system/xbin/busybox /data/rootkit/
Click to expand...
Click to collapse
Prerequisites
A rooted LG O4X HD with a v10 firmware. (SuperSU preferred - personally tested)
Device adb drivers installed (so that a phone is detected as an ADB device when in B&R Recovery mode), adb itself is included in the archive
You need an installed Busybox! (/system/bin preferred, or need to edit bat file)
Warning: Do NOT do factory reset between step 1 and step 3! Otherwise /data/rootkit will be deleted, and you will have to start over.
Important note for linux users: bat files are for Windows. If you are using linux, i assume that it will be easy for you to open bat files and do commands by hand.
Click to expand...
Click to collapse
Already mentioned in first post.

lukas77 said:
Already mentioned in first post.
Click to expand...
Click to collapse
I stated that I changed the line to work "on my system".
So everybody trying this will pay attention to that...

sry for this newbie ques,
but how to install adb drivers in our device..

jitesh22 said:
sry for this newbie ques,
but how to install adb drivers in our device..
Click to expand...
Click to collapse
There are many posts on these forums on how to do this - search for them, as this thread does not deal with that.

Everything works perfect, and now i have root on my JB .

Works like a charm! Thanks so much skydev! :laugh:

I upgraded to v20a with these instructions and now I have a rooted v20a.
Thank you very much skydev.
A picture for proof: http://g1303.hizliresim.com/17/7/ktz5m.png
I think we will be able to root when new versions arrive as long as we keep the /data/rootkit folder.
Edit: I upgraded to v20a with my LG PC Suite Version Hacker ( http://forum.xda-developers.com/showthread.php?t=2134192 ) and did no factory reset after the upgrade. Everything seems to work fine upto now.

quick and dirrrrrty
thats how i like it^^
well done

AW: [TUTORIAL] Keeping root after upgrade from v10x to v20x
Worked fine. There we're no problems. Did the kdz flashing via virtual machine with windows and the rooting part on mac os x since your scripts can be easily adapted. Also i dont have to care about adb or fastboot drivers.
Gesendet von meinem LG-P880 mit Tapatalk 2

[Q]I am unable to edit/delete the hosts file

Hello my friends,
I can not edit the hosts file.
I think i have to mount the partition but i do not know how to do it.
Could somebody help me please?
Thanks,
Zuka.

Hello,
Ya, you have to mount the partition.
An easy way to do this is to download es Explorer here https://play.google.com/store/apps/details?id=com.estrongs.android.pop
Then open the app, go to the left sidebar, tools, and click root Explorer. Select mount and mount /system.
In images
{
"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"
}
Don't forget to set system in RO back when finished.

When I click on the Root Explorer I get an error:
"Sorry,test failed.This feature can not run on your device"

Is your phone rooted?

Yes it is,i got SuperSU installed and the Root Checker says that my phone is rooted.

Strange... Did you allow root rights to es Explorer?

Yes,I gave ES file Explorer the permission, I got a screenshot:
Sent from my C6903 using XDA Free mobile app

I do not understand why Es Explorer doesn't work with your phone whereas it's rooted as well. But don't let's focusing on this, it's not the main subject. Try ROOT Explorer here https://play.google.com/store/apps/details?id=com.speedsoftware.explorer to get system mounted. If it doesn't work too, we will have to use command line through adb shell.

It's not working either,when I tap mount r/w nothing happens. I can't delete or edit the file.
Sent from my C6903 using XDA Free mobile app

quadrazid said:
It's not working either,when I tap mount r/w nothing happens. I can't delete or edit the file.
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
Disable mount space separation on SuperSU, reboot
If still doesn't work, try uninstall ES File Explorer and install it again
Make sure you granted all R/W permission for Es File Explorer
EDIT: if steps above still doesn't work, you need disable Sony RIC first

Yenkazu said:
Disable mount space separation on SuperSU, reboot
If still doesn't work, try uninstall ES File Explorer and install it again
Make sure you granted all R/W permission for Es File Explorer
EDIT: if steps above still doesn't work, you need disable Sony RIC first
Click to expand...
Click to collapse
What is Sony RIC and where can I disable it ?

Did you root woth kinguser and replace it with supersu? If so, you need to disable ric as @Yenkazu say.
Try to install busybox too

odie70 said:
Did you root woth kinguser and replace it with supersu? If so, you need to disable ric as @Yenkazu say.
Try to install busybox too
Click to expand...
Click to collapse
Yes i rooted my phone with KingRoot then I replaced KingUser with SuperSU with the Terminal Emulator.
So yeah,how to disable SonyRIC ?
Edit: I installed BusyBox after I installed SuperSU

Try to connect to flashtool, with usb debugging enabled

frankee207 said:
I do not understand why Es Explorer doesn't work with your phone whereas it's rooted as well. But don't let's focusing on this, it's not the main subject. Try ROOT Explorer here https://play.google.com/store/apps/details?id=com.speedsoftware.explorer to get system mounted. If it doesn't work too, we will have to use command line through adb shell.
Click to expand...
Click to collapse
How to use the command line with the adb shell ?

First, no need to have adb installed on your computer. Type adb devices to make sure your device is recognized by adb. Make sure debugging is enabled.
Type adb shell. When you're at Android shell then type su to become root user. (the command prompt becomes # instead of $)
Chen you're root, type
busybox mount -o remount, rw /[email protected]/system
System file is now RW. When finished type the same command replacing rw by ro.
It should work

frankee207 said:
First, no need to have adb installed on your computer. Type adb devices to make sure your device is recognized by adb. Make sure debugging is enabled.
Type adb shell. When you're at Android shell then type su to become root user. (the command prompt becomes # instead of $)
Chen you're root, type
busybox mount -o remount, rw /[email protected]/system
System file is now RW. When finished type the same command replacing rw by ro.
It should work
Click to expand...
Click to collapse
Where do I type that? In the cmd or in the terminal emulator ?

You can type this in Windows cmd or Linux shell (Linux : make sur adb is installed, to install it, sudo apt-get install adb-android-tools)
If you type it in shell emulator like the very known Android emulator, then skip the command adb devices and adb shell.
(type directly su and busybox mount etc... )
PS: busybox must to be installed to perform this action!

frankee207 said:
You can type this in Windows cmd or Linux shell (Linux : make sur adb is installed, to install it, sudo apt-get install adb-android-tools)
If you type it in shell emulator like the very known Android emulator, then skip the command adb devices and adb shell.
(type directly su and busybox mount etc... )
PS: busybox must to be installed to perform this action!
Click to expand...
Click to collapse
I do not understand what to do.Where to put these commands ?

OK. Let's make easy
Go to play store and download Android Terminal Emulator : https://play.google.com/store/apps/details?id=jackpal.androidterm
Open the app.
type
Code:
su
The command prompt becomes # instead of $ after you have accepted root rights in the popup window.
Then type
Code:
busybox mount -o remount, rw /[email protected]/system
When your modifications in/system are finished, reopen the terminal, become root (type su) and then
Code:
busybox mount -o remount, ro /[email protected]/system
If busybox not installed, intall it first here: https://play.google.com/store/apps/details?id=stericson.busybox
Hoping you'll success

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)