Database Develop

[Q] Fail to flash xposed framework

I downloaded framework and app here but everytime I flash the framework it shows ' error executing updater binary in zip'. However I can flash other zip like kernel. Could someone do me a faver?

Nick Huang said:
I downloaded framework and app here but everytime I flash the framework it shows ' error executing updater binary in zip'. However I can flash other zip like kernel. Could someone do me a faver?
Click to expand...
Click to collapse
I would guess that you need to use an older version of TWRP - the latest builds are a bit ropey.

Same issue here , on BlissPop 3.2 07 May 2015 Version with Blisspop's Stock Kernel and TWRP 2.8.6.0 -_- (For OnePlus One)

Cyanogen 12.1 flash issue on Moto X 2013

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.

[FinalBuild][patchrom] [6.0.1] FlymeOS 6 [SM-J320FN]

FlymeOS ROM For Samsung Galaxy J3 (2016)​
FlymeOS 6 is aftermarket firmware by Meizu. Flyme team work on Flyme ROM to make stable but good-skinned. FlymeOS 6 is AOSP Marshmallow 6.0.1 based with focus on latest Google security patches.
instalation instruction:
Boot to recovery
-Make a Nandroid Backup (Optional)
-Wipe Data, System, and Cache
-Power Off the Device and boot back up To recovery
-Install the ROM zip
-Reboot and Enjoy
what's working:
Everything Works well
Known Issues:
- front Camera need fix
-the same as lineageOS bugs
fix solutions (by @DeblaGaming):
How to Fix Sim-Card not detecting
-Boot to TWRP
-Install the ROM file (Without flashing anything)
-Boot back up
-All of your data should still be there
-Check if the Sim-Card is Detected
-And enter the Sim-Pin if prompted
How to fix Back Camera bad Scaling Picture Mode
-Open Camera
-Click the Gear Icon
-Click the Resolution Option
-Set it to 6M
-The Scaling should be fixed now
front camera fix:
https://forum.xda-developers.com/galaxy-j3-2016/development/6-0-1-flymeos-6-t3750717/post75780826
How to fix Brightness not Changing
The auto brightness it activated automatically for some reason so deactivate it in Setting/Display and Brightness and click Automatic Brightness Control
Magisk Root is Supported but Xposed Isn´t
- If u found any bugs or issues tell me
Download Links:
FlymeOS 6 ROM build 1
FlymeOS 6 ROM build 2
GAPPS(OpenGapps) <- select pico
or
search on app store google apps installer and click search other app stores
IMPORTANT:
If u face any boot errors or stuck on bootlogo(Samsung logo) replace the boot.img in the rom zip with LineageOS 13 boot.img
changelog:
（build 2）
-fixed theme
-removed kernel isnt seandroid enforcing
-added log report
-removed autorolate lockscreen string
Special Thanks to:
FlymeOS Team
@[email protected]
@flymeDevHub
DevHub
DeblaGaming
Enjoy! Thanks
Source Code: https://github.com/FlymeOS
ROM OS Version: 6.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 6.7.12.29IR
Created 2018-02-16
Last Updated 2018-02-18

Great work devs. ❤ keep it up ?

Good job

asarre said:
Good job
Click to expand...
Click to collapse
Yep MIUI is maybe next ?

OH MY GOD , THIS FLYME:laugh:
MIUI IS BUILDING?

Sign up for ROMHut.
I suggest it do start implomenting OTA Updates to this amazing rom!
Thanks for your patience!

PixelBoot said:
Sign up for ROMHut.
I suggest it do start implomenting OTA Updates to this amazing rom!
Thanks for your patience!
Click to expand...
Click to collapse
Ota updates already exist ^^

[email protected] said:
Ota updates already exist ^^
Click to expand...
Click to collapse
Cool!

Please help me
J320F
----
mount: failed to mount /dev/block/platform/sdio_emmc/by-name/SYSTEM at /system: Device or resource busy
minzip: Extracted 0 file(s)
minzip: Can't create containing directory for "/system/bin/IPSecService": I/O error
minzip: Extracted 89 file(s)
failed to mkdir /system/lib/modules: Read-only file system
symlink: failed to symlink /system/lib/modules to /lib/modules/autotst.ko: making parents failed
symlink: failed to symlink /system/lib/modules to /lib/modules/autotst.ko: No such file or directory
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
Процесс Updater завершился с ОШИБКОЙ: 7
I:Legacy property environment disabled.

Just a bug to talk about.
Downloads in software upgrades not updating and camera not allowing usage due to no SD.
I actually have an SD plugged in so...

software doesnt work because this is not official

Michal161 said:
software doesnt work because this is not official
Click to expand...
Click to collapse
I am install your ROM from TWRP .
What this?
------------
mount: failed to mount /dev/block/platform/sdio_emmc/by-name/SYSTEM at /system: Device or resource busy
minzip: Extracted 0 file(s)
minzip: Can't create containing directory for "/system/bin/IPSecService": I/O error
minzip: Extracted 89 file(s)
failed to mkdir /system/lib/modules: Read-only file system
symlink: failed to symlink /system/lib/modules to /lib/modules/autotst.ko: making parents failed
symlink: failed to symlink /system/lib/modules to /lib/modules/autotst.ko: No such file or directory
script aborted: symlink: some symlinks failed
symlink: some symlinks failed

Is it works on j320f

Looks difference with another i want to try after vacation

ntrimurthulu said:
Is it works on j320f
Click to expand...
Click to collapse
Yes, of course

ntrimurthulu said:
Is it works on j320f
Click to expand...
Click to collapse
Not work , i have error in TWRP

Ok i Will try

can I install gapps mini or do i must use pico ver?
Can i Root using Magisk and can i install xposed?
PS: Nice ROM
Love/ DeblaGaming

DeblaGaming said:
can I install gapps mini or do i must use pico ver?
Can i Root using Magisk and can i install xposed?
PS: Nice ROM
Love/ DeblaGaming
Click to expand...
Click to collapse
you can install it but i am not taking responsibility

ntrimurthulu said:
Is it works on j320f
Click to expand...
Click to collapse
Flymeos 6 not work on ( sm-j320f ) czzzz this rom make for only sm-j320fn user only

SM-T819 - Installation problem

Hallo, I hope someone in this forum can help me with a problem with my SM-T819 TWRP.
I tried to install a CustomRom without making a back-up copy and apparently I removed all details on the tablet.
The installation of TWRP was succesful, however all my recent trials to install a CustomRom failed with the following comments:
Updating partition details….
…done
Full SELinux support is present
MTP enabled
Installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Checking for digest file...
Updater process ended with ERROR: 7
Error installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Updating partition details…
…done
installing zip file `/ sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Checking for digest file...
Warning: No file_contexts
Comparing TZ version TZ.BF.3.0.3-00054 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00064 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00067 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00071 to TZ.BF.3.0.3-00077
assert failed: samsung.verify_trustzone ("TZ.BF.3.0.3-00054", "TZ.BF.3.0.3-00044",
"TZ.BF.3.0.3-00067", "TZ.BF.3.0.3-00071") == "1"
Updater process ended with ERROR: 7
Error installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Updating partition details…
… done
I have done this trial with various TWRP and Lineage varieties but in vain and always with the identical error.
The only thing I could do was via TWRP the installation of “SMT819_Deodex_Debloated Custom Rom” (based on Stock-Samsung-Firmware.
I have also tried via Odin (several versions) to apply the original firmware. The installation proceeds without error, the tablet starts,
the progress is shown on the blue screen and every time it is cancelled after 25 % and 32%. Then the tab shuts down and starts again and remains in a continous loop with the splash screen.

Well, what is the reason to install a ... REALLY REALLY OLD version like this?
Try this https://lineageos.wickenberg.nu/gts210velte/ or that https://drive.google.com/drive/folders/1VsHc9-k4LA3-n19dp6Gkvqwf0GZLTRcA depending on what you want to have, LOS 16 or 17.1

Pixel 5 w/ Jan Update - Flash of patched boot.img = loop

Hi all,
I seem to be struggling with my usual process of getting root on my Pixel 5.
I installed the latest Canary build of the Magisk Manager and patched my base boot.img and then flashed it and the phones goes into an infinite loop. Only way to get out of it is to flash-all.bat (w/out the -w). Any ideas on why this process, which I've used even on my previous P2XL, is no longer working?
When I open the manager, it says my installed version is 8.0.4 (4770) and the latest version is 6d88d8ad (4770) (15) but I can't update.

I have the January release and the same magisk version, and my device boots fine. What steps did you do to patch the boot.img file and how did you flash the patched magisk_patched.img file?

Amd4life said:
I have the January release and the same magisk version, and my device boots fine. What steps did you do to patch the boot.img file and how did you flash the patched magisk_patched.img file?
Click to expand...
Click to collapse
This is the process I follow each month/followed for this update:
Download and extract FW
Edit flash-all.bat to remove the -w
Run flash-all.bat while at bootloader screen
Copy \redfin-rq1a.210105.003\boot.img to device
Open Magisk Manager Canary (latest) and click on "Install"
Select "Select and Patch a File"
Copy \download\magisk_patched_0eKAS.img to platform-tools folder on PC
At bootloader screen, run: fastboot flash boot magisk_patched_0eKAS.img
Reboot
I've been using that process for months, going back to my Pixel 2 XL and used that process (with different .img names obviously) last month even for the December update on this here Pixel 5.
Only way to get out of the loop is to re-run step 3.

IlyaKol said:
Hi all,
I seem to be struggling with my usual process of getting root on my Pixel 5.
I installed the latest Canary build of the Magisk Manager and patched my base boot.img and then flashed it and the phones goes into an infinite loop. Only way to get out of it is to flash-all.bat (w/out the -w). Any ideas on why this process, which I've used even on my previous P2XL, is no longer working?
When I open the manager, it says my installed version is 8.0.4 (4770) and the latest version is 6d88d8ad (4770) (15) but I can't update.
Click to expand...
Click to collapse
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)

andybones said:
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)
Click to expand...
Click to collapse
Let me give that a whirl in a bit.

IlyaKol said:
Let me give that a whirl in a bit.
Click to expand...
Click to collapse
andybones said:
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)
Click to expand...
Click to collapse
I installed 8.0.4 but when I try to patch the image with it, it fails. When I try to sideload 21.2 or 20.4, it says:
E:footer is wrong
E:Signature verification failed
E:error: 21
Install from ADB completed with status 2.
Installation aborted.

I was able to patch the image after changing to the beta channel. However, it started to loop again and eventually went back to bootloader with the reason being "no valid slot to boot". I've flash-all.bat'ed again and am back to working. I don't understand why I can't get this to work.

I also had an inability to boot after I tried to do the December update using Minimal ADB. No valid slot.
I switched to a new platform tools install, and the same procedure has now worked twice. How old is your platform tools install?

If anyone is having problems patching the stock boot.img, you can upload it and I can patch it and re-upload it for you.

earlgrey_44 said:
I also had an inability to boot after I tried to do the December update using Minimal ADB. No valid slot.
I switched to a new platform tools install, and the same procedure has now worked twice. How old is your platform tools install?
Click to expand...
Click to collapse
It was pretty new/latest version but I went ahead and just re-downloaded the factory image and platform tools and am trying again...
If it matters, I'm back to Canary manager and here is what my patch screen says:
Code:
- Device platform: arm64-v8a
- Magisk Manager: 8.0.4 (4770)
- Install target: 6d88d8ad (21201)
- Copying image to cache
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
- Output file *path*
- All done!
My actual flash output is:
Code:
> fastboot flash boot magisk_patched_Mx5Yh.img
Sending 'boot_a' (98304 KB) OKAY [ 2.277s]
Writing 'boot_a' OKAY [ 0.312s]
Finished. Total time: 2.918s
UPDATE:
I got it working this time around using a fresh new factory image and platform tools download.
I'm actually wondering if, in my haste, I actually used the bootloader image, not the boot img...but wouldn't Magisk have complained? lol.
Who knows, but looks like my issue is resolved! Thanks all for having me try things like a new platform tools download.