Develop Bugs

[DEV] Porting rom from desire: can't boot

Hello,
I was trying to make a porting rom from Desire using dsixda Kitchen.
I used the option 19 to make a porting, using another rom ported from desire to desire z as working rom (to get kernel, kernel modules, keyboard and so on..)
Installation is ok but when I try to boot it stuck at HTC logo.
Using logcat or another ADB command I get only:
- exec '/system/bin/sh' failed: No such file or directory (2) -
So I pulled the recovery.log after installing my porting rom:
Code:
Starting recovery on Sun Apr 15 10:37:24 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sd-ext ext3 /dev/block/mmcblk1p2 (null)
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
7 /system ext3 /dev/block/mmcblk0p25 (null)
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.koush.20111028.180155
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Fri Oct 28 18:02:25 PDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=HTC Vision
ro.product.brand=htc_wwe
ro.product.name=htc_vision
ro.product.device=vision
ro.product.board=vision
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
ro.build.product=vision
ro.build.description=2.42.405.2 CL84109 release-keys
ro.build.fingerprint=htc_wwe/htc_vision/vision:2.3.3/GRI40/84109:user/release-keys
ro.sf.lcd_density=240
debug.fb.rgb565=0
ro.gsm.2nd_data_retry_config=max_retries=3, 2000, 2000, 2000
rild.libpath=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
ro.ril.enable.a53=1
ro.ril.enable.dtm=0
ro.ril.gprsclass=10
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.ril.def.agps.feature=1
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=0
ro.ril.enable.gea3=0
ro.telephony.default_network=0
wifi.interface=eth0
wifi.supplicant_scan_interval=15
mobiledata.interfaces=gannet0,rmnet0,rmnet1,rmnet2
ro.opengles.version=131072
dalvik.vm.heapsize=32m
ro.ril.def.agps.mode=2
ro.ril.disable.power.collapse=1
ro.com.google.clientidbase=android-tmobile-us
ro.com.google.clientidbase.vs=android-hms-tmobile-us
ro.com.google.clientidbase.ms=android-hms-tmobile-us
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.com.google.gmsversion=2.2_r5
ro.setupwizard.enable_bypass=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
media.a1026.nsForVoiceRec=0
media.a1026.enableA1026=1
htc.audio.alt.enable=0
htc.audio.hac.enable=0
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.1.0-vision-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=SH0B9RT04800
ro.bootmode=recovery
ro.baseband=26.13.04.19_M
ro.carrier=HTC-ITA
ro.bootloader=0.84.2000
ro.hardware=vision
ro.revision=128
init.svc.choice_fn=stopped
init.svc.recovery=running
init.svc.htcbatt=stopped
init.svc.adbd=running
ro.9kramdump=0
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /sdcard/2.Flashable/vision_signed_041512_121934.zip
Finding update package...
I:Update location: /sdcard/2.Flashable/vision_signed_041512_121934.zip
Opening update package...
Installing update...
mke2fs: can't format mounted filesystem
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25mount: failed to mount /dev/block/mmcblk0p25 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk0p26 at /data: Device or resource busy
minzip: Extracted file "/data/app/com.TEST.android.lvh-1.apk"
minzip: Extracted file "/data/app/com.adobe.flashplayer-1.apk"
minzip: Extracted file "/data/app/com.antutu.CpuMasterFree-1.apk"
minzip: Extracted file "/data/app/com.bigtincan.android.adfree.apk"
minzip: Extracted file "/data/app/com.estrongs.android.pop-1.apk"
minzip: Extracted file "/data/app/com.keramidas.TitaniumBackup-1.apk"
minzip: Extracted file "/data/app/com.koushikdutta.rommanager-1.apk"
minzip: Extracted file "/data/app/placeholder"
minzip: Extracted file "/data/app/ws.plattner.cifsmanager.apk"
minzip: Extracted file "/data/data/com.android.htcprofile/anr_history.txt"
minzip: Extracted file "/data/data/hosts"
minzip: Extracted file "/system/app/AccountSyncManager.apk"
minzip: Extracted file "/system/app/AccountSyncManager.odex"
minzip: Extracted file "/system/app/AppSharing.apk"
...
...
...
...
... (extraction of other /system files..)
...
...
...
minzip: Extracted file "/system/xbin/tcpdump"
minzip: Extracted file "/system/xbin/wireless_modem"
set_perm: chown of /system/etc/bluez to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/bluez to 775 failed: No such file or directory
set_perm: chown of /system/bin/openvpn to 1000 1000 failed: No such file or directory
set_perm: chmod of /system/bin/openvpn to 755 failed: No such file or directory
set_perm: chown of /system/bin/iproute-script.sh to 1000 1000 failed: No such file or directory
set_perm: chmod of /system/bin/iproute-script.sh to 755 failed: No such file or directory
set_perm: chown of /system/bin/vpnc to 1000 1000 failed: No such file or directory
set_perm: chmod of /system/bin/vpnc to 755 failed: No such file or directory
set_perm: chown of /system/bin/vpnc-script.sh to 1000 1000 failed: No such file or directory
set_perm: chmod of /system/bin/vpnc-script.sh to 755 failed: No such file or directory
set_perm: chown of /data/data/com.android.providers.contacts/files/* to 0 0 failed: No such file or directory
set_perm: chmod of /data/data/com.android.providers.contacts/files/* to 1232 failed: No such file or directory
mke2fs: can't format mounted filesystem
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p27script result was [/data]
Install from sdcard complete.
Formatting /sd-ext...
I:Formatting unknown device.
I:Formatting ext3 device.
warning: 287 blocks unused
I don't like that (NULL) after the block allocation, but this is the first rom cooking and I don't understand if it is normal.
Also there are some errors at the end and at the begin of the installation, but they don't seems to me to be fatal errors..
Someone can help?
I have tryed also to install RCMIX kernel after this rom, that kernel is working with the other rom ported from desire that I'm using as base, working rom, for my porting.
(PS: it is sense 1.9 rom)
maybe I have to change updater script?
There are blocks problems?

Failed to mount /system, IO error, what's going on...?

Hey my g3 is broken... After i installed resurrection remix marshmallow i ran into some issues with the screen tunring off a minute after starting and not coming back on (well backlight was on but nothing else), so i decided to revert back to lollipop. First i tried to flash a backup i had done before, that failed as it got stuck on "calculating details" or something like that, then i wiped the system partition cause it seems like that might work? but now everything is broken...
shorter version: had issues with marshmallow, tried to recovery from lollipop backup, it didn't, wiped system, now i can't install roms or anything
- can't flash another version of twrp (kinda funny how it says it succeeded...):
Code:
Installing '/external_sd/twrp-2.8.6.1_d855-bumped.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.
minzip: Error writing 2064 bytes from zip file from 0xbe88ece4: I/O error
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
script succeeded: result was []I:Legacy property environment disabled.
- cant flash roms, (example flashing ressurection remix) again it says it succeeds... but that's obviously a lie:
Code:
Installing '/external_sd/Resurrection-Remix-LP-v5.5.9-20151127-d855.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
minzip: Extracted 3 file(s)
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
Not backing up files from incompatible version: 5.1
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
___
/ /\
/ /::\
/ /:/\:\
/ /:/~/:/
/__/:/ /:/___
\ \:\/:::::/
\ \::/~~~~
\ \:\
\ \:\
\__\/
performing update
( ( )
)\ ) ( )\ ) ( /(
(()/( ( )\))( (()/( )\())
/(_)))\ ((_)()\ /(_))((_)\
(_)) ((_) (_()((_)(_)) __((_)
| _ \| __|| \/ ||_ _| \ \/ /
| /| _| | |\/| | | | > <
|_|_\|___||_| |_||___| /_/\_\
blockimg version is 3
maximum stash entries 0
using existing stash /cache/recovery/5a79362318d00cf4c316e86435b3ed38dd35082d/
Patching system image unconditionally...
erasing 528384 blocks
writing 145542 blocks of new data
ui_print
mount: mounting /dev/block/mmcblk0p40 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p43 on /data failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p40 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
mount: mounting /dev/block/mmcblk0p43 on /data failed: Device or resource busy
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: Device or resource busy
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.001710 seconds, 1.1KB/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.000335 seconds, 8.7KB/s
12+0 records in
12+0 records out
12 bytes (12B) copied, on: Could not label u:object_r:system_file:s0 with -h: No such file or directory
usage: chcon context path...
usage: chcon context path...
usage: chcon context path...
rm: can't remove '/system/xbin/daemonsu': No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
usage: chcon context path...
usage: chcon context path...
usage: chcon context path...
rm: can't remove '/system/xbin/sugote': No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
rm: can't remove '/system/xbin/sugote-mksh': No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
usage: chcon context path...
usage: chcon context path...
usage: chcon context path...
rm: can't remove '/system/xbin/supolicy': No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
usage: chcon context path...
usage: chcon context path...
usage: chcon context path...
rm: can't remove '/system/lib/libsupol.so': No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
usage: chcon context path...
usage: chcon context path...
usage: chcon context path...
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
usage: chcon context path...
usage: chcon context path...
usage: chcon context path...
rm: can't remove '/system/app/SuperSU/SuperSU.apk': No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
usage: chcon context path...
usage: chcon context path...
usage: chcon context path...
rm: can't remove '/system/etc/install-recovery.sh': No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
usage: chcon context path...
usage: chcon context path...
usage: chcon context path...
ln: /system/bin/install-recovery.sh: File exists
ln: /system/bin/install-recovery.sh: File exists
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
ln: /system/bin/app_process: File exists
ln: /system/bin/app_process: File exists
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
ln: /system/bin/app_process32: File exists
ln: /system/bin/app_process32: File exists
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
rm: can't remove '/system/bin/app_process_init': No such file or directory
cat: read error: I/O error
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
usage: chcon context path...
usage: chcon context path...
usage: chcon context path...
rm: can't remove '/system/etc/init.d/99SuperSUDaemon': No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
usage: chcon context path...
usage: chcon context path...
ui_print
unmount of /system failed; no such volume
minzip: Error writing 2064 bytes from zip file from 0xbeae1cd4: I/O error
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
script succeeded: result was [0.200000]I:Legacy property environment disabled.
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p40
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p40', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p43
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Data backup size is 0MB, free: 10044MB.
I:sending message to remove 65537
mtppipe remove storage 65537
I:Message sent, remove storage ID: 65537
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
I:Can't probe device /dev/block/mmcblk0p43
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p43', current file system: 'ext4'
E:Unable to mount storage.
So at this point im seriously just considering giving this phone a burial....
TWRP Version: 2.8.7.0
Model: D855

[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..

[KERNEL][F8131/F8132] AndroPlusKernel v26

I got Xperia X Performance Dual F8132 from one kind person,
so I created custom kernel for Xperia X Performance Dual F8132!
{
"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"
}
Download
MOD EDIT: Removed link to website.
I won't create kernel for device which I don't own.
If you want me to create, please give me the device.
Donate:
PayPal
Credit:
tobias.waldvogel for DRM patch
nilezon for refined script for booting recovery
flar2, Alucard24 and other developers for useful patch
XDA:DevDB Information
AndroPlusKernel for Xperia X Performance , Kernel for the Sony Xperia X Performance
Contributors
AndroPlus
Source Code: https://github.com/AndroPlus-org/android_kernel_sony_msm8996
Kernel Special Features:
Version Information
Status: Testing
Created 2016-06-25
Last Updated 2017-07-22

Did you select "Xperia X" on the Sony Developer site to get the BL unlock code? Just asking since the Xperia X Perfomance does not show in the list yet.
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/

sxtester said:
Did you select "Xperia X" on the Sony Developer site to get the BL unlock code? Just asking since the Xperia X Perfomance does not show in the list yet.
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Click to expand...
Click to collapse
Yes, just select "Xperia X" is ok. I have unlocked BL and rooted XP.

Thank you for the first kernel and root method.
I'm waiting recovery and xposed now.
Any "bad influence" after unlocked bootloder?

bkk99213 said:
Thank you for the first kernel and root method.
I'm waiting recovery and xposed now.
Any "bad influence" after unlocked bootloder?
Click to expand...
Click to collapse
same as Z5 (no X-Reality and noise reduction in camera because of no DRM key and brabra), and workaround for DRM key is included in kernel.

AndroPlus said:
same as Z5 (no X-Reality and noise reduction in camera because of no DRM key and brabra), and workaround for DRM key is included in kernel.
Click to expand...
Click to collapse
What do you mean by workaround? Do you mean X-Reality and noise reduction will still be there after using this kernel?

ashatter said:
What do you mean by workaround? Do you mean X-Reality and noise reduction will still be there after using this kernel?
Click to expand...
Click to collapse
Yes.

Sorry for OT but why there isnt any Xperia X forum in xda? Or Xperia X performance and X shares same forum?

okanb3 said:
Sorry for OT but why there isnt any Xperia X forum in xda? Or Xperia X performance and X shares same forum?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-x

Do you have the backup of stock kernel?
Thanks.

Running the script it gives a lot of error.
But my phone is unlocked and root successfully.
Thanks.
Code:
shell[email protected]:/ # ./SuperSU_files/install_SuperSU.sh
*****************
SuperSU installer
*****************
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
2+0 records in
2+0 records out
2 bytes transferred in 0.001 secs (2000 bytes/sec)
3+0 records in
3+0 records out
3 bytes transferred in 0.001 secs (3000 bytes/sec)
10+0 records in
10+0 records out
10 bytes transferred in 0.001 secs (10000 bytes/sec)
dd: skip reached end of input
DBG [23] [arm] [] [arm64-v8a] [arm64] [/system/bin/sh]
- Removing old files
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
- Creating space
- Placing files
mkdir: '/system/bin/.ext': File exists
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/bin/.ext/.su: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/su: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/daemonsu: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/sugote: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
rm: /system/xbin/sugote-mksh: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/supolicy: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/lib64/libsupol.so: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/app/SuperSU/SuperSU.apk: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/etc/install-recovery.sh: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
ln: no such tool
ln: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
ln: no such tool
ln: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
ln: no such tool
ln: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
rm: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
- Restoring files
rm: /system/app/Maps/Maps.apk: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/app/YouTube/YouTube.apk: No such file or directory
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
- Post-installation script
- Done !

AndroPlus said:
http://forum.xda-developers.com/xperia-x
Click to expand...
Click to collapse
I'm so sorry. I dont know how i miss that. Thanks and sorry again.

May I know if any recovery tool and xposed framwork is ready yet?

y2kbugleung said:
May I know if any recovery tool and xposed framwork is ready yet?
Click to expand...
Click to collapse
I built TWRP but it only boots when I run fastboot boot and touch didn't work, so I didn't upload TWRP for now.
I can control with USB mouse and I confirmed Xposed v85 is working well.
Maybe it's kernel problem (I'm using customized AOSP tree...), so I'll try to build working TWRP this week.

AndroPlus said:
I built TWRP but it only boots when I run fastboot boot and touch didn't work, so I didn't upload TWRP for now.
I can control with USB mouse and I confirmed Xposed v85 is working well.
Maybe it's kernel problem (I'm using customized AOSP tree...), so I'll try to build working TWRP this week.
Click to expand...
Click to collapse
Great!:good:
お願いします

Excuse me, it seems X-Reality and Vivid mode are gone.

y2kbugleung said:
Excuse me, it seems X-Reality and Vivid mode are gone.
Click to expand...
Click to collapse
Did you delete /data/credmgr/credmgr.db and reboot?
EDIT:
quoted code in the page

AndroPlus said:
Did you delete /data/credmgr/credmgr.db and reboot?
Click to expand...
Click to collapse
Sorry I have missed the line.
The display modes have came back! :fingers-crossed:
I have following the note on the homepage.
Maybe you could quote the line as code so others won't miss the line in the future?
Thanks again!

Thank you for this kernel
but i have problem here
my Build number is 35.0.A.1.227
I saw your source, the Build number is the same too
and i'm sure i flash the kernel in my xperia x performance
because the kernel version is
3.18.20-v01
[email protected] #21
but , my root is failed
the command messeage is this
can you help me ?
sorry about my pooooooor english.....
Code:
SuperSU installer
*****************
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
./SuperSU_files/install_SuperSU.sh[147]: can't create /system/toolbox: Read-only file system
chmod: /system/toolbox: No such file or directory
./SuperSU_files/install_SuperSU.sh[149]: /system/toolbox: not found
chcon: no such tool
chcon: /system/toolbox: No such file or directory
./SuperSU_files/install_SuperSU.sh[149]: /system/toolbox: not found
chcon: no such tool
chcon: /system/toolbox: No such file or directory
2+0 records in
2+0 records out
2 bytes transferred in 0.001 secs (2000 bytes/sec)
3+0 records in
3+0 records out
3 bytes transferred in 0.001 secs (3000 bytes/sec)
10+0 records in
10+0 records out
10 bytes transferred in 0.001 secs (10000 bytes/sec)
dd: skip reached end of input
./SuperSU_files/install_SuperSU.sh[195]: /system/toolbox: not found
DBG [23] [arm] [] [arm64-v8a] [arm64] [/system/bin/sh]
- Removing old files
mv: bad '/system/bin/install-recovery.sh': Read-only file system
./SuperSU_files/install_SuperSU.sh[212]: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/install-recovery_original.sh: No such file or directory
./SuperSU_files/install_SuperSU.sh[212]: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/install-recovery_original.sh: No such file or directory
rm: /system/bin/su: No such file or directory
rm: /system/xbin/su: No such file or directory
rm: /vendor/bin/su: No such file or directory
rm: /system/xbin/daemonsu: No such file or directory
rm: /system/xbin/sugote: No such file or directory
rm: /system/xbin/sugote-mksh: No such file or directory
rm: /system/xbin/supolicy: No such file or directory
rm: /system/xbin/ku.sud: No such file or directory
rm: /system/lib/libsupol.so: No such file or directory
rm: /system/lib64/libsupol.so: No such file or directory
rm: /system/bin/install-recovery.sh: Read-only file system
rm: /system/etc/install-recovery.sh: No such file or directory
rm: /system/etc/init.d/99SuperSUDaemon: No such file or directory
rm: /system/etc/.installed_su_daemon: No such file or directory
rm: /system/app/Superuser.apk: No such file or directory
rm: /system/app/Superuser.odex: No such file or directory
rm: /system/app/Superuser: No such file or directory
rm: /system/app/SuperUser.apk: No such file or directory
rm: /system/app/SuperUser.odex: No such file or directory
rm: /system/app/SuperUser: No such file or directory
rm: /system/app/superuser.apk: No such file or directory
rm: /system/app/superuser.odex: No such file or directory
rm: /system/app/superuser: No such file or directory
rm: /system/app/Supersu.apk: No such file or directory
rm: /system/app/Supersu.odex: No such file or directory
rm: /system/app/Supersu: No such file or directory
rm: /system/app/SuperSU.apk: No such file or directory
rm: /system/app/SuperSU.odex: No such file or directory
rm: /system/app/SuperSU: No such file or directory
rm: /system/app/supersu.apk: No such file or directory
rm: /system/app/supersu.odex: No such file or directory
rm: /system/app/supersu: No such file or directory
rm: /system/app/VenomSuperUser.apk: No such file or directory
rm: /system/app/VenomSuperUser.odex: No such file or directory
rm: /system/app/VenomSuperUser: No such file or directory
- Creating space
rm ro /system/app/Maps/Maps.apk (y/N):n
rm ro /system/app/YouTube/YouTube.apk (y/N):n
- Placing files
mkdir: '/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
./SuperSU_files/install_SuperSU.sh[329]: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext: No such file or directory
./SuperSU_files/install_SuperSU.sh[329]: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext: No such file or directory
./SuperSU_files/install_SuperSU.sh[329]: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.

nichael said:
Thank you for this kernel
but i have problem here
my Build number is 35.0.A.1.227
I saw your source, the Build number is the same too
and i'm sure i flash the kernel in my xperia x performance
because the kernel version is
3.18.20-v01
[email protected] #21
but , my root is failed
the command messeage is this
can you help me ?
sorry about my pooooooor english.....
Click to expand...
Click to collapse
Please reboot and try this:
Code:
adb root
adb shell
./SuperSU_files/install_SuperSU.sh
command window will look like this:
C:\～～～>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\～～～>adb shell
[email protected]:/ #./SuperSU_files/install_SuperSU.sh
......

Error while rooting HTC 826

Hello All,
I'm trying to root my HTC 826.
1. I have already Unlocked the bootloader.
2. Installed TWRP 2.8.5.0
3. Boot to recovery. Install -> SuperSU-v2.46
4. While installing SuperSU-v2.46.zip (from sdcard). I got the following error (I have not included the complete logs below as they are large in size. Please let me know if you require complete logs):
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP XianShiDeNiWo D826W TWRP 2.8.5.0 on Tue Jan 13 00:39:35 2015
(pid 262)
BOARD_HAS_NO_REAL_SDCARD := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/platform/usb_mass_storage/lun0/file' does not exist, USB storage mode disabled
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
Starting the UI...Pixel format: 1080x1920 @ 32bpp
Pixel format: RGBA_8888
.
.
.
Irocessing '/usb-otg'
E:Can not create '/usb-otg' folder.
I:Can not open /etc/fstab.
E:Error creating fstab
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/CC53ZYG09490'
I:Settings storage is '/data/media/0'
Updating partition details...
E:Unable to stat '/data/misc/adb'
E:Unable to stat '/data/misc/bluedroid'
E:Unable to stat '/data/misc/bluetooth'
E:Unable to stat '/data/misc/keystore'
.
.
.
E:Unable to stat '/data/property/persist.logd.size'
E:error opening '/data/dalvik-cache'
E:error: Permission denied
E:Unable to stat '/data/resource-cache'
E:Unable to stat '/data/drm'
E:Unable to stat '/data/mediadrm'
E:error opening '/data/security'
E:error: Permission denied
E:Unable to stat '/data/nfc'
E:Unable to stat '/data/connectivity'
.
.
.
Iata backup size is 238MB, free: 7637MB.
E: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:Can not open /etc/fstab.
E:Error creating fstab
I:Unmounting main partitions...
.
.
.
Installing '/sdcard/UPDATE-SuperSU-v2.46.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
E:Legacy property environment did not initialize successfully. Properties may not be detected.
*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: can't read '/etc/fstab': No such file or directory
mount: can't read '/etc/fstab': No such file or directory
I:Cannot find file /sys/class/thermal/thermal_zone0/temp
mount: can't find /system in /proc/mounts
mount: mounting /system on /system failed: Invalid argument
/tmp/updater: line 152: can't create /system/toolbox: Permission denied
chmod: /system/toolbox: No such file or directory
.
.
.
I:Checking resolution...
I:Loading resources...
open_png /twres/images/twrplogo.png
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
open_png /twres/images/menu-button.png
open_png /twres/images/file.png
open_png /twres/images/folder.png
.
.
.
I would really appreciate your help on this. Please let me know
if you require any additional help.
Thanks.

Follow up
kdgup said:
Hello All,
I'm trying to root my HTC 826.
1. I have already Unlocked the bootloader.
2. Installed TWRP 2.8.5.0
3. Boot to recovery. Install -> SuperSU-v2.46
4. While installing SuperSU-v2.46.zip (from sdcard). I got the following error (I have not included the complete logs below as they are large in size. Please let me know if you require complete logs):
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP XianShiDeNiWo D826W TWRP 2.8.5.0 on Tue Jan 13 00:39:35 2015
(pid 262)
BOARD_HAS_NO_REAL_SDCARD := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/platform/usb_mass_storage/lun0/file' does not exist, USB storage mode disabled
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
Starting the UI...Pixel format: 1080x1920 @ 32bpp
Pixel format: RGBA_8888
.
.
.
Irocessing '/usb-otg'
E:Can not create '/usb-otg' folder.
I:Can not open /etc/fstab.
E:Error creating fstab
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/CC53ZYG09490'
I:Settings storage is '/data/media/0'
Updating partition details...
E:Unable to stat '/data/misc/adb'
E:Unable to stat '/data/misc/bluedroid'
E:Unable to stat '/data/misc/bluetooth'
E:Unable to stat '/data/misc/keystore'
.
.
.
E:Unable to stat '/data/property/persist.logd.size'
E:error opening '/data/dalvik-cache'
E:error: Permission denied
E:Unable to stat '/data/resource-cache'
E:Unable to stat '/data/drm'
E:Unable to stat '/data/mediadrm'
E:error opening '/data/security'
E:error: Permission denied
E:Unable to stat '/data/nfc'
E:Unable to stat '/data/connectivity'
.
.
.
Iata backup size is 238MB, free: 7637MB.
E: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:Can not open /etc/fstab.
E:Error creating fstab
I:Unmounting main partitions...
.
.
.
Installing '/sdcard/UPDATE-SuperSU-v2.46.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
E:Legacy property environment did not initialize successfully. Properties may not be detected.
*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: can't read '/etc/fstab': No such file or directory
mount: can't read '/etc/fstab': No such file or directory
I:Cannot find file /sys/class/thermal/thermal_zone0/temp
mount: can't find /system in /proc/mounts
mount: mounting /system on /system failed: Invalid argument
/tmp/updater: line 152: can't create /system/toolbox: Permission denied
chmod: /system/toolbox: No such file or directory
.
.
.
I:Checking resolution...
I:Loading resources...
open_png /twres/images/twrplogo.png
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
open_png /twres/images/menu-button.png
open_png /twres/images/file.png
open_png /twres/images/folder.png
.
.
.
I would really appreciate your help on this. Please let me know
if you require any additional help.
Thanks.
Click to expand...
Click to collapse
Did you manage to fix it?

Hi
Backup the partation mmcblk0.img and upload it and put the link here I will see if you don't know how to backup I will show you