Hi guys, I want to share DualBoot Patcher for Xiaomi Mi Max Hydrogen 32gb, thanks to @chenxiaolong developer, that`s the link to download apk for Xiaomi where say test build you can download:
https://github.com/chenxiaolong/DualBootPatcher/pull/273
and in the github there`s a zip DualBoot utilities that it`s to flash in recovery in case that it is necessary, please read the thread to learning more about if you interested. This ability is ideal to try roms and flash mods in the secondary rom without damage primary rom. I use now like primary Mokee rom, I ever used like primary the rom stock in any devices in the past but I don`t try yet miui rom like primary but I think it must be work.
hi thank you for posting this exciting news .but could you give detailed information on how to implement this on our devices ? and also please link the required files directly
Nice work I used the same app for my previous phone the note 4 for months and I loved it. I will test it and report back
Sent from my Mi Max using Tapatalk
Well, I will explain the basic operation of this app for those who do not know it yet, in my experience in particular, other members will add other methods of operation but I use in this way and worked in more than 20 devices. that`s the link to general thread:
http://forum.xda-developers.com/showthread.php?t=2447534
This app has the ability to install another rom (or more) on the same device creating a separate slot, in this (these) slot(s) the ROM will be installed, too we can flash mods, zips like supersu for the next roms, or flash first a duplicate rom, patch a mod and flash on it before to flash in primary. all the mods, etc that we want to flash in others rom first we must to patch it, then flash; any mod that we want to flash in the primary rom just flash without patch.
First of all you must install the apk DualBootPatcher in the rom we are using, (of course unlock bootloader, custom recovery, root and recommended install busybox by Stericsson) go to options in three dots and set kernel first of nothing, this file was provided for developer @chenxiaolong, is a test build, download here:
https://jenkins.noobdev.io/job/Dual...tcher-builder && fast,target=android-all-gcc/
copy to your sdcard or internal memory the rom you want to install as secondary, open the app then look for the option patch file, then patch the zip rom you want to install, rename it with small letters without symbols or space, I always place all roms others in data-slot, not in another compartment, let patch, once did his work can now flash from the same application, the app duplicates the file, won`t erase original and will place it beside other zip in the same folder, once flashed give you reboot to go to the new rom, when reboot in new rom follow the same steps, root it, install busybox, install DualBootPatcher, set kernel and from the app you can reboot again to primary if you want, you can share the data from one to others roms, there`s an option to do it, in the first reboot after share data, it begin to work, then reboot to other rom and share data and reboot again in the same rom to active it. it is important to have the zip file DualBoot Utilities if a bootloop occurs, then we can choose to boot into the primary rom flashing this zip and follow steps to flash this zip is like a Aroma installer, you can download here:
https://snapshots.noobdev.io/files/...ties/DualBootUtilities-9.0.0.r61.g05501e3.zip
I get an error whenever I flash the latest miui beta rom.I currently have the RR. I posted a log on the original thread for the dev to look at
Sent from my Mi Max using Tapatalk
I flashed with sucess miui rom Angels & Daemons in secondary slot with Aroma installer just no work shared data, in primary I have Mokee rom.
SubwayChamp said:
I flashed with sucess miui rom Angels & Daemons in secondary slot with Aroma installer just no work shared data, in primary I have Mokee rom.
Click to expand...
Click to collapse
Which miui rom did you flash successfully, share link to the rom please. Im not able to flash any miui rom official or unofficial as secondary.
We are talking about hydrogen mi max 3/32 version here.
[email protected] said:
Which miui rom did you flash successfully, share link to the rom please. Im not able to flash any miui rom official or unofficial as secondary.
We are talking about hydrogen mi max 3/32 version here.
Click to expand...
Click to collapse
Sure, page is in spanish, this is direct link to download, v4. 0 is last version, it has Aroma installer, I patch it for secondary, then flashed from recovery not from DBP, when finish to flash don't reboot directly, go again to recovery it must do some things and flash supersu zip to root it.
Link to rom: http://www.mediafire.com/?1qvvrc6ap16h9q0
Link to supersu that works for me: https://mega.nz/#!kNZm0SIS!CV16nenP7qLiNpAIp0P9IE-ZeQoaZRfAd1DnHUuaXaM
SubwayChamp said:
Sure, page is in spanish, this is direct link to download, v4. 0 is last version, it has Aroma installer, I patch it for secondary, then flashed from recovery not from DBP, when finish to flash don't reboot directly, go again to recovery it must do some things and flash supersu zip to root it.
Link to rom: http://www.mediafire.com/?1qvvrc6ap16h9q0
Link to supersu that works for me: https://mega.nz/#!kNZm0SIS!CV16nenP7qLiNpAIp0P9IE-ZeQoaZRfAd1DnHUuaXaM
Click to expand...
Click to collapse
Hi, I followed exactly your steps and installed successfully 2nd rom. Thanks for it. I uses Angel&Demon 4.0 for Mi Max, too but after booting, I dont see any mentioned mod (center mod, dolby, sound mod, custom boot animation, etc.) as I selected on Aroma installer, otherwise, it's based on MiUI 6.9.15 build. Do you face the same things?
For Mi MAx Pro, on; Primary- set kernel , get this message : "Could not determine the boot partition because this device's codename 'helium' is not recognized." :-/ . Primary rom is MIUI8 - 8.0.3.0
dinhvtai said:
Hi, I followed exactly your steps and installed successfully 2nd rom. Thanks for it. I uses Angel&Demon 4.0 for Mi Max, too but after booting, I dont see any mentioned mod (center mod, dolby, sound mod, custom boot animation, etc.) as I selected on Aroma installer, otherwise, it's based on MiUI 6.9.15 build. Do you face the same things?
Click to expand...
Click to collapse
Hi, I recently read the post, excuse, really when I used Angels&Daemons like primary and unique rom I selected exactly these mods in Aroma installer but don`t appear when I reboot rom and of course like secondary with DBP neither
SubwayChamp said:
Hi, I recently read the post, excuse, really when I used Angels&Daemons like primary and unique rom I selected exactly these mods in Aroma installer but don`t appear when I reboot rom and of course like secondary with DBP neither
Click to expand...
Click to collapse
Yes. But I found about the screenshot of V3.0, this rom should have a logo of angel&demon in About setting which my 4.0 doesnt. Could you please give me the 3.0 link please since I only could found the screenshot of it?
Kindly add Helium support , i tried installing Primary as miui Global stable with root and busybox and CM on second partion , i am getting error saying dual zip is for hydrogen and your device is helium
KiranP23 said:
Kindly add Helium support , i tried installing Primary as miui Global stable with root and busybox and CM on second partion , i am getting error saying dual zip is for hydrogen and your device is helium
Click to expand...
Click to collapse
How you go that far because for me fail on first step , when going to primary rom . set kernel . get message ; "Could not determine the boot partition because this device's codename 'helium' is not recognized."
Mike0505 said:
How you go that far because for me fail on first step , when going to primary rom . set kernel . get message ; "Could not determine the boot partition because this device's codename 'helium' is not recognized."
Click to expand...
Click to collapse
actually no, initially i patched the rom zip ,but when it asked for Device model only model close to mine was Mi Max Hydrogen(since helium not available) > then after patching when i tried installing rom , i got error saying device need to be Hydrogen , i again edited patched rom zip and replaced Hydrogen with helium in installer script and saved , but while flashing it failed -_-
Hi, dinhvtai: definitely I don`t find version 3.0 from Angels&Demons, it looks was removed.
Mike0505: did you upload getlogs.zip to forum from developer Chenxiaolong to he make app for Helium?, this zip is in this link: https://snapshots.noobdev.io/misc/getlogs/GetLogs-20161019-2.zip you must to flash thiz zip and upload to Chenxiaolong to forum
SubwayChamp said:
Hi, dinhvtai: definitely I don`t find version 3.0 from Angels&Demons, it looks was removed.
Mike0505: did you upload getlogs.zip to forum from developer Chenxiaolong to he make app for Helium?, this zip is in this link: https://snapshots.noobdev.io/misc/getlogs/GetLogs-20161019-2.zip you must to flash thiz zip and upload to Chenxiaolong to forum
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=3939906&stc=1&d=1479411534
attached log
Patcher doesn't work:
Code:
[D] Initialized installer for zip file: /storage/emulated/0/Download/MUI_data-slot-2.zip
[D] [Installer] Initialization stage
[D] [Installer] Chroot creation stage
[V] Creating chroot environment
[D] Running executable: mount
[D] Running executable: mount
[D] Running executable: mount
[D] Running executable: mount
[D] Not mounting EFS partition because this is not a Samsung device
[D] [Installer] Environment set up stage
[D] [Installer] Device verification stage
[D] libmbp version: 9.0.0
[D] ro.product.device = hydrogen
[D] ro.build.product = hydrogen
[D] ro.patcher.device =
[D] Target device = hydrogen
[D] Boot block device: /dev/block/bootdevice/by-name/boot
[D] Recovery block device: /dev/block/bootdevice/by-name/recovery
[D] System block device: /dev/block/bootdevice/by-name/system
[E] /dev/block/platform/7824900.sdhci/by-name/boot: Failed to stat: No such file or directory
[W] Failed to copy /dev/block/platform/7824900.sdhci/by-name/boot. Continuing anyway
[D] Copied /dev/block/bootdevice/by-name/boot to the chroot
[D] Copied /dev/block/mmcblk0p60 to the chroot
[E] /dev/block/platform/7824900.sdhci/by-name/recovery: Failed to stat: No such file or directory
[W] Failed to copy /dev/block/platform/7824900.sdhci/by-name/recovery. Continuing anyway
[D] Copied /dev/block/bootdevice/by-name/recovery to the chroot
[D] Copied /dev/block/mmcblk0p61 to the chroot
[D] Symlinked /mb/loop.system to /chroot/dev/block/platform/7824900.sdhci/by-name/system
[D] Symlinked /mb/loop.system to /chroot/dev/block/bootdevice/by-name/system
[D] Symlinked /mb/loop.system to /chroot/dev/block/mmcblk0p64
[D] Boot image is a plain boot image
[D] Found Android boot image header at: 0
[D] - magic: ANDROID!
[D] - kernel_size: 9507351
[D] - kernel_addr: 0x80008000
[D] - ramdisk_size: 6462078
[D] - ramdisk_addr: 0x81000000
[D] - second_size: 0
[D] - second_addr: 0x80f00000
[D] - tags_addr: 0x80000100
[D] - page_size: 2048
[D] - dt_size: 0
[D] - unused: 0x00000000
[D] - name:
[D] - cmdline: console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlyprintk ramoops_memreserve=2M
[D] - id: 31f119d09c9717cdee7c49876533df1c57a58474000000000000000000000000
[E] Copying from recovery: default.recovery.prop
[E] Copying from recovery: sbin/[
[E] Copying from recovery: sbin/[[
[E] Copying from recovery: sbin/adbd
[E] Copying from recovery: sbin/adjtimex
[E] Copying from recovery: sbin/arp
[E] Copying from recovery: sbin/ash
[E] Copying from recovery: sbin/awk
[E] Copying from recovery: sbin/base64
[E] Copying from recovery: sbin/basename
[E] Copying from recovery: sbin/bbconfig
[E] Copying from recovery: sbin/blkid
[E] Copying from recovery: sbin/blockdev
[E] Copying from recovery: sbin/brctl
[E] Copying from recovery: sbin/bunzip2
[E] Copying from recovery: sbin/busybox
[E] Copying from recovery: sbin/bzcat
[E] Copying from recovery: sbin/bzip2
[E] Copying from recovery: sbin/cal
[E] Copying from recovery: sbin/cat
[E] Copying from recovery: sbin/catv
[E] Copying from recovery: sbin/chattr
[E] Copying from recovery: sbin/chcon
[E] Copying from recovery: sbin/chgrp
[E] Copying from recovery: sbin/chmod
[E] Copying from recovery: sbin/chown
[E] Copying from recovery: sbin/chroot
[E] Copying from recovery: sbin/chvt
[E] Copying from recovery: sbin/clear
[E] Copying from recovery: sbin/cmp
[E] Copying from recovery: sbin/comm
[E] Copying from recovery: sbin/cp
[E] Copying from recovery: sbin/cpio
[E] Copying from recovery: sbin/crond
[E] Copying from recovery: sbin/crontab
[E] Copying from recovery: sbin/cut
[E] Copying from recovery: sbin/date
[E] Copying from recovery: sbin/dc
[E] Copying from recovery: sbin/dd
[E] Copying from recovery: sbin/deallocvt
[E] Copying from recovery: sbin/depmod
[E] Copying from recovery: sbin/devmem
[E] Copying from recovery: sbin/df
[E] Copying from recovery: sbin/diff
[E] Copying from recovery: sbin/dirname
[E] Copying from recovery: sbin/dmesg
[E] Copying from recovery: sbin/dnsd
[E] Copying from recovery: sbin/dos2unix
[E] Copying from recovery: sbin/du
[E] Copying from recovery: sbin/dump_image
[E] Copying from recovery: sbin/e2fsck
[E] Copying from recovery: sbin/echo
[E] Copying from recovery: sbin/ed
[E] Copying from recovery: sbin/egrep
[E] Copying from recovery: sbin/env
[E] Copying from recovery: sbin/erase_image
[E] Copying from recovery: sbin/exfat-fuse
[E] Copying from recovery: sbin/expand
[E] Copying from recovery: sbin/expr
[E] Copying from recovery: sbin/false
[E] Copying from recovery: sbin/fatlabel
[E] Copying from recovery: sbin/fbsplash
[E] Copying from recovery: sbin/fdisk
[E] Copying from recovery: sbin/fgconsole
[E] Copying from recovery: sbin/fgrep
[E] Copying from recovery: sbin/find
[E] Copying from recovery: sbin/findfs
[E] Copying from recovery: sbin/flash_image
[E] Copying from recovery: sbin/flash_lock
[E] Copying from recovery: sbin/flash_unlock
[E] Copying from recovery: sbin/flashcp
[E] Copying from recovery: sbin/flock
[E] Copying from recovery: sbin/fold
[E] Copying from recovery: sbin/free
[E] Copying from recovery: sbin/freeramdisk
[E] Copying from recovery: sbin/fsck.exfat
[E] Copying from recovery: sbin/fsck.f2fs
[E] Copying from recovery: sbin/fsck.fat
[E] Copying from recovery: sbin/fstrim
[E] Copying from recovery: sbin/fsync
[E] Copying from recovery: sbin/ftpget
[E] Copying from recovery: sbin/ftpput
[E] Copying from recovery: sbin/fuser
[E] Copying from recovery: sbin/getenforce
[E] Copying from recovery: sbin/getopt
[E] Copying from recovery: sbin/getprop
[E] Copying from recovery: sbin/getsebool
[E] Copying from recovery: sbin/grep
[E] Copying from recovery: sbin/groups
[E] Copying from recovery: sbin/gunzip
[E] Copying from recovery: sbin/gzip
[E] Copying from recovery: sbin/halt
[E] Copying from recovery: sbin/head
[E] Copying from recovery: sbin/healthd
[E] Copying from recovery: sbin/hexdump
[E] Copying from recovery: sbin/hwclock
[E] Copying from recovery: sbin/id
[E] Copying from recovery: sbin/ifconfig
[E] Copying from recovery: sbin/inetd
[E] Copying from recovery: sbin/insmod
[E] Copying from recovery: sbin/install
[E] Copying from recovery: sbin/ionice
[E] Copying from recovery: sbin/iostat
[E] Copying from recovery: sbin/ip
[E] Copying from recovery: sbin/kill
[E] Copying from recovery: sbin/killall
[E] Copying from recovery: sbin/killall5
[E] Copying from recovery: sbin/less
[E] Copying from recovery: sbin/libaosprecovery.so
[E] Copying from recovery: sbin/libbacktrace.so
[E] Copying from recovery: sbin/libblkid.so
[E] Copying from recovery: sbin/libbmlutils.so
[E] Copying from recovery: sbin/libc.so
[E] Copying from recovery: sbin/libcrecovery.so
[E] Copying from recovery: sbin/libcryptfslollipop.so
[E] Copying from recovery: sbin/libcrypto.so
[E] Copying from recovery: sbin/libcutils.so
[E] Copying from recovery: sbin/libdl.so
[E] Copying from recovery: sbin/libexfat_twrp.so
[E] Copying from recovery: sbin/libext2_blkid.so
[E] Copying from recovery: sbin/libext2_com_err.so
[E] Copying from recovery: sbin/libext2_e2p.so
[E] Copying from recovery: sbin/libext2_profile.so
[E] Copying from recovery: sbin/libext2_quota.so
[E] Copying from recovery: sbin/libext2_uuid.so
[E] Copying from recovery: sbin/libext2fs.so
[E] Copying from recovery: sbin/libext4_utils.so
[E] Copying from recovery: sbin/libflashutils.so
[E] Copying from recovery: sbin/libft2.so
[E] Copying from recovery: sbin/libfusesideload.so
[E] Copying from recovery: sbin/libgccdemangle.so
[E] Copying from recovery: sbin/libgpt_twrp.so
[E] Copying from recovery: sbin/libhardware.so
[E] Copying from recovery: sbin/liblog.so
[E] Copying from recovery: sbin/libm.so
[E] Copying from recovery: sbin/libminadbd.so
[E] Copying from recovery: sbin/libmincrypttwrp.so
[E] Copying from recovery: sbin/libminuitwrp.so
[E] Copying from recovery: sbin/libminzip.so
[E] Copying from recovery: sbin/libmmcutils.so
[E] Copying from recovery: sbin/libmtdutils.so
[E] Copying from recovery: sbin/libnetd_client.so
[E] Copying from recovery: sbin/libopenaes.so
[E] Copying from recovery: sbin/libpcre.so
[E] Copying from recovery: sbin/libpng.so
[E] Copying from recovery: sbin/libselinux.so
[E] Copying from recovery: sbin/libsparse.so
[E] Copying from recovery: sbin/libstdc++.so
[E] Copying from recovery: sbin/libstlport.so
[E] Copying from recovery: sbin/libtar.so
[E] Copying from recovery: sbin/libtwrpmtp.so
[E] Copying from recovery: sbin/libunwind-ptrace.so
[E] Copying from recovery: sbin/libunwind.so
[E] Copying from recovery: sbin/libusbhost.so
[E] Copying from recovery: sbin/libutil-linux.so
[E] Copying from recovery: sbin/libutils.so
[E] Copying from recovery: sbin/libz.so
[E] Copying from recovery: sbin/linker
[E] Copying from recovery: sbin/linker64
[E] Copying from recovery: sbin/ln
[E] Copying from recovery: sbin/load_policy
[E] Copying from recovery: sbin/losetup
[E] Copying from recovery: sbin/ls
[E] Copying from recovery: sbin/lsattr
[E] Copying from recovery: sbin/lsmod
[E] Copying from recovery: sbin/lspci
[E] Copying from recovery: sbin/lsusb
[E] Copying from recovery: sbin/lzcat
[E] Copying from recovery: sbin/lzma
[E] Copying from recovery: sbin/lzop
[E] Copying from recovery: sbin/lzopcat
[E] Copying from recovery: sbin/make_ext4fs
[E] Copying from recovery: sbin/man
[E] Copying from recovery: sbin/matchpathcon
[E] Copying from recovery: sbin/md5sum
[E] Copying from recovery: sbin/mesg
[E] Copying from recovery: sbin/mkdir
[E] Copying from recovery: sbin/mke2fs
[E] Copying from recovery: sbin/mkexfatfs
[E] Copying from recovery: sbin/mkfifo
[E] Copying from recovery: sbin/mkfs.exfat
[E] Copying from recovery: sbin/mkfs.ext2
[E] Copying from recovery: sbin/mkfs.f2fs
[E] Copying from recovery: sbin/mkfs.fat
[E] Copying from recovery: sbin/mknod
[E] Copying from recovery: sbin/mkswap
[E] Copying from recovery: sbin/mktemp
[E] Copying from recovery: sbin/modinfo
[E] Copying from recovery: sbin/modprobe
[E] Copying from recovery: sbin/more
[E] Copying from recovery: sbin/mount
[E] Copying from recovery: sbin/mount.exfat
[E] Copying from recovery: sbin/mountpoint
[E] Copying from recovery: sbin/mpstat
[E] Copying from recovery: sbin/mv
[E] Copying from recovery: sbin/nanddump
[E] Copying from recovery: sbin/nandwrite
[E] Copying from recovery: sbin/nbd-client
[E] Copying from recovery: sbin/nc
[E] Copying from recovery: sbin/netstat
[E] Copying from recovery: sbin/nice
[E] Copying from recovery: sbin/nmeter
[E] Copying from recovery: sbin/nohup
[E] Copying from recovery: sbin/nslookup
[E] Copying from recovery: sbin/ntpd
[E] Copying from recovery: sbin/od
[E] Copying from recovery: sbin/openaes
[E] Copying from recovery: sbin/openvt
[E] Copying from recovery: sbin/patch
[E] Copying from recovery: sbin/permissive.sh
[E] Copying from recovery: sbin/pgrep
[E] Copying from recovery: sbin/pidof
[E] Copying from recovery: sbin/pigz
[E] Copying from recovery: sbin/ping
[E] Copying from recovery: sbin/pipe_progress
[E] Copying from recovery: sbin/pkill
[E] Copying from recovery: sbin/pmap
[E] Copying from recovery: sbin/poweroff
[E] Copying from recovery: sbin/printenv
[E] Copying from recovery: sbin/printf
[E] Copying from recovery: sbin/ps
[E] Copying from recovery: sbin/pstree
[E] Copying from recovery: sbin/pwd
[E] Copying from recovery: sbin/pwdx
[E] Copying from recovery: sbin/r
[E] Copying from recovery: sbin/rdate
[E] Copying from recovery: sbin/rdev
[E] Copying from recovery: sbin/readlink
[E] Copying from recovery: sbin/realpath
[E] Copying from recovery: sbin/reboot
[E] Copying from recovery: sbin/recovery
[E] Copying from recovery: sbin/renice
[E] Copying from recovery: sbin/reset
[E] Copying from recovery: sbin/resize
[E] Copying from recovery: sbin/resize2fs
[E] Copying from recovery: sbin/restorecon
[E] Copying from recovery: sbin/rev
[E] Copying from recovery: sbin/rm
[E] Copying from recovery: sbin/rmdir
[E] Copying from recovery: sbin/rmmod
[E] Copying from recovery: sbin/route
[E] Copying from recovery: sbin/run-parts
[E] Copying from recovery: sbin/runcon
[E] Copying from recovery: sbin/rx
[E] Copying from recovery: sbin/sed
[E] Copying from recovery: sbin/selinuxenabled
[E] Copying from recovery: sbin/seq
[E] Copying from recovery: sbin/sestatus
[E] Copying from recovery: sbin/setconsole
[E] Copying from recovery: sbin/setenforce
[E] Copying from recovery: sbin/setfiles
[E] Copying from recovery: sbin/setkeycodes
[E] Copying from recovery: sbin/setprop
[E] Copying from recovery: sbin/setsebool
[E] Copying from recovery: sbin/setserial
[E] Copying from recovery: sbin/setsid
[E] Copying from recovery: sbin/sgdisk
[E] Copying from recovery: sbin/sh
[E] Copying from recovery: sbin/sha1sum
[E] Copying from recovery: sbin/sha256sum
[E] Copying from recovery: sbin/sha3sum
[E] Copying from recovery: sbin/sha512sum
[E] Copying from recovery: sbin/simg2img
[E] Copying from recovery: sbin/sleep
[E] Copying from recovery: sbin/smemcap
[E] Copying from recovery: sbin/sort
[E] Copying from recovery: sbin/split
[E] Copying from recovery: sbin/start
[E] Copying from recovery: sbin/stat
[E] Copying from recovery: sbin/stop
[E] Copying from recovery: sbin/strings
[E] Copying from recovery: sbin/stty
[E] Copying from recovery: sbin/sum
[E] Copying from recovery: sbin/swapoff
[E] Copying from recovery: sbin/swapon
[E] Copying from recovery: sbin/sync
[E] Copying from recovery: sbin/sysctl
[E] Copying from recovery: sbin/tac
[E] Copying from recovery: sbin/tail
[E] Copying from recovery: sbin/tar
[E] Copying from recovery: sbin/taskset
[E] Copying from recovery: sbin/teamwin
[E] Copying from recovery: sbin/tee
[E] Copying from recovery: sbin/telnet
[E] Copying from recovery: sbin/telnetd
[E] Copying from recovery: sbin/test
[E] Copying from recovery: sbin/tftp
[E] Copying from recovery: sbin/tftpd
[E] Copying from recovery: sbin/time
[E] Copying from recovery: sbin/timeout
[E] Copying from recovery: sbin/toolbox
[E] Copying from recovery: sbin/top
[E] Copying from recovery: sbin/touch
[E] Copying from recovery: sbin/tr
[E] Copying from recovery: sbin/traceroute
[E] Copying from recovery: sbin/true
[E] Copying from recovery: sbin/ttysize
[E] Copying from recovery: sbin/tune2fs
[E] Copying from recovery: sbin/twrp
[E] Copying from recovery: sbin/twrpdec
[E] Copying from recovery: sbin/ueventd
[E] Copying from recovery: sbin/umount
[E] Copying from recovery: sbin/uname
[E] Copying from recovery: sbin/uncompress
[E] Copying from recovery: sbin/unexpand
[E] Copying from recovery: sbin/uniq
[E] Copying from recovery: sbin/unix2dos
[E] Copying from recovery: sbin/unlzma
[E] Copying from recovery: sbin/unlzop
[E] Copying from recovery: sbin/unpigz
[E] Copying from recovery: sbin/unxz
[E] Copying from recovery: sbin/unzip
[E] Copying from recovery: sbin/uptime
[E] Copying from recovery: sbin/usleep
[E] Copying from recovery: sbin/uudecode
[E] Copying from recovery: sbin/uuencode
[E] Copying from recovery: sbin/vi
[E] Copying from recovery: sbin/watch
[E] Copying from recovery: sbin/watchdogd
[E] Copying from recovery: sbin/wc
[E] Copying from recovery: sbin/wget
[E] Copying from recovery: sbin/which
[E] Copying from recovery: sbin/whoami
[E] Copying from recovery: sbin/xargs
[E] Copying from recovery: sbin/xz
[E] Copying from recovery: sbin/xzcat
[E] Copying from recovery: sbin/yes
[E] Copying from recovery: sbin/zcat
[D] [Installer] Retrieve install type stage
[V] ROM ID: data-slot-2
[V] - /system: /data/multiboot/data-slot-2/system
[V] - /cache: /cache/multiboot/data-slot-2/cache
[V] - /data: /data/multiboot/data-slot-2/data
[V] - System is image file: false
[V] - Cache is image file: false
[V] - Data is image file: false
[V] ROM ID: data-slot-2
[D] [Installer] Chroot set up stage
[D] Boot partition SHA512sum: acf775300ddd7c76c0cb741a406b9417e8be14875072b838ca46077da16b0d5d50957e44c224deb4db0870b8b3348dae33611f7d5f4613696cf530402844ff63
[V] Won't switch to non-existent target ROM
[D] [Installer] Filesystem mounting stage
[D] /data/.system.img.tmp: Creating new 3221225472 ext4 image
[D] Running executable: make_ext4fs
[V] make_ext4fs: Creating filesystem with parameters:
[V] make_ext4fs: Size: 3221225472
[V] make_ext4fs: Block size: 4096
[V] make_ext4fs: Blocks per group: 32768
[V] make_ext4fs: Inodes per group: 8192
[V] make_ext4fs: Inode size: 256
[V] make_ext4fs: Journal blocks: 12288
[V] make_ext4fs: Label:
[V] make_ext4fs: Blocks: 786432
[V] make_ext4fs: Block groups: 24
[V] make_ext4fs: Reserved block group size: 191
[V] make_ext4fs: Created filesystem with 11/196608 inodes and 25785/786432 blocks
[V] Copying system to temporary image
[D] Assigning /data/.system.img.tmp to loop device /dev/block/loop1
[D] Clearing loop device /dev/block/loop1
[D] [Installer] Installation stage
[D] Property 'ro.bootloader' does not exist in recovery's default.prop
[D] - 'ro.bootloader'='unknown' will be set in chroot environment
[V] Running real update-binary
[V] Here we go!
[D] update-binary is AROMA: 0
[D] Original properties environment: 9,0
[D] Switched to legacy properties environment: 10,32768
Updating package '/mb/install.zip' ...
__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 updater on Wed Nov 16 15:10:49 2016
============= emmc ===============
name: BJNB4R
manfid: 0x000015
date: 06/2000
cid: 150100424a4e42345207cc4df4e36300
csd: d02701320f5903fff6dbffef8e404000
oemid: 0x0100
erase_size: 524288
preferred_erase_size: 524288
stat: 56259 133412 5378957 43770 11447 16792 969422 149170 0 33210 192860
============= prop ===============
ro.build.fingerprint=Xiaomi/omni_hydrogen/hydrogen:6.0.1/LYZ28J/3:eng/test-keys
ro.build.version.release=6.0.1
ro.build.version.incremental=3
ro.build.product=hydrogen
ro.product.device=hydrogen
ro.product.mod_device=unknown
ro.miui.ui.version.name=unknown
replace /file_contexts with file_contexts in package: No such file or directory
'/cust/app/customized/partner-XMRemoteController/partner-XMRemoteController.apk' doesn't exist
'/cust/app/customized/ota-miui-XiaomiSmartHome/ota-miui-XiaomiSmartHome.apk' doesn't exist
mount: failed to mount /dev/block/bootdevice/by-name/cust at /cust: No such file or directory
MountFn took 00s.
'/cust/app/customized/recommended-3rd-com.immomo.momo.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.immomo.momo/recommended-3rd-com.immomo.momo.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.juanpi.ui.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.juanpi.ui/recommended-3rd-com.juanpi.ui.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.qiyi.video.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.qiyi.video/recommended-3rd-com.qiyi.video.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.qzone.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.qzone/recommended-3rd-com.qzone.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.sina.weibo.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.sina.weibo/recommended-3rd-com.sina.weibo.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.tencent.qqmusic.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.tencent.qqmusic/recommended-3rd-com.tencent.qqmusic.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.tuniu.app.ui.apk' doesn't exist
'/cust/app/customized/recommended-3rd-com.tuniu.app.ui/recommended-3rd-com.tuniu.app.ui.apk' doesn't exist
'/cust/app/customized/recommended-3rd-tv.danmaku.bili.apk' doesn't exist
'/cust/app/customized/recommended-3rd-tv.danmaku.bili/recommended-3rd-tv.danmaku.bili.apk' doesn't exist
package_extract_dir took 00s.
ApplyParsedPerms: removexattr of /cust/cust/cn_cta/ota_recommended_applist to 0 failed: Operation not supported on transport endpoint
SetMetadataFn took 00s.
set_metadata_recursive: some changes failed
minzip: Extracted 24 file(s)
script aborted: set_metadata_recursive: some changes failed
device name: /dev/block/bootdevice/by-name/system
Filesystem volume name: <none>
Last mounted on: <not availabel>
Filesystem UUID: 57f8f4bc-abf4-655f-bf67-946fc0f9f25b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem flags: unsigned_directory_hash
Filesystem features: has_journal ext_attr resize_inode filetype extents sparse_super large_file gdt_csum
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem os type: Linux
Inode count: 196608
Block count: 786432
Reserved block count: 0
Free blocks: 760647
Free inodes: 196597
First block: 0
Block size: 4096
Reserved GDT blocks: 191
Blocks per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Last mount time: Wed Nov 16 15:10:48 2016
Last write time: Wed Nov 16 15:10:49 2016
Mount count: 1
Maximum mount count: 65535
Last checked: Thu Jan 1 00:00:00 1970
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
[D] Updater exited with status: 7
[V] Elapsed time: 0:00min
[V] Failed to run real update-binary
[D] Running executable: /update-binary-tool
[D] [Installer] Filesystem unmounting stage
[D] Running executable: /update-binary-tool
[D] Running executable: /update-binary-tool
[E] update-binary-tool: /cache: Failed to unmount: Invalid argument
[D] Running executable: /update-binary-tool
[E] update-binary-tool: /data: Failed to unmount: Invalid argument
[V] Copying temporary image to system
[D] Assigning /data/.system.img.tmp to loop device /dev/block/loop1
[D] Clearing loop device /dev/block/loop1
[D] [Installer] Cleanup stage
[V] Failed to flash zip file.
[V] Destroying chroot environment
[E] Failed to unmount /chroot/system: Invalid argument
[E] Failed to unmount /chroot/cache: Invalid argument
[E] Failed to unmount /chroot/data: Invalid argument
[E] Failed to unmount /chroot/efs: Invalid argument
[E] Failed to unmount /chroot: Device or resource busy
[D] Attempting to unmount /chroot/mb/install.zip
[D] Attempting to unmount /chroot/mb/bind.data
[D] Attempting to unmount /chroot/mb/bind.cache
[D] Attempting to unmount /chroot
[E] /efs is not mounted
[V] The log file was saved as MultiBoot.log on the internal storage.
[V] Finished cleanup
don't know why
And TWRP can't do flash patched zip image - always error.
pehoko said:
Patcher doesn't work:
Try all this first;
be sure runs Busy Box,
Set kernel for first rom,
Patch on Dual Slot Partition,
DBP patchs the file correctly?
Flash in TWRP, aparently your rom has Aroma Installer, when finish to flash (if it does) don`t reboot, go again to recovery, it execute some scripts, wait, and if it is possible go to file systems and delete RecoveryFromBoot file, now reboot. Anyway miui is some complicate, in some device don`t accept being secondary rom.
Click to expand...
Click to collapse
Busy box installed, zip patched as dataslot or whatever, don't have any aromas as I don't know how to use it or install it. TWRP doesn't flash roms (or patched zip as rom?) as this is officially not supported by this software.
Related
Hey everyone, I don't think this issue has come up. I get the following error when I try to apply the prep-dualboot-0.1.zip to my nook.
-- Installing: /sdcard/prep-dualboot-0.1.zip
Finding update package...
I:Update location: /sdcard/prep-dualboot-0.1.zip
Opening update package...
Installing update...
about to run program [/tmp/resize.sh] with 1 args
Prepare dual-boot partitions
Resize /media partition. This will take a while...
Fatal: Bad FAT: cluster 89718784 outside file system in chain for \.F. You should run dosfsck or scandisk.
run_program: child exited with status 1
about to run program [/tmp/create.sh] with 1 args
Create secondary boot /system and /data
Error: You requested a partition from 2311MB to 2681MB.
The closest location we can manage is 2311MB to 2311MB.
Error: Can't have overlapping partitions.
run_program: child exited with status 1
format: formatting "/dev/block/mmcblk0p9" as ext2
mke2fs: can't open '/dev/block/mmcblk0p9': No such file or directory
Format secondary boot /system partition
E:Error in /sdcard/prep-dualboot-0.1.zip
(Status 0)
Installation aborted.
Any ideas? I'm new to all this, but learning.
I am using multirom v8, with TWRP v2.4.1.0 on a Nexus 7 Wi-fi version. I have stock Android 4.2.1 (but with Tasssadar's kexec-hardboot kernel) as internal and Ubuntu 13.04.
I received the notification that the 4.2.2 update was available. So, I started to install it but it was unsuccessful. I do not remember but I think it said that update had failed and it rebooted.
So, I manually downloaded the update ( to update build JOP40D to JDQ39) and tried to install it using the modified recovery. Got the following error message (relevant parts):
I:Attempt to load settings from settings file...
I:Version number saved to '/cache/recovery/.version'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying current system...
contents of partition "/dev/block/platform/sdhci-tegra.3/by-name/LNX" didn't match EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd
file "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
E:Error in /sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
(Status 7)
Error flashing zip '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'
Updating partition details...
Any suggestions to fix this issue?
PS: I would have posted this here: http://forum.xda-developers.com/showpost.php?p=38043472&postcount=1157 but I do not have sufficient priviledges...
rigved said:
I am using multirom v8, with TWRP v2.4.1.0 on a Nexus 7 Wi-fi version. I have stock Android 4.2.1 (but with Tasssadar's kexec-hardboot kernel) as internal and Ubuntu 13.04.
I received the notification that the 4.2.2 update was available. So, I started to install it but it was unsuccessful. I do not remember but I think it said that update had failed and it rebooted.
So, I manually downloaded the update ( to update build JOP40D to JDQ39) and tried to install it using the modified recovery. Got the following error message (relevant parts):
I:Attempt to load settings from settings file...
I:Version number saved to '/cache/recovery/.version'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying current system...
contents of partition "/dev/block/platform/sdhci-tegra.3/by-name/LNX" didn't match EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd
file "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
E:Error in /sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
(Status 7)
Error flashing zip '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'
Updating partition details...
Any suggestions to fix this issue?
PS: I would have posted this here: http://forum.xda-developers.com/showpost.php?p=38043472&postcount=1157 but I do not have sufficient priviledges...
Click to expand...
Click to collapse
I think the problem is with bootloader (not sure) ...i had same multirom (cyanogenmod +Ubuntu ) ..i deleted ubuntu then flashed Stock 4.2.1 with wugstool then updated to 4.2.2 ... try updating bootloader
rigved said:
I am using multirom v8, with TWRP v2.4.1.0 on a Nexus 7 Wi-fi version. I have stock Android 4.2.1 (but with Tasssadar's kexec-hardboot kernel) as internal and Ubuntu 13.04.
I received the notification that the 4.2.2 update was available. So, I started to install it but it was unsuccessful. I do not remember but I think it said that update had failed and it rebooted.
So, I manually downloaded the update ( to update build JOP40D to JDQ39) and tried to install it using the modified recovery. Got the following error message (relevant parts):
I:Attempt to load settings from settings file...
I:Version number saved to '/cache/recovery/.version'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying current system...
contents of partition "/dev/block/platform/sdhci-tegra.3/by-name/LNX" didn't match EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd
file "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
E:Error in /sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
(Status 7)
Error flashing zip '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'
Updating partition details...
Any suggestions to fix this issue?
PS: I would have posted this here: http://forum.xda-developers.com/showpost.php?p=38043472&postcount=1157 but I do not have sufficient priviledges...
Click to expand...
Click to collapse
I *just* fixed this problem. Mine was failing on the same line. The trick is to modify the updater-script. I modified it to stop the check, and it flashed without a problem on my tablet. I also removed the sections where it replaced the recovery.
I'm hesitant to post mine because I was NOT running multiboot, so when it patched the bootloader regardless of the checksum, I was fine (Or lucky). I don't know what will happen if you use the one I modified, or if 4.2.1 CAN be updated safely without touching the bootloader.
So here: This script is very untested, and modified by someone who doesn't fully understand what he did. Use this at your own risk, and realize I hold no responsibility if you brick your N7..
That said, if you replace the 'updater-script' in the update zip (located in META-ING/com/google/android) with this one, it will patch.
The LNX partition is the boot partition.
That check is failing because when the script looks at the existing LNX partition (boot), it does not find what it expects to find.
The OTA patches existing files, it doesn't replace them with a full replacement copy. So the starting condition of each file to be patched must be exact.
I believe that the check of the LNX partition is the very last checksum verified, so that is good news - it means nothing else checked in /system is mismatched.
You can either hack the installer script as above (and thus need to use a custom recovery to install it because this will break the signing of the factory package), or you can use a completely safe route:
- make full Nandroid backup (including recovery if possible)
- flash the stock 4.2.1 boot image ( not bootloader! ) to the boot partition
- copy the factory ota .zip file to /cache/update.zip
- create a file named "command" with a single line in it:
--update_package=/cache/update.zip
and copy it to /cache/recovery/command
- flash the stock 4.2.1 recovery to the recovery partition
- reboot to recovery
This runs the pure stock OTA install which does all the patching plus installs a new 4.18 bootloader, 4.2.2 boot partition, and 4.2.2 stock recovery.
Before you get too antsy bear in mind that this whole situation is likely to happen again with the next OTA - meaning, it would be a great time to get a backup of pure stock 4.2.2 (including stock recovery and stock boot partition).
So, now:
- perform a soft boot of a custom recovery (don't flash it in place just yet!)
- overflash a SuperSU/Superuser root kit
- make a Nandroid Backup of this entire "lightly rooted pure stock 4.2.2 ROM" - including the recovery partition!
- hard-flash your custom recovery
- restore only the boot partition from the first Nandroid backup described in these instructions.
cheers
I had a few issues and long story short my Nexus 4 will not boot correctly.
I am trying to sideload image-occam-krt16s.zip onto it. I have no problem transferring the file, but when it goes to install it errors
here is what the log reads:
Finding update package...
I: Update location: /tmp/update.zip
Opening update package...
Installing update...
Insallation aborted.
I:Can't partition non-vfat: datamedia
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /ennc
Any ideas on what I need to do?
thanks!
Sideload isn't going to work for you just flash a stock image through fastboot.
This seems to be an old problem.
My VS980 is on TWRP v2.8.0.1, and I see there is a newer TWRP from the official site: openrecovery-twrp-2.8.1.0-vs980.zip
So I downloaded that and put it on sdcard, by "installing" this zip, the error was as follows:
Code:
Installing '/usb_otg/ROM/openrecovery-twrp-2.8.1.0-vs980.zip'...
Checking for MD5 file...
MD5 matched
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
*******************************
* TWRP Recovery by Dees_Troy *
*******************************
minzip: Extracted file "/tmp/loki.sh"
minzip: Extracted file "/tmp/loki/loki_flash"
minzip: Extracted file "/tmp/loki/loki_patch"
about to run program [/tmp/loki.sh] with 1 args
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.033627 seconds, 29.7MB/s
[+] loki_patch v2.1
[-] Unsupported aboot image.
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/loki.sh") == 0
assert failed: run_program("/tmp/loki.sh") == 0
Is it because my aboot is already lokified? Or am I doing the upgrade wrong?
Hi everyone, I just want to let you all know that chenxiaolong has added support for our wonderful device to his Dual Boot Patcher so now we can all enjoy multi-boot.
Here is his thread:
http://forum.xda-developers.com/showthread.php?t=2447534
Bugs: for now updating ramdisk on lokjianming's CM12.1 breaks the microSD card access but it seems to be fine on MIUI android 5.0 and AOSP 5.0 (vova.vafin's one), did not test on other 5.1.1 ROMs and also I have my microSD card as ext4 since I have a 64GB one (so need to mount using Redmi Note 2 Tool on most ROMs), do not know if other formats will work fine but they might. I have already reported the bug and posted logs.
EDIT: Actually you can also mount the microSD card on the latest nightly of CM12.1 using Redmi Note 2 Tool but it will no longer mount it automatically but on older versions (the one I tried before was before the latest update server was made) that did also not work.
This is Awesome now i dont need to wipe everything to test new Roms. Thank you for sharing this
Can you write new thread about how to install this?
Wysłane z mojego Redmi Note 2 przy użyciu Tapatalka
Piorek99 said:
Can you write new thread about how to install this?
Wysłane z mojego Redmi Note 2 przy użyciu Tapatalka
Click to expand...
Click to collapse
The app should be pretty straight forward but here is something of a tutorial:
Download the android apk.
Install the android apk onto your phone.
Open it and go to the ROMS section and grant root.
Click on the 3 dots next to the Primary ROM.
Click update ramdisk.
Don't reboot when it asks, instead click set kernel.
Go to the Patch zip section to select one/multiple flashable zip files to patch.
Select your zip files and for what slot to patch them for (note: for some reason even with pico/nano GAPPS with CM12.1 we do not have enough space to have two ROMs on /system, ie: no dual slot and nor do we have enough space to have any ROM in the multi-slots which are saved on the cache partition so instead use a /data or extsd slot).
Patch your zip files (could take a while depending on the ROM type/s and number of them.
Now to flash your zip files either reboot to recovery and flash the zip files normally or go back to the ROMS section and click the little download button on the bottom right and click flash zip files, select your files (note: you CAN'T flash zip files meant for the slot you are booted in from within the app, ie: if you are booted in your /system ROM as you will probably be you can't flash any zip file meant for the primary slot, you will still need to reboot in recovery/boot an other ROM for that) and flash them.
Reboot and you should be in your other ROM, to switch ROMs you need to install the dual boot patcher in all your ROMs but you do not need to have root in all of them, just patch the zip file before flashing it and it should not require root for anything.
You can also do individual ROM wipes/switching from either withing the app, in the ROMS section, or using the flashable dual boot utilities zip.
Nice
Hi there,
thanks for this great opportunity but unfortunately does not work here.
Setting Kernel did work.
Update ram disk fails.
Patching a flashable zip does work (used secondary as slot).
Flashing patched zip from within app fails with following output (MultiBoot.log):
[D] Initialized installer for zip file: /mnt/shell/emulated/0/Download/ResurrectionRemix-M-v5.7.4-20161119-hermes_dual.zip
[D] Installer version: 9.2.0.r88.g35a35a6 (v9.2.0-88-g35a35a6b)
[D] [Installer] Initialization stage
[D] [Installer] Chroot creation stage
[V] Creating chroot environment
[D] Running executable: mount
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Running executable: mount
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Running executable: mount
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Running executable: mount
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Not mounting EFS partition because this is not a Samsung device
[D] [Installer] Environment set up stage
[D] [Installer] Device verification stage
[D] ro.product.device = hermes
[D] ro.build.product = hermes
[D] ro.patcher.device =
[D] Target device = hermes
[D] Boot block device: /dev/block/platform/mtk-msdc.0/by-name/boot
[D] Recovery block device: /dev/block/platform/mtk-msdc.0/by-name/recovery
[D] System block device: /dev/block/platform/mtk-msdc.0/by-name/system
[E] /dev/block/bootdevice/by-name/boot: Failed to stat: No such file or directory
[W] Failed to copy /dev/block/bootdevice/by-name/boot. Continuing anyway
[D] Copied /dev/block/platform/mtk-msdc.0/by-name/boot to the chroot
[D] Copied /dev/block/mmcblk0p7 to the chroot
[E] /dev/block/bootdevice/by-name/recovery: Failed to stat: No such file or directory
[W] Failed to copy /dev/block/bootdevice/by-name/recovery. Continuing anyway
[D] Copied /dev/block/platform/mtk-msdc.0/by-name/recovery to the chroot
[D] Copied /dev/block/mmcblk0p8 to the chroot
[D] Copied /dev/block/platform/mtk-msdc.0/by-name/lk to the chroot
[D] Copied /dev/block/mmcblk0p6 to the chroot
[D] Copied /dev/block/platform/mtk-msdc.0/by-name/logo to the chroot
[D] Copied /dev/block/mmcblk0p11 to the chroot
[D] Copied /dev/block/mmcblk0boot0 to the chroot
[D] Symlinked /mb/loop.system to /chroot/dev/block/bootdevice/by-name/system
[D] Symlinked /mb/loop.system to /chroot/dev/block/platform/mtk-msdc.0/by-name/system
[D] Symlinked /mb/loop.system to /chroot/dev/block/mmcblk0p15
[E] Failed to open archive: Unrecognized archive format
[V] Failed to extract recovery ramdisk
[D] [Installer] Cleanup stage
[V] Failed to flash zip file.
[V] Destroying chroot environment
[E] Failed to restore boot partition: No such file or directory
[V] Failed to restore boot partition
[E] Failed to unmount /chroot/system: Invalid argument
[E] Failed to unmount /chroot/cache: Invalid argument
[E] Failed to unmount /chroot/data: Invalid argument
[E] Failed to unmount /chroot/efs: Invalid argument
[E] /efs is not mounted
[V] The log file was saved as MultiBoot.log on the internal storage.
[V] Finished cleanup
Any ideas and hints welcome!
Ok, today I got a little bit further but could still not finish it successfully.
Error: Failed to copy /data/.system.img.tmp to /system/multiboot/dual/system
Any idea?
Logfile attached.
Seems mounting FS as rw does not work properly - still a bug?
Finally got it working using data slot and TWRP flashing.
After installing latest MIUI and afterwards downgrading it again both in Primary Slot I cannot boot into data slot ROM anymore. After switching to this ROM in DualBootPatcher and choosing Reboot I boot into normal MIUI again.
Any idea what went wrong here?
Renth said:
Hi there,
thanks for this great opportunity but unfortunately does not work here.
Setting Kernel did work.
Update ram disk fails.
Patching a flashable zip does work (used secondary as slot).
Flashing patched zip from within app fails with following output (MultiBoot.log):
[D] Initialized installer for zip file: /mnt/shell/emulated/0/Download/ResurrectionRemix-M-v5.7.4-20161119-hermes_dual.zip
[D] Installer version: 9.2.0.r88.g35a35a6 (v9.2.0-88-g35a35a6b)
[D] [Installer] Initialization stage
[D] [Installer] Chroot creation stage
[V] Creating chroot environment
[D] Running executable: mount
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Running executable: mount
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Running executable: mount
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Running executable: mount
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Not mounting EFS partition because this is not a Samsung device
[D] [Installer] Environment set up stage
[D] [Installer] Device verification stage
[D] ro.product.device = hermes
[D] ro.build.product = hermes
[D] ro.patcher.device =
[D] Target device = hermes
[D] Boot block device: /dev/block/platform/mtk-msdc.0/by-name/boot
[D] Recovery block device: /dev/block/platform/mtk-msdc.0/by-name/recovery
[D] System block device: /dev/block/platform/mtk-msdc.0/by-name/system
[E] /dev/block/bootdevice/by-name/boot: Failed to stat: No such file or directory
[W] Failed to copy /dev/block/bootdevice/by-name/boot. Continuing anyway
[D] Copied /dev/block/platform/mtk-msdc.0/by-name/boot to the chroot
[D] Copied /dev/block/mmcblk0p7 to the chroot
[E] /dev/block/bootdevice/by-name/recovery: Failed to stat: No such file or directory
[W] Failed to copy /dev/block/bootdevice/by-name/recovery. Continuing anyway
[D] Copied /dev/block/platform/mtk-msdc.0/by-name/recovery to the chroot
[D] Copied /dev/block/mmcblk0p8 to the chroot
[D] Copied /dev/block/platform/mtk-msdc.0/by-name/lk to the chroot
[D] Copied /dev/block/mmcblk0p6 to the chroot
[D] Copied /dev/block/platform/mtk-msdc.0/by-name/logo to the chroot
[D] Copied /dev/block/mmcblk0p11 to the chroot
[D] Copied /dev/block/mmcblk0boot0 to the chroot
[D] Symlinked /mb/loop.system to /chroot/dev/block/bootdevice/by-name/system
[D] Symlinked /mb/loop.system to /chroot/dev/block/platform/mtk-msdc.0/by-name/system
[D] Symlinked /mb/loop.system to /chroot/dev/block/mmcblk0p15
[E] Failed to open archive: Unrecognized archive format
[V] Failed to extract recovery ramdisk
[D] [Installer] Cleanup stage
[V] Failed to flash zip file.
[V] Destroying chroot environment
[E] Failed to restore boot partition: No such file or directory
[V] Failed to restore boot partition
[E] Failed to unmount /chroot/system: Invalid argument
[E] Failed to unmount /chroot/cache: Invalid argument
[E] Failed to unmount /chroot/data: Invalid argument
[E] Failed to unmount /chroot/efs: Invalid argument
[E] /efs is not mounted
[V] The log file was saved as MultiBoot.log on the internal storage.
[V] Finished cleanup
Any ideas and hints welcome!
Click to expand...
Click to collapse
How did you get pass the "Failed to extract recovery ramdisk" error ?
Hi there,
sorry - but do not have this setup anymore. Reinstalled dualboot and another RRemix lately and it works fine so far.
But I do not use it since I want to have only one installation of all of my apps and having one set of data for them (like messangers, browser, navigation etc).
So I am still within MIUI (while this one stucks more and more - but maybe due to the Theme I use).
** TO ALL THOSE WHO HAD A PROBLEM **
Try to install dual boot patcher version 9.1 it worked like charm for me
Unfortunately DualBootPatcher can no longer been downloaded. If I go to the section where all previous builds are stored I can click on any of these files (either patcher or utilities) and can select any of the provided mirrors => no download is starting. Only the file is chosen and a new sites opened but the countdown stays at 5 forever!
Is there any way to download latest version pf DBP and utilities from somewhere else?