Anyone tried this/these ROMs
crDroidAndroid-8.1-20180605-marmite-v4.3
https://androidfilehost.com/?w=files&flid=274407
crDroidAndroid-8.1-20180605-marmite-v4.3
https://androidfilehost.com/?w=files&flid=274407
Still trying to find a twrp for 8.1 can't even sign up for the twrp on 4PDA as the sign up is all in Russian (Google translate doesn't help) so installing ROMs etc will be awhile yet.Anyone tried this/these ROMs
crDroidAndroid-8.1-20180605-marmite-v4.3
https://androidfilehost.com/?w=files&flid=274407
Unzip the Los 14.1 rom.zip file and edit the updater file to reflect your bootloader version! Save it and then install via TWRP.Where would I find that script? There's nothing in the lineage zip that looks like an updater script that includes the bootloader ID.
I haven't tried installing 317G yet. I think I'll try installing the full 249H zip, then try lineage again. I can do that right? I've only flashed system/boot/recovery images through "fastboot flash" for now.
Didn't someone in here say they had the TWRP for 8.1, however they were unable to post any links to there google drive account for member to obtain?Still trying to find a twrp for 8.1 can't even sign up for the twrp on 4PDA as the sign up is all in Russian (Google translate doesn't help) so installing ROMs etc will be awhile yet.
It seems all roads lead to 4PDA. if the developer of that recovery puts it on the twrp site or makes it freely available,we will be just be going around in circles.Didn't someone in here say they had the TWRP for 8.1, however they were unable to post any links to there google drive account for member to obtain?
Thanks for the file names. I didn't know they were four folders deep in the zip. I unzipped, took the entire assert statement (line 2) out of updater-script, saved and rezipped. I'll flash everything to TOS249H and start fresh with this new zip.Unzip the Los 14.1 rom.zip file and edit the updater file to reflect your bootloader version! Save it and then install via TWRP.
0. Download and install notepad++It didn't affect my bootloader version. I tried flashing the bootloader zip I mentioned earlier and it gave me a lot of "is up to date" messages and didn't change anything. How do I make the lineage zip compatible with my bootloader?
Probably best if I don't delete that line, that seems like a pretty important assert.:silly: I deleted the line below it.3. Delete the line (getprop("ro.product.device") == "marmite" || getprop("ro.build.product") == "marmite") || abort("This package is for "marmite" devices
this is a "" + getprop("ro.product.device") + "".");
Yes of course, you can remove the rule too and that also circumvents the error, as its only been added by the author as a rule for TWRP to follow before running the main installation script.Thanks for the file names. I didn't know they were four folders deep in the zip. I unzipped, took the entire assert statement (line 2) out of updater-script, saved and rezipped. I'll flash everything to TOS249H and start fresh with this new zip.
It will actually install on the latest official build of TWRP with no issues on the 7.1.2 bootloader version.Still trying to find a twrp for 8.1 can't even sign up for the twrp on 4PDA as the sign up is all in Russian (Google translate doesn't help) so installing ROMs etc will be awhile yet.
No its a 8.1 Oreo build, I have restored my 7.1.2 Los 14.1 ROM after check the CR ROM out with no issues at all?Is that CR ROM for 7.1 and tweeted to look like 8.1 or built for 8.1? but if it is,I still have the same problem of installing it.no twrp,no install.might be easier to roll back to 7.1 lineage as didn't have any problems with twrp etc.
here is oreo twrp from 4pdaIt seems all roads lead to 4PDA. if the developer of that recovery puts it on the twrp site or makes it freely available,we will be just be going around in circles.
As I said I'm on stock 8.1 now.if you install 3.2.2.0 twrp,there is mount data issues and twrp does not see internal storage.
Official TWRP dont work normally with 8.1 .Is it possible that twrp is conflicting with data encryption? I had this issue on my Wileyfox Swift (the 1st one) and using adb to either push or flash zips seemed to work.