Bootloader Unlocked TWRP Recovery and root for xperia m5 [E5633]

Bootloader Unlocked TWRP Recovery and root for xperia m5 [E5633] - Sony Xperia M5

بنام خداوند بخشنده و مهربان
Sony Xperia M5 Dual (e5633). Remember to hit the Thanks button before leaving
Your warranty will be void!!!!
You will lose all your Data due to Factory Reset!!!
I am not responsible for bricked devices, loss of data
Working on:
Sony Xperia M5 (Dual) E5633 Bootloader Unlocked 30.0.B.1.23
How To:
Unlock the Bootloader
Install a custom recovery
(TWRP)Unlocking the Bootloader:
Pre Warning this worked on my phone and I cannot say it will work on yours you may end up with a soft brick so think and research before you proceed.
(In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.)
So now goto http://developer.sonymobile.com/unlockbootloader/ and select device Xperia Z5 Dual then follow all thier instruction. (Credit for this belongs to another member I will add it when I find the post)
Go to fastboot mod(volume up+power button)
Then enter:
fastboot -i 0x0fce oem unlock 0xMYDEVICEUNLOCKCODE
When it says “finished” or “Done” hopefully with no errors just enter
fastboot reboot
Install a custom recovery M5 (TWRP)
Pre Info:
Practice Entering recovery and fastboot using the buttons and keys quick tut.
Phone power off and make sure to unplug usb lead.
Recovery:
Press and keep held the Volume Down key (-)
Now Press and hold Power Key until you see the Sony Boot Logo then release the Power Key only.
You can release the Volume Down Key when you see the Logo screen change or you are in recovery.
Bootloader:
As above but using the Volume UP key (+) instead.
Check the bootloader status:
Code:
fastboot getvar all
output should show “(bootloader) secure: No” in the last few lines.
If it says No enter:
fastboot flash fotakernel fotakernel.img
It should display a size and some seconds info with complete or success you should see NO warning or errors.
Power off phone and press volume down + power button to intro recovery mod.
for root:
first I'm sorry for the phones boot loop
do not flash any supersu.zip to your phone
To correct phones only flash system.sin with flashtool .
see this video for how to flash your device:
http://hw16.asset.aparat.com/aparat-...15q__15d6e.mp4
Do not chick Wipes
only system should be unchiched
and chick cust-reset and simlock to exclude them
and remember do not flash Incompatible zip file.
THIS IS IMPORTANT
The rom has:
Go to root/system find recovery.from.boot.p and Delete it.
DOWNLOAD:
http://s1.picofile.com/file/8263348800/fotakernel.rar.html
password: farshad9500gy

Brilliant work, confirmed recovery is accessible on E5653 on Marshmallow, but the SuperSU won't install due to an error:
- Extracting ramdisk --- Failure, aborting
Luckily system still works however.
{
"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"
}

This work in E5603? I see that my fotakernel partition sice is 40 mb and this img is 12 mb.
Enviado desde mi E5603 mediante Tapatalk

グリッチ said:
Brilliant work, confirmed recovery is accessible on E5653 on Marshmallow, however after flashing the SuperSU zip I got stuck at Sony logo, use at own risk. BACKUP FIRST (Unlike me... luckily this isn't my main phone at the moment, so I don't care if I lose data.)
I'm able to access the recovery, but can't flash FTF or do PC Companion repair because it formatted. Can't flash system.sin from FTF via fastboot because it gives me a size error too. TWRP tells me there's no OS installed, so I'm pretty much softbricked, until there's a rom I can flash.
Anyone got some suggestions?
Click to expand...
Click to collapse
Extract system.sin with flashtool then rename system.ext4 to system.img and flash it by this command:
fastboot flash syatem system.img

Ninoh-FOX said:
This work in E5603? I see that my fotakernel partition sice is 40 mb and this img is 12 mb.
Enviado desde mi E5603 mediante Tapatalk
Click to expand...
Click to collapse
your fotakernel is image of fotakernel partition and after compression reaches its size to 12mb or 13mb.

Ok, thank for the reply.
Could I install this from terminal with the command "dd if= of= "? I not remenber if this partition is important for boot the os phone (I have a copy from ta.img, but I not unlocking bootloader for now) but I can reflash this original partition with flashtool in flashmode (I think).
Enviado desde mi E5603 mediante Tapatalk

-delete-

Well, finally this recovery not work in 5603... I injected the partition with dd command, but the phone shutdown when I try enter in recovery, I restored the original partition and work fine...
Enviado desde mi E5603 mediante Tapatalk

For Marshmallow, should we use systemless root or standard root? Especially in the case of dm-verity and unmodifiable system partition.

グリッチ said:
Here are my results:
fastboot flash system system.img
target reported max download size of 134217728 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.082s]
sending sparse 'system' 1/20 (130422 KB)...
OKAY [ 5.884s]
writing 'system' 1/20...
FAILED (remote: Unknown chunk type)
finished. total time: 6.100s
And with another command.
fastboot -S 256M flash system system.img
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.061s]
sending sparse 'system' 1/10 (258690 KB)...
FAILED (remote: data is too large)
finished. total time: 0.411s
I have tried from the fastboot in your release, and from minimal fastboot & adb.
I've tried system.sin, system.ext4 (renamed to system.img) from Marshmallow, AND tried from a Lollipop release as well. Same issue.
Click to expand...
Click to collapse
you can flash system.sin (only system.sin) with flashtool and remember use latest version and sync device.

Ninoh-FOX said:
Well, finally this recovery not work in 5603... I injected the partition with dd command, but the phone shutdown when I try enter in recovery, I restored the original partition and work fine...
Enviado desde mi E5603 mediante Tapatalk
Click to expand...
Click to collapse
dd command is a way to flash a image of the partition this fotakernel(recovery) is not a image of partition!
only way to flash this recovery is unlock the bootloader and use fastboot.
before unlock the bootloader take backup of this partition with dd command:
ta(drm keys and bootloader)
nvram(imei)
boot
fotakernel
you can restore drm keys and locked bootloader by restore ta partition with this tool:
https://github.com/DevShaft/Backup-TA/releases
remember:
when you want to restore ta partition first copy ta.img to internal storage.
DO NOT EVER flash the NVRAM or TA partition of another device, even if it's from exactly the same model. You'll hard brick your device by doing that.

farshad9500gy said:
you can flash system.sin (only system.sin) with flashtool and remember use latest version and sync device.
you con try with this to root android 6.0 (flash zip with recovery):
http://www.supersuroot.com/download/SuperSU-root-BETA-v2.67.zip
this video will help you:https://as4.asset.aparat.com/aparat...nrnp0sr856q5ppsqo3292n2105333-148c__d85fa.mp4
Click to expand...
Click to collapse
Thank you, but in addition, would method help in regaining functionality in DRM dependent services/features in scenarios that the TA partition was not backed up? Especially for Android 6.0 stock.
http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672

-delete-

I want to install S1Boot Fastboot driver but Device Manager doesn't show my Xperia M5 :/

If someone made a copy of fotakernel (recovery) as partition ...
Could I then rewrite the partition with dd command?
In case if it worked.
Could someone upload the copy of partition?
I'd be really grateful.
Enviado desde mi E5603 mediante Tapatalk

farshad9500gy said:
you can flash system.sin (only system.sin) with flashtool and remember use latest version and sync device.
you con try with this to root android 6.0 (flash zip with recovery):
http://www.supersuroot.com/download/SuperSU-root-BETA-v2.67.zip
this video will help you:https://as4.asset.aparat.com/aparat-video/a_6pr5f724i1sko90nrnp0sr856q5ppsqo3292n2105333-148c__d85fa.mp4
Click to expand...
Click to collapse
Also, I tried the rooting method stated, no success. Attached is the recovery log for the failed attempt to get systemless root. Please advice.
Code:
*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: mounting /dev/block/mmcblk0p23 on /data failed: Device or resource busy
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.005125 seconds, 390B/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.002917 seconds, 1.0KB/s
10+0 records in
10+0 records out
10 bytes (10B) copied, 0.002893 seconds, 3.4KB/s
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.004442 seconds, 0B/s
/tmp/updater: line 765: /system/toolbox: not found
- Extracting files
Archive: /sdcard/SuperSU-root-BETA-v2.67.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/000000deepsleep
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
supolicy v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Patching policy ...
-permissive:adbd_socket=ok
-permissive:functionfs=ok
-permissive:hci_attach_exec=ok
-permissive:system_server=ok
-permissive:nfc=ok
-permissive:rild_debug_socket=ok
-permissive:file_type=ok
-permissive:exec_type=ok
-permissive:property_type=ok
-permissive:surfaceflinger_service=ok
-permissive:binderservicedomain=ok
-permissive:mdns_socket=ok
-permissive:node_type=ok
-permissive:platform_app=ok
-permissive:ram_device=ok
-permissive:port_type=ok
-permissive:rootfs=ok
-permissive:tmpfs=ok
-permissive:usbfs=ok
-permissive:bootanim_exec=ok
-permissive:gpsd_tmpfs=ok
-permissive:installd_exec=ok
-permissive:su_tmpfs=ok
-permissive:untrusted_app_tmpfs=ok
-permissive:cpuctl_device=ok
-permissive:cgroup=ok
-permissive:drmserver_socket=ok
-permissive:ppp_device=ok
-permissive:wpa_socket=ok
-permissive:proc_net=ok
-permissive:vdc=ok
-permissive:clatd=ok
-permissive:netd=ok
-permissive:sdcardd=ok
-permissive:zygote=ok
-permissive:debuggerd=ok
-permissive:input_device=ok
-permissive:mediaserver_tmpfs=ok
-permissive:sysfs_ksm=ok
-permissive:ueventd_tmpfs=ok
-permissive:download_file=ok
-permissive:mtp=ok
-permissive:backup_data_file=ok
-permissive:servicemanager_tmpfs=ok
-permissive:su_exec=ok
-permissive:ppp_exec=ok
-permissive:tee_exec=ok
-permissive:vdc_exec=ok
-permissive:wpa_exec=ok
-permissive:dumpstate_tmpfs=ok
-permissive:mqueue=ok
-permissive:mtp_exec=ok
-permissive:system_ndebug_socket=ok
-permissive:tee=ok
-permissive:adb_data_file=ok
-permissive:anr_data_file=ok
-permissive:app_data_file=ok
-permissive:dhcp_data_file=ok
-permissive:logdr_socket=ok
-permissive:logdw_socket=ok
-permissive:net_data_file=ok
-permissive:shell_data_file=ok
-permissive:vpn_data_file=ok
-permissive:adb_keys_file=ok
-permissive:dalvikcache_data_file=ok
-permissive:keystore_tmpfs=ok
-permissive:kernel=ok
-permissive:dhcp_tmpfs=ok
-permissive:platform_app_data_file=ok
-permissive:dhcp=ok
-permissive:mediaserver_service=ok
-permissive:dnsmasq=ok
-permissive:drmserver=ok
-permissive:drmserver_tmpfs=ok
-permissive:keystore=ok
-permissive:property_data_file=ok
-permissive:vold_exec=ok
-permissive:adbd=ok
-permissive:dumpstate=ok
-permissive:racoon_exec=ok
-permissive:rild_exec=ok
-permissive:unlabeled=ok
-permissive:bluetooth=ok
-permissive:uncrypt_tmpfs=ok
-permissive:inputflinger=ok
-permissive:dhcp_exec=ok
-permissive:vcs_device=ok
-permissive:gpsd_exec=ok
-permissive:port=ok
-permissive:fuse=ok
-permissive:install_data_file=ok
-permissive:lmkd_exec=ok
-permissive:logd_exec=ok
-permissive:netd_exec=ok
-permissive:asec_image_file=ok
-permissive:recovery=ok
-permissive:radio_tmpfs=ok
-permissive:tee_tmpfs=ok
-permissive:wpa=ok
-permissive:dev_type=ok
-permissive:runas=ok
-permissive:vdc_tmpfs=ok
-permissive:wpa_tmpfs=ok
-permissive:hostapd=ok
-permissive:system_prop=ok
-permissive:vfat=ok
-permissive:fs_type=ok
-permissive:sdcard_external=ok
-permissive:sdcard_internal=ok
-permissive:sdcardd_exec=ok
-permissive:owntty_device=ok
-permissive:selinuxfs=ok
-permissive:tty_device=ok
-permissive:tun_device=ok
-permissive:clatd_exec=ok
-permissive:installd_tmpfs=ok
-permissive:uio_device=ok
-permissive:bootanim_tmpfs=ok
-permissive:install_recovery_tmpfs=ok
-permissive:sysinit_exec=ok
-permissive:system_app_service=ok
-permissive:full_device=ok
-permissive:null_device=ok
-permissive:fuse_device=ok
-permissive:usb_device=ok
-permissive:wfd_app=ok
-permissive:camera_device=ok
-permissive:hostapd_exec=ok
-permissive:keystore_exec=ok
-permissive:uncrypt=ok
-permissive:system_app_data_file=ok
-permissive:tee_device=ok
-permissive:uncrypt_exec=ok
-permissive:video_device=ok
-permissive:labeledfs=ok
-permissive:mtp_tmpfs=ok
-permissive:audio_device=ok
-permissive:radio_device=ok
-permissive:nfc_tmpfs=ok
-permissive:userinit_exec=ok
-permissive:ptmx_device=ok
-permissive:mdnsd_exec=ok
-permissive:system_app_tmpfs=ok
-permissive:bluetooth_data_file=ok
-permissive:usbaccessory_device=ok
-permissive:userinit_data_exec=ok
-permissive:lvm_placeholder=ok
-permissive:rmt_placeholder=ok
-permissive:nfc_prop=ok
-permissive:dex2oat_exec=ok
-permissive:socket_device=ok
-permissive:bluetooth_tmpfs=ok
-permissive:sysfs_lowmemorykiller=ok
-permissive:installd_socket=ok
-permissive:netd_tmpfs=ok
-permissive:servicemanager_exec=ok
-permissive:proc=ok
-permissive:asec_public_file=ok
-permissive:proc_cpuinfo=ok
-permissive:usermodehelper=ok
-permissive:bluetooth_socket=ok
-permissive:installd=ok
-permissive:debug_prop=ok
-permissive:inputflinger_exec=ok
-permissive:pan_result_prop=ok
-permissive:security_prop=ok
-permissive:zygote_socket=ok
-permissive:system_server_tmpfs=ok
-permissive:bluetooth_prop=ok
-permissive:ctl_rildaemon_prop=ok
-permissive:system_radio_prop=ok
-permissive:contextmount_type=ok
-permissive:lmkd_tmpfs=ok
-permissive:logd_tmpfs=ok
-permissive:uhid_device=ok
-permissive:ctl_dhcp_pan_prop=ok
-permissive:racoon_socket=ok
-permissive:ctl_bootanim_prop=ok
-permissive:wallpaper_file=ok
-permissive:install_recovery=ok
-permissive:net_radio_prop=ok
-permissive:asec_apk_file=ok
-permissive:console_device=ok
-permissive:userinit_prop=ok
-permissive:sensors_device=ok
-permissive:dhcp_prop=ok
-permissive:audio_prop=ok
-permissive:qtaguid_proc=ok
-permissive:ctl_bugreport_prop=ok
-permissive:healthd=ok
-permissive:init=ok
-permissive:sysinit=ok
-permissive:keychain_data_file=ok
-permissive:kmem_device=ok
-permissive:netif_type=ok
-permissive:gps_control=ok
-permissive:logd_prop=ok
-permissive:init_tmpfs=ok
-permissive:surfaceflinger_exec=ok
-permissive:kmsg_device=ok
-permissive:vold_prop=ok
-permissive:data_file_type=ok
-permissive:netif=ok
-permissive:bootanim=ok
-permissive:klog_device=ok
-permissive:zoneinfo_data_file=ok
-permissive:radio=ok
-permissive:inputflinger_service=ok
-permissive:mlstrustedobject=ok
-permissive:debuggerd_tmpfs=ok
-permissive:unconfineddomain=ok
-permissive:fscklogs=ok
-permissive:netd_socket=ok
-permissive:zygote_tmpfs=ok
-permissive:mlstrustedsubject=ok
-permissive:mediaserver=ok
-permissive:mediaserver_exec=ok
-permissive:ctl_fuse_prop=ok
-permissive:drmserver_service=ok
-permissive:mtpd_socket=ok
-permissive:debugfs=ok
-permissive:keystore_service=ok
-permissive:oemfs=ok
-permissive:pipefs=ok
-permissive:sockfs=ok
-permissive:sysfs=ok
-permissive:logd=ok
-permissive:pstorefs=ok
-permissive:default_android_service=ok
-permissive:drmserver_exec=ok
-permissive:inotify=ok
-permissive:vold_tmpfs=ok
-permissive:bluetooth_service=ok
-permissive:sysfs_devices_system_cpu=ok
-permissive:debuggerd_exec=ok
-permissive:untrusted_app=ok
-permissive:gps_socket=ok
-permissive:ueventd=ok
-permissive:node=ok
-permissive:proc_sysrq=ok
-permissive:adb_device=ok
-permissive:shared_relro=ok
-permissive:sysfs_type=ok
-permissive:system_data_file=ok
-permissive:alarm_device=ok
-permissive:camera_data_file=ok
-permissive:sysfs_bluetooth_writable=ok
-permissive:ctl_mdnsd_prop=ok
-permissive:hci_attach_tmpfs=ok
-permissive:devpts=ok
-permissive:sysfs_zram=ok
-permissive:audio_firmware_file=ok
-permissive:proc_bluetooth_writable=ok
-permissive:apk_data_file=ok
-permissive:audio_data_file=ok
-permissive:bluetooth_efs_file=ok
-permissive:dm_device=ok
-permissive:drm_data_file=ok
-permissive:gps_data_file=ok
-permissive:media_data_file=ok
-permissive:nfc_data_file=ok
-permissive:radio_data_file=ok
-permissive:tee_data_file=ok
-permissive:wifi_data_file=ok
-permissive:mdnsd_tmpfs=ok
-permissive:system_app=ok
-permissive:dumpstate_socket=ok
-permissive:sdcard_type=ok
-permissive:system_file=ok
-permissive:apk_private_tmp_file=ok
-permissive:hci_attach_dev=ok
-permissive:su=ok
-permissive:racoon_tmpfs=ok
-permissive:apk_tmp_file=ok
-permissive:proc_security=ok
-permissive:system_server_service=ok
-permissive:gps_device=ok
-permissive:gpu_device=ok
-permissive:nfc_service=ok
-permissive:gpsd=ok
-permissive:init_shell=ok
-permissive:mdnsd=ok
-permissive:device=ok
-permissive:system_wpa_socket=ok
-permissive:surfaceflinger=ok
-permissive:sysfs_nfc_power_writable=ok
-permissive:rild_tmpfs=ok
-permissive:isolated_app_tmpfs=ok
-permissive:runas_exec=ok
-permissive:untrusted_app_devpts=ok
-permissive:dex2oat=ok
-permissive:watchdogd=ok
-permissive:bluetoothdomain=ok
-permissive:dnsmasq_exec=ok
-permissive:fwmarkd_socket=ok
-permissive:qtaguid_device=ok
-permissive:inputflinger_tmpfs=ok
-permissive:shell_exec=ok
-permissive:ppp=ok
-permissive:dumpstate_exec=ok
-permissive:zero_device=ok
-permissive:resourcecache_data_file=ok
-permissive:systemkeys_data_file=ok
-permissive:shared_relro_tmpfs=ok
-permissive:binder_device=ok
-permissive:property_socket=ok
-permissive:sdcardd_tmpfs=ok
-permissive:hw_random_device=ok
-permissive:random_device=ok
-permissive:urandom_device=ok
-permissive:watchdog_device=ok
-permissive:ctl_default_prop=ok
-permissive:ctl_dumpstate_prop=ok
-permissive:security_file=ok
-permissive:media_rw_data_file=ok
-permissive:wfd_app_tmpfs=ok
-permissive:default_prop=ok
-permissive:debuggerd_prop=ok
-permissive:shared_relro_file=ok
-permissive:install_recovery_exec=ok
-permissive:coredump_file=ok
-permissive:netdomain=ok
-permissive:appdomain=ok
-permissive:lmkd_socket=ok
-permissive:logd_debug=ok
-permissive:racoon=ok
-permissive:graphics_device=ok
-permissive:serial_device=ok
-permissive:efs_file=ok
-permissive:powerctl_prop=ok
-permissive:rild=ok
-permissive:vold=ok
-permissive:adbtcp_prop=ok
-permissive:iio_device=ok
-permissive:ion_device=ok
-permissive:shell=ok
-permissive:tombstone_data_file=ok
-permissive:radio_service=ok
-permissive:apk_private_data_file=ok
-permissive:mdnsd_socket=ok
-permissive:service_manager_type=ok
-permissive:healthd_service=ok
-permissive:root_block_device=ok
-permissive:cache_backup_file=ok
-permissive:logd_socket=ok
-permissive:hci_attach=ok
-permissive:dalvikcache_profiles_data_file=ok
-permissive:sdcard_posix=ok
-permissive:vold_socket=ok
-permissive:block_device=ok
-permissive:zygote_exec=ok
-permissive:frp_block_device=ok
-permissive:radio_prop=ok
-permissive:loop_device=ok
-permissive:sysfs_writable=ok
-permissive:properties_device=ok
-permissive:misc_user_data_file=ok
-permissive:surfaceflinger_tmpfs=ok
-permissive:sysfs_ioscheduler=ok
-permissive:lmkd=ok
-permissive:nfc_device=ok
-permissive:servicemanager=ok
-permissive:sysfs_wake_lock=ok
-permissive:dnsproxyd_socket=ok
-permissive:rild_socket=ok
-permissive:shell_prop=ok
-permissive:keystore_data_file=ok
-permissive:ashmem_device=ok
-permissive:isolated_app=ok
-permissive:sysinit_tmpfs=ok
-permissive:shm=ok
-permissive:platform_app_tmpfs=ok
-permissive:rpmsg_device=ok
-permissive:shell_tmpfs=ok
-permissive:cache_file=ok
-permissive:fingerprint_prop=ok
-permissive:mtp_device=ok
-permissive:mtd_device=ok
-permissive:log_device=ok
-permissive:domain=ok
- Success
- Detecting system compatibility
sukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/dev/block/mmcblk0p10] ...
Could not find header
- System-less mode, boot image support required
- Creating image
/data/su.img: clean, 23/2048 files, 1318/8192 blocks
- Mounting image
mknod: /dev/block/loop0: File exists
CANNOT LINK EXECUTABLE: cannot locate symbol "error" referenced by "/system/bin/toolbox"...
page record for 0x7fb1b34010 was not found (block_size=64)
- Creating paths
mkdir: can't create directory '/su/bin': File exists
mkdir: can't create directory '/su/xbin': File exists
mkdir: can't create directory '/su/lib': File exists
mkdir: can't create directory '/su/etc': File exists
mkdir: can't create directory '/su/su.d': File exists
- Removing old files
- Placing files
rm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
rm: can't remove '/su/bin/sukernel': No such file or directory
mkdir: can't create directory '/su/xbin_bind': File exists
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/mmcblk0p10
- Extracting ramdisk
sukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/dev/block/mmcblk0p10] ...
Could not find header
--- Failure, aborting
*************************
IMPORTANT NOTICES
*************************
If TWRP offers to install
SuperSU, do *NOT* let it!
*************************
First reboot may take a
few minutes. It can also
loop a few times. Do not
interrupt the process!
*************************
- Unmounting /system
- Done !
I:Legacy property environment disabled.
Updating partition details...
I:Data backup size is 3156MB, free: 7933MB.
I:Unable to mount '/usbotg'
I:Actual block device: '', current file system: 'auto'
...done
I:Set page: 'flash_done'
I:operation_end - status=0
I:Set page: 'clear_vars'

Ninoh-FOX said:
If someone made a copy of fotakernel (recovery) as partition ...
Could I then rewrite the partition with dd command?
In case if it worked.
Could someone upload the copy of partition?
I'd be really grateful.
Enviado desde mi E5603 mediante Tapatalk
Click to expand...
Click to collapse
Do you need a specific version of the partition?
I currently have my M5 5606 with android 5.1
If it works for you just give me the steps to do it and Ill get you my backup

crisaegrim said:
Do you need a specific version of the partition?
I currently have my M5 5606 with android 5.1
If it works for you just give me the steps to do it and Ill get you my backup
Click to expand...
Click to collapse
This is the partition:
Well, the steps firts is the this post.
My computer, after 9 years of sevice, is dead (death programmer for the factory?), I can't unlock bootloader, then I only can install recovery for terminal emulator.
Then I need (and other users with bootloader locked):
1. A user with unlock bootloader, Install recovery via fastboot.
2. Reboot the phone and start terminal emulator (busybox installed previus)
3. Type the next commads:
- su
- dd if=/dev/block/mmcblk0p9 of=/sdcard/recovery.img
This is for make a copy the recovery partition. Only users with unlock bootloader.
If this work, then the users with bootloader lock could install the updated copy from recovery partition with the next command:
- su
- dd if=/dev/block/mmcblk0p9 of=/sdcard/fotakernelbackup.img
- dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p9.
This could work, I don't know.
Pd: sorry my english.
Enviado desde mi E5603 mediante Tapatalk

Luckily have Flash tool for Xperia devices.
developer.sonymobile.com/open-devices/flash-tool/how-to-download-and-install-the-flash-tool

Can somebody upload the flashed recovery partition please?
Enviado desde mi E5603 mediante Tapatalk

Related

OTA modifier

What is this:
- This is a script which can be used from a Linux PC (should work on Mac too) in order to modify the OTA updates.
- It is suitable for all 6039 and 6045 devices.
- The owners of 6039 which returned the fastboot commands to their devices by using the guide in this section need to use the script in order to modify and install future OTA updates.
- The script removes the checks and the patches for the recovery. In addition for the 6039 users removes the check and the patches which remove the fatsboot commands.
How to use it:
- There are dependencies (i.e. packages which are needed) in order the script to function properly. In order to be widely supported the script has been written as bash script and needs only zip and unzip binaries in order to modify the upgrade file. All other commands used in it should be available as core packages on any Linux system.
- The script must have executable permissions and the update file to be provided as argument e.g.
Code:
ota_modifier.sh /home/Downloads/update.zip
there a few questions which can be asked by the script, which must be answered with y/n. At the end, in the directory from where the script has been executed, you will have a modified flashable ZIP which can be installed through TWRP in order to upgrade the device.
md5sum: ca536d39ec63845eb55803e1e8b57e3d ota_modifier.zip
P.S. If someone can modify the script to work under Windows is welcome to do it.

petrov.0 said:
What is this:
- This is a script which can be used from a Linux PC (should work on Mac too) in order to modify the OTA updates.
- It is suitable for all 6039 and 6045 devices.
- The owners of 6039 which returned the fastboot commands to their devices by using the guide in this section need to use the script in order to modify and install future OTA updates.
- The script removes the checks and the patches for the recovery. In addition for the 6039 users removes the check and the patches which remove the fatsboot commands.
How to use it:
- There are dependencies (i.e. packages which are needed) in order the script to function properly. In order to be widely supported the script has been written as bash script and needs only zip and unzip binaries in order to modify the upgrade file. All other commands used in it should be available as core packages on any Linux system.
- The script must have executable permissions and the update file to be provided as argument e.g.
Code:
ota_modifier.sh /home/Downloads/update.zip
there a few questions which can be asked by the script, which must be answered with y/n. At the end, in the directory from where the script has been executed, you will have a modified flashable ZIP which can be installed through TWRP in order to upgrade the device.
md5sum: f401a1a5baafa20110cf47606b45d99a ota_modifier.zip
P.S. If someone can modify the script to work under Windows is welcome to do it.
Click to expand...
Click to collapse
Not a zip file?
[email protected]:/workarea/android/idol3/updates > ls
update_20150928.zip
[email protected]:/workarea/android/idol3/updates > ota_modifier.sh update_20150928.zip
The provided file is not a zip file!
[email protected]:/workarea/android/idol3/updates > unzip update_20150928.zip
Archive: update_20150928.zip
signed by SignApk
inflating: META-INF/com/android/metadata
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: firmware/VERINFO/NON.VER
inflating: patch/boot.img.p
inflating: patch/emmc_appsboot.mbn.p
inflating: patch/firmware/IMAGE/CMNLIB.B01.p
inflating: patch/firmware/IMAGE/CMNLIB.MDT.p
inflating: patch/firmware/IMAGE/DXHDCP2.B01.p
inflating: patch/firmware/IMAGE/DXHDCP2.MDT.p
inflating: patch/firmware/IMAGE/ISDBTMM.B01.p
inflating: patch/firmware/IMAGE/ISDBTMM.MDT.p
inflating: patch/firmware/IMAGE/KEYMASTE.B01.p
inflating: patch/firmware/IMAGE/KEYMASTE.MDT.p
inflating: patch/firmware/IMAGE/MBA.MBN.p
inflating: patch/firmware/IMAGE/MODEM.B00.p
*update* You need to strip the filename to make it case insensitive. You may have files that don't end in .zip at all if they use the name the update saves as which was a number like 67039
[email protected]:/workarea/android/idol3/updates > ota_modifier.sh update_20150928.Zip
The file update_20150928.Zip is OK!
Creating a copy of the file...
Working hard...
*** Would you like to remove the checks and the ***
*** patches which remove the fastboot commands ? ***
*** Note that if your device is 6045 probably is not ***
*** affected by this, therefore is recommended to ***
*** choose 'n' from the prompt below. ***
*** If the update is for 6039 choose 'y' ***
Clean them all [y/n]: n
Creating the modified update file
/workarea/android/idol3/updates/update_20150928_modified.zip has been created.
Cleaning of the mess !
DONE!!!
[email protected]:/workarea/android/idol3/updates > ls -l
total 57420
-rw-r--r-- 1 famewolf famewolf 58793801 Sep 14 01:30 update_20150928.Zip <--- Where is the file it says it just created? Only the original is present.

famewolf said:
Not a zip file?
[email protected]:/workarea/android/idol3/updates > ls
update_20150928.zip
[email protected]:/workarea/android/idol3/updates > ota_modifier.sh update_20150928.zip
The provided file is not a zip file!
[email protected]:/workarea/android/idol3/updates > unzip update_20150928.zip
Archive: update_20150928.zip
signed by SignApk
inflating: META-INF/com/android/metadata
....
*update* You need to strip the filename to make it case insensitive. You may have files that don't end in .zip at all if they use the name the update saves as which was a number like 67039
Click to expand...
Click to collapse
Hm, interesting. Actually the check is based on the 'magic' of the file. Can you run:
Code:
file update_20150928.zip
and to provide the output.
Edit: Probably I should remove this check and to unzip the file blindly. And then on unsuccessful unzip to exit with error. Probably this is a better approach.

petrov.0 said:
Hm, interesting. Actually the check is based on the 'magic' of the file. Can you run:
Code:
file update_20150928.zip
and to provide the output.
Click to expand...
Click to collapse
[email protected]:/workarea/android/idol3/updates > file update_20150928.zip
update_20150928.zip: ERROR: cannot open `update_20150928.zip' (No such file or directory)
/workarea is a NAS share mounted via NFS if that matters. It may also explain why the output file disappeared. I'll try running it on a "local" directory.
---------- Post added at 05:34 PM ---------- Previous post was at 05:31 PM ----------
I think your path is off somewhere. Also if you upzip "blindly" you can still check the return code to ensure it was 0.
[email protected]:/tmp > ota_modifier.sh update_20150928.Zip
The file update_20150928.Zip is OK!
Creating a copy of the file...
Working hard...
*** Would you like to remove the checks and the ***
*** patches which remove the fastboot commands ? ***
*** Note that if your device is 6045 probably is not ***
*** affected by this, therefore is recommended to ***
*** choose 'n' from the prompt below. ***
*** If the update is for 6039 choose 'y' ***
Clean them all [y/n]: n
Creating the modified update file
zip I/O error: Permission denied
zip error: Could not create output file (../update_20150928_modified.zip)
/tmp/update_20150928_modified.zip has been created.
Cleaning of the mess !
DONE!!!
[email protected]:/tmp > ls up*
update_20150928.Zip

famewolf said:
[email protected]:/workarea/android/idol3/updates > file update_20150928.zip
update_20150928.zip: ERROR: cannot open `update_20150928.zip' (No such file or directory)
/workarea is a NAS share mounted via NFS if that matters. It may also explain why the output file disappeared. I'll try running it on a "local" directory.
---------- Post added at 05:34 PM ---------- Previous post was at 05:31 PM ----------
I think your path is off somewhere.
[email protected]:/tmp > ota_modifier.sh update_20150928.Zip
The file update_20150928.Zip is OK!
Creating a copy of the file...
Working hard...
*** Would you like to remove the checks and the ***
*** patches which remove the fastboot commands ? ***
*** Note that if your device is 6045 probably is not ***
*** affected by this, therefore is recommended to ***
*** choose 'n' from the prompt below. ***
*** If the update is for 6039 choose 'y' ***
Clean them all [y/n]: n
Creating the modified update file
zip I/O error: Permission denied
zip error: Could not create output file (../update_20150928_modified.zip)
/tmp/update_20150928_modified.zip has been created.
Cleaning of the mess !
DONE!!!
[email protected]:/tmp > ls up*
update_20150928.Zip
Click to expand...
Click to collapse
Yes, on the local machine will be better (also try the script from there) ... It works without problems on Debian and openSUSE
... No write access to / tmp ... Come on, who does not have access to there. <- This was an error in the script.

OK there was an error indeed in the directory switch (it was behind the fi) when you select n on the prompt. Download the script again. It is already updated.
Edit: @famewolf thanks for the fast response in order to be corrected.

petrov.0 said:
OK there was an error indeed in the directory switch (it was behind the fi) when you select n on the prompt. Download the script again. It is already updated.
Edit: @famewolf thanks for the fast response in order to be corrected.
Click to expand...
Click to collapse
Are you checking the "n" branch because I'm still unable to generate an output file trying both /tmp and /workarea/idol3/updates I've posted my update file at the bottom.
Example:
[email protected]:/tmp > /workarea/android/idol3/ota_modifier.sh update_20150928.Zip
The file update_20150928.Zip is OK!
Creating a copy of the file...
Working hard...
*** Would you like to remove the checks and the ***
*** patches which remove the fastboot commands ? ***
*** Note that if your device is 6045 probably is not ***
*** affected by this, therefore is recommended to ***
*** choose 'n' from the prompt below. ***
*** If the update is for 6039 choose 'y' ***
Clean them all [y/n]: n
Creating the modified update file
zip I/O error: Permission denied
zip error: Could not create output file (../update_20150928_modified.zip)
/tmp/update_20150928_modified.zip has been created.
Cleaning of the mess !
DONE!!!
[email protected]:/tmp > ls up*
update_20150928.Zip
[email protected]:/tmp >
This is on Linux Mint 17.2 KDE which is based on Ubuntu 14.04.
Choosing Y at the check DOES produce an output file.
[email protected]:/tmp > /workarea/android/idol3/ota_modifier.sh update_20150928.Zip
The file update_20150928.Zip is OK!
Creating a copy of the file...
Working hard...
*** Would you like to remove the checks and the ***
*** patches which remove the fastboot commands ? ***
*** Note that if your device is 6045 probably is not ***
*** affected by this, therefore is recommended to ***
*** choose 'n' from the prompt below. ***
*** If the update is for 6039 choose 'y' ***
Clean them all [y/n]: y
Cleaning the patches which affect the fastboot commands...
Creating the modified update file
/tmp/update_20150928_modified.zip has been created.
Cleaning of the mess !
DONE!!!
[email protected]:/tmp > ls up*
update_20150928_modified.zip update_20150928.Zip
[email protected]:/tmp >
Try the file yourself:
*Removed to prevent people from trying to install it on the wrong devices*

famewolf said:
Are you checking the "n" branch because I'm still unable to generate an output file trying both /tmp and /workarea/idol3/updates I've posted my update file at the bottom.
....
Click to expand...
Click to collapse
Damn. Sorry somehow I messed files ... this not been updated ... This section from the script must look like this:
Code:
if [ -d patch ]; then
if [[ "$ans" == "y" ]] || [[ "$ans" == "Y" ]]; then
pushd patch &>/dev/null
for i in emmc_appsboot.mbn.p hyp.img.p rpm.img.p sbl1.img.p tz.img.p
do
rm "$i"
done
popd &>/dev/null
fi
I will upload the correct file after a minute.

@famewolf now is OK ... checked (twice) .

petrov.0 said:
@famewolf now is OK ... checked (twice) .
Click to expand...
Click to collapse
Success!
-rw-r--r-- 1 famewolf famewolf 58623940 Oct 1 19:48 update_20150928_modified.zip
-rw-r--r-- 1 famewolf famewolf 58793801 Sep 14 01:30 update_20150928.Zip
Will have to restore factory image of UE40 then try to apply the update (I have a modified build.prop and other files that will prevent an update).
Windows users can put the update and the script on a jump drive and boot into a linux live iso to run it...the live iso can be booted in virtualbox as well which is a free virtual pc package.
*update* Just a quick followup to say the modified update applied just fine via twrp and worked as expected.

I see almost everyone is using Ubuntu. Would Debian be ok (I don't see why it shouldn't)? I am dual booting W7/Debian 8.2 and would hate to change to Ubuntu.
Thanks
Sent from my 6045Y using XDA Free mobile app

famewolf said:
Success!
-rw-r--r-- 1 famewolf famewolf 58623940 Oct 1 19:48 update_20150928_modified.zip
-rw-r--r-- 1 famewolf famewolf 58793801 Sep 14 01:30 update_20150928.Zip
Will have to restore factory image of UE40 then try to apply the update (I have a modified build.prop and other files that will prevent an update).
Windows users can put the update and the script on a jump drive and boot into a linux live iso to run it...the live iso can be booted in virtualbox as well which is a free virtual pc package.
*update* Just a quick followup to say the modified update applied just fine via twrp and worked as expected.
Click to expand...
Click to collapse
Anghirrim said:
I see almost everyone is using Ubuntu. Would Debian be ok (I don't see why it shouldn't)? I am dual booting W7/Debian 8.2 and would hate to change to Ubuntu.
Thanks
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
Where you see this ? Of course it will work.

Anghirrim said:
I see almost everyone is using Ubuntu. Would Debian be ok (I don't see why it shouldn't)? I am dual booting W7/Debian 8.2 and would hate to change to Ubuntu.
Thanks
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
I used OpenSuse KDE for around 10 years. I only switched to Linux Mint in the last couple of years due to issues getting certain hardware to work under opensuse that just worked out of the box with linux mint. (gscan2pdf..a minolta 1250W printer) I also was frustrated that certain software packages were only available from users instead of being in the main opensuse repo and some of those were broken in various ways. Debian should work just fine...actually just about any linux should work just fine but you could always use a live iso in virtualbox or boot off a live iso directly.

No need for a live one don't worry. I was more guessing about dependencies name issue or conflicts.
I used to be an Archlinux user for several years and know how complicated it can be when you mix 32 and 64 bits libraries.
I'm using my computer less and less so moved to Debian for a slower update pace.
Regarding Ubuntu, in the compilation topics, most of the people talk about Ubuntu so I was guessing there was something specific.
Thanks guys.
Sent from my 6045Y using XDA Free mobile app

Web based OTA modifier
This is strictly just "pie in the sky" thinking.....what would be ideal would be to have a webpage where you can upload your update and it processes it then provides you the modified file. I've seen this done with similar things...I know there are places online that would provide a linux shell to run the script..not sure how the web page would integrate but that would allow people to request the update from a phone.
Anyway the safest update method is to go to TWRP and 1) Backup your system, data, boot of existing system in case of problems. 2)Restore a factory image of the version you are on so everything is as the update will expect. 3) Apply the modified update. 4) Make another backup..this time of system image and boot..this will become your new "factory image" for the next update. You can then apply zip's like the supersu.zip and any special ones you've created with the zipme app. Finally reboot.

Really nice. Please port to windows.

Bostrot said:
Really nice. Please port to windows.
Click to expand...
Click to collapse
You'd have better luck in googling how to run bash scripts under windows (or using my live iso + jumpdrive suggestion). petrov.0 doesn't use windows.

do you think it's possible to crossflash my 6045y with the 6045i latest update with this modification since the partitions are the same?

keyra74 said:
do you think it's possible to crossflash my 6045y with the 6045i latest update with this modification since the partitions are the same?
Click to expand...
Click to collapse
As stated many times before, NO! The most recent update will only install on UE40 firmware and it upgrades it to UER0. It checks for it and even if it didn't the source code for the 6045Y and the 6045i are different...even if you removed the check when it tried to patch your radio it would probably kill both cell and wifi and create a mess you probably could not get back from unless you've used @DallasCZ's Backup_All script to backup all partitions on your device.
Having partitions in the same order just means they can use the same recovery since system, data and boot will be in the same places...nothing more.

alright

[MOD][Z2 Tablet] MultiROM v33c

{
"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"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to "Advanced -> MultiROM" to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
Your device must not be encrypted.
To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Before installing MultiROM, make sure that your device is running a kernel that implements the so-called hardboot patch. Below is an (incomplete) list of these kernels. If your current kernel does not support hardbooting, flash one of these kernels that support your ROM.
NOTE:Currently, the only supported kernel is the M5-Kernel which is CM-based. Hence, only CM-based ROMs work for now until other kernels implement the harboot patches.
Download the MultiROM Manager application and launch it. This application will check again if your current kernel supports hardbooting. Please, DO NOT proceed if the application validates your kernel.
Press the "Install" button and let your device reboot into recovery to complete the installation.
That's it. You can now go to "Advanced -> MultiROM" to start flashing other ROMs.
SUPPORTED KERNELs
Here is an incomplete list of kernels that implement the harboot patch for the Z2 tablet:
M5-Kernel
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to "MultiROM menu" (Top right corner in the recovery) in recovery and do Inject curr. boot sector. if it is not done directly during installation of the Rom.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to "MultiROM menu" (Top right corner in the recovery) -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Using stock as primary / Installing MultiRom on stock
Applies only if don't run a custom kernel that supports loading the recovery from the FOTAKernel partition.
Install the multirom recovery (e.g. via the app).
Shutdown the device and get into the bootloader mode (VolUp + connect the USB cable attached to your PC which must have a functional fastboot/adb installation).
Boot a kernel that supports booting the recovery from the FOTAKernel partition. For instance, you can extract the boot.img file from the AOSP installation zip and flash it with "fastboot boot boot.img" in the directory where you extracted the boot.img file.
During boot hit the VolumeUp key as soon as the led shows a purple light. An orange light indicates that booting into recovery has successfully been triggered.
Install the multirom.zip from the Downloads folder.
Add secondary roms to your liking.
To re-access the multirom recovery, the above steps must repeated except the installation of the multirom.zip file.
Install a stock rom as secondary
This only works if you are using MultiRom version 33c or larger (excluding 33x-z).
1. Existing primary stock rom
Use these instructions if you plan to move an existing stock rom installed as primary. This guide assumes that multirom recovery is properly installed.
Shutdown the device.
Boot a kernel that supports booting the recovery from the FOTAKernel partition. For instance, you can extract the boot.img file from the AOSP installation zip and flash it with "fastboot boot boot.img" in the directory where you extracted the boot.img file.
During boot hit the VolumeUp key as soon as the led shows a purple light. An orange light indicates that booting into recovery has successfully been triggered.
MAKE A BACKUP!
Go to "MultiROM menu" (Top right corner in the recovery) in recovery and tap "Swap roms".
Select the option "Copy primary rom to secondary/internal" and start the operation.
Wait until the operation finishes and flash your desired rom. (Alternatively you can also use any secondary rom to be the primary rom using the "Swap option" mentioned above.
Reboot.
2. Fresh stock installation
Use these instructions if you do not have a stock rom installed as primary. This guide assumes that multirom recovery is properly installed.
Shutdown the device.
Boot a kernel that supports booting the recovery from the FOTAKernel partition. For instance, you can extract the boot.img file from the AOSP installation zip and flash it with "fastboot boot boot.img" in the directory where you extracted the boot.img file.
During boot hit the VolumeUp key as soon as the led shows a purple light. An orange light indicates that booting into recovery has successfully been triggered.
MAKE A BACKUP!
Install the stock rom via an install zip of via an FTF. NOTE: For the FTF method you need to shutdown the device and boot into download mode (VolDown pressed while connecting the USB cable; cable connected to the PC). Use for instance flashtool to flash ONLY the kernel, system, and cache image. In addition, you MUST select "Wipe apps_log"!
When the device reboots, let it boot up and finish the first time setup procedure.
Shutdown the device.
Start the device into multirom recovery (VolDown + Power).
Go to "MultiROM menu" (Top right corner in the recovery) in recovery and tap "Swap roms".
Select the option "Copy primary rom to secondary/internal" and start the operation.
Wait until the operation finishes and flash your desired rom. (Alternatively you can also use any secondary rom to be the primary rom using the "Swap option" mentioned above.
Reboot.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Myself5/android_kernel_sony_msm8974/ (M5-Kernel)
FAQs can be found here.
CHANGELOGs
LTE-Version:
Multirom
Multirom recovery
WIFI-Version:
Multirom
Multirom recovery
CREDITs
Tasssadar
Myself5
Olivier
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
AndroPlus
Panic Brothers
You might want to consider a Donation to Tasssadar, who is the Mastermind behind all of this.

Also, you might consider a donation to Myself5 since he did the port for devices based on the shinano board.
Thanks a lot to those who have donated!
XDA:DevDB Information
MultiROM for Sony Xperia Z2 Tablet, Tool/Utility for the Sony Xperia Z2 Tablet
Contributors
Diewi, Myself5
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Testing
Created 2016-02-08
Last Updated 2017-01-08

Reserved
FAQ
Q: Where are the files?
A: Typically, there is no need to fetch the multirom installer and the multirom recovery image directly. Flashing is performed via MultiRom Manager app. However, if you require these files for development purposes, or something similar, you can get them here (folder castor: LTE, folder castor_windy: WIFI-only): https://diewald-net.com/files/public/MultiRom/

Reserved for device specific stuff...

nice now its time for hardboot on aosp
When you will post the links

rcstar6696 said:
When you will post the links
Click to expand...
Click to collapse
Done I have added the link in post #2.
Note for user: please flash Mrom via the MultiRom Manager app as described in post #1.

Great to see multi-boot capability on Z2 Tab. I`m using 'Dual Boot Patcher' on my Galaxy S5 and it is awesome. Patch any rom with almost any kernel creating unlimited(almost) multi-rom environment with a selective app-data sharing capability. I wish you look into that app, I believe it is also an open source project.

Didn't know about this yet. Looks intersting.
Support for the Z2 (Tablet) seems to be quite easy:
https://github.com/chenxiaolong/DualBootPatcher/issues/8
https://github.com/chenxiaolong/DualBootPatcher/commit/31687add90b6da073306167cda8dc73a2f3cfda0
If you want to do it

I have tried this with cm12.1 and cm11, and it works great. Due to the limitation with the kernel, the primary rom had to be cm12.1 with M5 kernel and I successfully installed cm11 as a secondary rom in the internal memory. Switching between rom works fine and Multiboot recovery works as expected. I was confused at first if I needed an app to make this work? or not, but it seems just download the flashable zip file from the first post and you are good to go. 1. Install CM12.1 2.Install M5 kernel 3. Install Multiboot flashable zip file 4. Install Multiboot recovery.
Afterall, it is a shame that I cannot enjoy this experience with stock rom, but being able to have multiple roms on one device is very exciting.
Q : Do you know how do I access the other roms system and data filesystem through root explorer? (Is it possible?) Even after system, data wipe multirom stuff is still alive somewhere but I cannot find its location.

I get a bootloop when I try to reboot into secondary from secondary. Multiboot screen does not appear and gets stuck at boot animation(of the secondary rom). Then I reset the device and power it on, it boots just fine. So, whenever I want to reboot the secondary rom, I have to turn the device off or I have to reset.

Sorry for the very late reply! It may seem like a lame excuse, but my spam protection system ate almost all of my mails, also the xda notification mails (Did not check manually due to some busy weeks at work). I hope it is fixed for good now.
Accessing the data from other roms is intentionally not implemented in MRom such that one system cannot mess up the other (although there are some tricks to get it working).
If you want to completely remove multirom, you should flash the uninstaller in recovery since only then the original boot image is restored. MultiRom manipulates the boot image upon installation to inject its secondary boot manager.
The observation about booting a secondary from a secondary rom is quite interesting. I think, I have seen some suspicious lines in the code during porting that could cause this. However, I will first need to update MRom to version 33 such that I do not hunt already fixed bugs (could have been introduced during the transition from v31 to v32).

... deleted ...

Multirom v33b for the Tablet is out
This release features the following major changes:
- Multirom version bumb from v32 to v33.
- Multirom TWRP version 3.0.2.
- New nokexec version 4 (previous: version 2).
- Support for AOSP 1.3.3 kernels (1.2.2 based kernels are also supported).
- Support for Android N (>= 7.0).
- Support for Sony Z2 stock roms as primary rom (I am investigating the installation as a secondary rom: it's installing, but not yet booting).
NOTE: When booting into recovery, the screen my flicker one or two times. This is nothig worrysome, recovery starts normally.
NOTE 2: In order to directly boot the recovery you must have at least a M rom installed.
NOTE 3: I have just noticed an issue that may cause LP-based roms not being able to boot if installed as secondary Rom. I will have a look at this tomorrow.
Update note (version a -> b): Some LP based Roms have so-called "embedded/combined" ramdisks in the boot image, like the cm12.1 roms for the Z2 Tablet, which were not properly handled. This is fixed now.
P.S.: Seems like XDA is not properly handling some of my posts. I cannot see the previous one in the browser, only in the XDA app. So, please excuse if this post occurs as a double post for you.

New build is out: v33c
Main feature: You can now use stock as secondary rom. Please follow the instructions in the OP.
Other than that, there are mainly maintenance updates. Further, the update notification from the app should now function correctly, as the version information is now correctly compiled into the multirom binary. It was a very stupid mistake from my side that I forgot this in the previous release
.

Can't install this ROM as primary: [SGP521][23.5.A.1.291][6.0.1] VMo RU:UA:KZ flashable-prerooted.zip
ROM seems to install, but stuck on infinite boot animation. Installation log:
Code:
Starting ADB sideload feature...
RECOVERY_SDCARD_ON_DATA := true
TW_NO_USB_STORAGE := true
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
I:LANG: en
sideload-host file size 1649560979 block size 65536
Installing zip file '/sideload/package.zip'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /sideload/package.zip
inflating: META-INF/com/google/android/update-binary2
installing samsung updater extensions
===========================================
| |
| *** Pre-Rooted Firmware *** |
| SGP521_23.5.A.1.291_1281-7867_R3D(1) |
| |
| Created with PRFCreator |
| by zxz0O0 |
| |
===========================================
Extracting files...
about to run program [/tmp/create-uuidlinks.sh] with 2 args
about to run program [/tmp/busybox] with 3 args
PRF is using UUIDs
Installing firmware. This might take a while...
umount: can't umount /system: Invalid argument
run_program: child exited with status 1
about to run program [/tmp/busybox] with 3 args
/dev/block/platform/msm_sdcc.1/by-uuid/F9CDF7BA-B834-A72A-F1C9-D6E0C0983896
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
about to run program [/sbin/sh] with 3 args
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx 1 root root 21 Dec 31 19:32 9DE21554-8B13-4E7D-B1E4-0371EB92073F -> /dev/block/mmcblk0p18
LTALabel flashed.
about to run program [/sbin/sh] with 3 args
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx 1 root root 21 Dec 31 19:32 DBE0B276-4DB9-4A0D-ACA7-00684DE9C467 -> /dev/block/mmcblk0p16
FOTAKernel flashed.
about to run program [/sbin/sh] with 3 args
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx 1 root root 21 Dec 31 19:32 2F50DBC8-FC14-93E4-4A9D-496FBA338B45 -> /dev/block/mmcblk0p14
package_extract_file: no rpm.elf in package
Kernel flashed.
about to run program [/tmp/busybox] with 3 args
/dev/block/platform/msm_sdcc.1/by-uuid/02CE263F-A65F-FFD7-3722-3FC2C04EC394
about to run program [/tmp/busybox] with 5 args
1213+1 records in
1213+1 records out
621352 bytes (606.8KB) copied, 0.065296 seconds, 9.1MB/s
about to run program [/tmp/busybox] with 3 args
/dev/block/platform/msm_sdcc.1/by-uuid/195FF692-DD9F-D3A5-7FA1-5A9E5669FF4B
about to run program [/tmp/busybox] with 5 args
2+0 records in
2+0 records out
1024 bytes (1.0KB) copied, 0.000680 seconds, 1.4MB/s
about to run program [/tmp/busybox] with 3 args
/dev/block/platform/msm_sdcc.1/by-uuid/90D8F5F9-BB0A-F840-A12C-E69B426DA474
about to run program [/tmp/busybox] with 5 args
2+0 records in
2+0 records out
1024 bytes (1.0KB) copied, 0.000669 seconds, 1.5MB/s
Modem flashed.
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
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/chromeos/futility
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/000000deepsleep
inflating: common/99SuperSUDaemon
inflating: common/Superuser.apk
inflating: common/chromeos/kernel.bootloader
inflating: common/chromeos/kernel.config
inflating: common/chromeos/kernel.keyblock
inflating: common/chromeos/kernel_data_key.vbprivk
inflating: common/file_contexts_image
inflating: common/init.supersu.rc
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/mmcblk0p23 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p23 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p26 on /data failed: Device or resource busy
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.007186 seconds, 278B/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.004332 seconds, 692B/s
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.004073 seconds, 2.9KB/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.004609 seconds, 650B/s
/tmp/SuperSU_extracted/META-INF/com/google/android/update-binary: line 841: /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/chromeos/futility
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/000000deepsleep
inflating: common/99SuperSUDaemon
inflating: common/Superuser.apk
inflating: common/chromeos/kernel.bootloader
inflating: common/chromeos/kernel.config
inflating: common/chromeos/kernel.keyblock
inflating: common/chromeos/kernel_data_key.vbprivk
inflating: common/file_contexts_image
inflating: common/init.supersu.rc
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
(Android M policy compatibility mode)
supolicy v2.76 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire
Patching policy ...
-permissive:adbd_socket=ok
-permissive:camera_socket=ok
................
- Success
- Detecting system compatibility
sukernel v2.76 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/dev/block/mmcblk0p14] ...
Could not find header
- System-less mode, boot image support required
- Creating image
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
/data/su.img: 11/6144 files (0.0% non-contiguous), 1422/24576 blocks
- Mounting image
mknod: /dev/block/loop0: File exists
- Creating paths
- Removing old files
- Placing files
rm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
rm: can't remove '/su/bin/sukernel': No such file or directory
rm: can't remove '/data/SuperSU.apk': No such file or directory
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/mmcblk0p14
sukernel v2.76 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/dev/block/mmcblk0p14] ...
Could not find header
- Extracting ramdisk
sukernel v2.76 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/dev/block/mmcblk0p14] ...
Could not find header
--- Failure, aborting
*************************
IMPORTANT NOTICES
*************************
First reboot may take a
few minutes. It can also
loop a few times. Do not
interrupt the process!
*************************
- Unmounting /system
- Done !
about to run program [/tmp/busybox] with 3 args
about to run program [/tmp/busybox] with 5 args
Archive: /tmp/dualrecovery.zip
creating: files/
inflating: files/adb.exe
inflating: files/AdbWinApi.dll
inflating: files/AdbWinUsbApi.dll
inflating: files/boot_twrp_recovery.sh
inflating: files/busybox
inflating: files/chargemon.sh
inflating: files/install_twrp_recovery.sh
inflating: files/recbox
inflating: files/recovery.twrp.cpio.lzma
inflating: install.bat
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
inflating: META-INF/com/google/android/updater-script
creating: RXSW/
creating: RXSW/Recovery/
inflating: RXSW/Recovery/boot_twrp_recovery.sh
inflating: RXSW/Recovery/busybox
inflating: RXSW/Recovery/chargemon.sh
inflating: RXSW/Recovery/install_twrp_recovery.sh
inflating: RXSW/Recovery/recbox
inflating: RXSW/Recovery/recovery.twrp.cpio.lzma
creating: RXSW/Root/
inflating: RXSW/Root/byeselinux.ko
creating: RXSW/Root/utils/
inflating: RXSW/Root/utils/busybox
inflating: RXSW/Root/utils/installbyeselinux.sh
inflating: RXSW/Root/utils/installmount.sh
inflating: RXSW/Root/utils/modulecrcpatch
inflating: RXSW/Root/wp_mod.ko
creating: RXSW/Script/
inflating: RXSW/Script/RXSW.sh
creating: RXSW/SuperSU/
inflating: RXSW/SuperSU/SuperSU.zip
about to run program [/tmp/dualrecovery_extracted/META-INF/com/google/android/update-binary] with 4 args
===================================
Installing RecRoot
Version 4.0.0 by Wolfbreak
about to run program [/sbin/busybox] with 3 args
===================================
Installing RecRoot...
about to run program [/tmp/RXSW.sh] with 1 args
Installing Root and Recovery...
minzip: Extracted file "/tmp/SuperSU/SuperSU.zip"
about to run program [/sbin/busybox] with 6 args
Archive: /tmp/SuperSU/SuperSU.zip
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
about to run program [/sbin/busybox] with 6 args
*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: mounting /dev/block/mmcblk0p23 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p23 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p26 on /data failed: Device or resource busy
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.007307 seconds, 273B/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.004548 seconds, 659B/s
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.004516 seconds, 2.6KB/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.005491 seconds, 546B/s
/tmp/SuperSU/META-INF/com/google/android/update-binary: line 841: /system/toolbox: not found
- Extracting files
mkdir: can't create directory 'supersu': File exists
Archive: /tmp/SuperSU/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/chromeos/futility
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/000000deepsleep
inflating: common/99SuperSUDaemon
inflating: common/Superuser.apk
inflating: common/chromeos/kernel.bootloader
inflating: common/chromeos/kernel.config
inflating: common/chromeos/kernel.keyblock
inflating: common/chromeos/kernel_data_key.vbprivk
inflating: common/file_contexts_image
inflating: common/init.supersu.rc
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
(Android M policy compatibility mode)
supolicy v2.76 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire
Patching policy ...
-permissive:adbd_socket=ok
-permissive:camera_socket=ok
.........
- Success
- Detecting system compatibility
sukernel v2.76 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/dev/block/mmcblk0p14] ...
Could not find header
- System mode
- Disabling OTA survival
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/bin/su
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/xbin/su
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/bin/.ext/.su
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/sbin/su
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /vendor/sbin/su
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /vendor/bin/su
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /vendor/xbin/su
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/xbin/daemonsu
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/xbin/sugote
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/xbin/sugote_mksh
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/xbin/supolicy
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/xbin/ku.sud
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/xbin/.ku
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/xbin/.su
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/lib/libsupol.so
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/lib64/libsupol.so
/tmp/supersu/armv7/chattr.pie: No such file or directory while trying to stat /system/etc/install-recovery.sh
- Removing old files
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/lib/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/META-INF/com/google/android/update-binary: line 1386: 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 !
unmount of /system failed; no such volume
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 3 args
about to run program [/tmp/install_twrp_recovery.sh] with 1 args
about to run program [/tmp/installbyeselinux.sh] with 1 args
mount: mounting /dev/block/mmcblk0p23 on /system failed: Device or resource busy
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/system on /system failed: Device or resource busy
modulecrcpatch (by zxz0O0)
module_layout: patched to 0x2067C442
memcmp: not found
kallsyms_lookup_name: not found
__aeabi_unwind_cpp_pr0: match
call_usermodehelper_exec: not found
call_usermodehelper_setfns: not found
call_usermodehelper_setup: not found
printk: match
........
Stock mount does not exist. Creating dir and link
Installing of mount.sh finished
================================
Thanks for your Support of RXSW
================================
script succeeded: result was [/system]about to run program [/tmp/busybox] with 3 args
about to run program [/tmp/busybox] with 5 args
Archive: /tmp/Z2-6.0.1_570_bootloop_fix.zip
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
inflating: META-INF/com/google/android/updater-script
creating: system/
creating: system/etc/
creating: system/etc/firmware/
...........
inflating: system/usr/xperia_keyboard_dictionaries/en_US.zip
about to run program [/tmp/Z2-6.0.1_570_bootloop_fix_extracted/META-INF/com/google/android/update-binary] with 4 args
==================================
updating..
minzip: Extracted 293 file(s)
Done!!!
script succeeded: result was [Done!!!]
about to run program [/tmp/busybox] with 3 args
mount: mounting /dev/block/mmcblk0p26 on /data failed: Device or resource busy
run_program: child exited with status 111
about to run program [/tmp/busybox] with 4 args
about to run program [/tmp/busybox] with 3 args
about to run program [/tmp/flash_apps.sh] with 2 args
Error: Could not find busybox
run_program: child exited with status 1
script result was []
I:Updater process ended with RC=0
I:Legacy property environment disabled.
I:Install took 412 second(s).
I:Signaling child sideload process to exit.
sideload_host finished
I:Waiting for child sideload process to exit.
I:Set page: 'action_complete'
I:TWFunc::Set_Brightness: Setting brightness control to 255
I:operation_end - status=0
Any thoughts?
Thanks

bam80 said:
Can't install this ROM as primary: [SGP521][23.5.A.1.291][6.0.1] VMo RU:UA:KZ flashable-prerooted.zip
ROM seems to install, but stuck on infinite boot animation. Installation log:
...
Any thoughts?
Thanks
Click to expand...
Click to collapse
Hi, thanks for the report and the log! From the log, I can see that there multiple attempts to root the rom (SuperSU and some other). Did you try to root it by installing some additional zip, or is the log about the rom installation exclusively (i.e., only installing the rom's zip, then getting the log)?
Also, are you using the multirom recovery or a pure TWRP one to flash the rom? I am asking, since I see no line "injecting boot.img" or similar that is printed by the Multirom Recovery if the injection box is ticked (which it should) before flashing a rom.
BTW, sorry for the delayed answer: I was very busy with "real life" in the days.

Hi Diewi, thank you for your response.
It was the log about the rom installation exclusively, but the rom inself seems contain SuperSU ("flashable-prerooted" in the name).
I tried to install it from multirom recovery through "Add ROM" menu, then I read first post which mentions that to install as secondary, stock rom must be installed first as usual single ROM (as I understand - not through "Add ROM" multiboot menu but by flashing .zip from the main menu), and then transfer to secondary rom. I didn't try the transferring yet, but installing as single ROM went flawlessly.

Can't access adb shell after system wipe:
Code:
$ adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Also, seems device name can't be recognized due to /system/build.prop inaccessible any more. ROM can't be installed:
Code:
E3004: This package is for device: SGP521, .., castor; this device is .
Updater process ended with ERROR: 7

Still can't boot stock ROM SGP521_23.5.A.1.291_R3D_SGP521_VMo\ RU-UA-KZ_1281-7867.ftf installed as primary through FlashTool and then transferred to secondary rom - instead of booting, it just enters recovery after a while. Should I change boot.img for it - disable dm-verity, ect.?
---------- Post added at 02:54 AM ---------- Previous post was at 02:11 AM ----------
Diewi said:
Main feature: You can now use stock as secondary rom. Please follow the instructions in the OP.
Click to expand...
Click to collapse
Which stock ROMs did you tried to boot that way? Can't boot stock MM, see above

bam80 said:
Hi Diewi, thank you for your response.
It was the log about the rom installation exclusively, but the rom inself seems contain SuperSU ("flashable-prerooted" in the name).
I tried to install it from multirom recovery through "Add ROM" menu, then I read first post which mentions that to install as secondary, stock rom must be installed first as usual single ROM (as I understand - not through "Add ROM" multiboot menu but by flashing .zip from the main menu), and then transfer to secondary rom. I didn't try the transferring yet, but installing as single ROM went flawlessly.
Click to expand...
Click to collapse
Well, I should have thought of this earlier... These additional scripts, update zips, etc. may cause these issues for non-primary roms.
bam80 said:
Can't access adb shell after system wipe:
Code:
$ adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Also, seems device name can't be recognized due to /system/build.prop inaccessible any more. ROM can't be installed:
Code:
E3004: This package is for device: SGP521, .., castor; this device is .
Updater process ended with ERROR: 7
Click to expand...
Click to collapse
You can either remove the assert from the update zip (dangerous), but this seems a rom issue to me, since I other roms installed fine for me after wiping /system. Which rom did you try to install? The one mentioned before?
bam80 said:
Still can't boot stock ROM SGP521_23.5.A.1.291_R3D_SGP521_VMo\ RU-UA-KZ_1281-7867.ftf installed as primary through FlashTool and then transferred to secondary rom - instead of booting, it just enters recovery after a while. Should I change boot.img for it - disable dm-verity, ect.?
---------- Post added at 02:54 AM ---------- Previous post was at 02:11 AM ----------
Which stock ROMs did you tried to boot that way? Can't boot stock MM, see above
Click to expand...
Click to collapse
I noticed as well that stock is a bit picky when being installed as secondary. It worked for me using the instructions in OP. What you can do is to wipe the cache and you could try to wipe the apps_log partition using FlashTool.
Which version of Mrom are you using? Please post the Mrom and the Recovery version.
Used rom: 23.5.A.1.29

Diewi said:
You can either remove the assert from the update zip (dangerous), but this seems a rom issue to me, since I other roms installed fine for me after wiping /system. Which rom did you try to install? The one mentioned before?
Click to expand...
Click to collapse
Sorry but it doesn't seems the ROM issue - that was rather standard device check in the beginning of the installation, maybe your ROM missing it:
Code:
assert(getprop("ro.product.device") == "SGP521" || getprop("ro.build.product") == "SGP521" || getprop("ro.product.device") == "SGP541" || getprop("ro.build.product") == "SGP541" || getprop("ro.product.device") == "SGP551" || getprop("ro.build.product") == "SGP551" || getprop("ro.product.device") == "castor" || getprop("ro.build.product") == "castor" || abort("E3004: This package is for device: SGP521,SGP541,SGP551,castor; this device is " + getprop("ro.product.device") + "."););
So,
getprop("ro.product.device")
Click to expand...
Click to collapse
returns empty string.
Anyway, not being able to access adb shell after system wipe doesn't seems proper behavior.
The ROM is AICP
I noticed as well that stock is a bit picky when being installed as secondary. It worked for me using the instructions in OP. What you can do is to wipe the cache and you could try to wipe the apps_log partition using FlashTool.
Which version of Mrom are you using? Please post the Mrom and the Recovery version.
Used rom: 23.5.A.1.29
Click to expand...
Click to collapse
I used OP instructions too, flashing using FlashTool. I wiped data, cache and apps_log partition.
I am using MultiROM v33d(from the app status) and Recovery 2017-01-08 (installed from the app).
When booting the stock ROM as secondary, I can't even get the logs using 'adb logcat' during boot. When primary boots, the logs showed normally.
Did you use stock kernel to boot 23.5.A.1.291 as secondary?
UPDATE:
somehow, I could get it booted. Maybe running Restorecon from Recovery helped, donno..

CUOCO92 11S V4.1-V4.3 OTA to V4.4 doesn't seems to get applied ?!

Hi,
today I noticed that there is again an OTA update from 4.3 to 4.4 for the CUOCO 11S US version.
The OTA Update Tool from CUOCO downloaded it without problems, but after TWRP flashing it seems that the described fixes weren't included or the update didn't apply.
I tested this by trying the quick fixes described in the change log, e.g. setting for calculator and qrcode.
Does anyone successful installed this OTA update on his CUOCO 11S US ROM ?
https://onedrive.live.com/redir?res...authkey=!AA4n9ilwV6oagbs&v=3&ithint=photo,jpg
https://www.androidfilehost.com/?fid=24580943222145278

BetaHydri said:
Hi,
today I noticed that there is again an OTA update from 4.3 to 4.4 for the CUOCO 11S US version.
The OTA Update Tool from CUOCO downloaded it without problems, but after TWRP flashing it seems that the described fixes weren't included or the update didn't apply.
I tested this by trying the quick fixes described in the change log, e.g. setting for calculator and qrcode.
Does anyone successful installed this OTA update on his CUOCO 11S US ROM ?
https://onedrive.live.com/redir?res...authkey=!AA4n9ilwV6oagbs&v=3&ithint=photo,jpg
https://www.androidfilehost.com/?fid=24580943222145278
Click to expand...
Click to collapse
Yes, I've installed the ROM 11s Cuoco92, updated to v44 and now both the calculator and code-bar work correctly from quick settings

massymoroboshi said:
Yes, I've installed the ROM 11s Cuoco92, updated to v44 and now both the calculator and code-bar work correctly from quick settings
Click to expand...
Click to collapse
Even with a factory reset on my actual CUOCO92 V4.2 build I'm not able to update to 4.3 and then 4.4 via OTA-Updater.
After installation without errors regarding the TWRP install output my phone ist still on build 4.2. Maybe I have to delete all partitions and do a restore to the factory ROM via TWRP 3.0.2 restore.
Look at my last "last_ota_log". I tried also to install another ZIP here for example SuperSU Beta 2.74 this one also has problems:
.....
I:Set page: 'flash_zip'
Iperation_start: 'Flashing'
Installing zip file '/sdcard/SuperSU-v2.74-2-20160519174328.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.
*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: mounting /dev/block/mmcblk0p40 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p47 on /data failed: Device or resource busy
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.002538 seconds, 788B/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.000582 seconds, 5.0KB/s
10+0 records in
10+0 records out
10 bytes (10B) copied, 0.000735 seconds, 13.3KB/s
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.002195 seconds, 0B/s
mount: mounting /dev/block/mmcblk0p40 on /system failed: Device or resource busy
mount: mounting /dev/block/bootdevice/by-name/system on /system failed: Device or resource busy
/tmp/updater: line 804: can't create /system/toolbox: Read-only file system
chmod: /system/toolbox: No such file or directory
/tmp/updater: line 839: /system/toolbox: not found
- Extracting files
Archive: /sdcard/SuperSU-v2.74-2-20160519174328.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/chromeos/futility
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/000000deepsleep
inflating: common/99SuperSUDaemon
inflating: common/Superuser.apk
inflating: common/chromeos/kernel.bootloader
inflating: common/chromeos/kernel.config
inflating: common/chromeos/kernel.keyblock
inflating: common/chromeos/kernel_data_key.vbprivk
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
supolicy v2.74 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Patching policy ...
-permissive:adbd_socket=ok
-permissive:functionfs=ok
-permissive:hci_attach_exec=ok
-permissive:system_server=ok
-permissive:nfc=ok
-permissive:rild_debug_socket=ok
-permissive:file_type=ok
-permissive:exec_type=ok
-permissiveroperty_type=ok
-permissive:surfaceflinger_service=ok
-permissive:binderservicedomain=ok
-permissive:mdns_socket=ok
-permissive:node_type=ok
-permissivelatform_app=ok
-permissive:ram_device=ok
-permissiveort_type=ok
-permissive:rootfs=ok
-permissive:tmpfs=ok
-permissive:usbfs=ok
-permissive:bootanim_exec=ok
-permissive:gpsd_tmpfs=ok
-permissive:installd_exec=ok
-permissive:su_tmpfs=ok
-permissive:untrusted_app_tmpfs=ok
-permissive:cpuctl_device=ok
-permissive:cgroup=ok
-permissive:drmserver_socket=ok
-permissivepp_device=ok
-permissive:wpa_socket=ok
-permissiveroc_net=ok
-permissive:vdc=ok
-permissive:clatd=ok
-permissive:netd=ok
-permissive:sdcardd=ok
-permissive:zygote=ok
-permissive:debuggerd=ok
-permissive:input_device=ok
-permissive:mediaserver_tmpfs=ok
-permissive:sysfs_ksm=ok
-permissive:ueventd_tmpfs=ok
-permissive:download_file=ok
-permissive:mtp=ok
-permissive:backup_data_file=ok
-permissive:servicemanager_tmpfs=ok
-permissive:su_exec=ok
-permissivepp_exec=ok
-permissive:tee_exec=ok
-permissive:vdc_exec=ok
-permissive:wpa_exec=ok
-permissive:dumpstate_tmpfs=ok
-permissive:mqueue=ok
-permissive:mtp_exec=ok
-permissive:system_ndebug_socket=ok
-permissive:tee=ok
-permissive:adb_data_file=ok
-permissive:anr_data_file=ok
-permissive:app_data_file=ok
-permissive:dhcp_data_file=ok
-permissive:logdr_socket=ok
-permissive:logdw_socket=ok
-permissive:net_data_file=ok
-permissive:shell_data_file=ok
-permissive:vpn_data_file=ok
-permissive:adb_keys_file=ok
-permissive:dalvikcache_data_file=ok
-permissive:keystore_tmpfs=ok
-permissive:kernel=ok
-permissive:dhcp_tmpfs=ok
-permissivelatform_app_data_file=ok
-permissive:dhcp=ok
-permissive:mediaserver_service=ok
-permissive:dnsmasq=ok
-permissive:drmserver=ok
-permissive:drmserver_tmpfs=ok
-permissive:keystore=ok
-permissiveroperty_data_file=ok
-permissive:vold_exec=ok
-permissive:adbd=ok
-permissive:dumpstate=ok
-permissive:racoon_exec=ok
-permissive:rild_exec=ok
-permissive:unlabeled=ok
-permissive:bluetooth=ok
-permissive:uncrypt_tmpfs=ok
-permissive:inputflinger=ok
-permissive:dhcp_exec=ok
-permissive:vcs_device=ok
-permissive:gpsd_exec=ok
-permissiveort=ok
-permissive:fuse=ok
-permissive:install_data_file=ok
-permissive:lmkd_exec=ok
-permissive:logd_exec=ok
-permissive:netd_exec=ok
-permissive:asec_image_file=ok
-permissive:recovery=ok
-permissive:radio_tmpfs=ok
-permissive:tee_tmpfs=ok
-permissive:wpa=ok
-permissive:dev_type=ok
-permissive:runas=ok
-permissive:vdc_tmpfs=ok
-permissive:wpa_tmpfs=ok
-permissive:hostapd=ok
-permissive:system_prop=ok
-permissive:vfat=ok
-permissive:fs_type=ok
-permissive:sdcard_external=ok
-permissive:sdcard_internal=ok
-permissive:sdcardd_exec=ok
-permissivewntty_device=ok
-permissive:selinuxfs=ok
-permissive:tty_device=ok
-permissive:tun_device=ok
-permissive:clatd_exec=ok
-permissive:installd_tmpfs=ok
-permissive:uio_device=ok
-permissive:bootanim_tmpfs=ok
-permissive:install_recovery_tmpfs=ok
-permissive:sysinit_exec=ok
-permissive:system_app_service=ok
-permissive:full_device=ok
-permissive:null_device=ok
-permissive:fuse_device=ok
-permissive:usb_device=ok
-permissive:wfd_app=ok
-permissive:camera_device=ok
-permissive:hostapd_exec=ok
-permissive:keystore_exec=ok
-permissive:uncrypt=ok
-permissive:system_app_data_file=ok
-permissive:tee_device=ok
-permissive:uncrypt_exec=ok
-permissive:video_device=ok
-permissive:labeledfs=ok
-permissive:mtp_tmpfs=ok
-permissive:audio_device=ok
-permissive:radio_device=ok
-permissive:nfc_tmpfs=ok
-permissive:userinit_exec=ok
-permissivetmx_device=ok
-permissive:mdnsd_exec=ok
-permissive:system_app_tmpfs=ok
-permissive:bluetooth_data_file=ok
-permissive:usbaccessory_device=ok
-permissive:userinit_data_exec=ok
-permissive:lvm_placeholder=ok
-permissive:rmt_placeholder=ok
-permissive:nfc_prop=ok
-permissive:dex2oat_exec=ok
-permissive:socket_device=ok
-permissive:bluetooth_tmpfs=ok
-permissive:sysfs_lowmemorykiller=ok
-permissive:installd_socket=ok
-permissive:netd_tmpfs=ok
-permissive:servicemanager_exec=ok
-permissiveroc=ok
-permissive:asec_public_file=ok
-permissiveroc_cpuinfo=ok
-permissive:usermodehelper=ok
-permissive:bluetooth_socket=ok
-permissive:installd=ok
-permissive:debug_prop=ok
-permissive:inputflinger_exec=ok
-permissivean_result_prop=ok
-permissive:security_prop=ok
-permissive:zygote_socket=ok
-permissive:system_server_tmpfs=ok
-permissive:bluetooth_prop=ok
-permissive:ctl_rildaemon_prop=ok
-permissive:system_radio_prop=ok
-permissive:contextmount_type=ok
-permissive:lmkd_tmpfs=ok
-permissive:logd_tmpfs=ok
-permissive:uhid_device=ok
-permissive:ctl_dhcp_pan_prop=ok
-permissive:racoon_socket=ok
-permissive:ctl_bootanim_prop=ok
-permissive:wallpaper_file=ok
-permissive:install_recovery=ok
-permissive:net_radio_prop=ok
-permissive:asec_apk_file=ok
-permissive:console_device=ok
-permissive:userinit_prop=ok
-permissive:sensors_device=ok
-permissive:dhcp_prop=ok
-permissive:audio_prop=ok
-permissive:qtaguid_proc=ok
-permissive:ctl_bugreport_prop=ok
-permissive:healthd=ok
-permissive:init=ok
-permissive:sysinit=ok
-permissive:keychain_data_file=ok
-permissive:kmem_device=ok
-permissive:netif_type=ok
-permissive:gps_control=ok
-permissive:logd_prop=ok
-permissive:init_tmpfs=ok
-permissive:surfaceflinger_exec=ok
-permissive:kmsg_device=ok
-permissive:vold_prop=ok
-permissive:data_file_type=ok
-permissive:netif=ok
-permissive:bootanim=ok
-permissive:klog_device=ok
-permissive:zoneinfo_data_file=ok
-permissive:radio=ok
-permissive:inputflinger_service=ok
-permissive:mlstrustedobject=fail
-permissive:debuggerd_tmpfs=ok
-permissive:unconfineddomain=ok
-permissive:fscklogs=ok
-permissive:netd_socket=ok
-permissive:zygote_tmpfs=ok
-permissive:mlstrustedsubject=fail
-permissive:mediaserver=ok
-permissive:mediaserver_exec=ok
-permissive:ctl_fuse_prop=ok
-permissive:drmserver_service=ok
-permissive:mtpd_socket=ok
-permissive:debugfs=ok
-permissive:keystore_service=ok
-permissiveemfs=ok
-permissiveipefs=ok
-permissive:sockfs=ok
-permissive:sysfs=ok
-permissive:logd=ok
-permissivestorefs=ok
-permissive:default_android_service=ok
-permissive:drmserver_exec=ok
-permissive:inotify=ok
-permissive:vold_tmpfs=ok
-permissive:bluetooth_service=ok
-permissive:sysfs_devices_system_cpu=ok
-permissive:debuggerd_exec=ok
-permissive:untrusted_app=ok
-permissive:gps_socket=ok
-permissive:ueventd=ok
-permissive:node=ok
-permissiveroc_sysrq=ok
-permissive:adb_device=ok
-permissive:shared_relro=ok
-permissive:sysfs_type=ok
-permissive:system_data_file=ok
-permissive:alarm_device=ok
-permissive:camera_data_file=ok
-permissive:sysfs_bluetooth_writable=ok
-permissive:ctl_mdnsd_prop=ok
-permissive:hci_attach_tmpfs=ok
-permissive:devpts=ok
-permissive:sysfs_zram=ok
-permissive:audio_firmware_file=ok
-permissiveroc_bluetooth_writable=ok
-permissive:apk_data_file=ok
-permissive:audio_data_file=ok
-permissive:bluetooth_efs_file=ok
-permissive:dm_device=ok
-permissive:drm_data_file=ok
-permissive:gps_data_file=ok
-permissive:media_data_file=ok
-permissive:nfc_data_file=ok
-permissive:radio_data_file=ok
-permissive:tee_data_file=ok
-permissive:wifi_data_file=ok
-permissive:mdnsd_tmpfs=ok
-permissive:system_app=ok
-permissive:dumpstate_socket=ok
-permissive:sdcard_type=ok
-permissive:system_file=ok
-permissive:apk_private_tmp_file=ok
-permissive:hci_attach_dev=ok
-permissive:su=ok
-permissive:racoon_tmpfs=ok
-permissive:apk_tmp_file=ok
-permissiveroc_security=ok
-permissive:system_server_service=ok
-permissive:gps_device=ok
-permissive:gpu_device=ok
-permissive:nfc_service=ok
-permissive:gpsd=ok
-permissive:init_shell=ok
-permissive:mdnsd=ok
-permissive:device=ok
-permissive:system_wpa_socket=ok
-permissive:surfaceflinger=ok
-permissive:sysfs_nfc_power_writable=ok
-permissive:rild_tmpfs=ok
-permissive:isolated_app_tmpfs=ok
-permissive:runas_exec=ok
-permissive:untrusted_app_devpts=ok
-permissive:dex2oat=ok
-permissive:watchdogd=ok
-permissive:bluetoothdomain=ok
-permissive:dnsmasq_exec=ok
-permissive:fwmarkd_socket=ok
-permissive:qtaguid_device=ok
-permissive:inputflinger_tmpfs=ok
-permissive:shell_exec=ok
-permissivepp=ok
-permissive:dumpstate_exec=ok
-permissive:zero_device=ok
-permissive:resourcecache_data_file=ok
-permissive:systemkeys_data_file=ok
-permissive:shared_relro_tmpfs=ok
-permissive:binder_device=ok
-permissiveroperty_socket=ok
-permissive:sdcardd_tmpfs=ok
-permissive:hw_random_device=ok
-permissive:random_device=ok
-permissive:urandom_device=ok
-permissive:watchdog_device=ok
-permissive:ctl_default_prop=ok
-permissive:ctl_dumpstate_prop=ok
-permissive:security_file=ok
-permissive:media_rw_data_file=ok
-permissive:wfd_app_tmpfs=ok
-permissive:default_prop=ok
-permissive:debuggerd_prop=ok
-permissive:shared_relro_file=ok
-permissive:install_recovery_exec=ok
-permissive:coredump_file=ok
-permissive:netdomain=ok
-permissive:appdomain=ok
-permissive:lmkd_socket=ok
-permissive:logd_debug=ok
-permissive:racoon=ok
-permissive:graphics_device=ok
-permissive:serial_device=ok
-permissive:efs_file=ok
-permissiveowerctl_prop=ok
-permissive:rild=ok
-permissive:vold=ok
-permissive:adbtcp_prop=ok
-permissive:iio_device=ok
-permissive:ion_device=ok
-permissive:shell=ok
-permissive:tombstone_data_file=ok
-permissive:radio_service=ok
-permissive:apk_private_data_file=ok
-permissive:mdnsd_socket=ok
-permissive:service_manager_type=ok
-permissive:healthd_service=ok
-permissive:root_block_device=ok
-permissive:cache_backup_file=ok
-permissive:logd_socket=ok
-permissive:hci_attach=ok
-permissive:dalvikcache_profiles_data_file=ok
-permissive:sdcard_posix=ok
-permissive:vold_socket=ok
-permissive:block_device=ok
-permissive:zygote_exec=ok
-permissive:frp_block_device=ok
-permissive:radio_prop=ok
-permissive:loop_device=ok
-permissive:sysfs_writable=ok
-permissiveroperties_device=ok
-permissive:misc_user_data_file=ok
-permissive:surfaceflinger_tmpfs=ok
-permissive:sysfs_ioscheduler=ok
-permissive:lmkd=ok
-permissive:nfc_device=ok
-permissive:servicemanager=ok
-permissive:sysfs_wake_lock=ok
-permissive:dnsproxyd_socket=ok
-permissive:rild_socket=ok
-permissive:shell_prop=ok
-permissive:keystore_data_file=ok
-permissive:ashmem_device=ok
-permissive:isolated_app=ok
-permissive:sysinit_tmpfs=ok
-permissive:shm=ok
-permissivelatform_app_tmpfs=ok
-permissive:rpmsg_device=ok
-permissive:shell_tmpfs=ok
-permissive:cache_file=ok
-permissive:fingerprint_prop=ok
-permissive:mtp_device=ok
-permissive:mtd_device=ok
-permissive:log_device=ok
-permissive:domain=ok
- Success
- System mode
mount: mounting /dev/block/mmcblk0p40 on /system failed: Device or resource busy
mount: mounting /dev/block/bootdevice/by-name/system on /system failed: Device or resource busy
- Disabling OTA survival
chmod: /tmp/supersu/arm64/chattr.pie: No such file or directory
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
/tmp/updater: line 1382: /tmp/supersu/arm64/chattr.pie: not found
- Removing old files
mv: can't rename '/system/etc/install-recovery.sh': Read-only file system
rm: can't remove '/system/bin/install-recovery.sh': Read-only file system
rm: can't remove '/system/etc/install-recovery.sh': Read-only file system
rm: can't remove '/system/xbin/su': Read-only file system
rm: can't remove '/system/xbin/daemonsu': Read-only file system
rm: can't remove '/system/xbin/sugote': Read-only file system
rm: can't remove '/system/xbin/sugote-mksh': Read-only file system
rm: can't remove '/system/xbin/supolicy': Read-only file system
rm: can't remove '/system/lib64/libsupol.so': Read-only file system
rm: can't remove '/system/etc/.installed_su_daemon': Read-only file system
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
mkdir: can't create directory '/system/bin/.ext': Read-only file system
chown: /system/bin/.ext: No such file or directory
chown: /system/bin/.ext: No such file or directory
chmod: /system/bin/.ext: No such file or directory
rm: can't remove '/system/bin/.ext/.su': No such file or directory
/tmp/updater: line 1382: can't create /system/bin/.ext/.su: nonexistent directory
chown: /system/bin/.ext/.su: No such file or directory
chown: /system/bin/.ext/.su: No such file or directory
chmod: /system/bin/.ext/.su: No such file or directory
rm: can't remove '/system/xbin/su': Read-only file system
/tmp/updater: line 1382: can't create /system/xbin/su: Read-only file system
chown: /system/xbin/su: Read-only file system
chown: /system/xbin/su: Read-only file system
chmod: /system/xbin/su: Read-only file system
rm: can't remove '/system/xbin/daemonsu': Read-only file system
/tmp/updater: line 1382: can't create /system/xbin/daemonsu: Read-only file system
chown: /system/xbin/daemonsu: Read-only file system
chown: /system/xbin/daemonsu: Read-only file system
chmod: /system/xbin/daemonsu: Read-only file system
rm: can't remove '/system/xbin/sugote': Read-only file system
/tmp/updater: line 1382: can't create /system/xbin/sugote: Read-only file system
chown: /system/xbin/sugote: Read-only file system
chown: /system/xbin/sugote: Read-only file system
chmod: /system/xbin/sugote: Read-only file system
rm: can't remove '/system/xbin/sugote-mksh': Read-only file system
/tmp/updater: line 1382: can't create /system/xbin/sugote-mksh: Read-only file system
chown: /system/xbin/sugote-mksh: Read-only file system
chown: /system/xbin/sugote-mksh: Read-only file system
chmod: /system/xbin/sugote-mksh: Read-only file system
rm: can't remove '/system/xbin/supolicy': Read-only file system
/tmp/updater: line 1382: can't create /system/xbin/supolicy: Read-only file system
chown: /system/xbin/supolicy: Read-only file system
chown: /system/xbin/supolicy: Read-only file system
chmod: /system/xbin/supolicy: Read-only file system
rm: can't remove '/system/lib64/libsupol.so': Read-only file system
/tmp/updater: line 1382: can't create /system/lib64/libsupol.so: Read-only file system
chown: /system/lib64/libsupol.so: Read-only file system
chown: /system/lib64/libsupol.so: Read-only file system
chmod: /system/lib64/libsupol.so: Read-only file system
mkdir: can't create directory '/system/app/SuperSU': Read-only file system
chown: /system/app/SuperSU: No such file or directory
chown: /system/app/SuperSU: No such file or directory
chmod: /system/app/SuperSU: No such file or directory
rm: can't remove '/system/app/SuperSU/SuperSU.apk': No such file or directory
/tmp/updater: line 1382: can't create /system/app/SuperSU/SuperSU.apk: nonexistent directory
chown: /system/app/SuperSU/SuperSU.apk: No such file or directory
chown: /system/app/SuperSU/SuperSU.apk: No such file or directory
chmod: /system/app/SuperSU/SuperSU.apk: No such file or directory
rm: can't remove '/system/etc/install-recovery.sh': Read-only file system
/tmp/updater: line 1382: can't create /system/etc/install-recovery.sh: Read-only file system
chown: /system/etc/install-recovery.sh: Read-only file system
chown: /system/etc/install-recovery.sh: Read-only file system
chmod: /system/etc/install-recovery.sh: Read-only file system
rm: can't remove '/system/bin/app_process': Read-only file system
rm: can't remove '/system/bin/app_process64': Read-only file system
rm: can't remove '/system/etc/init.d/99SuperSUDaemon': No such file or directory
/tmp/updater: line 1382: 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
/tmp/updater: line 1382: can't create /system/etc/.installed_su_daemon: Read-only file system
chown: /system/etc/.installed_su_daemon: Read-only file system
chown: /system/etc/.installed_su_daemon: Read-only file system
chmod: /system/etc/.installed_su_daemon: Read-only file system
- Restoring files
- 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
umount: can't umount /system: Device or resource busy
- Done !
I:Updater process ended with RC=0
I:Legacy property environment disabled.
Updating partition details...
Iata backup size is 7446MB, free: 28981MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
Iperation_end - status=0
I:Set page: 'rebootcheck'
I:Unable to unmount '/system'
I:Unable to unmount '/system'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
Rebooting...
I:InfoManager saving '/data/media/0/TWRP/.twrps'
I:Saved settings file values
Obviously it has something todo with the rw mount permissions of the system partition. It seems that the CUOCOS update script can't overwrite or replace the files:
ui_print("_________________________");
ui_print("LEECO OTA UPDATE CUOCO92");
sleep(5);
ui_print("Preparing update...");
show_progress(1.34,70);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
sleep(4);
ui_print("Patching system...");
package_extract_dir("system", "/system");
sleep(5);
ui_print("Cleaning...");
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/data", "/data");
delete_recursive("/data/data/com.otaupdater");
delete_recursive("/data/media/0/OTA-Updater");
unmount("/data");
sleep(10);
ui_print("Done");
show_progress(1.34,10);
sleep(5);
run_program("/sbin/reboot");
The script seems to fail during extraction of the package when it tries to replace the several folders under /system/...

[Q] Magisk root method

Does anyone know how to root with Magisk in stock deodexed rom?

This section is for "Roms,Kernel and Recovery etc" not for QnA. Keep this forum clean. Delete this thread.

Korax94 said:
Does anyone know how to root with Magisk in stock deodexed rom?
Click to expand...
Click to collapse
Dont post in wrong section..
You can Post your questions in QUESTIONS/ANSWER section.

I don't know how to delete

Try flashing su remove first and then simply flash latest magisk.
Sent from my Lenovo P2a42 using Tapatalk

abhayruparel said:
Try flashing su remove first and then simply flash latest magisk.
Click to expand...
Click to collapse
It says "error 1", I'll take a look at the official Magisk's thread

Korax94 said:
It says "error 1", I'll take a look at the official Magisk's thread
Click to expand...
Click to collapse
I was able to root with magisk in stock rom.

HI can i have some more info please how did you do it i would like to root and be able to use android pay thats the only thing stopping me.

sam00561 said:
HI can i have some more info please how did you do it i would like to root and be able to use android pay thats the only thing stopping me.
Click to expand...
Click to collapse
You will run into a lot of problems down the road.
Systemless root is complicated in itself and according to the developer Magisk isn't really meant for passing safetynet. I also noted incompatibility with Tasker, Secure Settings, that is, apps which require traditional root. In the end it's just to much of a hassle to be worth it.
I just went back to SuperSU after discovering It was quite difficult to pass safetynet. I did manage though, but it's a never-ending fight against cooperations with ridicilous amounts of money involved. There will only be one outcome.
You can read about how to install Magisk in the TWRP-thread.

Ok thanks i guess that answered my question i guess ill wait untill android pay workaround becomes available with normal root method.

Hi,
Which is the lastest working version of Magisk on Lenovo P2 nougat?
As for me I can only install v11.2, not the lastest v13.2
Thanks for your answers!
Edit : here is the error log when I try to install the last version:
Code:
Installing zip file '/sdcard/Magisk-v13.2.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Segmentation fault
Archive: /sdcard/Magisk-v13.2.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: addon.d/99-magisk.sh
inflating: arm/magisk
inflating: arm/magiskboot
inflating: arm64/magisk
inflating: arm64/magiskboot
inflating: chromeos/futility
inflating: chromeos/kernel.keyblock
inflating: chromeos/kernel_data_key.vbprivk
inflating: common/boot_patch.sh
inflating: common/init.magisk.rc
inflating: common/magisk.apk
inflating: common/util_functions.sh
inflating: x64/magisk
inflating: x64/magiskboot
inflating: x86/magisk
inflating: x86/magiskboot
************************
* Magisk v13.2 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm64
- Constructing environment
- Adding addon.d survival script
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
I:Install took 1 second(s).
Error installing zip file '/sdcard/Magisk-v13.2.zip'
Updating partition details...
I:Data backup size is 1737MB, free: 20382MB.
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'vfat'
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: 'copylog'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log

http://blox2.com/fixmagisk-install-error-1-twrp-recovery/
Try this
Sent from my Lenovo P2a42 using Tapatalk

Problem installing SuperSU or Magisk

I've successfully unlocked the bootloader of my One M8 (Android 6.0) and installed TWRP 3.4.0.1 but I am unable to install any version of SuperSU (ex Chainfire) by flashing the zip through TWRP or install Magisk 20.4(20400) via the Magisk Manager app.
In the case of SuperSU it fails on the extraction of ramdisk.
In the case of Magisk the system responds "! Unsupported/Unknown image format"
Does anyone have any suggestions ?

the only thing i can think of that might shine more light on the SuperSU error , at least ; is after failure , in twrp go > advanced > copy log.
maybe the log will provide more details of the error.
srry , thats all i got. good luck.

Thanks for your advice.
Since what I'm trying to do is fairly "fundamental" can you advise a combination of TWRP version & Super SU version that will work together. I'm assuming tha the failure to unzip properly is a functional of TWRP. I've looked at the beginner's guide here but all point to (what appears to me) to be very old versions of the two pieces of software required. Should I even be using Super SU....has it been superceded by something better. Presumably others in the HTC One M8 community could tell which combinations worked successfully for them

I looked in the log as suggested and got the following :-
*****************
SuperSU installer
*****************
mount: losetup failed 1
cat: /fstab.*: No such file or directory
- Mounting /system, /data and rootfs
mount: '/dev/block/mmcblk0p47'->'/data': Device or resource busy
mount: '/' not in /proc/mounts
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)
12+0 records in
12+0 records out
12 bytes transferred in 0.001 secs (12000 bytes/sec)
3+0 records in
3+0 records out
3 bytes transferred in 0.001 secs (3000 bytes/sec)
/tmp/updater[989]: /system/toolbox: not found
- Extracting files
mkdir: 'supersu': File exists
Archive: /external_sd/UPDATE-SuperSU-v2.82-20170528234214.zip
inflating: common/chromeos/kernel_data_key.vbprivk
inflating: mips/supolicy
inflating: arm/suinit
inflating: armv7/supolicy
inflating: arm/chattr.pie
inflating: arm64/suinit
inflating: common/chromeos/kernel.bootloader
inflating: x86/supolicy
inflating: arm64/libsupol.so
inflating: mips/sukernel
inflating: armv7/sukernel
inflating: common/chromeos/kernel.keyblock
inflating: mips64/libsupol.so
inflating: mips/libsupol.so
inflating: mips64/su
inflating: x86/chattr
inflating: x86/sukernel
inflating: x86/su
inflating: common/init.supersu.rc
inflating: common/99SuperSUDaemon
inflating: META-INF/MANIFEST.MF
inflating: arm64/chromeos/futility
inflating: mips64/suinit
inflating: x64/libsupol.so
inflating: META-INF/CERT.RSA
inflating: x86/chattr.pie
inflating: x86/suinit
inflating: common/Superuser.apk
inflating: common/hexpatch
inflating: META-INF/com/google/android/update-binary
inflating: x86/su.pie
inflating: common/chromeos/kernel.config
inflating: META-INF/CERT.SF
inflating: common/000000deepsleep
inflating: mips64/supolicy
inflating: x64/supolicy
inflating: arm/libsupol.so
inflating: armv7/libsupol.so
inflating: mips/su
inflating: armv7/su
inflating: common/init.supersu.rc.24
inflating: mips64/sukernel
inflating: x64/sukernel
inflating: x64/su
inflating: common/frp_install
inflating: META-INF/com/google/android/updater-script
inflating: mips/suinit
inflating: armv7/suinit
inflating: mips/chattr.pie
inflating: armv7/chattr.pie
inflating: arm/supolicy
inflating: arm/chattr
inflating: arm64/supolicy
inflating: x64/suinit
inflating: x86/libsupol.so
inflating: arm/sukernel
inflating: arm64/sukernel
inflating: arm/su
inflating: common/launch_daemonsu.sh
inflating: arm64/su
inflating: common/install-recovery.sh
inflating: common/file_contexts_image
CANNOT LINK EXECUTABLE: cannot locate symbol "__aeabi_memcpy" referenced by "/sbin/liblog_htc_sbin.so"...
page record for 0xa77a102c was not found (block_size=16)
- Detecting system compatibility
CANNOT LINK EXECUTABLE: cannot locate symbol "__aeabi_memcpy" referenced by "/sbin/liblog_htc_sbin.so"...
page record for 0xb634302c was not found (block_size=16)
- System-less mode, boot image support required
- Creating image
CANNOT LINK EXECUTABLE: cannot locate symbol "__aeabi_memcpy" referenced by "/sbin/liblog_htc_sbin.so"...
page record for 0xa752b03c was not found (block_size=16)
- Mounting image
mkdir: '/su': File exists
- Creating paths
mkdir: '/su/bin': File exists
mkdir: '/su/xbin': File exists
mkdir: '/su/lib': File exists
mkdir: '/su/etc': File exists
mkdir: '/su/su.d': File exists
- Removing old files
- Placing files
rm: /su/bin/su: No such file or directory
rm: /su/bin/daemonsu: No such file or directory
rm: /su/bin/supolicy_wrapped: No such file or directory
rm: /su/lib/libsupol.so: No such file or directory
rm: /su/bin/sukernel: No such file or directory
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/mmcblk0p42
CANNOT LINK EXECUTABLE: cannot locate symbol "__aeabi_memcpy" referenced by "/sbin/liblog_htc_sbin.so"...
page record for 0xb10eb03c was not found (block_size=16)
- Extracting ramdisk
CANNOT LINK EXECUTABLE: cannot locate symbol "__aeabi_memcpy" referenced by "/sbin/liblog_htc_sbin.so"...
page record for 0xab02003c was not found (block_size=16)
--- Failure, aborting
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop0' - change
See losetup --help
losetup: needs 1 arg
*************************
IMPORTANT NOTICES
*************************
First reboot may take a
few minutes. It can also
loop a few times. Do not
interrupt the process!
*************************
.....any bright ideas about what went wrong here ?

no , i'm really no good at reading logs.
but i'm using the same twrp ver. with SuperSU-v.2.82 which i'm pretty sure was the last buid.
maybe if you posted the log in the SuperSU thread someone could read it? '

mrrocketdog said:
no , i'm really no good at reading logs.
but i'm using the same twrp ver. with SuperSU-v.2.82 which i'm pretty sure was the last buid.
maybe if you posted the log in the SuperSU thread someone could read it? '
Click to expand...
Click to collapse
Finally succeeded with Magdisk BUT it doesn't seem to give me root access.
Tried "su" with Terminal Emulator expecting to get a "#" prompt but nothing !!!!
Root Checker says it hasn't happened ! Do I need to install anything as well as Magisk ?

CRJ343 said:
Finally succeeded with Magdisk BUT it doesn't seem to give me root access.
Tried "su" with Terminal Emulator expecting to get a "#" prompt but nothing !!!!
Root Checker says it hasn't happened ! Do I need to install anything as well as Magisk ?
Click to expand...
Click to collapse
try asking here
https://forum.xda-developers.com/showthread.php?t=3432382

Develop Bugs

welcome