Database Develop

Linking from /mnt/sdcard to /mnt/sdcard-ext - automatization

Found the solution, it's in the fifth post
Hey, first of all I'm Linux and Android newbie, so sorry if my question reveals it a bit
As my Internal Storage a.k.a. /mnt/sdcard is getting full and I hate to be reminded of it by notification I can't get rid of, I decided to put some effort into moving the largest files to the SD card. I have a 64GB SD an there still are several free gigs So after some googling I found out a way to link it. It works like this:
Code:
mount -o bind /origdir /newdir
where both /origdir and /newdir must exist, in my case as an example:
Code:
mount -o bind /mnt/sdcard-ext/sd/DictionariesNGHS /mnt/sdcard/DictionariesNGHS
where /mnt/sdcard-ext/sd/DictionariesNGHS is the data containing folder and /mnt/sdcard/sd/DictionariesNGHS is an empty folder for linking. It works like a charm, tried with several applications including some off-line navigations. The downside is that such links are forgotten after a reboot.
I didn't find out how to automatize that. I tried putting the line from second code to the end of /system/etc/init.goldfish.sh (I run Eclipse ICS 1.2) and it didn't get linked after a reboot (but works OK after mounting manually in terminal) - I suspect it runs before sdcard-ext is mounted. Any thoughts on how to make it run after reboot? Or maybe of an app that does this for me?
EDIT:
Put my links into /data/data/init.sh
Tried several not working apps:
ScriptMe by gilsken says Script run mount: No such file or directory
Script Manager - SManager by devworm says
Code:
exec sh '/data/data/init.sh'
[email protected]_maserati:/ # exec sh '/data/data/init.sh'
mount: No such file or directory
while interestingly when I write it by myself in its built-in console it works...
App that works: Tasker by Crafty Apps
I can have scripts run on boot and it works, but I can add only one line at time (or at least it's the only option I found) which is still kinda inconvenient plus it runs all the time consuming system resources. I'd like some less robust solution, preferably executed after boot and exiting after mounts proceed. Any ideas?
EDIT 2:
My "workaround" in Tasker: Profiles -> New -> Event -> System -> Device Boot -> OK -> New Task -> OK -> + -> Script -> Run Shell -> Command: /data/data/init.sh -> OK
Surprisingly enough it doesn't even need root permission...
In init.sh I have several lines with different mounts, it all works well. I'm still looking for less robust solution than Tasker is, or maybe a way to kill it after the init.sh is processed?

hey
can you please post the content of youre
Code:
/data/data/init.sh
---------- Post added at 04:35 PM ---------- Previous post was at 03:50 PM ----------
youre problem is, at the runtime form the mount command, the mount is not in youre path.
can you add to you script the command
Code:
env
and post the output?

I tried it with a file containing only this line:
Code:
mount -o bind /mnt/sdcard-ext/sd/DictionariesNGHS /mnt/sdcard/DictionariesNGHS
OK, after running it by SManager it looks like giving errors, but the folder gets mounted.
Also it seems apps get access to /mnt/sdcard faster after reboot then to /data/data (I wonder why...?) so I moved the script there.
Here you have the output with env at the end of init.sh, run by SManager as root (mounted OK):
Code:
exec sh '/mnt/sdcard/init.sh'
[email protected]_maserati:/ # exec sh '/mnt/sdcard/init.sh'
mount: No such file or directory
_=/system/xbin/env
ANDROID_BOOTLOGO=1
ANDROID_PROPERTY_WORKSPACE=8,69632
LOOP_MOUNTPOINT=/mnt/obb
SM_API=15
RANDOM=26725
ANDROID_ASSETS=/system/app
USER=root
EXTERNAL_STORAGE=/mnt/sdcard
ANDROID_DATA=/data
PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
SM_LAUNCHER=MANUAL
TERM=vt100
PS1=$(precmd)[email protected]$HOSTNAME:${PWD:-?} #
SM_VERSION=2.5.3.1
SM_GUIFD=3
LD_LIBRARY_PATH=/vendor/lib:/system/lib
SECONDARY_STORAGE=/mnt/sdcard-ext
SM_ALIAS=init.sh
ASEC_MOUNTPOINT=/mnt/asec
SM_HOME=/mnt/sdcard
HOSTNAME=cdma_maserati
HOME=/
SM_VERSIONCODE=77
BOOTCLASSPATH=/system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework-ext.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/filterfw.jar:/system/framework/com.motorola.android.frameworks.jar:/system/framework/com.motorola.android.widget.jar:/system/framework/com.motorola.frameworks.core.addon.jar:/system/framework/kafdex.jar:/system/framework/com.motorola.orange.simauth.jar
ANDROID_ROOT=/system
SHELL=/system/bin/sh
MKSH=/system/bin/sh
ANDROID_SOCKET_zygote=9
So it works after all with the SManager as I intended, I just don't understand why it gives that error when everything actually is OK...
Any ideas on how to make it run automatically after every mount of sdcard-ext instead of on reboot? Because when I connect it to the computer as Mass Storage, the directory mounts disappear and I have to run the script manually...

LuH said:
I tried it with a file containing only this line:
Code:
mount -o bind /mnt/sdcard-ext/sd/DictionariesNGHS /mnt/sdcard/DictionariesNGHS
...
Any ideas on how to make it run automatically after every mount of sdcard-ext instead of on reboot? Because when I connect it to the computer as Mass Storage, the directory mounts disappear and I have to run the script manually...
Click to expand...
Click to collapse
for the first, replace the mount with this:
Code:
/system/bin/mount -o bind /mnt/sdcard-ext/sd/DictionariesNGHS /mnt/sdcard/DictionariesNGHS

Found out that the "mount: No such file or directory" error was due to typo in folder path
So to wrap it up:
You need to be rooted first.
Create your init.sh script file, works fine when put to /mnt/sdcard/
Example file (also attached so you have a sample in UNIX formatting - don't open with Notepad under Windows, better edit it in your phone):
Code:
# mount -o bind /sourcedir /fakedir - both sourcedir and fakedir MUST exist!
mount -o bind /mnt/sdcard-ext/sd/DictionariesNGHS /mnt/sdcard/DictionariesNGHS
mount -o bind /mnt/sdcard-ext/sd/Android/obb /mnt/sdcard/Android/obb
Note: you should use a UNIX formatting of the file, not Windows (I'm not sure if it's necessary though).
As hinted in the beginning note, sourcedir and fakedir must exist and after successful mount the fakedir folder will appear to have the contents of the sourcedir folder. Any fakedir's contents are ignored ("disappear") after mount and reappear only after it gets unmounted.
It gets automatically unmounted after unmounting of either fakedir's or sourcedir's media (typically when connecting phone to a computer as mass storage) and I haven't found any workaround for running the script after remounting of media... Any suggestions?
Install SManager (free version here).
In SManager navigate to your script file, tap it and select Script/Executable and tap Su and Boot icons (see attached screenshot).
Done, your folders get mounted on reboot

[DEV/Add-On]bash for android.

Hello all.
This is my first share at the Android forums:
On my first device -- Samsung Galaxy S2 - I9100 Intl. -- I have BASH shell, so I've got used to working with it so i was missing it on my second device -- LG Nexus 4 -- the installer from the market was not working on the last one...
So I've remembered seeing here a post by nubecoder saying he compiled bash 4.2.2 for android, ang gave it a shot, but it was not working as expected on my device...
I've decided to recreate it for my Nexus 4.
All credit goes to nubecoder, I've only re-created the ZIP installer.
So, I hope someone else will enjoy nubecoder (I've tested it on my device and it is working) work remake by me.
Highlights and remarks are most welcome...
1.1:
Fixed mounting order error...
If it worth a donation, PM me and I'll give my paypal donation details (I have not done it ever, so when it will be relevant, I will...)

dmagician said:
Hello all.
This is my first share at the Android forums:
On my first device -- Samsung Galaxy S2 - I9100 Intl. -- I have BASH shell, so I've got used to working with it so i was missing it on my second device -- LG Nexus 4 -- the installer from the market was not working on the last one...
So I've remembered seeing here a post by nubecoder saying he compiled bash 4.2.2 for android, ang gave it a shot, but it was not working as expected on my device...
I've decided to recreate it for my Nexus 4.
All credit goes to nubecoder, I've only re-created the ZIP installer.
So, I hope someone else will enjoy nubecoder (I've tested it on my device and it is working) work remake by me.
Highlights and remarks are most welcome...
If it worth a donation, PM me and I'll give my paypal donation details (I have not done it ever, so when it will be relevant, I will...)
Click to expand...
Click to collapse
thank you for this! i tried to install it. however i am running in to some problems. the installation partially fails with twrp. the update script tries to set the permission on some files in /data/local but the files are not there:
Code:
set_perm(0, 2000, 0666, "/data/local/.bash_history");
set_perm(0, 2000, 0666, "/data/local/.editor");
set_perm(0, 2000, 0666, "/data/local/.inputrc");
set_perm(0, 2000, 0666, "/data/local/.minttyrc");
these files are in the zip, but no permissions are set via the update-script:
Code:
.bashrc
.bashrc_support
.bashrc_user
.profile
can you help me out?

-- 1st Reserved --
-- 1st Reserved --

-- 2nd Reserved --
-- 2nd Reserved --

Fixed -- I Hope
UnitedOceanic said:
thank you for this! i tried to install it. however i am running in to some problems. the installation partially fails with twrp. the update script tries to set the permission on some files in /data/local but the files are not there:
Code:
set_perm(0, 2000, 0666, "/data/local/.bash_history");
set_perm(0, 2000, 0666, "/data/local/.editor");
set_perm(0, 2000, 0666, "/data/local/.inputrc");
set_perm(0, 2000, 0666, "/data/local/.minttyrc");
these files are in the zip, but no permissions are set via the update-script:
Code:
.bashrc
.bashrc_support
.bashrc_user
.profile
can you help me out?
Click to expand...
Click to collapse
Fixed mounting.
Explanation:
The data partition was mounted AFTER expanding contents, so the content was lost on mounting data partition.

Some changes failed
Hi there, I've tried to apply it on my N4 (4.4.2 stock with MultiROM, Dalvik / Bionic patches and 4Way Reboot / Volume Wake) and I got stuck in an error.
Here is my log:
* Mounting '/system'
* Mounting '/data'
/data is already mounted.
Extracting files
minzip: Extracted 318 file(s)
minzip: Extracted 2 file(s)
Setting permissions on /system/xbin/bash4.2.0.1
Setting different instalation shell scripts to be used...
about to run program [/sbin/sh] with 2 args
Creating 'b' shell excutable file for quick launching BASH
in /system/bin/
run_program: child exited with status 1
Created '/system/bin/b'
Creating symlink for BASH as /system/bin/bash
Setting permissions on directories:
/system/etc/terminfo
Setting permissions for /system/etc/bash.bashrc
and /system/etc/profile
Creating symlink for BASH as /system/xbin/bash
Settings '/data/local' owner to UID to 0 (root) and GID to 2000 (shell)
Settings '/data/local' owner to UID to 0 (root) and GID to 2000 (shell)
Settings permissions on '/data/local/bin' to 0755 (a=rwx)
Settings permissions on '/data/local/sbin' to 0755 (a=rwx)
Settings permissions on '/data/local/xbin' to 0755 (a=rwx)
Settings permissions on '/data/local' to 0755 (u+rwx,go+rx)
set_perm: chown of /data/local/.bash_history to 0 2000 failed: No such file or directory
set_perm: chmod of /data/local/.bash_history to 666 failed: No such file or directory
script aborted: set_perm: some changes failed
Settings permissions on '/data/local/.*' to 0666 (a=rw)
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard/Bash4.2.x-Installer(Nexus4)-v1.1.zip'
Error flashing zip '/sdcard/Bash4.2.x-Installer(Nexus4)-v1.1.zip'
Updating partition details...
Iata backup size is 2098MB, size: 13231MB, used: 8904MB, free: 4326MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'settings'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Click to expand...
Click to collapse
Thank you for your help!

@dmagician thank you for the update. i just noticed the zip files contains ssh, scp, vim, nano, 7z and more :good::good: thats really aewsome!
i took a look at the scripts and i can't find anywhere a reference to these files.
Code:
/data/local/.bash_history
/data/local/.editor
/data/local/.inputrc
/data/local/.minttyrc
i need your help configuring bash. if i start bash from the default shell with "bash" the profiles is not loaded. is it possible to "symlik bash to "bash -l"? the
@Grushteniak
easiest quick fix
open terminal add this commands:
Code:
su
cd /data/local/
touch .editor
touch .inputrc
touch .minttyrc
after that flash the zip again

Worked now
@UnitedOceanic
I have created the files you asked and I had to create the '.bash_history' file too.
After that, successfully flashed it. Thank you for your help!

UnitedOceanic said:
@dmagician thank you for the update. i just noticed the zip files contains ssh, scp, vim, nano, 7z and more :good::good: thats really aewsome!
i took a look at the scripts and i can't find anywhere a reference to these files.
Code:
/data/local/.bash_history
/data/local/.editor
/data/local/.inputrc
/data/local/.minttyrc
Click to expand...
Click to collapse
These are mainly not required (I think I've packed them accidentally...), the files .bash_history and .editor are created automatically, so all of these can be safely deleted (from the device).
I will remove then sometime later - when I'll have some free time - from the ZIP...
UnitedOceanic said:
i need your help configuring bash. if i start bash from the default shell with "bash" the profiles is not loaded. is it possible to "symlik bash to "bash -l"? the
Click to expand...
Click to collapse
1st:
You can't...
Unless it is a multi-call binary like BusyBox (I'm not Linux expert... but as of my understanding -- By far: Any EXPERT that knows Linux better than me, PLEASE: Correct me if I'm wrong) -- You cannot link a binary with its switches in any way...
You can only link the the binary itself, any command line switch should be via the command line or shell script.
2nd:
There should be a small executable shell script named “b” located in /system/bin/ (its whole target is executing “/system/xbin/su -c /system/bin/bash --login” -- for ease of running and saving some taps).
Check if it exists, as the installer itself SHOULD have created it.
In case the file does not exist, you can try the following:
Open terminal emulator - any of those are good:
If you don't have any terminal emulator installed and/or don't want to install one...
ADB shell
PuTTY Tray - by Chris West (Faux):good:<--strongly recommended
If you have one installed already, open it.
If you don't have any (and/or you want one to be always available to you), IT'S TIME TO GET ONE
Open Google Play Store and search "terminal emulator", pick one and install it.
Then execute (one by one):
In case of using ADB command (option 1 listed above)
Code:
adb root
adb remount
In case of using terminal emulator (e.g. any one of options 2 or 3 as listed above)
Code:
su
mount -o remount,rw /system
and the rest: (if using ADB (e.g. option 1 listed above), prefix the commands with "adb shell" noobs: [no quotes, and with trailing space])
Code:
cd /system/bin
rm /system/bin/b
echo '#!/system/bin/sh' > /system/bin/b
echo '/system/xbin/su -c /system/bin/bash --login' >> /system/bin/b
chown 0.0 /system/bin/b
chmod 0755 /system/bin/b
remount -o remount,ro /system
exit
In some (pretty rare - I believe...) cases, you may need to add /sbin/busybox or /system/xbin/busybox
before the commands above:
As exmple, line 3:
instead of echo '#!/system/bin/sh' > /system/bin/b would be something like
/system/xbin/busybox echo '#!/system/bin/sh' > /system/bin/b​OR
/sbin/busybox echo '#!/system/bin/sh' > /system/bin/b​
UnitedOceanic said:
easiest quick fix
open terminal add this commands:
Code:
su
cd /data/local/
touch .editor
touch .inputrc
touch .minttyrc
after that flash the zip again
Click to expand...
Click to collapse
If so, (and I'm not sure of it because you are basically extracting files from a ZIP archive to location and then executing commands over them... BUT I'm neither Linux nor Edify expert... Enlightments, Corrections and Learning new things ARE ALWAYS welcome!), It is good to know that executing touch on the files will cause the installer to forcibly update them...
You meant "execute these commands" not "add this commands" -- right?
Sorry, I've misunderstood -- You ware CREATING the file by the touch command, NOT CHANGING DATE/TIME....

Could I ask what does this do? Isnt this the same thing that we can have using terminal emulator?

bamsbamx said:
Could I ask what does this do? Isnt this the same thing that we can have using terminal emulator?
Click to expand...
Click to collapse
It is not related to terminal emulator itself, but to the underlying Android shell layer.
To be specific:
It is adding SOME of the advanced BASH style capabilities to Android's shell scripting.
SOME - since not ALL (as I remember, but the most important and used, do exist) - of bash capabilities are implemented in this (small) binary.
It is an alternative to the Android's basic shell.

dmagician said:
It is not related to terminal emulator itself, but to the underlying Android shell layer.
To be specific:
It is adding SOME of the advanced BASH style capabilities to Android's shell scripting.
SOME - since not ALL (as I remember, but the most important and used, do exist) - of bash capabilities are implemented in this (small) binary.
It is an alternative to the Android's basic shell.
Click to expand...
Click to collapse
Thanks for the quick reply!!!
I do not understand too much about linux...
Could you tell me some examples of how this would benefit us??
Thanks

bamsbamx said:
Thanks for the quick reply!!!
I do not understand too much about linux...
Could you tell me some examples of how this would benefit us??
Thanks
Click to expand...
Click to collapse
It is mainly used by users - some may add - who've rooted their devices, - and ment as a low level for doing stuff that cannot be done via GUI (graphical user interface).
This is what you probably know as "hacking" - not necessarily for doing bad suff,
but for low level control of the device or for learning purposes.

[Q&A] [ROM][MI3][5.1.1] Opticancro[03/05/15]

Q&A for [ROM][MI3][5.1.1] Opticancro[03/05/15]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][MI3][5.1.1] Opticancro[03/05/15]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

:laugh:Can't wait to flash it

Hi, i am trying to install the extended version but i got the following messages.
minzip: Extracted 4 file(s)
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 12.1
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
blockimg version is 2
erasing 318848 blocks
Patching system image unconditionally...
script aborted: blkdiscard failed: Invalid argument
blkdiscard failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12.1-20150503-UNOFFICIAL-Opticancro-cancro.zip'
Error flashing zip '/sdcard/cm-12.1-20150503-UNOFFICIAL-Opticancro-cancro.zip'
Updating partition details...
Iata backup size is 0MB, free: 56225MB.
I:Unable to mount '/usbotg'
I:Actual block device: '', current file system: 'vfat'
...done
Click to expand...
Click to collapse

can we extend partition to 1.2gb with the flashable zip available on xda?
any demerits of increasing the partition size?

Can this done if I use twrp?how to partition system1 and system2 if I use twrp this not have dual boot?

this rom is already rooted?
or flash again supersu?
sorry for my english

d'joker said:
can we extend partition to 1.2gb with the flashable zip available on xda?
any demerits of increasing the partition size?
Click to expand...
Click to collapse
Yes you can do it but not necessary for this rom.
With extended system1 you'll lose ability to dual boot (dual boot not recommended by the way), and normally you lose ability to use MiFlash to clean flash MIUI on your phone if something went wrong.
jaliee85 said:
Can this done if I use twrp?how to partition system1 and system2 if I use twrp this not have dual boot?
Click to expand...
Click to collapse
Yes you can flash this rom using TWRP. With stock partition layout go to download "stock".No TWRP is not supporting dualboot, it only detects system1.
By the way I don't understand what you mean by "how to partition system1 and system2. Do you mean format them or resize them?
husen96 said:
this rom is already rooted?
or flash again supersu?
sorry for my english
Click to expand...
Click to collapse
Yes this rom include root, you won't need to flash supersu.zip. In order to enable root in /settings/about this phone fast press multiple time build number.
That'll enable devloper options, in devloper options (settings) enable root access.

I got this error when i flash extended version using twrp.i already extend my partition using in the post method...pls i need this solution
Code:
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:operation_start: 'Flashing'
Installing '/sdcard/Download/cm-12.1-20150503-UNOFFICIAL-Opticancro-cancro.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
minzip: Extracted 4 file(s)
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12.1
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
blockimg version is 2
Patching system image unconditionally... erasing 318848 blocks
script aborted: blkdiscard failed: Invalid argument
blkdiscard failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/cm-12.1-20150503-UNOFFICIAL-Opticancro-cancro.zip'
Error flashing zip '/sdcard/Download/cm-12.1-20150503-UNOFFICIAL-Opticancro-cancro.zip'
Updating partition details...
I:Data backup size is 1216MB, free: 5906MB.
I:Unable to mount '/usbotg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1

Hi
What is the diferent between stock and Extended?

adsim said:
Hi
What is the diferent between stock and Extended?
Click to expand...
Click to collapse
Stock is made for flashing on stock system partition layout (system1 and system2 both ~640Mb)
Extended is made for flashing on resized partition system : system1 = 1.2Gb and system2 = 5Mb
Edit : @jaliee85 sorry but I don't know from where it may come.
If you made manual repartition just try to flash CWM and flash repartition script made by audahadi (second or third thread page about repartitioning)

having error issues with status 7
hi,
sorry for this if this question already been answer before.
i having the error with status 7
i tried many times to install the rom through CWM.
and i tried to change the binary script and still the same.
anyone of here face this problem before?
is there any solution for this?
thanks for advanced.

Riichard63 said:
Stock is made for flashing on stock system partition layout (system1 and system2 both ~640Mb)
Extended is made for flashing on resized partition system : system1 = 1.2Gb and system2 = 5Mb
Edit : @jaliee85 sorry but I don't know from where it may come.
If you made manual repartition just try to flash CWM and flash repartition script made by audahadi (second or third thread page about repartitioning)
Click to expand...
Click to collapse
Thank yous.
My device made manual repartition to system1 = 1.0Gb and system2 = 1.0Gb. Is OK?

Has anyone tried the extended version? It is work?is there any problem with the .zip ?

jaliee85 said:
I got this error when i flash extended version using twrp.i already extend my partition using in the post method...pls i need this solution
Code:
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:operation_start: 'Flashing'
Installing '/sdcard/Download/cm-12.1-20150503-UNOFFICIAL-Opticancro-cancro.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
minzip: Extracted 4 file(s)
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12.1
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
blockimg version is 2
Patching system image unconditionally... erasing 318848 blocks
script aborted: blkdiscard failed: Invalid argument
blkdiscard failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/cm-12.1-20150503-UNOFFICIAL-Opticancro-cancro.zip'
Error flashing zip '/sdcard/Download/cm-12.1-20150503-UNOFFICIAL-Opticancro-cancro.zip'
Updating partition details...
I:Data backup size is 1216MB, free: 5906MB.
I:Unable to mount '/usbotg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
Click to expand...
Click to collapse
i had the exact same error.
i solve it by install CWM and resize both my partitions (system1, system2) back to default size and then install the stock rom instead of extended.

Cant restore from titanium.

YES
d'joker said:
can we extend partition to 1.2gb with the flashable zip available on xda?
any demerits of increasing the partition size?
Click to expand...
Click to collapse
yes we can. i myself extended to 1.2GB one via a flashable zip.
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
wonderboys said:
hi,
sorry for this if this question already been answer before.
i having the error with status 7
i tried many times to install the rom through CWM.
and i tried to change the binary script and still the same.
anyone of here face this problem before?
is there any solution for this?
thanks for advanced.
Click to expand...
Click to collapse
diable stock partitions and make extended partition of 1.2GB.

heating issue
Battery drain and heating issue.
Why mi band operates differently when unlocking miui or non miui ROM ?
Previously on mi3 when i was using miui phone could only be unlocked if band was in approximately 1 metre radius but now phone unlocks from 7-8 metres too(normal Bluetooth range)
I used to boast my friends by handing then my mi3 and ask then to unlock and when they encountered Patten lock, I would approach the phone and the moment i grabbed it, it got unlocked.
But note this doesn't happens
Apart from this boasting, it is really very unsafe and USELESS smart lock it it has this much big operating radius.

will there be OTA updates?

BigFatTony said:
will there be OTA updates?
Click to expand...
Click to collapse
it will be too much to ask for OTA updates, we have bigger issues to solve first like camera, ambient display etc.

having problem installing it..need a little help.. this is the error executing updater binary in zip

Unable to extract zip file

I've got a freshly installed Magisk v14, with manager 5.6.0, running on an Oukitel K10 with Android 7.1.1.
Version 15+ of Magisk causes a boot loop on this device, so I'm stuck on 14.
Anyway, installing downloaded Magisk modules from the zip file, or from the Downloads section in the manager, I get logs like:
Code:
- Copying zip to temp directory
- Installing Emoji_one-v1.311.zip
- Mounting /system, /vendor, /data, /cache
! Unable to extract zip file!
Failed!
! Installation failed
The MagiskManager directory does exist. I also deleted it and let the manager recreate it by downloading the magisk zip again. No change.
What can I do?

Might be an issue with unzip. Try if installing the Busybox module from the Downloads section works, and if it does, try installing modules again (after rebooting).

Installing BusyBox worked, but even after a reboot I get the same result when attempting to install other stuff. Also, BusyBox is listed under "Update Available" in the downloads section even though I already installed 1.27.2, twice.

norbolt said:
Installing BusyBox worked, but even after a reboot I get the same result when attempting to install other stuff. Also, BusyBox is listed under "Update Available" in the downloads section even though I already installed 1.27.2, twice.
Click to expand...
Click to collapse
That most likely means it did not work. Post the install log from installing the Busybox module.

Hm. Yes, the log doesn't seem as fine.
Code:
- Copying zip to temp directory
- Installing Busybox_for_Android_NDK-1.27.2.zip
Busybox Installer Script
by osm0sis @ xda-developers
Mounting...
mount: bad /etc/fstab: No such file or directory
mount: bad /etc/fstab: No such file or directory
mount: bad /etc/fstab: No such file or directory
Extracting files...
update-binary[110]: unzip: not found
Installing...
Using architecture: arm64
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 16384
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4096 inodes and 1294/16384 blocks
umount: /dev/magisk_merge: No such file or directory
mount: losetup failed 1
mknod: /dev/block/loop0: File exists
losetup: /dev/block/loop0=/data//magisk_merge.img: Device or resource busy
mknod: /dev/block/loop1: File exists
Using path: /dev/magisk_merge/busybox-ndk/system/xbin
cp: busybox-arm64: No such file or directory
cp: bad 'busybox-arm64': No such file or directory
chown: /dev/magisk_merge/busybox-ndk/system/xbin/busybox: No such file or directory
chmod: /dev/magisk_merge/busybox-ndk/system/xbin/busybox: No such file or directory
cp: module.prop: No such file or directory
cp: bad 'module.prop': No such file or directory
cp: module.prop: No such file or directory
cp: bad 'module.prop': No such file or directory
Cleaning...
update-binary[189]: /dev/magisk_merge/busybox-ndk/system/xbin/busybox: not found
update-binary[191]: /dev/magisk_merge/busybox-ndk/system/xbin/busybox: not found
update-binary[210]: /dev/magisk_merge/busybox-ndk/system/xbin/busybox: not found
Creating symlinks...
Unmounting...
umount: /system: Device or resource busy
umount: /data: Device or resource busy
umount: /cache: Device or resource busy
Done!
- All done!

Yeah, there's an issue with unzip:
Code:
update-binary[110]: unzip: not found
Might be an issue with your Magisk installation or a device thing, hard to say....
Have you tried installing a zip through recovery? If you can install the Busybox module in recovery it might fix things.

Didgeridoohan said:
Have you tried installing a zip through recovery? If you can install the Busybox module in recovery it might fix things.
Click to expand...
Click to collapse
I have not tried that. I currently have the stock recovery flashed. So I guess this means flashing TWRP, then flashing Busybox, and perhaps also attempting to flash Magisk itself through the recovery?
Hopefully I got that right. I'm a bit new to this.

norbolt said:
I have not tried that. I currently have the stock recovery flashed. So I guess this means flashing TWRP, then flashing Busybox, and perhaps also attempting to flash Magisk itself through the recovery?
Hopefully I got that right. I'm a bit new to this.
Click to expand...
Click to collapse
You don't have to install TWRP, you can just boot it:
Code:
fastboot boot recovery twrp.img

I attempted to install both Magisk and Busybox from TWRP, and while the Magisk installer seems to run fine, I get to allow root access to stuff in Android afterwards and I get the Magisk Manager and such, I still can't install Busybox. Also, it seems from the log that Magisk itself is also having some issues the UI isn't telling me about.
The main issue seems to be the following error:
Code:
I:[MTP] MtpServer::run fd: 26
E:[MTP] got unsupported command UNKNOWNE:[MTP] response write returned -1, errno: 19, exiting MtpServer::run loop
Searching Google for the above error returns very little help.
I pasted the entire log here, from me booting TWRP and attempting to install Magisk and Busybox a few times. The Busybox installer claims Magisk isn't installed.
I can't post links yet, so this is code:
Code:
http://paste.debian.net/1010746/

norbolt said:
I've got a freshly installed Magisk v14, with manager 5.6.0, running on an Oukitel K10 with Android 7.1.1.
Version 15+ of Magisk causes a boot loop on this device, so I'm stuck on 14.
Anyway, installing downloaded Magisk modules from the zip file, or from the Downloads section in the manager, I get logs like:
Code:
- Copying zip to temp directory
- Installing Emoji_one-v1.311.zip
- Mounting /system, /vendor, /data, /cache
! Unable to extract zip file!
Failed!
! Installation failed
The MagiskManager directory does exist. I also deleted it and let the manager recreate it by downloading the magisk zip again. No change.
What can I do?
Click to expand...
Click to collapse
hello,
Very simple solution for me at least.
i found this thread because the same thing just happened to me on g900t s5 running lineageOS. Magisk said couldnt extract Zip everytime.
My problem i believe was that i installed busybox from Apkpure and not playstore
Because when i uninstalled Busybox from apkpure then installed busybox from playtore the unzip errors are gone!
Maybe its because i has a bad copy of busybox?
Idk but that was the solution for me!
Hope this helps someone

Me helps install again magisk by twrp.

Install the es file explorer once and extract the zip at least once, It will show a list of programs by which to extract, select es file extractor and check the always button now go back to the magisk manager and try again you should be good to go.

magisk zip

My problem solved by typing real path.
I was use command to install a module using this code
Code:
twrp install sdcard/module.zip
Give an error, so i change to
Code:
twrp install /sdcard/module.zip
Everything ok.

alfanveykov said:
My problem solved by typing real path.
I was use command to install a module using this code
Code:
twrp install sdcard/module.zip
Give an error, so i change to
Code:
twrp install /sdcard/module.zip
Everything ok.
Click to expand...
Click to collapse
where I must try this command?
because I have same problem

Question Renaming a system file?

I have a rooted Pixel 7 and It was suggested that I rename a system file to prevent the system from updating itself (despite my having turned off all such options). My first attempt was to merely try renaming the file, but that didn’t work because the file systems in mounted RO.
I did some looking around, and the common approach to dealing with this issue is to remount the file system. Following is a ‘screen grab’ of my abd session:
Code:
cheetah:/ $ su
cheetah:/ $ ls /product
app etc fonts framework lib lib64 lost+found media overlay priv-app tts usr wallpaper
(this has the directory I want, so this file system)
cheetah:/ $ mount | grep product
/dev/block/dm-15 on /product type ext4 (ro,seclabel,relatime)
(this is a mounted file system)
cheetah:/ # mount -o rw,remount /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount -t ext4 /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount /dev/block/dm-15 /product
'/dev/block/dm-15' is read-only
(three attempts to remount – all failed)
So, now what should I try?

groston said:
I have a rooted Pixel 7 and It was suggested that I rename a system file to prevent the system from updating itself (despite my having turned off all such options). My first attempt was to merely try renaming the file, but that didn’t work because the file systems in mounted RO.
I did some looking around, and the common approach to dealing with this issue is to remount the file system. Following is a ‘screen grab’ of my abd session:
Code:
cheetah:/ $ su
cheetah:/ $ ls /product
app etc fonts framework lib lib64 lost+found media overlay priv-app tts usr wallpaper
(this has the directory I want, so this file system)
cheetah:/ $ mount | grep product
/dev/block/dm-15 on /product type ext4 (ro,seclabel,relatime)
(this is a mounted file system)
cheetah:/ # mount -o rw,remount /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount -t ext4 /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount /dev/block/dm-15 /product
'/dev/block/dm-15' is read-only
(three attempts to remount – all failed)
So, now what should I try?
Click to expand...
Click to collapse
I haven't used this, but maybe it can help you.

Lughnasadh said:
I haven't used this, but maybe it can help you.
Click to expand...
Click to collapse
Thank you. Seems like this might work, but after reading several pages, I am not sure how to install/use overlayfs. I have a Windows system - any chance you could point me to something that provides some guidance?

groston said:
Thank you. Seems like this might work, but after reading several pages, I am not sure how to install/use overlayfs. I have a Windows system - any chance you could point me to something that provides some guidance?
Click to expand...
Click to collapse
I've never used this before but I believe once you flash the module it makes the /system RW so you can start making modifications. There's a README that provides some information. I don't know of any other guides besides the information on that Github page.

Checking out the thread below might reveal a solution and/or give a clue or hint...
Pixel 7 Pro Stuck in read only mode (rooted with magisk 26.1) Am I missing something? HELP
Everything ive tried in FX Explorer fails. No matter what I try, for example editing build.prop or anything else, it constantly says read only. i cannot use any method to allow write access. Did i miss something when i rooted with Magisk? I dont...
forum.xda-developers.com

simplepinoi177 said:
Checking out the thread below might reveal a solution and/or give a clue or hint...
Pixel 7 Pro Stuck in read only mode (rooted with magisk 26.1) Am I missing something? HELP
Everything ive tried in FX Explorer fails. No matter what I try, for example editing build.prop or anything else, it constantly says read only. i cannot use any method to allow write access. Did i miss something when i rooted with Magisk? I dont...
forum.xda-developers.com
Click to expand...
Click to collapse
Good suggestion. I installed FX File Explorer, gave it the appropriate permissions, but was unable to change the /product filesystem to read/write.

groston said:
Good suggestion. I installed FX File Explorer, gave it the appropriate permissions, but was unable to change the /product filesystem to read/write.
Click to expand...
Click to collapse
When you say "gave it the appropriate permissions", just to confirm -- that doesn't mean that you changed the security permissions on the folder & files, correct? I hope it means you did not do what the OP in that thread had done and actually did enable root access particularly (hoping that's what you meant on "gave it appropriate permissions").
Because, in certain cases, I've changed permissions on files/folders vs. simply enabling root access mode....
Apologies in advanced if my inquiry seems fairly obvious (to the point of insulting maybe; it is not meant to be), but you never know and many foolish things has been done/assumed on this site that missed many (obvious) things because it wasn't confirmed....