Meizu MX5 Flyme 5 Xposed how???

Meizu MX5 Flyme 5 Xposed how??? - Meizu MX

Hi to all
Can someone tell me step by step hiw to install Xposed and Flyme Tools for Meizu MX5 Flyme 5?
Sent from my MX5 using Tapatalk

isko01 said:
Hi to all
Can someone tell me step by step hiw to install Xposed and Flyme Tools for Meizu MX5 Flyme 5?
Sent from my MX5 using Tapatalk
Click to expand...
Click to collapse
Hello.
First of all, you need to have rooted phone. (if you have, skip this steps)
ROOT:
1). Because on flyme os 5 there is no more Meizu Account option in settings you need to download this app: https://drive.google.com/file/d/0B4xXHWEm81OlUk1hazU4UHFvcG8/view?usp=docslist_api
2). After you download it a install it, log in to your account ans after that the root permision option should apear under fingerprint and security tab.
3). Open it, tick i understand etc. and ok.
4). Phone will reboot and you have successfuly rooted.
How to install Xposed:
1). Download and install xposed installer: https://drive.google.com/file/d/0B4xXHWEm81OlX0EzWDdWZWpHV0k/view?usp=docslist_api
2). Download and install busybox: https://play.google.com/store/apps/details?id=stericson.busybox&hl=cs
3.) Download installer.bin: https://drive.google.com/file/d/0B4xXHWEm81OleTk2TG9jVl9Dd0E/view?usp=docslist_api
and than this version of xposed: https://drive.google.com/file/d/0B4xXHWEm81OldXdyZGxWcU5YNDA/view?usp=docslist_api
4). Paste both files in root of your device
5). Download Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=cs
6). Open Terminal Emulator and type this codes:
a). su (it will get root access for the Emulator)
b). sh /sdcard/installer.bin (this will start the instalation)
c). after you see green si=1 and red no=2 type 1 to continue.
d). after instalation is completed there will be grean text with someting in italien.
7). Reboot you device and you have succesfully installed Xposed.
To be honest, i have no idea how to make Flyme tools work, and it is really hard to even find updated version.
Hope it work (for me it worked perfectly) and have a fun.

Kubas_inko_CZ said:
Hello.
First of all, you need to have rooted phone. (if you have, skip this steps)
ROOT:
1). Because on flyme os 5 there is no more Meizu Account option in settings you need to download this app: https://drive.google.com/file/d/0B4xXHWEm81OlUk1hazU4UHFvcG8/view?usp=docslist_api
2). After you download it a install it, log in to your account ans after that the root permision option should apear under fingerprint and security tab.
3). Open it, tick i understand etc. and ok.
4). Phone will reboot and you have successfuly rooted.
How to install Xposed:
1). Download and install xposed installer: https://drive.google.com/file/d/0B4xXHWEm81OlX0EzWDdWZWpHV0k/view?usp=docslist_api
2.) Download installer.bin: https://drive.google.com/file/d/0B4xXHWEm81OleTk2TG9jVl9Dd0E/view?usp=docslist_api
and than this version of xposed: https://drive.google.com/file/d/0B4xXHWEm81OldXdyZGxWcU5YNDA/view?usp=docslist_api
3). Paste both files in root of your device
4). Download Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=cs
5). Open Terminal Emulator and type this codes:
a). su (it will get root access for the Emulator)
b). sh /sdcard/installer.bin (this will start the instalation)
c). after you see green si=1 and red no=2 type 1 to continue.
d). after instalation is completed there will be grean text with someting in italien.
6). Reboot you device and you have succesfully installed Xposed.
Tobe honest, i have no idea how to make Flyme tools work, and it is really hard to even find updated version.
Hope it work (for me it worked perfectly) and have a fun.
Click to expand...
Click to collapse
Thx a lot my firend. But i need help again. On the step number 5 I write su and sh but it tell me invalide command. I have root phone on your way and with kingroot but i dont know what us problem. Maybe i dont write good in emukator. Here is the photo:
{
"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"
}
Sent from my MX5 using Tapatalk

isko01 said:
Thx a lot my firend. But i need help again. On the step number 5 I write su and sh but it tell me invalide command. I have root phone on your way and with kingroot but i dont know what us problem. Maybe i dont write good in emukator. Here is the photo:
View attachment 3606549
Sent from my MX5 using Tapatalk
Click to expand...
Click to collapse
install supersu and busybox

yes i have suoer su and busybox
I think i dint write a good code. can you tel me what to write correct
Sent from my MX5 using Tapatalk

isko01 said:
yes i have suoer su and busybox
I think i dint write a good code. can you tel me what to write correct
Sent from my MX5 using Tapatalk
Click to expand...
Click to collapse
Use terminal emulator. it also does look like you dont have su installed.

koaaN said:
install supersu and busybox
Click to expand...
Click to collapse
sorry, i forgot about bussybox AND i edited my first post now you have the bussybox install part too (you dont really nead supersu)
Use therminal emulator, it is way bether then terminal delux

Ok my firends. I do again all. Now it is root. But it is the same problem. Look at the photo pleaseeee.
I think I put the wrong way my download filea. I put it in sdcard I will put the photo.
Or I write wrong code in terminal. Please help me Im near to finish this.
Sent from my MX5 using Tapatalk

if i write install sdcard/installer.bin it will show me a list of things but i dont know what to choose and how to write
Sent from my MX5 using Tapatalk

isko01 said:
Ok my firends. I do again all. Now it is root. But it is the same problem. Look at the photo pleaseeee.
I think I put the wrong way my download filea. I put it in sdcard I will put the photo.View attachment 3606942
Or I write wrong code in terminal. Please help me Im near to finish this.
View attachment 3606941
Sent from my MX5 using Tapatalk
Click to expand...
Click to collapse
You almost wrote the right thing at one time there, you forgot to write sh in front of /sdcard/installer.bin
1.Open terminal
2. write su
3. write sh /sdcard/installer.bin

Thx you both. At last i make Xposed. I restart my phone and waith 20 minutes to finish with "optimization application". Just logo of Flyme was been and numbers of applications. uhh now works everything. THX YOU ONE MORE TIME!!!
can you tel me which modules eom Xposed are you using on your Flyme sistem?
Sent from my MX5 using Tapatalk

You have done it almost right but the code is not: sh/sdcard/installer.bin BUT sh /sdcard/installer.bin
You forget about the space between sh and /
Thx you both. At last i make Xposed. I restart my phone and waith 20 minutes to finish with "optimization application". Just logo of Flyme was been and numbers of applications. uhh now works everything. THX YOU ONE MORE TIME!!!
can you tel me which modules eom Xposed are you using on your Flyme sistem?
Sent from my MX5 using Tapatalk
Click to expand...
Click to collapse
I am using only OGyoutube. It is modified YouTube app, where you can play on beckround, download MP3/MP4 and watch it in window MOD like on Samsung device's.
http://ogmods.net/home/OGYouTube

you can download the global flyme5 at flymeos.com
there's new flyme official site launched last month, you can find the stable firmware there

jerome_2016 said:
there's new flyme official site launched last month, you can find the stable firmware there
Click to expand...
Click to collapse
we are not talking about OS/firmware, but about root and xposed
+ it is fake

Why do you think it's fake?
Why do you think it's fake? it's linked from meizu.com/en
Kubas_inko_CZ said:
we are not talking about OS/firmware, but about root and xposed
+ it is fake
Click to expand...
Click to collapse

jerome_2016 said:
Why do you think it's fake? it's linked from meizu.com/en
Click to expand...
Click to collapse
Because of this:
P.S.: It is in Czech but it means: This webpage is unavailable.

ok, you need to add www before it
ok, you need to add www in front of it
Kubas_inko_CZ said:
Because of this:
P.S.: It is in Czech but it means: This webpage is unavailable.
Click to expand...
Click to collapse

something went wrong.
could you please tell me what can be done?
the log is below:
Comienzo del Log:
[2J[H
[00;41m Instalador de Xposed [00;37;40m
[31m --------------------------------------- [00;37;40m
[31m -------------------------------- [00;37;40m
[01;34m por iicc [00;37;40m
[2J[H
[1;35m¿Seguro que deseas instalar Xposed?[0m
[1;34mSelecciona una opcion:[0m
[1;32m[ Si = 1[0m [1;33m|[0m [1;31mNo = 2 ][0m
Busybox instalado correctamente en Xbin
Montando particiones y creando directorios...
Archive: /sdcard/xposed-v79-sdk22-arm64.zip
inflating: META-INF/com/google/android/flash-script.sh
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: system/bin/app_process32_xposed
inflating: system/bin/app_process64_xposed
inflating: system/bin/dex2oat
inflating: system/bin/oatdump
inflating: system/bin/patchoat
inflating: system/framework/XposedBridge.jar
inflating: system/lib/libart-compiler.so
inflating: system/lib/libart.so
inflating: system/lib/libsigchain.so
inflating: system/lib/libxposed_art.so
inflating: system/lib64/libart-disassembler.so
inflating: system/lib64/libart.so
inflating: system/lib64/libsigchain.so
inflating: system/lib64/libxposed_art.so
inflating: system/xposed.prop
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
Ejecutando el script principal...
/sdcard/installer.bin[199]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[199]: can't create /proc/self/fd/: Is a directory
2+0 records in
2+0 records out
2 bytes transferred in 0.001 secs (2000 bytes/sec)
3+0 records in
3+0 records out
3 bytes transferred in 0.001 secs (3000 bytes/sec)
10+0 records in
10+0 records out
10 bytes transferred in 0.001 secs (10000 bytes/sec)
dd: skip reached end of input
3+0 records in
3+0 records out
3 bytes transferred in 0.001 secs (3000 bytes/sec)
6+0 records in
6+0 records out
6 bytes transferred in 0.001 secs (6000 bytes/sec)
3+0 records in
3+0 records out
3 bytes transferred in 0.001 secs (3000 bytes/sec)
3+0 records in
3+0 records out
3 bytes transferred in 0.001 secs (3000 bytes/sec)
/sdcard/installer.bin[224]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[224]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[239]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[239]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[274]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[274]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[274]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[274]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[277]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[277]: can't create /proc/self/fd/: Is a directory
failed: Device or resource busy
/sdcard/installer.bin[280]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[280]: can't create /proc/self/fd/: Is a directory
[2J[HFin de la instalacion
Ahora ve a Xposed y haz un reinicio suave
Al iniciar el sistema estara optimizando apps
Dependiendo de las aplicaciones instaladas,
tardara segundos hasta una hora.
Si todo esta bien, Xposed estara activo.
Se ha creado un Log de la instalacion
en la ruta /sdcard
Saludos!

straycat73 said:
something went wrong.
could you please tell me what can be done?
the log is below:
Comienzo del Log:
[2J[H
[00;41m Instalador de Xposed [00;37;40m
[31m --------------------------------------- [00;37;40m
[31m -------------------------------- [00;37;40m
[01;34m por iicc [00;37;40m
[2J[H
[1;35m¿Seguro que deseas instalar Xposed?[0m
[1;34mSelecciona una opcion:[0m
[1;32m[ Si = 1[0m [1;33m|[0m [1;31mNo = 2 ][0m
Busybox instalado correctamente en Xbin
Montando particiones y creando directorios...
Archive: /sdcard/xposed-v79-sdk22-arm64.zip
inflating: META-INF/com/google/android/flash-script.sh
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: system/bin/app_process32_xposed
inflating: system/bin/app_process64_xposed
inflating: system/bin/dex2oat
inflating: system/bin/oatdump
inflating: system/bin/patchoat
inflating: system/framework/XposedBridge.jar
inflating: system/lib/libart-compiler.so
inflating: system/lib/libart.so
inflating: system/lib/libsigchain.so
inflating: system/lib/libxposed_art.so
inflating: system/lib64/libart-disassembler.so
inflating: system/lib64/libart.so
inflating: system/lib64/libsigchain.so
inflating: system/lib64/libxposed_art.so
inflating: system/xposed.prop
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
Ejecutando el script principal...
/sdcard/installer.bin[199]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[199]: can't create /proc/self/fd/: Is a directory
2+0 records in
2+0 records out
2 bytes transferred in 0.001 secs (2000 bytes/sec)
3+0 records in
3+0 records out
3 bytes transferred in 0.001 secs (3000 bytes/sec)
10+0 records in
10+0 records out
10 bytes transferred in 0.001 secs (10000 bytes/sec)
dd: skip reached end of input
3+0 records in
3+0 records out
3 bytes transferred in 0.001 secs (3000 bytes/sec)
6+0 records in
6+0 records out
6 bytes transferred in 0.001 secs (6000 bytes/sec)
3+0 records in
3+0 records out
3 bytes transferred in 0.001 secs (3000 bytes/sec)
3+0 records in
3+0 records out
3 bytes transferred in 0.001 secs (3000 bytes/sec)
/sdcard/installer.bin[224]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[224]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[239]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[239]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[274]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[274]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[274]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[274]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[277]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[277]: can't create /proc/self/fd/: Is a directory
failed: Device or resource busy
/sdcard/installer.bin[280]: can't create /proc/self/fd/: Is a directory
/sdcard/installer.bin[280]: can't create /proc/self/fd/: Is a directory
[2J[HFin de la instalacion
Ahora ve a Xposed y haz un reinicio suave
Al iniciar el sistema estara optimizando apps
Dependiendo de las aplicaciones instaladas,
tardara segundos hasta una hora.
Si todo esta bien, Xposed estara activo.
Se ha creado un Log de la instalacion
en la ruta /sdcard
Saludos!
Click to expand...
Click to collapse
It looks like, it dont have permission to write to device. What is your OS version ?

so guys...I have MX4 PRO with Flyme 5 the stable version!
Can I use this guide to install xposed in my phone?

Related

Prerooted stock rom 32.0.A.6.200 E5823 z5c

Created with prf-creator.
Just flash the zip-file with twrp.
If someone is able to debloat the rom it would be great.
Just click the megalink below:
https://mega.nz/#!eFFDDbwB!ipn3TXNcVwEZSbEmXbJBXsXEi05UvaISxTOetbiwW-M
Sent from my E5823 using XDA Free mobile app

harrywarry said:
Created with prf-creator.
Just flash the zip-file with twrp.
If someone is able to debloat the rom it would be great.
Just click the megalink below:
https://mega.nz/#!eFFDDbwB!ipn3TXNcVwEZSbEmXbJBXsXEi05UvaISxTOetbiwW-M
Sent from my E5823 using XDA Free mobile app
Click to expand...
Click to collapse
could you tell me how did you do??
Thanks!

acabreram said:
could you tell me how did you do??
Thanks!
Click to expand...
Click to collapse
You can find all information about the prfcreator tool here:
http://forum.xda-developers.com/showthread.php?p=55082588
You can download the ftf's from xperifirm.
Sent from my E5823 using XDA Free mobile app

harrywarry said:
Created with prf-creator.
Just flash the zip-file with twrp.
If someone is able to debloat the rom it would be great.
Just click the megalink below:
https://mega.nz/#!eFFDDbwB!ipn3TXNcVwEZSbEmXbJBXsXEi05UvaISxTOetbiwW-M
Sent from my E5823 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for putting this together! Is this based on the most recently released software (not Marshmallow of course)? I'm not the most avid technical expert in the world so please excuse my question.

sumguyatvt1128 said:
Thanks for putting this together! Is this based on the most recently released software (not Marshmallow of course)? I'm not the most avid technical expert in the world so please excuse my question.
Click to expand...
Click to collapse
As far as I know it is the most recent stock version available.
I'm not a techical expert either :beer:
Sent from my E5823 using XDA Free mobile app

Haha sweet thanks! Won't boot up now. I get blinking red lights, and the phone resets. I believe I'm stuck in a boot loop

I think you have to flash a custom kernel you could try Andro kernel. The stock kernel is not compatible i think

acabreram said:
I think you have to flash a custom kernel you could try Andro kernel. The stock kernel is not compatible i think
Click to expand...
Click to collapse
You could be right. I came from this one:
http://forum.xda-developers.com/showthread.php?p=63443547
But.... It is a stock rom including the stock kernel.
Sent from my E5823 using XDA Free mobile app

harrywarry said:
You could be right. I came from this one:
http://forum.xda-developers.com/showthread.php?p=63443547
But.... It is a stock rom including the stock kernel.
Sent from my E5823 using XDA Free mobile app
Click to expand...
Click to collapse
well you could flash a prerooted firmware and after power off and boot in fastbootmode and flash a custom kernel with cmd
check this one too http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605

Code:
.
Installing '/external_sd/1 Rom and Apk/flashable-prerooted.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /external_sd/1 Rom and Apk/flashable-prerooted.zip
inflating: META-INF/com/google/android/update-binary2
installing samsung updater extensions
===========================================
| |
| *** Pre-Rooted Firmware *** |
| E5823_32.0.A.6.200_SG |
| |
| Created with PRFCreator |
| by zxz0O0 |
| |
===========================================
Extracting files...
about to run program [/tmp/busybox] with 3 args
PRF is using sinflash
Installing firmware. This might take a while...
about to run program [/tmp/sinflash] with 6 args
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing system.sin to /dev/block/mmcblk0p43. Please wait...
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 3511
Finished
System flashed.
about to run program [/tmp/sinflash] with 6 args
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Couldn't find partition with matching uuid
run_program: child exited with status 1
Error flashing ltalabel.sin
about to run program [/tmp/sinflash] with 6 args
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing fotakernel.sin to /dev/block/mmcblk0p32. Please wait...
run_program: child terminated by signal 11
Error flashing fotakernel.sin
about to run program [/tmp/sinflash] with 6 args
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing boot.sin to /dev/block/mmcblk0p29. Please wait...
run_program: child terminated by signal 11
about to run program [/tmp/sinflash] with 6 args
Error flashing kernel.sin
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing amss_fsg.sin to /dev/block/mmcblk0p13. Please wait...
run_program: child terminated by signal 11
about to run program [/tmp/sinflash] with 4 args
Modem flashed.
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing amss_fs_1.sin to /dev/block/mmcblk0p17. Please wait...
Finished
about to run program [/tmp/sinflash] with 4 args
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing amss_fs_2.sin to /dev/block/mmcblk0p18. Please wait...
Finished
about to run program [/tmp/busybox] with 3 args
Cleaning up...
Finished!
Launching SuperSU and Recovery zip
umount: can't umount /system: Invalid argument
run_program: child exited with status 1
about to run program [/tmp/busybox] with 4 args
blockdev: can't open '/dev/block/platform/msm_sdcc.1/by-name/system': No such file or directory
run_program: child exited with status 1
about to run program [/tmp/busybox] with 3 args
about to run program [/tmp/busybox] with 3 args
about to run program [/tmp/busybox] with 5 args
Archive: /tmp/SuperSU.zip
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: arm/chattr
inflating: arm/chattr.pie
inflating: arm/libsupol.so
inflating: arm/su
inflating: arm/sukernel
inflating: arm/supolicy
inflating: arm64/libsupol.so
inflating: arm64/su
inflating: arm64/sukernel
inflating: arm64/supolicy
inflating: armv7/chattr.pie
inflating: armv7/libsupol.so
inflating: armv7/su
inflating: armv7/sukernel
inflating: armv7/supolicy
inflating: common/99SuperSUDaemon
inflating: common/Superuser.apk
inflating: common/file_contexts_image
inflating: common/install-recovery.sh
inflating: common/launch_daemonsu.sh
inflating: mips/chattr.pie
inflating: mips/libsupol.so
inflating: mips/su
inflating: mips/sukernel
inflating: mips/supolicy
inflating: mips64/libsupol.so
inflating: mips64/su
inflating: mips64/sukernel
inflating: mips64/supolicy
inflating: x64/libsupol.so
inflating: x64/su
inflating: x64/sukernel
inflating: x64/supolicy
inflating: x86/chattr
inflating: x86/chattr.pie
inflating: x86/libsupol.so
inflating: x86/su
inflating: x86/su.pie
inflating: x86/sukernel
inflating: x86/supolicy
about to run program [/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary] with 4 args
*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: mounting /dev/block/mmcblk0p43 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p43 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p42 on /data failed: Device or resource busy
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.008291 seconds, 241B/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.001581 seconds, 1.9KB/s
10+0 records in
10+0 records out
10 bytes (10B) copied, 0.000171 seconds, 57.1KB/s
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.005504 seconds, 0B/s
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 761: /system/toolbox: not found
- Extracting files
Archive: /tmp/SuperSU.zip
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: arm/chattr
inflating: arm/chattr.pie
inflating: arm/libsupol.so
inflating: arm/su
inflating: arm/sukernel
inflating: arm/supolicy
inflating: arm64/libsupol.so
inflating: arm64/su
inflating: arm64/sukernel
inflating: arm64/supolicy
inflating: armv7/chattr.pie
inflating: armv7/libsupol.so
inflating: armv7/su
inflating: armv7/sukernel
inflating: armv7/supolicy
inflating: common/99SuperSUDaemon
inflating: common/Superuser.apk
inflating: common/file_contexts_image
inflating: common/install-recovery.sh
inflating: common/launch_daemonsu.sh
inflating: mips/chattr.pie
inflating: mips/libsupol.so
inflating: mips/su
inflating: mips/sukernel
inflating: mips/supolicy
inflating: mips64/libsupol.so
inflating: mips64/su
inflating: mips64/sukernel
inflating: mips64/supolicy
inflating: x64/libsupol.so
inflating: x64/su
inflating: x64/sukernel
inflating: x64/supolicy
inflating: x86/chattr
inflating: x86/chattr.pie
inflating: x86/libsupol.so
inflating: x86/su
inflating: x86/su.pie
inflating: x86/sukernel
inflating: x86/supolicy
- System mode
- Disabling OTA survival
chmod: /tmp/supersu/arm64/chattr.pie: No such file or directory
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
- Removing old files
rm: can't remove '/data/su.img': No such file or directory
rm: can't remove '/cache/su.img': No such file or directory
- Creating space
- Placing files
rm: can't remove '/system/bin/.ext/.su': No such file or directory
rm: can't remove '/system/xbin/su': No such file or directory
rm: can't remove '/system/xbin/daemonsu': No such file or directory
rm: can't remove '/system/xbin/supolicy': No such file or directory
rm: can't remove '/system/lib64/libsupol.so': No such file or directory
rm: can't remove '/system/app/SuperSU/SuperSU.apk': No such file or directory
rm: can't remove '/system/etc/install-recovery.sh': No such file or directory
rm: can't remove '/system/bin/app_process_init': No such file or directory
rm: can't remove '/system/etc/init.d/99SuperSUDaemon': No such file or directory
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: can't create /system/etc/init.d/99SuperSUDaemon: nonexistent directory
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chmod: /system/etc/init.d/99SuperSUDaemon: No such file or directory
- Restoring files
rm: can't remove '/system/app/Maps/Maps.apk': No such file or directory
rm: can't remove '/system/app/YouTube/YouTube.apk': No such file or directory
- Post-installation script
rm: can't remove '/system/toybox': No such file or directory
rm: can't remove '/system/toolbox': No such file or directory
- Unmounting /system
- Done !
package_extract_file: no dualrecovery.zip in package
about to run program [/tmp/busybox] with 3 args
mount: mounting /dev/block/mmcblk0p42 on /data failed: Device or resource busy
run_program: child exited with status 111
about to run program [/tmp/busybox] with 4 args
blockdev: can't open '/dev/block/platform/msm_sdcc.1/by-name/system': No such file or directory
run_program: child exited with status 1
about to run program [/tmp/busybox] with 3 args
about to run program [/tmp/flash_apps.sh] with 3 args
run_program: child exited with status 1
script result was []
I:Legacy property environment disabled.
I:operation_start: 'Flashing'
Installing '/external_sd/1 Rom and Apk/Zombie-b5.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/1 Rom and Apk/Zombie-b5.zip'
Updating partition details...
I:Data backup size is 0MB, free: 20025MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'install'
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:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.lo
Tried flashing this again today, no luck.
I'm on .152 trying to get a deodexed ROM to be able to run xposed. Is this the way to go?

civicsr2cool said:
Code:
.
Installing '/external_sd/1 Rom and Apk/flashable-prerooted.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /external_sd/1 Rom and Apk/flashable-prerooted.zip
inflating: META-INF/com/google/android/update-binary2
installing samsung updater extensions
===========================================
| |
| *** Pre-Rooted Firmware *** |
| E5823_32.0.A.6.200_SG |
| |
| Created with PRFCreator |
| by zxz0O0 |
| |
===========================================
Extracting files...
about to run program [/tmp/busybox] with 3 args
PRF is using sinflash
Installing firmware. This might take a while...
about to run program [/tmp/sinflash] with 6 args
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing system.sin to /dev/block/mmcblk0p43. Please wait...
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 3511
Finished
System flashed.
about to run program [/tmp/sinflash] with 6 args
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Couldn't find partition with matching uuid
run_program: child exited with status 1
Error flashing ltalabel.sin
about to run program [/tmp/sinflash] with 6 args
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing fotakernel.sin to /dev/block/mmcblk0p32. Please wait...
run_program: child terminated by signal 11
Error flashing fotakernel.sin
about to run program [/tmp/sinflash] with 6 args
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing boot.sin to /dev/block/mmcblk0p29. Please wait...
run_program: child terminated by signal 11
about to run program [/tmp/sinflash] with 6 args
Error flashing kernel.sin
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing amss_fsg.sin to /dev/block/mmcblk0p13. Please wait...
run_program: child terminated by signal 11
about to run program [/tmp/sinflash] with 4 args
Modem flashed.
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing amss_fs_1.sin to /dev/block/mmcblk0p17. Please wait...
Finished
about to run program [/tmp/sinflash] with 4 args
__bionic_open_tzdata: couldn't find any tzdata when looking for EST5EDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Flashing amss_fs_2.sin to /dev/block/mmcblk0p18. Please wait...
Finished
about to run program [/tmp/busybox] with 3 args
Cleaning up...
Finished!
Launching SuperSU and Recovery zip
umount: can't umount /system: Invalid argument
run_program: child exited with status 1
about to run program [/tmp/busybox] with 4 args
blockdev: can't open '/dev/block/platform/msm_sdcc.1/by-name/system': No such file or directory
run_program: child exited with status 1
about to run program [/tmp/busybox] with 3 args
about to run program [/tmp/busybox] with 3 args
about to run program [/tmp/busybox] with 5 args
Archive: /tmp/SuperSU.zip
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: arm/chattr
inflating: arm/chattr.pie
inflating: arm/libsupol.so
inflating: arm/su
inflating: arm/sukernel
inflating: arm/supolicy
inflating: arm64/libsupol.so
inflating: arm64/su
inflating: arm64/sukernel
inflating: arm64/supolicy
inflating: armv7/chattr.pie
inflating: armv7/libsupol.so
inflating: armv7/su
inflating: armv7/sukernel
inflating: armv7/supolicy
inflating: common/99SuperSUDaemon
inflating: common/Superuser.apk
inflating: common/file_contexts_image
inflating: common/install-recovery.sh
inflating: common/launch_daemonsu.sh
inflating: mips/chattr.pie
inflating: mips/libsupol.so
inflating: mips/su
inflating: mips/sukernel
inflating: mips/supolicy
inflating: mips64/libsupol.so
inflating: mips64/su
inflating: mips64/sukernel
inflating: mips64/supolicy
inflating: x64/libsupol.so
inflating: x64/su
inflating: x64/sukernel
inflating: x64/supolicy
inflating: x86/chattr
inflating: x86/chattr.pie
inflating: x86/libsupol.so
inflating: x86/su
inflating: x86/su.pie
inflating: x86/sukernel
inflating: x86/supolicy
about to run program [/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary] with 4 args
*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: mounting /dev/block/mmcblk0p43 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p43 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p42 on /data failed: Device or resource busy
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.008291 seconds, 241B/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.001581 seconds, 1.9KB/s
10+0 records in
10+0 records out
10 bytes (10B) copied, 0.000171 seconds, 57.1KB/s
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.005504 seconds, 0B/s
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 761: /system/toolbox: not found
- Extracting files
Archive: /tmp/SuperSU.zip
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: arm/chattr
inflating: arm/chattr.pie
inflating: arm/libsupol.so
inflating: arm/su
inflating: arm/sukernel
inflating: arm/supolicy
inflating: arm64/libsupol.so
inflating: arm64/su
inflating: arm64/sukernel
inflating: arm64/supolicy
inflating: armv7/chattr.pie
inflating: armv7/libsupol.so
inflating: armv7/su
inflating: armv7/sukernel
inflating: armv7/supolicy
inflating: common/99SuperSUDaemon
inflating: common/Superuser.apk
inflating: common/file_contexts_image
inflating: common/install-recovery.sh
inflating: common/launch_daemonsu.sh
inflating: mips/chattr.pie
inflating: mips/libsupol.so
inflating: mips/su
inflating: mips/sukernel
inflating: mips/supolicy
inflating: mips64/libsupol.so
inflating: mips64/su
inflating: mips64/sukernel
inflating: mips64/supolicy
inflating: x64/libsupol.so
inflating: x64/su
inflating: x64/sukernel
inflating: x64/supolicy
inflating: x86/chattr
inflating: x86/chattr.pie
inflating: x86/libsupol.so
inflating: x86/su
inflating: x86/su.pie
inflating: x86/sukernel
inflating: x86/supolicy
- System mode
- Disabling OTA survival
chmod: /tmp/supersu/arm64/chattr.pie: No such file or directory
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: /tmp/supersu/arm64/chattr.pie: not found
- Removing old files
rm: can't remove '/data/su.img': No such file or directory
rm: can't remove '/cache/su.img': No such file or directory
- Creating space
- Placing files
rm: can't remove '/system/bin/.ext/.su': No such file or directory
rm: can't remove '/system/xbin/su': No such file or directory
rm: can't remove '/system/xbin/daemonsu': No such file or directwNshoumove '/system/xbin/supolicy': No such file or directory
rm: can't remove '/system/lib64/libsupol.so': No such file or directory
rm: can't remove '/system/app/SuperSU/SuperSU.apk': No such file or directory
rm: can't remove '/system/etc/install-recovery.sh': No such file or directory
rm: can't remove '/system/bin/app_process_init': No such file or directory
rm: can't remove '/system/etc/init.d/99SuperSUDaemon': No such file or directory
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 1205: can't create /system/etc/init.d/99SuperSUDaemon: nonexistent directory
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chmod: /system/etc/init.d/99SuperSUDaemon: No such file or directory
- Restoring files
rm: can't remove '/system/app/Maps/Maps.apk': No such file or directory
rm: can't remove '/system/app/YouTube/YouTube.apk': No such file or directory
- Post-installation script
rm: can't remove '/system/toybox': No such file or directory
rm: can't remove '/system/toolbox': No such file or directory
- Unmounting /system
- Done !
package_extract_file: no dualrecovery.zip in package
about to run program [/tmp/busybox] with 3 args
mount: mounting /dev/block/mmcblk0p42 on /data failed: Device or resource busy
run_program: child exited with status 111
about to run program [/tmp/busybox] with 4 args
blockdev: can't open '/dev/block/platform/msm_sdcc.1/by-name/system': No such file or directory
run_program: child exited with status 1
about to run program [/tmp/busybox] with 3 args
about to run program [/tmp/flash_apps.sh] with 3 args
run_program: child exited with status 1
script result was []
I:Legacy property environment disabled.
I:operation_start: 'Flashing'
Installing '/external_sd/1 Rom and Apk/Zombie-b5.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/1 Rom and Apk/Zombie-b5.zip'
Updating partition details...
I:Data backup size is 0MB, free: 20025MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'install'
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:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.lo
Tried flashing this again today, no luck.
I'm on .152 trying to get a deodexed ROM to be able to run xposed. Is this the way to go?
Click to expand...
Click to collapse
I don't understand why It doesn't work for you. It is a completely stock Sony .200 rom with supersu added.
Nothing more, nothing less.....
Sent from my SGP521 using XDA Free mobile app

harrywarry said:
I don't understand why It doesn't work for you. It is a completely stock Sony .200 rom with supersu added.
Nothing more, nothing less.....
Sent from my SGP521 using XDA Free mobile app
Click to expand...
Click to collapse
Me neither. I can't even flash tool the .200 either. Common denominator would be bootloader?

civicsr2cool said:
Me neither. I can't even flash tool the .200 either. Common denominator would be bootloader?
Click to expand...
Click to collapse
I wouldn't know. Are you on E5823 or e5803?
Sent from my E5823 using XDA Free mobile app

harrywarry said:
I wouldn't know. Are you on E5823 or e5803?
Sent from my E5823 using XDA Free mobile app
Click to expand...
Click to collapse
5823. I unlocked the bootloader right out of the box and put twrp without taking the ota to .200 and now I'm stuck. I'm hoping when m comes out next week or so that's not the case!

civicsr2cool said:
5823. I unlocked the bootloader right out of the box and put twrp without taking the ota to .200 and now I'm stuck. I'm hoping when m comes out next week or so that's not the case!
Click to expand...
Click to collapse
The phone is not working at all now?
Sent from my E5823 using XDA Free mobile app

harrywarry said:
The phone is not working at all now?
Sent from my E5823 using XDA Free mobile app
Click to expand...
Click to collapse
Phone functions fine. I can't get xposed to work at all so I'm trying to update to test. Currently using hotspot to keep my prior phone running the xposed apps I need lol

Hi
I installed this in twrp and did a wipe system before installing.. I'm just wondering if the system should be as big as 20,54gb??
Have i done something wrong?
Thanks in advance.

asl0501 said:
Hi
I installed this in twrp and did a wipe system before installing.. I'm just wondering if the system should be as big as 20,54gb??
Have i done something wrong?
Thanks in advance.
Click to expand...
Click to collapse
I Am not using this rom anymore, so i can't check. I am on mm now and that 'android system' is 9.4 gb.
20 gb seems very large to me.
Sent from my SGP521 using XDA Free mobile app

Hi,
It tried to install this rom, but now my phone is stuck showing "Android is starting" popup.
Sometimes, before being stuck, it optimize some applications (18 or 23, it's depends) but it's still stuck after.
I try to came back in recovery (twrp) but my phone is not listed in adb devices and plug the charger when holding vol- does nothing ...
If anyone know how to save my phone ? ^^
Thanks !
Edit: Saved my phone with Flashtool, updated to a 6.0.1 firmware

Issue Installing Busybox via Magisk

On Android version 8.1 v9.6.8.0
Magisk 19.1
Not entirely sure what's happening, but I can't install the Busybox or ADB/Fastboot modules in Magisk.
I've tried:
- installing through Magisk downloads section
- installing through Magisk manually
- reinstalling Magisk
- installing from TWRP
- reflashing the stock system image
Other modules are installing fine, but these both go through the motions and look like they've successfully installed, only not to be in the list of installed modules.
Saved log from my last attempt through Magisk:
- Copying zip to temp directory
- Installing Busybox_for_Android_NDK-1.30.1.zip
- Current boot slot: _b
- Device is system-as-root
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: install.sh
inflating: module.prop
Busybox Installer Script
mount: can't read '/etc/fstab': No such file or directory
mount: can't read '/etc/fstab': No such file or directory
mount: can't read '/etc/fstab': No such file or directory
by osm0sis @ xda-developers
Mounting...
Extracting files...
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
creating: META-INF/
creating: META-INF/com/
umount: can't unmount /dev/tmp/su: No such file or directory
creating: META-INF/com/google/
creating: META-INF/com/google/android/
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: README.md
inflating: busybox-arm
inflating: busybox-arm64
inflating: busybox-mips
inflating: busybox-mips64
inflating: busybox-x86
inflating: busybox-x86_64
inflating: install.sh
inflating: module.prop
Installing...
Using architecture: arm64
Using path: /dev/tmp/su/xbin
Cleaning...
Creating symlinks...
Unmounting...
umount: can't unmount /system: Device or resource busy
umount: can't unmount /data: Device or resource busy
umount: can't unmount /cache: Invalid argument
Done!
At my wits end and I'm not sure what to try next, short of wiping my phone and flashing the ROM again.

did you reformat to f2fs?

Never_Sm1le said:
did you reformat to f2fs?
Click to expand...
Click to collapse
No, it's still ext4.
The strange thing is that other modules installed fine like xposed.

azthemansays said:
No, it's still ext4.
The strange thing is that other modules installed fine like xposed.
Click to expand...
Click to collapse
Maybe something makes fstab unreadable. Aside from formatting to f2fs I can't think of another.

Thread Closed

Thread Closed

Thread Closed

Thread Closed

Thread Closed

Update :
Initial ARM build up.

Update :
Build v0.2 is up.
Check #post1 for downloads and #post2 for changelogs.

Thank you for this great work.
Only two bug google assistant force close,YouTube vanced to.
https://del.dog/dojijuranu

durukanx said:
Thank you for this great work.
Only two bug google assistant force close,YouTube vanced to.
https://del.dog/dojijuranu
Click to expand...
Click to collapse
Remove or disable /system/priv-app/googlepartnersetup
Remove dalvik-cache arm,64 [email protected]@[email protected]@classes.dex -vdex
_____
@TheHitMan
Unpack System Lib64
Archive: /tmp/zip/sys_Lib64.zip
inflating: libbarhopper.so
inflating: libfacenet.so
inflating: libfilterpack_facedetect.so
inflating: libfrsdk.so
inflating: libjni_latinimegoogle.so
inflating: libsketchology_native.so----------> MarkupGoogle ( arm 64 )

.MoHaMaD said:
Remove or disable /system/priv-app/googlepartnersetup
Remove dalvik-cache arm,64 [email protected]@[email protected]@classes.dex -vdex
_____
@TheHitMan
Unpack System Lib64
Archive: /tmp/zip/sys_Lib64.zip
inflating: libbarhopper.so
inflating: libfacenet.so
inflating: libfilterpack_facedetect.so
inflating: libfrsdk.so
inflating: libjni_latinimegoogle.so
inflating: libsketchology_native.so----------> MarkupGoogle ( arm 64 )
Click to expand...
Click to collapse
Ok,thanks problem solved

Hi,
I'm not able to set up a trusted face (I would like to use face unlock).
When I touch "set up" the wizard quits.
Is that something correctable?
I'm on android pie, arm
Thanks,
Bye

Project Update:
Check OP post for latest update about this project.

Thread closed per OP request.

Thread re-opened at OP's request.

Android 10 Stable, Issue while mounting system.

Hello Guys
I upgraded to android 10 stable using ota
Then i flashed magisk_patched.img in fastboot mode to get root.
Magisk 20.1 is installed currently.
Everything is working fine with regards to root, like i can give root priviledge to Titanium backup and use it, Installed root checker to check root, root is working fine..
But i cannot flash modules in magisk manager. i am getting system mount error.
here is the log while flashing magisk module..
- Copying zip to temp directory
- Installing SystemMods_Magisk_BlackedOut[TEST].zip
- Current boot slot: _a
- Mounting system
mount: mounting /system on /system_root failed: No such file or directory
mount: mounting /system_root/system on /system failed: No such file or directory
- Device is system-as-root
Archive: /data/user/0/com.LuwFv4d84mjH.aMG/cache/flash/install.zip
inflating: install.sh
inflating: module.prop
inflating: post-fs-data.sh
inflating: service.sh
inflating: system.prop
******************************
System Mods
Made for OxygenOS
By SyCreed \ BaaDNwZ
******************************
Powered by Magisk (@topjohnwu)
******************************
Initialize safety checks... Be patient
Checking if the device is OnePlus...
update-binary: line 1: getprop: Too many symbolic links encountered
[ABORTED!] It's not a OnePlus device... Sorry.
! Installation failed
Click to expand...
Click to collapse
Is anyone aware of this issue.
Or any suggestion to fix this??

[SOLVED] Installing no-verity-opt-encrypt-6.1.zip failed > Logo Bootloop after installing TWRP on SM-G950F

Hi,
after I successfully customized my Samsung S II years ago (thanks to the XDA-community), I wanted to start with my S8, since to official support ended.
I could install TWRP. I think I followed the steps correctly as guided in:
https://forum.xda-developers.com/t/...1-x-twrp-for-galaxy-s8-and-s8-exynos.3847712/
twrp-3.5.2_9-0-dreamlte.img.tar is installed and it's possible to boot into it.
As described within the steps, I tried to install "no-verity-opt-encrypt-6.1.zip", which is failing.
At first I couldn't mount the data partition, so I formatted data partition as described.
The mouting of /preload failed, so I wiped it as described.
After that I got the following error:
######################################## dm-verity and forced encryption #
# disabler by jcadduono #
# version 6.1 #
#######################################
Unpacking the installer...Archive: /usb-otg/no-verity-opt-encrypt-6.1.zip
inflating: config.sh
creating: META-INF/
creating: META-INF/com/
creating: META-INF/com/google/
creating: META-INF/com/google/android/
inflating: META-INF/com/google/android/update-binary
creating: patch.d/
inflating: patch.d/02-no-dm-verity
inflating: patch.d/01-no-force-encrypt
creating: chromeos/
inflating: chromeos/kernel_data_key.vbprivk
inflating: chromeos/kernel.keyblock
inflating: patch.d-env
inflating: boot-patcher.sh
inflating: LICENSE
creating: tools/
creating: tools/x86_64/
inflating: tools/x86_64/futility
inflating: tools/x86_64/bootimg
inflating: tools/x86_64/bzip2
inflating: tools/x86_64/lz4
creating: tools/arm64/
inflating: tools/arm64/futility
inflating: tools/arm64/bootimg
inflating: tools/arm64/bzip2
inflating: tools/arm64/lz4
creating: tools/x86/
inflating: tools/x86/futility
inflating: tools/x86/bootimg
inflating: tools/x86/bzip2
inflating: tools/x86/lz4
creating: tools/arm/
inflating: tools/arm/futility
inflating: tools/arm/bootimg
inflating: tools/arm/bzip2
inflating: tools/arm/lz4
/tmp/updater[63]: .: config.sh: No such file or directory
Updater process ended with ERROR: 1
I:Install took 1 second(s).
Click to expand...
Click to collapse
Full recovery.log in the attachment.
Currently I'm stuck within a Samsung Logo Bootloop. What do I do wrong? Can I fix this?
I didn't found a similar problem within:
https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
Maybe someone can hint me in the right direction, please?
Thanks for any help.
Best regards
---
EDIT:
I successfully installed `RMM_Bypass_v3_corsicanu.zip` without an error, but `no-verity-opt-encrypt-6.1.zip` still doesn't work and the bootloop stays.
I tried to install the previous version `no-verity-opt-encrypt-6.0.zip` too. With no difference.
Download mode says:
CURRENT BINARY: Custom (0xc)
FRP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CARRIER_ID: DBT

Just a suggestion
The no-verity zip - if failing try using earlier versions of twrp ( can be flashed using twrp or odin )
or use this no-verity zip. You will have to add ' quota ' to the downloaded zip file name.
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com

Thank you @spawnlives for your help.
Downgrading TWRP wasn't working. So I tried to install `Disable_Dm-Verity_quota_ForceEncrypt_11.02.2020.zip` from https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ as suggested.
The S8 is booting again and Android has started successfully.

Database Users

welcome