Develop Bugs

[Q] help installing ucyan cm 12

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

[Q] TWRP Error "E:unable to mount data"

Current Problems:
E:unable to mount storage
E:unable to mount data
Stuck at fastboot oem format
The Story:
I factory reset my Xperia M, then I unlocked Bootloader and also flashed TWRP through FastBoot. After that I flashed "Lollipop 5.1 Cyanogenmod 12.1 Official Nightly Build 20150630" through External Memory Card (TWRP). I rebooted my phone, it was stuck on Sony logo for sometime then it again rebooted itself and TWRP was gone and Cyanogenmod's recovery was there. I again flashed TWRP and tried other ROM but then also the same thing happened. So I again flashed TWRP through FastBoot. I searched and tried the following command in Terminal TWRP:
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
But I didn't know which folder to select so I selected the directory which was showing all folders, but it said "not enough space to build proposed file system.................". No matter which folder I selected it always showed that error.
Currently I am using the following command through FastBoot:
Code:
fastboot oem format
and it's been stuck there for 1 hour showing 3 dots. Is it working, does it take hours to format?
P.S.: I also tried ADB sideload but the same thing happened - it rebooted and I got Cyanogen Recovery and then again I flashed TWRP.
Please help!!!!!!!!!!!!!!!!!!!!!!!!!

E: Failed to mont / efs (invalid argument) sm-g925i

Help me friends.
By passing the ROM STOCK 5.1.1 by ODIN , the phone does not start , and when I enter the RECOVERY appears this message . I am no expert what can I do to save my Galaxy S6 edge ?
Recovery and Rom Stock

JucielM said:
Help me friends.
By passing the ROM STOCK 5.1.1 by ODIN , the phone does not start , and when I enter the RECOVERY appears this message . I am no expert what can I do to save my Galaxy S6 edge ?
Recovery and Rom Stock
Click to expand...
Click to collapse
What options did you choose in Odin? What all did you flash? And what baseband version? What your gonna have to do is flash custom recovery like twrp and then boot into recovery and mount system and then use terminal emulator in twrp and enter
mke2fs /dev/block/mmcblk0p3
then
mount -w -t ext4 /dev/block/mmcblk0p3
then reboot

e:failed to mount /efs (invalid argument)
Hi i have the same problem even if i install stock rom (SM-G920X) with pit and bootloader by odin. When i tried to use your command in twrp terminal there is "Could not stat /dev/block/mmcblk0p3 - no such file or directory. Could anyone help me?

you are not alone, i am having same problem with my samsung s6. stock fw not helping, i was able to boot to twrp and that command is not help me! if anyone finds solution pls share thanks

hey guys i tried flashing an efs.img file and now my phones bootlooping please help

[Q] [q] sm-n930f boot loops and error messages after hydra rom install & stock flash

[Q] [q] sm-n930f boot loops and error messages after hydra rom install & stock flash
Hello,
I've incurred ENDLESS boot loops after trying to install Hydra Rom. I've been getting very strange error messages also. In light of this, I've tried to flash back to stock through ODIN multiple times, but I've only been successful after I change the partition files to FAT through TWRP RECOVERY beforehand. It gets stalled up, I reset, then only Download mode is accessible, at this point I can get a success message through ODIN when I flash stock.
Interesting enough, the files seem to have reset after the stock flash through ODIN is successful... well, halfway successful. Everything seems to look good but then the screen pictured below shows. I reboot and NOTHING but boot loops. I have to go through obstacles to reflash TWRP and get it working again too, which is how I found the files go from FAT, back to 4.
I'm not sure what's going on, and I wish I had more information, but I'm terribly confused at this point. Anyone have any ideas??????
No Support SINGLE-SKU
Supported API: 3
E: failed to mount /efs (invalid argument)
E: failed to mount /efs (invalid argument)
E: failed to mount /efs (invalid argument)
dm-verity verification failed...

try to install newest twrp and format all or repair partitions ... then try to flash hydra 1.3.5 with hydra kernel 1.2.5 select in aroma .... after this flash csc selection be sure to select your csc and then reboot hope it comes back hehe

How to Unbrick SM-A720F ?! (FRP = On) | E:failed to mount /efs | Combination not work

Hi everyone
I have some questions about Samsung SM-A720F
here is Samsung SM-A720F which has frp lock ! (FRP = On)
I know how to solve this problem, but it has another problem that doesn't let the device to become Ok.
First, the "System Status = Custom" in Downloading Mode , which usually flashing device with Official Firmware it should be changed to "Official
it's wired !!! I've tried 10 different Firmwares with correct binary (the phone's binary is 3 and firmware's binary is also 3)
but it doesn't changed to "Official" ( still System Status = custom :| )
note : i also tried combination files on this phone !
Second , after device flashing , it's just rebooted to recovery mode and shows the below error messages :
- E:failed to mount /efs (Invalid argument)
- E:failed to clear BCB message: failed to find /misc partition
- dm-verity verification failed...
As i know flashing the custom recovery on phone and adb commands solved my problem ! but frp lock is on and i can't flash the custom recovery !!!
note : phone not booted after flashing !
Does anyone know how to deal with this ?!

same problem
My phone also same problem
1) i try to solve from twrp but any rom flashing time - E:failed to mount /efs (Invalid argument)
2) i flash from odin its showing pass but till now mobile booting not complet.
3) i tryied from smart switch also s/n not correct.
please help me before i was used hadesh rom.
SM-A720f/ds
Android IR said:
Hi everyone
I have some questions about Samsung SM-A720F
here is Samsung SM-A720F which has frp lock ! (FRP = On)
I know how to solve this problem, but it has another problem that doesn't let the device to become Ok.
First, the "System Status = Custom" in Downloading Mode , which usually flashing device with Official Firmware it should be changed to "Official
it's wired !!! I've tried 10 different Firmwares with correct binary (the phone's binary is 3 and firmware's binary is also 3)
but it doesn't changed to "Official" ( still System Status = custom :| )
note : i also tried combination files on this phone !
Second , after device flashing , it's just rebooted to recovery mode and shows the below error messages :
- E:failed to mount /efs (Invalid argument)
- E:failed to clear BCB message: failed to find /misc partition
- dm-verity verification failed...
As i know flashing the custom recovery on phone and adb commands solved my problem ! but frp lock is on and i can't flash the custom recovery !!!
note : phone not booted after flashing !
Does anyone know how to deal with this ?!
Click to expand...
Click to collapse