Tried flashing firmware upgrade on I747.
File corruption error occurs.
Log File from TWRP (1)
Running boot script...
I:/sbin/postrecoveryboot.sh process ended with RC=0
Finished running boot script.
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/data/media/0/TWRP/.twrps'.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/ce166490'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
I:TWFunc::Fixup_Time: Setting time offset from file /data/time/ats_2, offset 1390591287137
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/I747_UCUFNE4_Base_Firmware.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/I747_UCUFNE4_Base_Firmware.zip.md5
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
I:read key e=3 hash=20
I:read key e=65537 hash=20
I:2 key(s) loaded from /res/keys
E:footer is wrong
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/I747_UCUFNE4_Base_Firmware.zip'
Updating partition details...
Iata backup size is 3245MB, free: 3053MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/I747_UCUFNE4_Base_Firmware.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/I747_UCUFNE4_Base_Firmware.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
Log File from TWRP (2)
I747 UCUFNE4 Base Firmware
Preparing to Flash!
Extracting files and setting permissions...
minzip: Extracted file "/tmp/NON-HLOS.bin"
minzip: Extracted file "/tmp/aboot.mbn"
minzip: Extracted file "/tmp/dd"
minzip: Extracted file "/tmp/rpm.mbn"
minzip: Extracted file "/tmp/sbl2.mbn"
minzip: Extracted file "/tmp/sbl3.mbn"
minzip: Extracted file "/tmp/tz.mbn"
Verifying checksums...
FILE CORRUPTION DETECTED!!!
ABORTING FLASH.......
Cleaning up...
script result was [7]
Updating partition details...
Iata backup size is 3245MB, free: 3053MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Forgot to say the phone is an I747 ATT. Running TWRP 2.7.1
Did you check the md5sum on the download? The NE4 package has been confirmed working.
Yes. The md5 did check out. It was correct.
One other note. When trying to install on TWRP. I checked the zip signature box, and i did receive the error message zip signature failed.
...
Dumb question can I flash through mobile odin, using the OTA/update ZIP file option. All other options require a .tar file
Thanks for any help.
Currently I'm parsing the updater-script and rechecked all of the sha1 checksums and they are all processing correctly. At least on the pc they are.
So I checked the md5 on the pc transfered the file to the phone and rechecked the md5.
All is good. So I know the file on the phone is the same as the file on the pc. Hence the checksums on the phone are correct.
So it leads me to believe the problem could be in the directory or file permissions??
I'm relatively new to this field, but I can tell you with 100% definition that the checksums are correct and the md5 file is 100% correct. At least on the pc they are.
Try using twrp 2.6.3.1, or maybe philz recovery. Could be a compatibility issue between the recovery and update binary.
DocHoliday77 said:
Try using twrp 2.6.3.1, or maybe philz recovery. Could be a compatibility issue between the recovery and update binary.
Click to expand...
Click to collapse
OK. I have new information to report back. (To Repeat I've checked the md5)
I flashed
twrp 2.6.3.1 ->File Corruption Detected
Philz Recover ->File Corruption Detected
CWM 6.0.4.7 -> File Corruption Detected
However on CWM when I click show log
I get
Install from sdcard complete.
I:using /data/media for /sdcard/0/clockworkmod/.last_install_path.
I:Can't partition non mmcblk device:/devices/platform/msm_sdoc.3/mmc_host/mmc1
Just rechecked...
Received the same exact error message through Philz Recovery. (in the log)
I've also run the Fix Permisions Tool. (In case the problem was a permision) However same outcome.
Any other ideas greatly appreciated.
Thanks to Doc for all the help also.
Non mmcblk device?!!!? Never seen that before, and it is wrong! The S3 is an mmcblk device! If you use a root capable file manager you can browse to /dev/block and you will see all the different mmcblk0p* partitions.
I hate to say it but i have no idea what could be going on. I hope someone else might have an idea. I am sorry for all the trouble. Hopefully we will figure it out soon. Ill try to find a different update-binary to see if that might help...
Hi guys!
I'm running a rootd Android KitKat, after unrooting the device and downloading the OTA file and trying to running it through TWRP since I couldnt update it automatically. But I get this error, what am I doing wrong? Kindly help!
Thanks.
PHP:
Installing '/external_sd/OTA.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.
load_volume_table(): failed to read /etc/recovery.fstab
I:emmc_scan_partitions:[partition_count:0] [allocat_num:128]
load_volume_table_v1(): Can't get the /proc/emmc table
main(): parse version 1 recovery.fstab
L50QCT.01.401.016
ensure_path_mounted(): unknown volume for path [/system]
ensure_path_mounted_v1(): unknown volume for path [/system]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: File exists
ensure_path_mounted(): unknown volume for path [/data]
ensure_path_mounted_v1(): unknown volume for path [/data]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: File exists
script aborted: Package expects build fingerprint of htc/htc_europe/htc_a5dug:4.4.2/KOT49H/408055.11:user/release-keys or htc/htc_europe/htc_a5dug:5.0.2/LRX22G/510432.1:user/release-keys; this device has htc/omni_a5/a5:4.4.4/KTU84P/eng.dees_troy.20150212.043028:eng/test-keys.
Package expects build fingerprint of htc/htc_europe/htc_a5dug:4.4.2/KOT49H/408055.11:user/release-keys or htc/htc_europe/htc_a5dug:5.0.2/LRX22G/510432.1:user/release-keys; this device has htc/omni_a5/a5:4.4.4/KTU84P/eng.dees_troy.20150212.043028:eng/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/OTA.zip'
Error flashing zip '/external_sd/OTA.zip'
Updating partition details...
I:Data backup size is 67MB, free: 4006MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log
Izz0_ said:
Hi guys!
I'm running a rootd Android KitKat, after unrooting the device and downloading the OTA file and trying to running it through TWRP since I couldnt update it automatically. But I get this error, what am I doing wrong? Kindly help!
Thanks.
PHP:
Installing '/external_sd/OTA.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.
load_volume_table(): failed to read /etc/recovery.fstab
I:emmc_scan_partitions:[partition_count:0] [allocat_num:128]
load_volume_table_v1(): Can't get the /proc/emmc table
main(): parse version 1 recovery.fstab
L50QCT.01.401.016
ensure_path_mounted(): unknown volume for path [/system]
ensure_path_mounted_v1(): unknown volume for path [/system]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: File exists
ensure_path_mounted(): unknown volume for path [/data]
ensure_path_mounted_v1(): unknown volume for path [/data]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: File exists
script aborted: Package expects build fingerprint of htc/htc_europe/htc_a5dug:4.4.2/KOT49H/408055.11:user/release-keys or htc/htc_europe/htc_a5dug:5.0.2/LRX22G/510432.1:user/release-keys; this device has htc/omni_a5/a5:4.4.4/KTU84P/eng.dees_troy.20150212.043028:eng/test-keys.
Package expects build fingerprint of htc/htc_europe/htc_a5dug:4.4.2/KOT49H/408055.11:user/release-keys or htc/htc_europe/htc_a5dug:5.0.2/LRX22G/510432.1:user/release-keys; this device has htc/omni_a5/a5:4.4.4/KTU84P/eng.dees_troy.20150212.043028:eng/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/OTA.zip'
Error flashing zip '/external_sd/OTA.zip'
Updating partition details...
I:Data backup size is 67MB, free: 4006MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log
Click to expand...
Click to collapse
Read This post
http://forum.xda-developers.com/desire-816/help/how-to-install-ota-update-t3097232
Can't update ota through twrp. Or any custom recovery
.you need to flash the stock recovery..
Then relock bootloader..
slkpmp said:
Can't update ota through twrp. Or any custom recovery
.you need to flash the stock recovery..
Then relock bootloader..
Click to expand...
Click to collapse
Hey! Thanks for you reply, I've tried flashing the stock recovery via fastboot and this is what happenedm what do you suggest I do?
PHP:
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.016s]
finished. total time: 0.018s
C:\adb>fastboot flash zip OTA_A5_DUG_L50_DESIRE_SENSE60_MR_HTC_Europe_2.34.401.1
-1.58.401.11_release_426622iqqf91v0oa9sb1r9.zip
sending 'zip' (859807 KB)...
OKAY [ 32.227s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 37.386s
sheenobis said:
Read This post
http://forum.xda-developers.com/desire-816/help/how-to-install-ota-update-t3097232
Click to expand...
Click to collapse
Thanks for your reply but I couldn't understand the 3rd and 4th steps in the first method!
Appears your trying to flash the ota not just the stock recovery..
The goal is to
1 unroot
2 flash stock recovery
3 relock bootloader..
4 reboot..accept..download..and update OTA
or run the RUU.exe program let it convert you back to stock unrooted..
I have he a5-chl .and these were the steps I needed.
your phone may be diffrent..
slkpmp said:
Appears your trying to flash the ota not just the stock recovery..
The goal is to
1 unroot
2 flash stock recovery
3 relock bootloader..
4 reboot..accept..download..and update OTA
or run the RUU.exe program let it convert you back to stock unrooted..
I have he a5-chl .and these were the steps I needed.
your phone may be diffrent..
Click to expand...
Click to collapse
Thanks for you reply! How to run an RUU program? Thanks!
{
"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..