I'm using F2FS on my 4X HD for system/data/cache and it is working fine.
I used the way which is described here: http://forum.xda-developers.com/showthread.php?t=2799610
The ROM i'm using is CM11 unofficial from here: http://goo.im/devs/laufersteppenwolf/CM11
Now the problem:
With TWRP the last Version of CM11 unofficial i can install is cm-11-20140709-UNOFFICIAL-p880.zip.
All the following versions bring an updater binary error on both recoveries: TWRP_F2FS_2.7.1.0.zip and CWM_Recovery_6.0.4.9_F2FS_new.zip.
Does anybody know if CM11 unofficial ist still compatible with F2FS and especially with these recoveries?
If yes: What's my failure?
Hello,
Same problem here (at least when i tryed 2 days ago).
Basically i followed the recommendations (formated 3 partitions in f2fs, rebooting, checking if FS are ok), then trying to flash 2 differents version (CM11-UNOFFICIAL-20140715 and 20140722)n then trying with 2 differents recoveries (both Lauffenstepper's ones, TWRP and CWM was given not working correctly).
My message was related to updater-script error.
See at the second laufersteppenwolf's post in the first topic linked by Sylvan86. There's a patch.
As i understand this means we can't use the prebuilds.
It is only for people who compile the rom on their own.
Or did i understand it the wrong way?
Related
I have been running an Snapshot M10 of CM11 (eMMC) for quite a while. I decided to see if there was a new version of CM11 as development seems to have slowed some what since the advent of CM12.
When I navigated to the CM download page for the Ovation I found a recovery image is now listed next to Nightly ROM.
I have flashed the NIGHTLY and have been trying to flash the recovery image, using ADB or Terminal Emulator, without success. In all honesty, I would also like to update the bootloader if possible.
Can anyone explain if I even need this new recovery? (I think the recovery is currently CWM 6.0.4.6)
How do I flash it?
Should I use the TWRP released for CM12 as a better option? (I will update to CM12 in the future)
Can I update the bootloader? How do I do that?
With my Moto X (Ghost) XT1052 I have strange problems installing custom ROMs and root.
TWRP
If using the latest stable TWRP 2.8.7.0 and trying to install CM13 I get an error message like this:
Code:
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc, xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,x t1060,ghost_verizon; this device is )".
There is a thread about making changes to the updater-script to get around this problem which did not solve the problem for me, and I don't see it as a permanent solution.
What did work was to install an older version, specifically TWRP 2.6.3.1.
Question: Is there a solution to this problem with a specific current build of TWRP or have ro.product.device permanently set?
SuperSU
After flashing the latest SuperSU from TWRP and rebooted, the device just hangs on the boot logo and does not pass.
Using the much older SuperSU 2.63 works without a problem.
Question: Is there any solution to get the latest SuperSU installed?
gotling said:
With my Moto X (Ghost) XT1052 I have strange problems installing custom ROMs and root.
TWRP
If using the latest stable TWRP 2.8.7.0 and trying to install CM13 I get an error message like this:
Code:
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc, xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,x t1060,ghost_verizon; this device is )".
There is a thread about making changes to the updater-script to get around this problem which did not solve the problem for me, and I don't see it as a permanent solution.
What did work was to install an older version, specifically TWRP 2.6.3.1.
Question: Is there a solution to this problem with a specific current build of TWRP or have ro.product.device permanently set?
Click to expand...
Click to collapse
Mate, I installed the unofficial TWRP from the post below, it worked fine in my moto X (XT1058). Try flash the TWRP 3.0.2 via fastboot (using computer).
https://forum.xda-developers.com/moto-x/development/twrp-touch-recovery-unofficial-t3309449
Try to verify the downloaded archives, because they may contain errors and a re download is needed.
Hi guys today I tried to update my RR rom to newer version but everytime I try to flash rom i get error:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/Download/RR-N-v5.8.1-20170208-oneplus3t-Official.zip'
Updating partition details...
...done
I tried wiping data, factory resetting, switching system image back to f2fs and on ext4 but nothing, same error every time.. I have TWRP 3.0.4.1 and phone boots to system normaly
99% chance of a corrupt zip.
ast00 said:
99% chance of a corrupt zip.
Click to expand...
Click to collapse
Its not corrupt, i redownloaded zip couple of times, tried different rom zip too, checked md5 it matches, its something else
There is also this error in log:
Comparing TZ version TZ.BF.4.0.1-76917 to TZ.BF.4.0.1-0028.2
assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-76917") == "1"
Your phones firmware partitions are to old, you need to update to the Oxygen OS 4.0.1 stable or even better to 4.0.2 for it to accept it and install.
This is the second thread with the same problem I'm answering.
Just check out koenkks unofficial LOS 14.1 thread, he has linked to the zip packages for TZ 4.0.2 for both 3/3t in the first post.
https://forum.xda-developers.com/showthread.php?t=2522762
Thanks guys I solved the issue yesterday, I just flashed OS 4.0.2 and reflashed latest version of RR over that
That's the long road of doing it, but end result is the same of course.
I'll use this thread since I have a very smiliar problem and I can't post in the developers forums.
I tried to install the latest LineageOS Nightly on my 3t but I also got the assert failed error message.
I used the unofficial TWRP 3.0.4-1 as suggested but one thing I overlooked was this:
"Started from lineage-14.1-20170207-nightly-oneplus3-signed.zip, we provide unified builds for both 3&3T, and you need to install certain firmware to pass the TrustZone assertion. Currently they're the OxygenOS 4.0.2 ones. As oneplus won't update them every time new OTAs are rolling out, firmware from other versions might also pass the assertion."
Yesterday I updated to OOS 4.0.3. (haven't had a custom rom installed yet) Can anyone confirm that this causes the error? Or did someone manage to switch from 4.0.3 to LineageOS?
Since I have a nandroid backup it's not that big of a deal but it's still annoying.
Hope anyone has an idea.
Best Regards
Hi everyone,
I'm new here though but am a Xiaomi user from the beggining of Xiaomi into devices with Redmi Note 3G Enhanced.
Currently, I own a Redmi 4X and I would like your expert lights please. I've flashed the latest twrp from twrp.me for my santoni device. Then flashed the latest build from LineageOS Official source + Gapps before booting up for first time. Everything was working perfectly until I decided to flash the latest update of LineageOS as I've seen in my updater it was released. So, I downloaded it through the updater and tried to flash it...
I came up with this "Failed to unmount /system (device or resource busy)" after that re-booted to LineageOS and everything was messed up with Google Services & Apps etc. Then I went back to twrp recovery and tried to flash again the rom but I was still getting that message so I understood something am doing wrong. Also santoni has dm-verity enabled which I know something about but just an info. I really wanna stick with LineageOS on my Redmi 4X forever but I'm afraid to flash it again. I've flashed MIUI 10 Beta by fastboot but now I wanna go back to LineageOS forever (addicted).
My only problem is: After successfuly flashing LineageOS and Gapps, I cannot apply (flash) updates to update the ROM to the latest nightly build due to this error above.
Kind regards,
peryson
Try with different recovery. For example with this
Harukey said:
Try with different recovery. For example with this
Click to expand...
Click to collapse
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
peryson said:
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
Click to expand...
Click to collapse
You can download latest Lineage OS build and dirty flash it (without any wipes) (so you can unmout system parition). And I don't see any issue in using unoffical twrp.
I also have experienced same error once during upgrade "failed to unmount /system"
Eventually I wiped everything and did clean flash from scratch. This is really annoying issue and demonstrates that upgrade system is not 100% reliable for some reason.
I'm not sure however is it Lineage or twrp issue.
Hello,
I'm trying to install custom ROMs but I can't get past Error 7 on my T710
Tried different versions of TWRP 3.3.1 and TWRP 3.4.0, tried many other ROMs, tried removing 'assert' from ROMs and many other different methods, still no luck.
Flashed the original firmware now, tried everything over again (flash TWRP, flash ROMs (full wipe/format) and still same issue.
I was able to flash LineageOS on my T713 without any issues, like that ROM a lot and want to use the unofficial version for T710.
Please help.
mx900 said:
Hello,
I'm trying to install custom ROMs but I can't get past Error 7 on my T710
Tried different versions of TWRP 3.3.1 and TWRP 3.4.0, tried many other ROMs, tried removing 'assert' from ROMs and many other different methods, still no luck.
Flashed the original firmware now, tried everything over again (flash TWRP, flash ROMs (full wipe/format) and still same issue.
I was able to flash LineageOS on my T713 without any issues, like that ROM a lot and want to use the unofficial version for T710.
Please help.
Click to expand...
Click to collapse
Any chance of testing older versions of TWRP?
Found this: "Q: Whenever I try flashing any (lineage-17.1) build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Q-based rom within a version of TWRP older than 3.4. Simply flash the linked below version 3.4 or higher, reboot back into recovery, and flash the rom zip again. "
From: "https://forum.xda-developers.com/t/...ab-s2-sm-t710-t810-t715-t815-19-9-15.3187202/ "
might help