Develop Bugs

Can't mount /system as read-write

Hello folks,
on my HTC Desire with OpenDesire 3.5.2 I'm trying to install the dropbear ssh-deamon according to a german tutorial (I'm not allowed to put the link here... ).
It is on www and then android-hilfe.de and then, go /root-hacking-modding-fuer-motorola-milestone/14241-per-ssh-auf-den-milestone.html
I'm connected to the phone using adb and shell'd into.
Now, they say that I have to mount /system as read-write to put a file (dropbear) into /system/bin. The command is
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
and results in no errors. mount then says:
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
so in my opinion, /system shoult be writable.
But everything I try results in an "Out of memory" error: Creating directories, copying files - anything.
Only deleting files is possible: I backed-up and then deleted some ringtones from /system/media/audio/ringtones, and I'm also not able to copy the backup of them I did before onto the sdcard back into the directory again
I read in another thread, that the error "Out of memory" itself is a bug and should mean "No permission". But why don't I have permission?
df -h gives me
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 203.4M 0 203.4M 0% /dev
tmpfs 203.4M 0 203.4M 0% /mnt/asec
/dev/block/mtdblock3 250.0M 106.4M 143.6M 43% /system
/dev/block/mtdblock5 147.6M 53.9M 93.8M 36% /data
/dev/block/mtdblock4 40.0M 1.1M 38.9M 3% /cache
/dev/block/vold/179:1
3.7G 2.9G 744.3M 80% /mnt/sdcard
/dev/block/vold/179:1
3.7G 2.9G 744.3M 80% /mnt/secure/asec
so there definitively IS enough memory for a 720kB file.
Any ideas?

You can only write to system on the desire via adb from recovery.

If above post didn't explain it enough...
There is no write access to /system partition yet, except via a overlay file system. Have a search and you'll find, like everybody else.

thank you! Yes, that is the problem. I read this also somewhere, but didn't remember it.

I still cant write files even though im in recovery?

zoltrix said:
I still cant write files even though im in recovery?
Click to expand...
Click to collapse
Type "adb remount"
(Without "")

zHk3R said:
Type "adb remount"
(Without "")
Click to expand...
Click to collapse
Im trying to relfash my recovery and i keep getting the no space issue.
If i type in adb remount, i can no longer mount my sd card that is holding my image..
http://forum.xda-developers.com/showthread.php?t=805141
EDIT: If i figure out how to s-off my phone, will that fix it?

zoltrix said:
Im trying to relfash my recovery and i keep getting the no space issue.
If i type in adb remount, i can no longer mount my sd card that is holding my image..
http://forum.xda-developers.com/showthread.php?t=805141
EDIT: If i figure out how to s-off my phone, will that fix it?
Click to expand...
Click to collapse
Just follow the thread in Desire Android Development and you'll have S-OFF easy.
PRO TIP: Use a flash drive rather than burning the .iso on a CD.

Yea but, will i need s-off to flash this recovery?
I know s-off lets you do stuff within fastboot, but im not too sure what taht really means

zoltrix said:
Yea but, will i need s-off to flash this recovery?
I know s-off lets you do stuff within fastboot, but im not too sure what taht really means
Click to expand...
Click to collapse
nevermind, ive done my research and s-off fixed my problem!

details
could you please describe in a little bit more details how you have managed to write the /system mount point ?
thanks in advance ...
btw, there are o bunch of guys that want this answer

What? and Why?
I too would like to know more about writing to /system.
adb remount appears to switch the mount point from "ro" to "rw" (as shown with mount command) but I still get the same "Read-only file system" response when I try to adb push files.
What exactly is the issue here? Is it related to S-ON / S-OFF ?
What do I have to do to be able to write to /system?
(other than reboot into recovery; when I copy files in Recovery, they are gone after a normal reboot)
Thanks

[q] superoneclick

I just downloaded this after finding it online. it says im missing the runtime. how do i fix this

Make sure you use the most recent version which can be found in the Android dev section on these forums.

DirkGently1 said:
Make sure you use the most recent version which can be found in the Android dev section on these forums.
Click to expand...
Click to collapse
I was on the SuperOneClick Android dev. page but it would not allow me to post as I am a horrible underling and have no privileges.
So if anyone can post it there or answer it here then this is the failure error I get for the device (A coby Kyros MID8024)
I have everything set up and the tablet is running android 2.2 all drivers and other files needed are installed.
Installed terminal emulator confirms NO SU allowed.
Getting mount path...
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /proc/bus/usb type usbfs (rw,relatime,devmode=666)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p3 on /data type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/vold/179:1 on /mnt/nand type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=utf8,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=utf8,shortname=
FAILED
Thanks if anyone can assist.

I used the super 1click method to root. It failed the first time but I rebooted my tablet and ran the super1click a second time and it sucessfully rooty my tablet...now looking for instructon for installing market.

Vernox701 said:
I used the super 1click method to root. It failed the first time but I rebooted my tablet and ran the super1click a second time and it sucessfully rooty my tablet...now looking for instructon for installing market.
Click to expand...
Click to collapse
Why not just flash google apps? That should install the market or you could download the apk for the market directly. See this thread: http://forum.xda-developers.com/showthread.php?t=1231290 .

Market fails to download anything on CM7 RC1V2 - screwed up partitioning?

I have installed CM7 RC1 on top of a brand new SBF179 (did a factory reset after the flashing of that one). While the market initially downloaded all the old apps, it now fails to install or update any apps from the market with a download unsuccessful message. To resolve this, I was looking at s0be's fix which supposedly works:
Here is the s0be's fix
1. adb shell
2. su
3. mkdir /cache/download
4. chown system:cache /cache/download
5. chmod ug+rwx /cache/download
6. chmod a+x /cache/download
I can su but my /cache dir is read only, which presumably is because there is not really a cache partition:
Code:
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk1p21 on /system type ext3 (ro,noatime,nodiratime,barrier=1,data
=ordered)
/dev/block/userdata on /data type ext3 (rw,nosuid,nodev,noatime,nodiratime,error
s=continue,data=ordered)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
tmpfs on /data/tmp type tmpfs (rw,relatime,size=2048k)
/dev/block/pds on /pds type ext3 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,d data=ordered)
Can anyone shed some light on this? Is there something wrong with the setup here? And why is the cache folder read only?

Market "Download paused" over WiFi
i also had market issue after downgrade cm7 rc1 to froyo rom somebody plz help ......
Market "Download paused" over WiFi

I had the same issue. I found this, and the "fix" worked.
http://www.androidpolice.com/2011/0...on-usb-storage-or-sd-card-problem-on-android/

That does not seem to be my issue - in any case that file does not exist in either locations. In my case I dont even get an error pop up just a silent, quick note in the download bar that the download was unsuccessful.
I still think its weird that my /cache folder is entirely empty and on a read only filesystem to boot?

in my case there is no download folder on /cache
i can able to download file from 2g/2g but download pause if i do it from WiFi ...

did u try flashing google apps again?
it works normally..

how to do it on stock froyo ?

ankit360 said:
how to do it on stock froyo ?
Click to expand...
Click to collapse
well u need to root it and install 2ndInit Recovey and then u can flash anything u like from custom recovery

I just reflashed gapps-2011-03-XX from stable recovery, no change.

nupi said:
I just reflashed gapps-2011-03-XX from stable recovery, no change.
Click to expand...
Click to collapse
i even try gapps-gb-20110613-signed.zip not working

I think I may just go back to RC0 tomorrow, that seemed to be more stable after all

So wiped data and cache on RC1V2, still same issue. Going back to RC0 now

Ok so I did reinstall 177 Nordic, flashed CM7.1RC0 and it STILL does not work.
However, I am still thinking there is something wrong with my partioning of the Defy as custom recovery gave me the following errors:
Can't mount /dev/block/memblk1p24
Can't mount /cache
Can't mount cache:recovery/log
Similarly, stock recovery upon starting also gives me:
Can't mount CACHE:recovery/command
Can't mount CACHE:recovery/caller
Can't mount CACHE:recovery/log
Last vain hope of going back to 177-Nordic and not installing CM7 for now, let's see what happens there.

where apk get save ? /cache/download or /cache ?
when i create download folder in cache it get deleted automatically and downloadfile.apk is get created is this normal plz help me ....

On vanilla 177-NORDIC it works. Confuses the hell out of me.

But also, I get a much different filesystem hierarchy - now I actually get /cache, android secure etc!
$mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk1p21 /system ext3 ro,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/userdata /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/cache /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
tmpfs /tmp tmpfs rw,relatime,size=2048k 0 0
/dev/block/pds /pds ext3 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.trueaxis.jetcarstuntslite-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
Click to expand...
Click to collapse
I still think there is something wrong with the CM7 mount points I get!

I had the problem at rc0. Also got the mounting error. What worked for me was to unmount the cache and than mount again via recovery.
Sent from my MB525 using XDA App

How do I unmount/mount stuff in recovery? Also, did that fix market issues?

For me it fixed the problem. I had also this problem on RC0 and got the error of cant mount cache.
You can unmount and mount it in custom recovery. It do not exactly know where it is in recovery. Thought it was at the advanced menu.
Sent from my MB525 using XDA App

This explains why this happens and how to fix it:
http://forum.cyanogenmod.com/topic/19100-cm7-rc3-market-fails-to-download-big-apps/
Give me thanks for this if it helps, it took me hours to find this fix! thanks

[Q] Phone is not seeing any of it's memory

I don't know what happened, my battery died, I plugged it in, turned the phone back on, and boom, my phone is throwing errors out left and right, and ES File Explorer is saying '/sdcard/' is not found. I've tried going to storage/emulated/0 & legacy, but I get the same not found message.
Storage in System Settings shows that the storage is still being used, and the file browser in TWRP shows all the files are still there. It just seems like the mount points or bindings got all screwy.
My phone is on the BOF5 firmware, it's stock rooted. I've had no problems restarting my phone, usually have to atleast twice a week. Nothing funky installed, atleast nothing that would mess with the SD card. No SW was uninstalled, just frozen, and it wasn't much [Voicemail, Internet (Browser), Hangouts]
I'm really just hoping that someone, somewhere knows a way to help me fix this so I don't have to restore!

krakerx said:
I don't know what happened, my battery died, I plugged it in, turned the phone back on, and boom, my phone is throwing errors out left and right, and ES File Explorer is saying '/sdcard/' is not found. I've tried going to storage/emulated/0 & legacy, but I get the same not found message.
Storage in System Settings shows that the storage is still being used, and the file browser in TWRP shows all the files are still there. It just seems like the mount points or bindings got all screwy.
My phone is on the BOF5 firmware, it's stock rooted. I've had no problems restarting my phone, usually have to atleast twice a week. Nothing funky installed, atleast nothing that would mess with the SD card. No SW was uninstalled, just frozen, and it wasn't much [Voicemail, Internet (Browser), Hangouts]
I'm really just hoping that someone, somewhere knows a way to help me fix this so I don't have to restore!
Click to expand...
Click to collapse
Youre taking all the fun out of it. Backing up and restoring from scratch is half the fun with android phones. If youre gonna root to have fun, be prepared to do the dirty work as well. JMHO

xxSTARBUCKSxx said:
Youre taking all the fun out of it. Backing up and restoring from scratch is half the fun with android phones. If youre gonna root to have fun, be prepared to do the dirty work as well. JMHO
Click to expand...
Click to collapse
Well, I'm looking to do the dirty work, otherwise I would have just restored the phone from my backup weeks ago. But I don't want to do that, because, honestly, there has got to be a way to see this data. With that said, here is the output from running 'mount' in TWRP and Terminal Emulator:
C:\MiniADB\adb shell
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1418352k,nr_inodes=154938,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=1418352k,nr_inodes=154938)
pstore on /sys/fs/pstore type pstore (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p27 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p27 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p25 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
===========================================================================================================
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1414720k,nr_inodes=153121,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=700 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=755,gid=1000 0 0
/dev/block/bootdevice/by-name/modem /firmware-modem vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/apnhlos /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,norecovery 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/carrier /carrier ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persdata /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=1414720k,nr_inodes=153121,mode=050,gid=1028 0 0
tmpfs /storage/emulated/legacy tmpfs rw,seclabel,nosuid,nodev,relatime,size=1414720k,nr_inodes=153121,mode=050,gid=1028 0 0
[email protected]:/ #
Hopefully someone with BOF5 rooted stock can take a look at their mount points and see if they lineup with what I'm getting

krakerx said:
Well, I'm looking to do the dirty work, otherwise I would have just restored the phone from my backup weeks ago. But I don't want to do that, because, honestly, there has got to be a way to see this data. With that said, here is the output from running 'mount' in TWRP and Terminal Emulator:
Click to expand...
Click to collapse
Thanks for posting this.
Hopefully someone who is still on OF5 can match and compare/contrast whats there or not there. Maybe unrooting and OG5 is the way to go or simply trying it in your laptop(if it has a SD cardslot reader and see if it functions properly there) Might be time to get a new card

SD card is fine, internal memory is fine... Found the issue was a corrupted sdcard pointer, once fixed, phone runs like it should

Creating partition backup with dd

Hi,
I want to create a partition backup with dd because TWRP fails.
I have opened a relevant posting in TWRP thread here, but there's no reply.
Now checking the available partitions and mount points is confusing me.
There is partition
Code:
/dev/block/sda13
mounted to /data and /sdcard.
Code:
/sdcard/TWRP/BACKUPS/b94a5888/2020-02-13--13-54-00 # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,noatime,size=3930984k,nr_inodes=982746,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,noatime,mode=600)
proc on /proc type proc (rw,noatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,noatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,noatime)
none on /acct type cgroup (rw,noatime,cpuacct)
tmpfs on /tmp type tmpfs (rw,seclabel,noatime,size=3930984k,nr_inodes=982746)
pstore on /sys/fs/pstore type pstore (rw,seclabel,noatime)
none on /config type configfs (rw,noatime)
adb on /dev/usb-ffs/adb type functionfs (rw,noatime)
/dev/block/sda3 on /cache type ext4 (rw,seclabel,noatime,data=ordered)
/dev/block/sde10 on /firmware type vfat (ro,noatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/sda13 on /data type ext4 (rw,seclabel,noatime,data=ordered)
/dev/block/sda13 on /sdcard type ext4 (rw,seclabel,noatime,data=ordered)
/sdcard/TWRP/BACKUPS/b94a5888/2020-02-13--13-54-00 # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 3.7G 184.0K 3.7G 0% /dev
tmpfs 3.7G 21.6M 3.7G 1% /tmp
/dev/block/sda3 248.0M 6.6M 236.3M 3% /cache
/dev/block/sde10 109.9M 106.2M 3.8M 97% /firmware
/dev/block/sda13 111.4G 91.2G 19.0G 83% /data
/dev/block/sda13 111.4G 91.2G 19.0G 83% /sdcard
/sdcard/TWRP/BACKUPS/b94a5888/2020-02-13--13-54-00 #
This means I cannot create a backup with dd because the target would be /sdcard/TWRP/BACKUPS/, and then I would write the backup to itself.
Can you please advise?
THX