Related
0
down vote
favorite
I've been trying to install cyanogen 12.1 on my Moto X 2013.
Followed all the steps mentioned in the official Cyanogen Mod Wiki (Allowed to include the link only after 10 posts)
Flew through the steps however, the final flash of ROM fails.
Here are the logs.
Installing '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghos
t_att,ghost_rcica,xt1060,ghost_verizon; this device is .
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcic
a,xt1060,ghost_verizon; this device is .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Error flashing zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Looking at the bold face logs, my hunch is the TWRP isn't able to recognize my device's model XT1052.
Is this what's happening here? If no, what seems to be going wrong?
How do I fix this?
[email protected] said:
0
down vote
favorite
I've been trying to install cyanogen 12.1 on my Moto X 2013.
Followed all the steps mentioned in the official Cyanogen Mod Wiki (Allowed to include the link only after 10 posts)
Flew through the steps however, the final flash of ROM fails.
Here are the logs.
Installing '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghos
t_att,ghost_rcica,xt1060,ghost_verizon; this device is .
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcic
a,xt1060,ghost_verizon; this device is .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Error flashing zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Looking at the bold face logs, my hunch is the TWRP isn't able to recognize my device's model XT1052.
Is this what's happening here? If no, what seems to be going wrong?
How do I fix this?
Click to expand...
Click to collapse
Which version of TWRP are you using? Try 3.x, some of the older ones aren't working correctly.
Or alternatively, edit the "updater_script" in the ROM zip (META-INF/com/google/android), and delete the first line, starting with "assert(getprop.."
rumkugel13 said:
Which version of TWRP are you using? Try 3.x, some of the older ones aren't working correctly.
Or alternatively, edit the "updater_script" in the ROM zip (META-INF/com/google/android), and delete the first line, starting with "assert(getprop.."
Click to expand...
Click to collapse
Been using twrp-2.8.7.0-ghost
twep 3.x.x isn't released for Moto X 2013 (Ghost) yet. I tried using twrp-3.0.0.0-victaria built for Moto X 2014(Victaria), however, the phone never booted into recovery.
Also tried out removing the first line from the updater script which checks for models just as you suggested.
The flash still fails. This time with barely any logs
just says Error occurred while.. Fail
Double checked the versions(of everything) but it still isn't working.
I've had simular issue . download twrp 2.6.3.1 ... worked for me and many others
Polishpolisher said:
I've had simular issue . download twrp 2.6.3.1 ... worked for me and many others
Click to expand...
Click to collapse
Didn't work out for me. Flash just fails without any useful logs
You've probably applied compression when you've changed the updste script. It should be Store only, try again, because the error you were getting is exactly from the get prop in the first line.
[email protected] said:
0
down vote
favorite
I've been trying to install cyanogen 12.1 on my Moto X 2013.
Followed all the steps mentioned in the official Cyanogen Mod Wiki (Allowed to include the link only after 10 posts)
Flew through the steps however, the final flash of ROM fails.
Here are the logs.
Installing '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghos
t_att,ghost_rcica,xt1060,ghost_verizon; this device is .
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcic
a,xt1060,ghost_verizon; this device is .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Error flashing zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Looking at the bold face logs, my hunch is the TWRP isn't able to recognize my device's model XT1052.
Is this what's happening here? If no, what seems to be going wrong?
How do I fix this?
Click to expand...
Click to collapse
First i installed cm-12.1-20150901-SNAPSHOT-YOG4PAO237-ghost.zip then i flashed CM Recovery cm-12.1-20150901-SNAPSHOT-YOG4PAO237-ghost-recovery.img then i updated the CM by the CM Updater inside the settings and it worked great !!
Hi,
I had same issue.
My Moto X 2013 had still Android 4.4.2 as I rooded it.
Then I tried to flash CM12.1 with instuctions from wiki.cyanogenmod.org and failed with same error message as [email protected]
I tried several things mentioned here and from other forums but failed.
At least the hint from Polishpolisher was working. Many many thanks!
Found twrp-2.6.3.1-ghost-4.4.img at rootjunkysdl.com.
Herewith install of cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip was possible.
Had the same issue..
Here's what you do..
Extract the cm 12.1 file and file update script file in there ( look for it it's in there in Android or Google folder ) then delete the first line in the script " JUST THE FIRST LINE "
And voilà
Enjoy CM 12.1
I've had the same problem. The solution for me was to install the rom stock using the RSD. Then I installed the latest official version of TWRP and had no problems.
Dear all,
I currently use the Minotaurus S8 Port V11.0 (pre-rooted ROM) on a Samsung S7 Edge.
During the installation I chose SuperSU.
Now I'd like to switch to MagiskSU - if possible without flashing the complete ROM one again.
Nevertheless my efforts currently are not successful.
I read that I have to unroot first what I did with using osm0sis unSU. This worked and root was gone.
Trying then to install Magisk (v12) ended up with an error:
****************************************
Magisk v12.0 Boot Image Patcher
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking patch status
- SuperSU patched boot detected!
- Adding ramdisk patch script for SuperSU
- We are using SuperSU's own tools, mounting su.img
! SuperSU image mount failed...
! Magisk scripts are placed correctly
! Flash SuperSU immediately to finish installation
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v12.0.zip'
Updating partition details...
...done
Then I installed SuperSU v2.82 again which brought back root (with SuperSU).
I tried to flash Magisk v13.0 (96f8efc) but again end up in an error:
****************************************
Magisk v13.0 (96f8efc) Installer
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v13.0(96f8efc).zip'
Updating partition details...
...done
Is anybody able to help me and give me some guidance to get MagiskSU (with v13.0)
Thank you in advance,
Best regards,
MarkusTh
Besides flashing the unSU script you'll need to also flash a boot image without the SuperSU patches. That's gonna be an issue on a pre-rooted ROM. You say you chose SuperSU during installation? Did you have any other options (Magisk or no root)? If so, reinstall the ROM and make a different choice.
Didgeridoohan said:
Besides flashing the unSU script you'll need to also flash a boot image without the SuperSU patches. That's gonna be an issue on a pre-rooted ROM. You say you chose SuperSU during installation? Did you have any other options (Magisk or no root)? If so, reinstall the ROM and make a different choice.
Click to expand...
Click to collapse
Thanks for the quick answer.
Yes, the other options mentioned by you are available.
Is it possible to do a "dirty" flash over the current ROM without having to reinstall everything again afterwards ?
If yes, I assume the steps would be:
1) "dirty" flash of original ROM with choosing "MagiskSU" or "no root"
2) reboot necessary ?
3) flashing Magisk v13
4) reboot and ready ?
That easy ?
Thx,
MarkusTh
Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.
Maik268 said:
Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.
Click to expand...
Click to collapse
Thanks so much for this!! I would have been in a mess without this method which worked perfectly on my Samsung GS6. Thanks.
MarkusTh said:
Dear all,
I currently use the Minotaurus S8 Port V11.0 (pre-rooted ROM) on a Samsung S7 Edge.
During the installation I chose SuperSU.
Now I'd like to switch to MagiskSU - if possible without flashing the complete ROM one again.
Nevertheless my efforts currently are not successful.
I read that I have to unroot first what I did with using osm0sis unSU. This worked and root was gone.
Trying then to install Magisk (v12) ended up with an error:
****************************************
Magisk v12.0 Boot Image Patcher
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking patch status
- SuperSU patched boot detected!
- Adding ramdisk patch script for SuperSU
- We are using SuperSU's own tools, mounting su.img
! SuperSU image mount failed...
! Magisk scripts are placed correctly
! Flash SuperSU immediately to finish installation
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v12.0.zip'
Updating partition details...
...done
Then I installed SuperSU v2.82 again which brought back root (with SuperSU).
I tried to flash Magisk v13.0 (96f8efc) but again end up in an error:
****************************************
Magisk v13.0 (96f8efc) Installer
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v13.0(96f8efc).zip'
Updating partition details...
...done
Is anybody able to help me and give me some guidance to get MagiskSU (with v13.0)
Thank you in advance,
Best regards,
MarkusTh
Click to expand...
Click to collapse
Mate, just unroot from supersu as you did earlier, then copy original boot image to internal memory, boot into TWRP, flash original boot image and then flash Magisk. It should work now.
atf2m4 said:
Mate, just unroot from supersu as you did earlier, then copy original boot image to internal memory, boot into TWRP, flash original boot image and then flash Magisk. It should work now.
Click to expand...
Click to collapse
I got the same issue and I tried to fix that but I don't know where the original boot image is located respectively where can I get the orginal boot image back? Could you help me out with my Samsung S8?
Thanks a bunch!
cocolish said:
I got the same issue and I tried to fix that but I don't know where the original boot image is located respectively where can I get the orginal boot image back? Could you help me out with my Samsung S8?
Thanks a bunch!
Click to expand...
Click to collapse
SOLVED! I managed to extract the boot.img from the original Samsung firmware and flashed the original boot.img via TWRP!
Maik268 said:
Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.
Click to expand...
Click to collapse
Im having a similar problem. i have an lgms550. my problem is when i flash the stock boot img, magisk still states unable to mount. im not sure whats wrong here
So, I got a Huawei P9 (L09) and want to UnSU as well to install Magisk.
I once took apart an update file and therefore also have a boot.img from this package.
Is this file the one I would need to restore my boot partition on this phone?
If so, then I got super lucky here.
I am on J7 Prime (SM-G610F) the issue is I'm on the stock Nougat ROM which comes in a .tar.md5 format which I don't know how to disassemble.
The .md5 files are in fact .TAR files with the MD5 sum appended at the end.
If you rename each .md5 to a .tar file, they can be unpacked with 7zip or Winrar.
Can someone please please help me. I have j7 prime with supersu & trying to move on magisk but it says boot image is patched by another program. I'm soo tired with this issue please help me.
MarkusTh said:
Dear all,
I currently use the Minotaurus S8 Port V11.0 (pre-rooted ROM) on a Samsung S7 Edge.
During the installation I chose SuperSU.
Now I'd like to switch to MagiskSU - if possible without flashing the complete ROM one again.
Nevertheless my efforts currently are not successful.
I read that I have to unroot first what I did with using osm0sis unSU. This worked and root was gone.
Trying then to install Magisk (v12) ended up with an error:
****************************************
Magisk v12.0 Boot Image Patcher
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking patch status
- SuperSU patched boot detected!
- Adding ramdisk patch script for SuperSU
- We are using SuperSU's own tools, mounting su.img
! SuperSU image mount failed...
! Magisk scripts are placed correctly
! Flash SuperSU immediately to finish installation
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v12.0.zip'
Updating partition details...
...done
Then I installed SuperSU v2.82 again which brought back root (with SuperSU).
I tried to flash Magisk v13.0 (96f8efc) but again end up in an error:
****************************************
Magisk v13.0 (96f8efc) Installer
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v13.0(96f8efc).zip'
Updating partition details...
...done
Is anybody able to help me and give me some guidance to get MagiskSU (with v13.0)
Thank you in advance,
Best regards,
MarkusTh
Click to expand...
Click to collapse
I can't find mt boot.img file
And unsu.zip is not unrooting my phone
And unroot failed saying in supersu
Please help????
And magisk 14.0 is not flashing saying error 1
Same as described
---------- Post added at 07:37 PM ---------- Previous post was at 06:39 PM ----------
Maik268 said:
Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.
Click to expand...
Click to collapse
I did bit nothing happens
Showing my device is rooted even after uninstalling supersu
I can't flash magisk
First of all I've no boot.img file in my phone
brdude said:
I can't find mt boot.img file
And unsu.zip is not unrooting my phone
And unroot failed saying in supersu
Please help????
And magisk 14.0 is not flashing saying error 1
Same as described
---------- Post added at 07:37 PM ---------- Previous post was at 06:39 PM ----------
I did bit nothing happens
Showing my device is rooted even after uninstalling supersu
I can't flash magisk
First of all I've no boot.img file in my phone
Click to expand...
Click to collapse
The boot image you can extract from your device's factory image/firmware/ROM.
One of the best ways to unroot is to flash the unSU zip and then restore the stock boot image. That should be it.
If it doesn't work, provide logs (recovery log from flashing) and more details about your setup.
What is recovery log????
I have only copy log in my twrp recovery
And i tried copy log still saying boot image patched by other program
---------- Post added at 09:23 PM ---------- Previous post was at 09:12 PM ----------
I tried recently that unsu.zip
But still showing root is properly installed
brdude said:
What is recovery log????
I have only copy log in my twrp recovery
And i tried copy log still saying boot image patched by other program
---------- Post added at 09:23 PM ---------- Previous post was at 09:12 PM ----------
I tried recently that unsu.zip
But still showing root is properly installed
Click to expand...
Click to collapse
That is the recovery log.
Save the log after flashing the unSU zip and upload it. Or, just wipe and clean flash your device. Sounds like it might be easier... There are so many questions raised from your posts, but so few answers...
I'd suggest to go over to your device's forum and read up on the basics.
I have uninstalled SuperSU by flashing unsu.zip .
But when i tried to install magisk,it is failed showing this message "Boot image patched by other program,please restore stock boot image "
What to do??
madhuresh11 said:
I have uninstalled SuperSU by flashing unsu.zip .
But when i tried to install magisk,it is failed showing this message "Boot image patched by other program,please restore stock boot image "
What to do??
Click to expand...
Click to collapse
You do what the message says (the unSU zip doesn't restore the stock boot image for you)...
You'll find some pointers here:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
Didgeridoohan said:
You do what the message says (the unSU zip doesn't restore the stock boot image for you)...
You'll find some pointers here:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
Click to expand...
Click to collapse
Thanks. It worked!!
I don't feel like downloading 1.6GB just for 60M update, so this is partial OxygenOS OTA update converted into file based patch using xdelta3 so that it works with modified system partition. Every file is checked by its md5 first before patching to prevent incorrect update.
Notes
the stock recovery (recovery-from-boot.p & bin/install-recovery.sh) is not included in this recovery, so it will not overwrite your TWRP and there is not need to reboot to TWRP after appying the update
text files are not patched but installed full
files in lib/modules are installed full
first boot will takes longer time than usual
Requirements
You should be on stock OxygenOS 4.5.13
Download
https://drive.google.com/open?id=0BwihXEEuntymZERzaGJSZmFVZEE
How to install
reboot to recovery
backup boot, system, data
install firmware.zip
install system.zip
install boot.img
install any custom kernel
install any mods that modifies the ramdisk e.g. magisk, supersu, dm-no-verity.zip
reboot
Hello. I'm attempting to install magisk on a Samsung Galaxy Tab 4 10.1 (SM-T530NU). Base android has been replaced with crDroid (crDroid-7.1.1-20170312-v2.3).
When I go to flash the magisk .zip via TWRP the log reads:
...
-Flashing new boot image
! Insufficient partition size
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/download/Magisk-v17.1(17100)'
Updating partition details...
...done.
I have tried the following:
made sure to have the latest zip from Magisk Manager
removed previous partial installs of Magisk by using the flashable remover
unrooted supersu (which I'm also no longer able to flash now, systemless or not, to reestablish root and try other methods--it sticks on the boot screen)
reflashed base crDroid
pulling Magisk 17.3 separately from Manager and using that to flash
I haven't found any resources on whether the 'insufficient partition size' problem is with TWRP or the Magisk flashing process so I haven't found anything to try specifically to fix that.
The last thing I have to try is making the flashable boot image and fastbooting it.
Linked here is an image of the TWRP output: imgur . com/a/CATYid4
Thanks
did you manage to fix this
My phone has the TWRP custom recovery and ive attempted to install magisk on my Samsung Galaxy S7 device but it came up with an error and failed to install. I cant send links yet but this is what it said:
Installing zip file '/sdcard/Magisk-v20.4.zip'
Checking for Digest file...
***********************
Magisk 20,l.4 Installer
***********************
- Mounting /system
- Target image: /dev/block/sda5
- Device platform: arm64
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by unsupported programs
! Please restore back to stock boot image
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v20.4.zip'
Updating partition details...
...done
Anyone got any ideas on how to help? I am pretty new to this so its likely ive missed a step somewhere but this is my 3rd time trying and ive made sure ive followed every step
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
U must flash the zip ". no-verity-opt-encrypt-6.0.zip" and then flash zip magisk