Related
Q&A for Rom Lollipop AOSP 5.1.0 (Released 2015-03-13) port for ZR testing
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Rom Lollipop AOSP 5.1.0 (Released 2015-03-13) port for ZR testing. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks for your post
tonytee said:
@uncomment : Did u test it? How about battery and free ram?
Click to expand...
Click to collapse
I just Flash the rom , its smooth , free ram is 1.3 GB thanks a lots
but there is no battery percentage , cant change drawable shortcuts , i need clipboard too could u help me to bring this item ?
Xperia zr said:
I just Flash the rom , its smooth , free ram is 1.3 GB thanks a lots
but there is no battery percentage , cant change drawable shortcuts , i need clipboard too could u help me to bring this item ?
Click to expand...
Click to collapse
Its AOSP, cause that no much options. Waiting xposed for 5.1 release
Sent from my Xperia ZR using XDA Free mobile app
Hi Dear
uncomment said:
Its AOSP, cause that no much options. Waiting xposed for 5.1 release
Sent from my Xperia ZR using XDA Free mobile app
Click to expand...
Click to collapse
I have another problem ,after i turn airplane mode on , i have to reboot my phone to detect sim card, how can i fix it ?
sorry for my bad english
Xperia zr said:
I have another problem ,after i turn airplane mode on , i have to reboot my phone to detect sim card, how can i fix it ?
sorry for my bad english
Click to expand...
Click to collapse
Its a known bug from Z noticed here:
http://forum.xda-developers.com/showpost.php?p=59458446&postcount=17
Sent from my Xperia ZR using XDA Free mobile app
anyone know when we will have a update to lol 5.0 original ?
Cant Flash Rom
Omni Rom 5.1 - Cant Flash zip through TWRP.
The error i get is failed Sym link. Some Simlinks failed.??
Shray said:
Omni Rom 5.1 - Cant Flash zip through TWRP.
The error i get is failed Sym link. Some Simlinks failed.??
Click to expand...
Click to collapse
It say symlinks fail or it say script updater fail ?
Try install my twrp from RR rom v5.4.0 CM5.1 base
Let me check about 2days cause im not near my copmputer
Sent from my Xperia ZR using XDA Free mobile app
uncomment said:
It say symlinks fail or it say script updater fail ?
Try install my twrp from RR rom v5.4.0 CM5.1 base
Let me check about 2days cause im not near my copmputer
Sent from my Xperia ZR using XDA Free mobile app
Click to expand...
Click to collapse
Okay, so this is what it says.
Symlink: Some symlinks failed
E: Error executing updater binary in zip.
Used TWRP from RR rom v5.4.0 and got the same error.
I also tried flashing with old Twrp. It didn't work.
Fixed for Rom zip
Shray said:
Okay, so this is what it says.
Symlink: Some symlinks failed
E: Error executing updater binary in zip.
Used TWRP from RR rom v5.4.0 and got the same error.
I also tried flashing with old Twrp. It didn't work.
Click to expand...
Click to collapse
I checked: my zip upload is old script-updater
TO fixed:
- download script-updater below and rename it by delete .zip
- Use 7zip on your PC to open rom zip and follow path:
omni-5.1-20150330-dogo-EXPERIMENTAL.zip\META-INF\com\google\android\
- Replace updater-script in zip by: Drag new updater-script from Explorer to zip
- Done!
Sorry for my fault! :angel:
uncomment said:
I checked: my zip upload is old script-updater
TO fixed:
- download script-updater below and rename it by delete .zip
- Use 7zip on your PC to open rom zip and follow path:
omni-5.1-20150330-dogo-EXPERIMENTAL.zip\META-INF\com\google\android\
- Replace updater-script in zip by: Drag new updater-script from Explorer to zip
- Done!
Sorry for my fault! :angel:
Click to expand...
Click to collapse
Its all okay, mate. Its how things progress.
Also, thank you for providing the steps for the fix.
I tried them just as you mentioned (exactly word to word) and this is what i got.
Formatting /system
Mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: device or resource busy
Symlinking
Symlink: some symlinks failed
E: Error executing updater binary in zip
Tried with some variations and still got the same message.
Shray said:
Its all okay, mate. Its how things progress.
Also, thank you for providing the steps for the fix.
I tried them just as you mentioned (exactly word to word) and this is what i got.
Formatting /system
Mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: device or resource busy
Symlinking
Symlink: some symlinks failed
E: Error executing updater binary in zip
Tried with some variations and still got the same message.
Click to expand...
Click to collapse
Enter twrp and tick mount system. Try it again. I did it before show you how to fix
Sent from my Xperia ZR using XDA Free mobile app
uncomment said:
Enter twrp and tick mount system. Try it again. I did it before show you how to fix
Sent from my Xperia ZR using XDA Free mobile app
Click to expand...
Click to collapse
I tried it, again.
Checked that the system is mounted and flashed the Rom.
This time its able to extract the system but some symlinks still fail and the error is still the same (E: error executing UPDATER BINARY in zip)
I deleted the extension (.zip) from the file you uploaded before using 7zip to replace it.
Shray said:
I tried it, again.
Checked that the system is mounted and flashed the Rom.
This time its able to extract the system but some symlinks still fail and the error is still the same (E: error executing UPDATER BINARY in zip)
I deleted the extension (.zip) from the file you uploaded before using 7zip to replace it.
Click to expand...
Click to collapse
Oh, it like as be crazy! I check script again and see it call mount program from sbin but not found
Forget it! Hope you enjoy with resurrection remix 5.4.0
Olivier release new omni 5.1 with video fix. I will do it later.
Thank you for testing!
Sent from my Xperia ZR using XDA Free mobile app
uncomment said:
Oh, it like as be crazy! I check script again and see it call mount program from sbin but not found
Forget it! Hope you enjoy with resurrection remix 5.4.0
Olivier release new omni 5.1 with video fix. I will do it later.
Thank you for testing!
Sent from my Xperia ZR using XDA Free mobile app
Click to expand...
Click to collapse
Anytime.
Thanks again for RR.
uncomment said:
Oh, it like as be crazy! I check script again and see it call mount program from sbin but not found
Forget it! Hope you enjoy with resurrection remix 5.4.0
Olivier release new omni 5.1 with video fix. I will do it later.
Thank you for testing!
Sent from my Xperia ZR using XDA Free mobile app
Click to expand...
Click to collapse
I'm not sure if it was my mistake or TWRP had problems while installing.
I flashed TWRP 2.8.5.0 (Uploaded by you previously) and tried flashing again Omni 5.1.
This time it worked.
Shray said:
I'm not sure if it was my mistake or TWRP had problems while installing.
I flashed TWRP 2.8.5.0 (Uploaded by you previously) and tried flashing again Omni 5.1.
This time it worked.
Click to expand...
Click to collapse
Thank for testing.
I will not upload AOSP rom more. For me it less bug but not much options for me like CM base rom.
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.
Universal Systemless Installer for Xposed Framework
>> disclaimer: imagine the most horrible possible outcome and multiply it by 6
(did you get the Megamind joke ?) , you have been warned though <<
what is this ?
basically its an on-the-fly systemless converter/installer for xposed framework
the beauty is that you can install the latest releases of Xposed Framework: systemless
install it from twrp like any other zip
queu your rom with supersu and this zip
it will automatically detect the needed framework (which you still have to download)
versions:
xposed-usi-v0.1l (8bce9f8)
- revised bootdetection properly
- revised file attribute detection completely
- revised loopback options
- updated mount script
- added multiarch archive check (arm/arm64/x86/x64/mips/mips64)
xposed-usi-v0.1k (3f236e6)
- revised imgsize
- revised unpack method
- revised mount script and init.rc
xposed-usi-v0.1j (b96ab4c)
- revised mount options, removed comma for compatibility busybox,toolbox and toybox
- added diskfree check for /tmp
- revised paths and librarypaths properly
- rollback aapt search
- fixed chown problem for toolbox
xposed-usi-v0.1i (5ff57eb)
- removed awk for compatibility whether busybox,toolbox and toybox
- fixed search for paths with spaces
- revised librarypath
- added aapt check, if not found, apkname defaults to filename (omnirom)
- removed incorrect 64-bit patch check
- revised mount process and cleanup
xposed-usi-v0.1h (75403d1)
- revised imgsize detection, revised imgbuild (reduced by 30%)
- added sanity checks throughout the script
- boot.img backup to /data or /cache, with md5sum and origin
- removed some obsolete loops, added log optimizations
- added 1mb imgsize buffer for inline patching
xposed-usi-v0.1g - Changed imgsize detection, fixed ui_print, some minor bugs and typo's (124184f)
xposed-usi-v0.1f - Changed abi detection, fixed apk install for /cache (ac0e0f0)
xposed-usi-v0.1e - Changed bootpartition detection (997e0af)
xposed-usi-v0.1d - Some bug fixes (edf3c9b)
xposed-usi-v0.1c - MIUI / TouchWiz support (untested) (89d44b6)
xposed-usi-v0.1b - first public beta (c1f9fb7)
xposed-usi-v0.1a - non-public release
features:
universal: works on all devices xposed is written for (auto-detect cpu and sdk)
futureproof: compatible with any future versions of xposed-framework ( v87+ )
trustability: installs and patches the official xposed-framework zipfiles
compatible: also works with any unofficial release although not tested
secure: xposed.img is mounted read-only
small: smallest possible footprint for xposed.img
requirements:
twrp (tested with 3.0+)
supersu (tested with 2.65+)
urls/credits
rovo89 - xposed framework
chainfire - systemless idea & tools
topjohnwu - systemless xposed idea
dvdandroid - xposed-installer
romracer - systemless xposed
gh2923 - arm64 tester (awesome guy :good
HypoTurtle - proof of concept for supersu image/su.d
FAQ
why did you write it?
i thought i could do a better job, you decide
is it safe?
backup your device, in case the installation fails just restore your boot partition
its the first release and beta, make no assumptions,
how to install ?
>>> WARNING: it will overwrite /data/xposed.img without prompt! <<<
download supersu by chainfire
download the xposed-usi-v*.zip (download link below)
download the proper xposed-v*-sdk*-*.zip version for your device
and place it alongside or in a subfolder (auto-detect)
Official Xposed Framework
Xposed for Samsung/TouchWiz
Xposed for MIUI
download one of the installers below
Xposed Installer by dvdandroid or
Xposed Installer by romracer
and place it alongside or in a subfolder (auto-detect)
queue and install supersu 2.65+ followed by xposed-usi-v*.zip
(already on supersu?, just install the xposed-usi-v*.zip)
reboot
how do i know what version of xposed i need ?
run the xposed installer by dvdandroid
or run the xposed-usi-*.zip
both will show which version you need
bugs/problems:
probably, i only have one device
donate:
bitcoin address: 1HPRug5MFDp2eA3rr4kDEhV1gEguinRnpQ
download: (latest version is at the bottom of the list)
saved for future reference
Customized Frameworks and Installers
(supported from 0.1c and above)
Do you want your custom Xposed Framework supported ? Follow these rules:
installer searches for: "xposed-v*-sdkAPI-ARCH-*.zip"
API = 21, 22, 23 ... etc
ARCH = arm, arm64, x86, x64, mips, mips64 (case insensitive)
zipfile must contain "/system" folder with the xposed system files.
Do you want your custom Xposed Installer App supported ? Follow these rules:
installer searches for: "*xposed*installer*.apk" (case insensitive)
I'l try and give report
Minions_Army said:
I'l try and give report
Click to expand...
Click to collapse
Thanks mate, appreciate it
st0rm77 said:
Thanks mate, appreciate it
Click to expand...
Click to collapse
Failed on xperia m running rr 569 lp
Edit
My fault
I'm not install xposed framework official before
Test again
On my hammerhead nexus 5
Failed too
Minions_Army said:
Failed on xperia m running rr 569 lp
Edit
My fault
I'm not install xposed framework official before
Test again
Click to expand...
Click to collapse
I changed the bootpartition detection, tested it and it should run now.
Updated to xposed-usi-v0.1.e
BTW: the recovery.log file is now copied after the installation and can be found in same directory as the ZIP file, with the same name.log (xposed-usi-v0.1e.zip.log) just to make things easy.
st0rm77 said:
I changed the bootpartition detection, tested it and it should run now.
Updated to xposed-usi-v0.1.e
BTW: the recovery.log file is now copied after the installation and can be found in same directory as the ZIP file, with the same name.log (xposed-usi-v0.1e.zip.log) just to make things easy.
Click to expand...
Click to collapse
I'll try latest build
Might want to try the latest version.
@everyone: i need some more testers, so if you're up for it, post away.
I need to wait more feed backs before installing this one. Sdk22 user here anyway
MrBrowseGierza said:
I need to wait more feed backs before installing this one. Sdk22 user here anyway
Click to expand...
Click to collapse
Updated version to >> 0.1h <<
It works flawlessly on my own device, so try it out and if you run into problems let me know.
First time the folder name contains a space, it just says error.
After I rename the folder, it still failed, and the log is as follows:
Code:
I:operation_start: 'Flashing'
正在安装刷机包 '/sdcard/1/SystemlessXposed_by_st0rm77/xposed-usi-v0.1h.zip'
检查 MD5 文件…
跳过 MD5 校验：无法找到 MD5 文件
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
******************************
Universal Systemless Installer
for Xposed Framework
ver: 0.1h
written by: st0rm
Licensed under: GPL v2
******************************
- Mounting /system(ro), /data, /cache
- Setting library path: /system/lib64
- Cpu architecture: arm64-v8a/arm64, sdk23
*************
Image builder
*************
- UnZipping into TMPDIR: /tmp/30499
Archive: /sdcard/1/SystemlessXposed_by_st0rm77/xposed-usi-v0.1h.zip
inflating: /tmp/30499/arm64-v8a/sukernel
creating: /tmp/30499/common/
creating: /tmp/30499/common/ramdisk/
inflating: /tmp/30499/common/ramdisk/init.xposed.rc
creating: /tmp/30499/common/ramdisk/sbin/
inflating: /tmp/30499/common/ramdisk/sbin/mount_xposed.sh
/tmp/updater[176]: awk: not found
! Failed: /sdcard/1/SystemlessXposed_by_st0rm77/xposed-v86-sdk23-arm64.zip is corrupt
***********
Cleaning up
***********
- Unsetting library path
- Unmounting
- Removing TMPDIR: /tmp/30499
I checked the xposed-v86-sdk23-arm64.zip, the md5sum it is just the same as the official. Then I down a new one, but it still failed.
I'm using Oneplus 3, TWRP 3.0.2-0.
Sorry for my poor English...
gh2923 said:
First time the folder name contains a space, it just says error.
After I rename the folder, it still failed, and the log is as follows:
Code:
I:operation_start: 'Flashing'
正在安装刷机包 '/sdcard/1/SystemlessXposed_by_st0rm77/xposed-usi-v0.1h.zip'
检查 MD5 文件…
跳过 MD5 校验：无法找到 MD5 文件
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
******************************
Universal Systemless Installer
for Xposed Framework
ver: 0.1h
written by: st0rm
Licensed under: GPL v2
******************************
- Mounting /system(ro), /data, /cache
- Setting library path: /system/lib64
- Cpu architecture: arm64-v8a/arm64, sdk23
*************
Image builder
*************
- UnZipping into TMPDIR: /tmp/30499
Archive: /sdcard/1/SystemlessXposed_by_st0rm77/xposed-usi-v0.1h.zip
inflating: /tmp/30499/arm64-v8a/sukernel
creating: /tmp/30499/common/
creating: /tmp/30499/common/ramdisk/
inflating: /tmp/30499/common/ramdisk/init.xposed.rc
creating: /tmp/30499/common/ramdisk/sbin/
inflating: /tmp/30499/common/ramdisk/sbin/mount_xposed.sh
[SIZE="5"]/tmp/updater[176]: awk: not found[/SIZE]
! Failed: /sdcard/1/SystemlessXposed_by_st0rm77/xposed-v86-sdk23-arm64.zip is corrupt
***********
Cleaning up
***********
- Unsetting library path
- Unmounting
- Removing TMPDIR: /tmp/30499
I checked the xposed-v86-sdk23-arm64.zip, the md5sum it is just the same as the official. Then I down a new one, but it still failed.
I'm using Oneplus 3, TWRP 3.0.2-0.
Sorry for my poor English...
Click to expand...
Click to collapse
Poor English is better than 'No English'
There isnt a problem with your files, >> awk is missing << and the script does a check for you to make sure the zip file isnt broken. (contains files)
No awk, no correct check it seems, i will work something out for you.
Please download en run tool-test zip file, post logfile as attachment
st0rm77 said:
Poor English is better than 'No English'
There isnt a problem with your files, >> awk is missing << and the script does a check for you to make sure the zip file isnt broken. (contains files)
No awk, no correct check it seems, i will work something out for you.
Please download en run tool-test zip file, post logfile as attachment
Click to expand...
Click to collapse
That is to say, some busybox command not support?
st0rm77 said:
Updated version to >> 0.1h <<
It works flawlessly on my own device, so try it out and if you run into problems let me know.
Click to expand...
Click to collapse
Thanks, work perfectly fine on my LG G3 dual SIM D856.
MrBrowseGierza said:
Thanks, work perfectly fine on my LG G3 dual SIM D856.
Click to expand...
Click to collapse
And we have a winner
Thanks for posting the result mate :good:
I want to test. I have an htc m10. I have Xposed v85. I just tried v86 and im having lots of problems. Im not to good with this stuff so im not sure how to install it. Im going to do a fresh install of rom and Xposed. I have you're file, Xposed v85, and my rom ready to go. After I flash my rom, boot and restore my apps. Then? Im not sure what to do with you're file and the Xposed v85 file. Do I flash them both?
Sent from my 2PS64 using XDA-Developers mobile app
gh2923 said:
That is to say, some busybox command not support?
Click to expand...
Click to collapse
Well it seems you have no busybox in /sbin at all instead i found toolbox,
which is limited and does not have awk.
So i have to work around this somehow. I would hate to include a complete installation of busybox for all architectures.
Im working on a solution.
l1ttl3z said:
I want to test. I have an htc m10. I have Xposed v85. I just tried v86 and im having lots of problems. Im not to good with this stuff so im not sure how to install it. Im going to do a fresh install of rom and Xposed. I have you're file, Xposed v85, and my rom ready to go. After I flash my rom, boot and restore my apps. Then? Im not sure what to do with you're file and the Xposed v85 file. Do I flash them both?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you read the how to install from the first post ?
Download your rom
Download supersu (see 1st post)
Download xposed-usi- latest version (see 1st post)
Download xposed version you want (85 in your case)
Download xposed-installer-apk (see 1st post)
Put only these files in a new folder
folder/yourrom.zip
folder/supersu*.zip
folder/xposed-usi-*.zip
folder/xposed-v85-*.zip
folder/xposed-installer*.apk
Start TWRP and navigate to your folder
Select your yourrom.zip and press "Add more Zips"
Select your supersu*.zip and press "Add more Zips"
Select --> xposed-usi-*.zip and "Swipe to install"
And that should do it
st0rm77 said:
Well it seems you have no busybox in /sbin at all instead i found toolbox,
which is limited and does not have awk.
So i have to work around this somehow. I would hate to include a complete installation of busybox for all architectures.
Im working on a solution.
Click to expand...
Click to collapse
I'm using H2OS, maybe it just delete many things...
Perhaps I should first flash a systemless busybox?
Like this one:
http://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543
It's 0:40am, sorry but I have to go to sleep
LineageOS 14.1 for Galaxy A5 A500xxYou've probably known that cm is "dead", and that there is a new project called "LineageOS" which is a fork on the cyanogenmod project, so this is the "continue" of my cyanogenmod thread. Enjoy
NOTE: this ROM is for any A500 model and will not work for 2016 models (A510)
Disclaimer:
Code:
I'm not responsable for bricked devices :( , dead phone chargers,
nuclear explosions or global warming.
Flash it at YOUR OWN RISK
Downloads1) You need a custom recovery to flash the ROM (zip). You can download TWRP HERE or CTR HERE
2) Optional but recomended: Google Apps (aka gapps). You can download them here: http://opengapps.org/
3) You need marshmallow bootloader and modem. Install latest mm stock ROM to update them
4) You need the ROM obviusly . You can download it here:
LineageOS-14.1: https://www.androidfilehost.com/?w=files&flid=145997
How to InstallIf you have TWRP Recovery:
1) Go to wipe section and wipe: cache, dalvik, system and data (internal storage wipe is not needed!)
2) Go to install box and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
If you have CTR Recovery:
1) Go to Wipe Menu, tap Wipe ALL - Preflash button and then tap - Yes - Wipe ALL! button
2) Go to Install zip menu and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
How to Update
If you have TWRP Recovery:
1) Go to install box and choose the zip which contains the ROM
2) Go to wipe section and wipe: cache and dalvik
If you have CTR Recovery:
1) Go to Install zip menu and choose the zip which contains the ROM
2) Go to Wipe Menu, and wipe cache and dalvik
NOTE: For Updating you don't have to wipe data, you only have to wipe data when install different cm version, for example cm-13->cm-14.0 or cm12->12.1
SM-A500XX SECTIONNote1: if you are on SM-A500FU you don't have to follow this section. Just follow the "How to install" one
NOTE2: some device requires some modifications in blobs and/or in device tree in order to get RIL worling
How to install CyanogenMod-14.1 on any SM-A500XX variant:
1) Install the zip of lineageos rom
2) Install RIL fix zip from this thread's attachements
3) Flash gapps (optional but better)
4) Reboot and enjoy
For people running multirom with lineage as secondary ROM:
1) Install the zip of lineageos rom
2) Install gapps (optional but better)
3) Download (from this thread's attachements) and open RIL fix zip for your device
4) Open (inside the zip) /META-INF/com/google/android/updater-script
5) Remove these two lines:
ifelse(is_mounted("/system"), unmount("/system"));
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
6) Save the new file and close
7) Go in twrp "Advanced"->"Terminal" and run this command:
ln -s /sdcard/multirom/roms/ROMNAME/system /system
Note: if the output of ln command is "File exists" you made a typo, so, re-run the command without making typos (tab helps); if it gives no output, you typed it correctly, so, you can proceed to the 8th step
8) Flash RIL fix zip
9) Reboot and enjoy
NOTE: If you don't find the RIL fix from your variant and you have RIL problems like sim card not detected, read the section for people with RIL problems and follow the instructions
Knowing Bugs
None for now
Report bugs here, or at https://github.com/DeadSquirrel01/android_device_samsung_a5-common/issues
F2FS Guide
If you want to use F2FS, first you need a twrp that supports F2FS partitions formatting like mine:
https://www.androidfilehost.com/?fid=817550096634793304
Then, reboot in twrp, go in "Wipe"->"Advanced Wipe"->Select "System" box->"Repair or Change File System"->"Change File System"->"F2FS"
Do this also for "Data" and "Cache" partitions
NOTE: Everything in the partitions you turn into F2FS will be deleted!!!
NOTE: If you turn userdata partition (/data), everything in /data/media/0 (/sdcard) will be deleted!!!
Now, open the zip of lineage os and change:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
to
mount("f2fs", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
Read this if you are having problems with RIL
If you have issue with RIL, post a zip with these libs taken from stock rom, and I'll create a flashable zip:
Code:
/system/lib/libsec-ril.so
/system/lib/libsec-ril-dsds.so (for dual sim variants only)
SOURCES
Device tree: https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx Branch: cm-14.1
Device Config: https://github.com/DeadSquirrel01/android_device_samsung_a5-common Branch: cm-14.1
Kernel: https://github.com/DeadSquirrel01/android_kernel_samsung_msm8916 Branch: cm-14.0
Telegram group: @GalaxyA5dev
Telegram channel for project updates: @ds01news
Note: If you want to contact me for any question which is off topic, just pm me or email me at [email protected]
XDA:DevDB Information
LineageOS-14.1 for Galaxy A5 SM-A500, ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
DeadSquirrel01
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Lollipop or Marshmallow bootloader/modem (mm suggested)
Version Information
Status: Stable
Created 2017-02-17
Last Updated 2017-02-17
CHANGELOGFifth release (07/09/2017):
Support calls through LTE (VoLTE)
Fix touchscreen freezes on wakeup
Fix GPS: Now it takes about 10 seconds outdoor and 20 seconds outdoor to get the position (these values may change a bit)
Remove NFC button and everything related to NFC. Since it always stucked on turning on, his crashes were slowing down the system a lot
Fourth release (22/08/2017):
Add button to switch data to LTE for variants that support it
Bring CPU core 1 online (active) (improves performance)
Fix touchkey lights
Update some things in ramdisk
Add screencast to record screen
Third release (17/08/2017):
Fix in-call audio
Fix FM radio
Fix LTE (for variants that support it)
Add OMS support for substratum themes (You can download them from google play. See screenshot's dark theme as example)
Add kernel driver to stop touchkey vibration when device is suspended (replaced InputDisabler)
Upgrade kernel to 3.10.106
Lot of other kernel updates and upgrade to LA.BR.1.2.9_rb1.23 (caf)
Upgrade blobs to A500FUXXU1CPG1 (marshmallow)
Add F2FS formatted /data,/system,/cache support. To do it you also need my twrp 3.1.1. (download in first post) or a twrp that supports f2fs formatting
Improved battery life on suspend (fixed doze)
Remove "ANDROID IS NOT SEANDROID ENFORCING" warning on samsung splash screen
Obviously compile ROM on latest lineage sources
Second Release (17/02/2017):
Fix camera that couldn't take videos
Add touch screen gestures
Minor updates to kernel and device tree (see github commits)
First Release (18/01/2017):
Fixed Screen Rotation
Fixed Cellular Data
Lots of minor updates in kernel, device config (see github commits)
NOTE: You can see all changes (github commits) here: https://github.com/DeadSquirrel01/android_device_samsung_a5-common/commits/cm-14.0
and here:https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx/commits/cm-14.0
And for kernel here: https://github.com/DeadSquirrel01/android_kernel_samsung_msm8916/commits/cm-14.1
Excuse me. Why do you put SM-A500 stuff into the A Series (2017) Thread? Or have you misplaced it here and it belongs there?:
https://forum.xda-developers.com/samsung-a-series
saintsimon said:
Excuse me. Why do you put SM-A500 stuff into the A Series (2017) Thread? Is this clutter supposed to look clever? Or have you misplaced it here and it belongs there:
https://forum.xda-developers.com/samsung-a-series
Click to expand...
Click to collapse
Damn, I will ask to a moderator to move it
Good work my friend keeping an eye closely on this thread and wating penalty for audio fix to use it as daily driver
Pls when can we get the audio bug during call fixed? @DeadSquirrel01
---------- Post added at 19:30 ---------- Previous post was at 19:30 ----------
My device is A500H
unimke said:
Pls when can we get the audio bug during call fixed? @DeadSquirrel01
---------- Post added at 19:30 ---------- Previous post was at 19:30 ----------
My device is A500H
Click to expand...
Click to collapse
Please read the thread and follow it:
IMPORTANT: ETA askers: please grow up and make this thread clean; if you ask for ETAs I'll ignore you and your request(s)
Click to expand...
Click to collapse
Ok
Hey, I tried this Rom but was not able to flash it. It showed UNKNOWN ERROR while flashing through TWRP.
Does this error exit or I have done something wrong ?
My device is SM-A500G.
aryan1997 said:
Hey, I tried this Rom but was not able to flash it. It showed UNKNOWN ERROR while flashing through TWRP.
Does this error exit or I have done something wrong ?
My device is SM-A500G.
Click to expand...
Click to collapse
Its only for a500fu variant only...waiting for another variant..cheers man..
leviz0689 said:
Its only for a500fu variant only...waiting for another variant..cheers man..
Click to expand...
Click to collapse
Doh, still don't know why people don't read the full thread (or at least first 4-5 lines also wit "NOTE" in bold) and then cry if it doesn't work
Anyway that's not only for a500fu, when i have time I'll upload A500XX version, too
Sorry man..im only answer that comment too...
leviz0689 said:
Sorry man..im only answer that comment too...
Click to expand...
Click to collapse
You should ignore those comments
leviz0689 said:
Sorry man..im only answer that comment too...[/QUOTE
Dude, if you want to developers continued to work on a project, stop the ETA, wait for a stable version. The developers are people too, they have their own lives, and they do not have to answer stupid questions everyday The Developers works very hard, be patient.
Sorry, if you understand me, i don't speak English. )
Click to expand...
Click to collapse
DeadSquirrel01 said:
You should ignore those comments
Click to expand...
Click to collapse
Sorry, If I offended you in any way. I know that you work very hard and I really appreciate your work. Thanks for all of it.
Its just that there was a section in the post on how to install the Lineage OS on A500xx devices.
So, I just wanted to know that if there is an error or did I do something wrong.
I did not wanted to be rude or anything. Once again SORRY !!!!!!
DeadSquirrel01 said:
LineageOS 14.1 for Galaxy A5 A500xxYou've probably known that cm is "dead", and that there is a new project called "LineageOS" which is a fork on the cyanogenmod project, so this is the "continue" of my cyanogenmod thread. Enjoy
NOTE: this ROM is for any A500 model and will not work for 2016 models (A510)
NOTE2: The First build is for A500FU only!!!
NOTE3: 1st zip is only for SM-A500FU, I'll upload A500XX zip soon, when I have time
Disclaimer:
Code:
I'm not responsable for bricked devices :( , dead phone chargers,
nuclear explosions or global warming.
Flash it at YOUR OWN RISK
Downloads1) You need a custom recovery to flash the ROM (zip). You can download TWRP HERE or CTR HERE
2) Optional but recomended: Google Apps (aka gapps). You can download them here: http://opengapps.org/
3) You need marshmallow bootloader and modem. you can download them HERE (for A500FU only) thanks to @jimbomodder that has uploaded them or you can easily extract them in stock firmware
4) You need the ROM obviusly . You can download it here:
LineageOS-14.1: https://www.androidfilehost.com/?w=files&flid=145997
How to InstallIf you have TWRP Recovery:
1) Go to wipe section and wipe: cache, dalvik, system and data (internal storage wipe is not needed!)
2) Go to install box and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
If you have CTR Recovery:
1) Go to Wipe Menu, tap Wipe ALL - Preflash button and then tap - Yes - Wipe ALL! button
2) Go to Install zip menu and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
How to Update
If you have TWRP Recovery:
1) Go to install box and choose the zip which contains the ROM
2) Go to wipe section and wipe: cache and dalvik
If you have CTR Recovery:
1) Go to Install zip menu and choose the zip which contains the ROM
2) Go to Wipe Menu, and wipe cache and dalvik
NOTE: For Updating you don't have to wipe data, you only have to wipe data when install different cm version, for example cm-13->cm-14.0 or cm12->12.1
SM-A500XX SECTIONHow to install CyanogenMod-14.1 on any SM-A500XX variant:
1) Download the sm-a500xx cm-14.1 zip on "Downloads" section"
2) For make "port" process a bit easier do as following:
_1) Delete all files in system/etc/firmware (inside the zip)
_2) Go to META-INF/com/google/android/updater-script (in the zip) and remove all symlinks which start with /firmware and /firmware-modem
2) Use a root browser or adb pull and pull all files located in /firmware/image and /firmware-modem/image in the zip in /system/etc/firmware
2_a) If your device is dualsim, go to stock rom and copy /system/lib/libsecril.so and /system/lib/libsecril-dsds.so in the zip in system/lib/ Then open the system/build.prop in the zip and add:
persist.radio.multisim.config=dsds
3) Flash it and enjoy lineageos on you SM-A500XX variant!!
Knowing Bugs:
_Camera cannot take videos
_Audio during calls bug
Segnale other bugs if u find in bugs section or here https://github.com/DeadSquirrel01/android_device_samsung_a5-common/issues
IMPORTANT: ETA askers: please grow up and make this thread clean; if you ask for ETAs I'll ignore you and your request(s)
SOURCES
Device tree: https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx Branch: cm-14.0
Device Config: https://github.com/DeadSquirrel01/android_device_samsung_a5-common Branch: cm-14.0
Kernel: https://github.com/DeadSquirrel01/android_kernel_samsung_msm8916 Branch: cm-14.1
Note: If you want to contact me for any question which is off topic, just pm me or email me at [email protected]
XDA:DevDB Information
LineageOS-14.1 for Galaxy A5 SM-A500, ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
DeadSquirrel01
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Lollipop or Marshmallow bootloader/modem (mm suggested)
Version Information
Status: Stable
Created 2017-01-18
Last Updated 2017-01-18
Click to expand...
Click to collapse
1) Delete all files in system/etc/firmware (inside the zip)
_2) Go to META-INF/com/google/android/updater-script (in the zip) and remove all symlinks which start with /firmware and /firmware-modem
2) Use a root browser or adb pull and pull all files located in /firmware/image and /firmware-modem/image in the zip in /system/etc/firmware
cant find those location inside the zip sir sorry noob here and im using a500f sir thank you so much
ian0326 said:
LineageOS 14.1 for Galaxy A5 A500xx
You've probably known that cm is "dead", and that there is a new project called "LineageOS" which is a fork on the cyanogenmod project, so this is the "continue" of my cyanogenmod thread. Enjoy
NOTE: this ROM is for any A500 model and will not work for 2016 models (A510)
NOTE2: The First build is for A500FU only!!!
NOTE3: 1st zip is only for SM-A500FU, I'll upload A500XX zip soon, when I have time
Disclaimer:
1) Delete all files in system/etc/firmware (inside the zip)
_2) Go to META-INF/com/google/android/updater-script (in the zip) and remove all symlinks which start with /firmware and /firmware-modem
2) Use a root browser or adb pull and pull all files located in /firmware/image and /firmware-modem/image in the zip in /system/etc/firmware
cant find those location inside the zip sir sorry noob here and im using a500f sir thank you so much
Click to expand...
Click to collapse
you take /firmware/image and /firmware-modem/image from your stock rom and put them in /system/etc/firmware in the zip
hit thanks if it helped
You can post screenshots of what exactly the device would look like after installing the rom ?
Cannot install on samsung A500F updator error 7
carlossennin56 said:
You can post screenshots of what exactly the device would look like after installing the rom ?
Click to expand...
Click to collapse
Now i have rr on my device, maybe I'll add them later, but they are basically the same as cm14.1
Unofficial TWRP and OrangeFox builds.
TWRP : https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/
OrangeFox - deprecated : https://sourceforge.net/projects/ep...overy/OrangeFox-Unofficial-sagit.img/download
This is TWRP-3.3.1 unofficially updated with lots of new improvements!
What's here but not in the official one?
Compiled with Pie blobs and in pie environment
Updated kernel, based on CAF's latest pie tag and compiled with latest Clang 9.0.3 by Google
Additional debug support - This TWRP won't overwrite /sys/fs/pstore
F2FS support
Cleaned unused HALs from manifests
System as Root variant available
How to install this TWRP?
Boot into fastboot mode by pressing volume down + power when the device is turned off
Connect your device to your computer
Download the TWRP build
Open a shell at the download folder
Rename the downloaded file to twrp.img
Type
Code:
fastboot flash recovery twrp.img
To leave the fastboot mode type
Code:
fastboot reboot
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers
Click to expand...
Click to collapse
- Wikipedia
How to use F2FS for /data and /cache?
Reboot into this TWRP
Select wipe > format data then type yes and reboot into recovery again
Then select wipe > advanced wipe select cache then select repair or change file system and select F2FS
Do the same step with Data
Install a supported ROM and GApps
Reboot into the ROM
Thank you for your great work . keep it up
Thanks,I'm following the topic
Sorry for my ignorance....but can somebody tell me the difference between these two?
Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Between orange fox and twrp? Orange fox is a fork of twrp with some special features and a redesign.
Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Have a look here - https://orangefox.tech/
DarthJabba9 said:
Have a look here - https://orangefox.tech/
Click to expand...
Click to collapse
happy to see you here, Will sagit devices have an official version? We are looking forward
fr0bs said:
happy to see you here, Will sagit devices have an official version? We are looking forward
Click to expand...
Click to collapse
In due course
New TWRP test build is available!
TWRP was updated to version 3.3.0 and is usable with f2fs.
Download : https://drive.google.com/file/d/1UwT5UBz_8PVugEhWLYlcwKM3VAi25jkI/view
This build is possible due to Ultraschorsch 's support by providing a Google Cloud trial ?
Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0
Decryption problem
NeoArian said:
Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0
Click to expand...
Click to collapse
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?
perspicio said:
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?
Click to expand...
Click to collapse
There is a problem with decrypting devices formatted with may ASB, I see about it. You could go f2fs or setup rom on April build and upgrade to new one for now.
Edit:// should be fixed here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1
I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...
Hi @NeoArian, it seems that at least your latest TWRP-sar version has issues with mounting external usb storages: at least my sandisk 64GB key that I always used to save nandroids to is not detected, thus I have to rely on internal memory to save nandroids, fw, and user data.
Using TWRP version 3.2.3-sagit-shev.img I have no issues (but unfortunately no support for your lineageos unofficial builds if I'm not mistaken).
Am I doing something wrong? Do you have any suggestions?
Cavaler said:
I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...
Click to expand...
Click to collapse
I thought it was some codes in twrp that cause the problem.
If I use 3.3.1.0 everything works fine. but it won't decrypt my data even I had no pattern for lock screen with 3.3.1.2.
( all mentioned above are official builds )
This version TWRP have arch bug.
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444
New twrp update available: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1-20191204
AmaoBilibili said:
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444
Click to expand...
Click to collapse
I assume that's a problem with OpenGapps installer.
Hi, I'm running twrp 3.3.1-20191204 with your Lineage 17 very happily thanks!
For the last couple of lineage installs though (2019-12-24 and 2020-01-08) I'm getting a failure in twrp when running a backup, on data partition specifically:
createTarFork() process ended with ERROR: 255
recovery.log is far more helpful:
Code:
# tail -n 50 /tmp/recovery.log
I:addFile '/data/anr/anr_2020-01-10-11-49-31-592' including root: 1
==> set selinux context: u:object_r:anr_data_file:s0
I:addFile '/data/per_boot' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/per_boot' - '0eb5afb598811574'
I:Error adding file '/data/per_boot' to '/data/media/0/TWRP/BACKUPS/161a6490/2020-01-10--16-29-03_lineage_sagit-userdebug_10_QQ1B200105004_en/data.ext4.win008'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
There's an (empty) folder '/data/per_boot' which seems to be breaking the backup process. I'm not sure if it's lineage itself or one of my apps creating this dir, but if I manually delete it the backup works... then it gets recreated next boot.
A somewhat minor issue, in case it's either easy enough to fix and/or other's run into the same problem!
I assume this twrp version use for flashing gsi. Am I correct?