Hello,
It looks like big step forward to make this brick useable, but I havenāt done anything like this beforeā¦
So before I start I would like to know if there are any tricky parts?
Are there any risks or disadvantages of this installation?
Pc with Ubuntu is must or it can be done without it somehow? (I have only pc with windows 10)
Linux is a must to mount the volumes even I had OSX and Windows both didnāt work except I used fedora live cd
and it will void your warranty
finally if any problems we here to help
I did it because poor battery with WD Discovery app
now I use It with NAS and no battery drain on OSX
Also I installed torrent client and Rsync Server to create custom backups
My problem has been solved. The subfolder permissions involved have been changed to read and write. The MCH synchronized folder is located in the /data/data/com. transmissionbt.WD/auth0|xxxxxxx folder. Thank you again.
hi juju thank you for your help, your tutorial will be handy to me for sure, with this done, is there a way for the plex server to be moded to be able to use the folders we want?
I have the same problem running the ā./sbin/busybox --installā.
C:\Share\platform-tools_r28.0.1-windows\platform-tools>adb connect 192.168.1.99
connected to 192.168.1.99:5555
C:\Share\platform-tools_r28.0.1-windows\platform-tools>adb root
C:\Share\platform-tools_r28.0.1-windows\platform-tools>adb shell
root@monarch32_mini:/ # /system/bin/mount -o rw,remount /
root@monarch32_mini:/ # mkdir /opt
root@monarch32_mini:/ # /system/bin/mount -o ro,remount /
root@monarch32_mini:/ # mkdir /data/entware.arm
mkdir: ā/data/entware.armā: File exists
1|root@monarch32_mini:/ # mount -o bind /data/entware.arm /opt
root@monarch32_mini:/ # /system/bin/mount -o rw,remount /system
root@monarch32_mini:/ # ./sbin/busybox --install
busybox: /usr/bin/[: No such file or directory
busybox: /usr/bin/[[: No such file or directory
busybox: /sbin/acpid: Read-only file system
busybox: /usr/sbin/add-shell: No such file or directory
busybox: /usr/sbin/addgroup: No such file or directory
busybox: /usr/sbin/adduser: No such file or directory
busybox: /sbin/adjtimex: Read-only file system
busybox: /sbin/arp: Read-only file system
busybox: /usr/sbin/arping: No such file or directory
busybox: /bin/ash: Read-only file system
busybox: /usr/bin/awk: No such file or directory
busybox: /bin/base64: Read-only file system
busybox: /usr/bin/basename: No such file or directory
busybox: /usr/bin/beep: No such file or directory
busybox: /sbin/blkid: Read-only file system
busybox: /sbin/blockdev: Read-only file system
busybox: /sbin/bootchartd: Read-only file system
busybox: /usr/sbin/brctl: No such file or directory
busybox: /usr/bin/bunzip2: No such file or directory
busybox: /usr/bin/bzcat: No such file or directory
busybox: /usr/bin/bzip2: No such file or directory
busybox: /usr/bin/cal: No such file or directory
busybox: /bin/cat: Read-only file system
busybox: /bin/catv: Read-only file system
busybox: /usr/sbin/chat: No such file or directory
busybox: /bin/chattr: Read-only file system
busybox: /bin/chgrp: Read-only file system
busybox: /bin/chmod: Read-only file system
busybox: /bin/chown: Read-only file system
ā¦
Could you please advise how to fix it with commands? Or anyone who know please advise.
What would be the best way to take an image/ backup of the disk before we start messing with it.
I assume this would done at the step when itās connect to Linux before adjusting the build.prop.
But you donāt need to worry about that. You can restore the system partition as there is a separate restore partition with the system files. You can restore the system by pressing the reset button for 60 seconds.
Please help me. I did the first few steps and enabled ADB. I can connect, but when I try to remount the / partition I get:
/system/bin/mount -o rw,remount /
mount: Operation not permitted
I really need this what am I doing wrong? I double checked that I followed all the steps. I also opened the adb_enable.sh script to see what itās doingā¦and it does the same that I did already.
[edit]
I fixed it! I was mounting the wrong partition. There are 2 partitions that have the build.props file. Be sure to have the one that already has ro.debuggable=0 in it! I thought I had to add it
Thanks for an amazing tutorial.