yesterday . i downloaded this ucyan cm 12 for my xperia s . and every time when i try to install this rom through CMW and TWRP i get this error
warning: no file_contexts detected filesystem ext4 for /dev/block/mmcblk0p12
and cmw freezes after this error ....
please help .... how to fix this error ?????????????????????????????
P.S : english is not my native language so ignore my mistakes
I have ALMOST the same issue:
I get:
detected filesystem ext4 for /dev/block/mmcb1k0p12
And it's here forever.
Update: After waiting a LOOONG time, I got this:
"ApplyParsedPerms: 1setfilecon of /system/lost+found to ubject_r: system_file: s0 failed: Operation not supported on transport endpoint set_metadata_recursive: some changes failed"
Error executing updater binary in zip ...
Click to expand...
Click to collapse
Re
Maybe first of all you two write the steps performed for flashing Lollipop Roms? I've tried all the Lollipop Roms compiled for SXS and nor,ally I used to do this way:
1. TWRP recovery (but CWM also worked)
Install TWRP recovery in FOTA partition using Terminal apk provided your phone is running on 4.1.2. kernel supporting TWRP recovery. Flash kernel from ROM zip file prior entering TWRP (this step helps avoiding an error like "update binary...").
2. In TWRP recovery - Advanced - wipe everything but sdcard. In Mount section unmount everything but sdcard.
3. Flash the ROM and wipe Cashe&Dalvik
4. Flash appropriate GAPPS, wipe Cashe&Dalvik and reboot.
that's all
I can install magisk itself just fine, and root works through magisk, but I cannot install any modules.
I keep getting this error:
- Copying zip to temp directory
- Installing injected_YouTube_Background_Playback_Vanced_-_Magisk_Repo-v12.49.55b012.zip
- Mounting /system, /vendor
update-binary[73]: unzip: not found
! Unable to extract zip file!
Failed!
! Installation failed
[EDIT]
I did a full uninstall of magisk and installed the latest beta (15.4), and whatever the problem was, it is gone now
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOADS:
HANNAH-8.x (Oreo 32bit & 64bit)
HANNAH-9.x (Pie 64bit)
JAMES
NORA
PETTYL
HOW TO FLASH (fastboot method):
Code:
adb reboot bootloader
Code:
fastboot flash recovery twrp*.img
Code:
fastboot boot twrp*.img
CREDITS:
TeamWin
CyanogenMod/Lineage Android
HyperTeam
Barry Allen
XDA:DevDB Information
TWRP for Moto E5 Plus, Tool/Utility for the Moto E5
Contributors
karthick mostwanted, whodat711
Source Code: https://github.com/TeamWin/android_device_motorola_hannah
Version Information
Status: Stable
Created 2019-03-17
Last Updated 2019-05-18
How to solve /data mount issue? (Not really needed now with latest twrp)
Or
How to remove encryption?
Here you go:
1. Reboot your device to fastboot
2. Remove encryption
Code:
fastboot -w
3. Reboot to recovery
4. Mount vendor partition
5. In twrp terminal or adb shell
Code:
sed -i 's/forceencrypt/encryptable/g' /vendor/etc/fstab.qcom
6. Reboot to system
Aternate way
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
karthick mostwanted said:
Reserved
Click to expand...
Click to collapse
Bro I looked over the git is this 64 bit one if not all good ill see if I can get one from ur trees also u r the man
Nice even though we got pitch black recovery and orangefox to
skullkid383 said:
Bro I looked over the git is this 64 bit one if not all good ill see if I can get one from ur trees also u r the man
Click to expand...
Click to collapse
What's the reason behind switching the arch to 64bit now? When we don't have any 64bit based ROMs.
Delete
skullkid383 said:
Cause I know some one that needs 64 bit twrp to test his builds u would know this if u werent hanging with the guy (barry aka. whodat) who deleted our 80+ ppl telegram by getting someone he knew to make him a admin and kicking everyone when we slept
Click to expand...
Click to collapse
What? Not sure what you're talking about
Maybe request the same guy to make 64bit recovery.
karthick mostwanted said:
What?
Click to expand...
Click to collapse
A lot to explain
skullkid383 said:
A lot to explain
Click to expand...
Click to collapse
What you mean alot to explain??
Can you make recovery for moto e5 "Nora"
Sent from my moto e5 using XDA Labs
Bootloader Image not signed or corrupt
When I install the TWRP image of the official website via the fastboot commands on my XT1924-4 I get the message below:
"(bootloader) is-logical: recovery: Not found
Sending ' recovery ' (22324 KB)
Writing ' recovery '
OKAY [0.709 S]
Finished. Total Time: 1.732 s
OKAY [0.926 S]
Bootloader Image not signed or corrupt."
I can reboot in TWRP but when I turn off the phone and turn on in FastBoot mode to enter the recovery pops up the message "no command"
Twrp error
I managed to install TWRP and Magisk but recovery has several errors. When I try to do a wipe cache for example, appears the message:
"Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (invalid argument)
Unable to recreate /data/media folder.
Updating parttition details...
Failed to mount '/data' (invalid argument)
...done
unable to mount storage
Failed to mount '/data' (invalid argument)
Full Selinux support is present.
Unable to mount /data/media/TWRP/. twrp
MPT Enabled
Formatting Cache using make_ext4fs...
Updating partition details...
Failed to mount '/data' (invalid argument)
...done
Unable to mount storage"
---------- Post added at 07:34 PM ---------- Previous post was at 07:30 PM ----------
But I managed to install Magisk through TWRP, although have appeared some error messages during installation. The magisk is running smoothly.
Ex novo said:
I managed to install TWRP and Magisk but recovery has several errors. When I try to do a wipe cache for example, appears the message:
"Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (invalid argument)
Unable to recreate /data/media folder.
Updating parttition details...
Failed to mount '/data' (invalid argument)
...done
unable to mount storage
Failed to mount '/data' (invalid argument)
Full Selinux support is present.
Unable to mount /data/media/TWRP/. twrp
MPT Enabled
Formatting Cache using make_ext4fs...
Updating partition details...
Failed to mount '/data' (invalid argument)
...done
Unable to mount storage"
---------- Post added at 07:34 PM ---------- Previous post was at 07:30 PM ----------
But I managed to install Magisk through TWRP, although have appeared some error messages during installation. The magisk is running smoothly.
Click to expand...
Click to collapse
Remove encryption first
Code:
fastboot -w
And reboot to recovery
Mount vendor and in terminal
Code:
sed -i 's/forceencrypt/encryptable/g' vendor/etc/fstab.qcom
Reboot to system
Whoever facing /data mount issue you have to remove your encryption first No longer needed, just flash the new twrp
Detailed information in 2nd post
Thank you, now the recovery is working perfectly.
iCowCool said:
Can you make recovery for moto e5 "Nora"
Sent from my moto e5 using XDA Labs
Click to expand...
Click to collapse
Thread updated with Nora & other devices
You need to create a patched boot image using Magisk Manager. Make a boot backup in TWRP, then reboot system. Open Magisk Manager and click install Magisk zip..... it'll ask you to download zip, or create boot image. Flash TWRP again, then flash the patched boot. You should be good to go.
RobD691973 said:
You need to create a patched boot image using Magisk Manager. Make a boot backup in TWRP, then reboot system. Open Magisk Manager and click install Magisk zip..... it'll ask you to download zip, or create boot image. Flash TWRP again, then flash the patched boot. You should be good to go.
Click to expand...
Click to collapse
Huh? Your instructions are only for how to root stock.
Custom ROM only needs flash magisk zip for root.
Done.
Twrp 3.3.1-0 arm64 version for Hannah
HANNAH
Question about the TWRP version and Installation Methods
I have a XT1924-4 with TWRP 3.3.0.0 downloaded from the official website. To install your LineageOS 15.1 should I use which version of TWRP? TWRP 3.3.1-0 version arm64 or the other? Can I install the image by my TWRP or does it have to be by fastboot method?
As explained in an other thread i got this issue :
with TWRP-offain and original one downloaded from TWRP website i received this error message after installation attempts of different custom ROMs
No OS installed
I wiped System and Data partition on each A and B slots and then tried to install on each slots some custom ROMs
At the end of each installations i received also this error message :
failed to mount "/System" (Permission denied)
How can i solve the issue ?
updater process ended with ERROR: 1
i have also tried to solve issue installing dm-verity disabler KO again
now when i try to install custom ROMs smartphone returns this error :
updater process ended with ERROR: 1
Error installing zip file "/external SD/name_custom_rom.zip
johnjohnmel said:
i have also tried to solve issue installing dm-verity disabler KO again
now when i try to install custom ROMs smartphone returns this error :
updater process ended with ERROR: 1
Error installing zip file "/external SD/name_custom_rom.zip
Click to expand...
Click to collapse
You need to use this twrp. Then it will work. About twrp errors: just ignore...
I've already used also that TWRP version
twrp-installer-daisy-3.3.0-0-offain.zip
KO
Voodoojonny said:
You need to use this twrp. Then it will work. About twrp errors: just ignore...
Click to expand...
Click to collapse
I started and completed successfully installation of TWRP and custom ROM in a slot, but when i try to change slot i received this error message "Failed to mount /system (permission denied)"
In TWRP > advanced i'm not enable to mount /system partition
How can i solve ?
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Fabian R�ling said:
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Click to expand...
Click to collapse
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
SubwayChamp said:
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
Click to expand...
Click to collapse
I have never heard of a "super partition". How do I do that?
Fabian R�ling said:
I have never heard of a "super partition". How do I do that?
Click to expand...
Click to collapse
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
SubwayChamp said:
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
Click to expand...
Click to collapse
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Fabian R�ling said:
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Click to expand...
Click to collapse
Super partition is where some logical partitions are grouped like system, vendor, odm, product, etc.; it depends on the device we're talking about.
As you got a used device, it seems that the last owner did some stuff with it, probably unlocked bootloader (then relocked it) and mess with some custom ROMs (maybe). You can totally fix it by flashing the stock ROM and starting from there, being sure first that you can log in without issues in Google Play (that your account is authorized).
To have this partition readable, you may read this https://forum.xda-developers.com/t/...-mount-system-rw-super-rw-read-write.4247311/ in case this doesn't solve flashing the super partition it is a part of the process to flash the stock ROM.
SubwayChamp said:
flashing the super partition it is a part of the process to flash the stock ROM
Click to expand...
Click to collapse
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Fabian R�ling said:
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Click to expand...
Click to collapse
You can update through the stock recovery in case your TWRP have actually some issues, flash the stock recovery through fastboot (get it from your stock ROM) and then do the sideload through stock recovery, it's probable that the stock recovery can mount super partition and made readable again the system files that´s within, or you can simply flash this or that partition using fastboot commands, for this you need an unlocked bootloader, nothing more.
BTW did you try formatting data?.
And this tool should work for you https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4217855/
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Fabian R�ling said:
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Click to expand...
Click to collapse
The ROM to be flashed through recovery contains a payload.bin file within others one, this file can be unpacked, not sure if it contains a recovery image though, but you should get it from the full ROM that in some variant comes in oplus format and can be decrypted too, this full ROM contains all the images, it's useful to unbrick a OP device.
Linux doesn't have a counterpart of the Windows applications for smartphones and vice versa in regard to Android development, this is one of the reasons why I have a dual boot machine.
As per the last part it could be an issue from your browser, I didn't have this kind of behaviors from the XDA site.
For "boot.img" and "recovery.img" in the "EU" and the "global" section I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.
Apparently I have a "OnePlus 7 Pro", not a "OnePlus 7T Pro". I bought that accidentally, but the specs are fine. Actually following the instructions for the correct device worked, who would have thought…