@Calkulin (because you uploaded the rom)
@katinatez (because you are good folk)
@zaphodbeeb (becasue you are the one that taught me to convert to mixed partitions)
hoping to get some help on this for me and others wanting to try out the update.
i am trying to get the rooted 05q to work on my mixed f2fs/etx4 partitions. data/cache f2fs - system etx4 so i don't have to wipe my /data partition.
i have gone through several routes so far to no avail. sideloading/flashing. flashing the ak 113 kernel with instructions for the new update. updated to the new katinatez philz with the new f2fs comits.
1. updater script - i did not see a need in changing the /data to use busybox for f2fs as the line of code is already there.
2. fstab.bacon - i used zaphods new f2fs all or f2fs mixed
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/system /system f2fs ro,noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=panic wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/reserve4
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait,nonremovable,encryptable=/dev/block/platform/msm_sdcc.1/by-name/reserve4
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/devices/platform/xhci-hcd auto vfat defaults voldmanaged=usbdisk:auto
at first i just flashed the the new extras file (firmware modem linked with Calkulin's rom. then flashed the rom. i got stuck on the bootanimation for ten minutes.
then i thought it might be the kernel not 'jiving' with f2fs. so i sideloaded the ak_113 (on top of what i had already done) with the instructionsfrom @xlollomanx (thanks) linked from the ak kernel thread.
still.... stuck on cyanogen boot for ten minutes
then i restored my backup and sideloaded everything, ak kernel and all, from scratch.
once again... grrr. still stuck on boot animation for ten minutes.
any ideas on what i can do?
Related
Can somebody with F2FS working test this kernel?
It's only adds patched hammerhead.fstab to ramdisk.
/dev/block/platform/msm_sdcc.1/by-name/system /system f2fs ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid,nodev,errors=panic wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/metadata
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nosuid,nodev,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/persist /persist f2fs nosuid,nodev,errors=panic wait
Click to expand...
Click to collapse
Download: http://rghost.ru/57107617
Just gave it a go. It wouldn't boot (stopped at Google logo).
My set up: http://forum.xda-developers.com/google-nexus-5/general/running-nexus-5-t2598207/page99#post54418646
Hi developers, I'm trying to compile cwm from sources. When I do "make -j4 recoveryimage" I can test the recovery and it works, but when I flash it seems it installs in download mode (see attached image). I think the recovery.fstab is the problem), but I can't find the problem
Here's my recovery.fstab:
Code:
# mount point fstype device [device2] fstype2
/boot emmc /dev/block/bootdevice/by-name/boot
/system ext4 /dev/block/bootdevice/by-name/system
/cache ext4 /dev/block/bootdevice/by-name/cache
/data ext4 /dev/block/bootdevice/by-name/userdata length=-16384
/sdcard vfat /dev/block/mmcblk1p1
I've created TWRP 3.0.2 from sources (to be honest - only TWRP, Kernel is prebuilt from Stock ROM)
HowTo Flash TWRP
http://ulefone.com/download/power.html (no root required)
Or extract twrp.img from zip File and use Apps like Flashify (root required)
HowTo gain root
After this you can Flash flash SuperSU via TWRP:
http://forum.xda-developers.com/showthread.php?t=1538053
Thanks to
@BlueFlame4
Nice!
Perfect thanks!!!
Thanks for your work.
Are you able to create a twrp for the ulefone power 2, if I provide you a scatter file of the power 2 stockrom?
I already tried it myself but ended up in many bootloops.
Greetings
Good evening.please help me.i want to uninstall custom recovery twrp (teamwin) can you tell me how to uninstall in order to install the official one?
kraftmaschine said:
Thanks for your work.
Are you able to create a twrp for the ulefone power 2, if I provide you a scatter file of the power 2 stockrom?
I already tried it myself but ended up in many bootloops.
Greetings
Click to expand...
Click to collapse
After I unlocked the bootloader, I tried to port TWRP from Oukitel k6000 plus since both have same chipset MT6750T and same resolution. I tried to follow this guide on youtube video using Carliv Image Kitchen. But I failed. Heck, I tried to flash the k6000 plus recovery and nothing. Not even boot loops , the stock recovery still shows up.
Edit: I was partially successful. I was able to get to TWRP but touch screen not working. I connected a mouse and was able to change the Russian language of the original k6000+ TWRP port. But what is not working is the mounts of partitions. I tried to copy the mount points from fstab.mt6755 which is in stock recovery to the new port. But the new port doesn't have such file, instead it has goldfish fstab files, I tried editing them manually to match them, but it didn't work.
This is just a stab in the dark. If anyone know how to fix partition mounts and why touch screen not working, I would be grateful.
I replaced recovery.fstab from stock to the ported one also replaced default.prop.
fstab.mt6755 <- That comes with stock recovery
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system /system ext4 ro wait,verify
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,forceencrypt=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/metadata
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata /nvdata ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,formattable
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/frp /persistent emmc defaults defaults
/devices/mtk-msdc.0/11230000.msdc0* auto vfat defaults voldmanaged=sdcard0:auto
/devices/mtk-msdc.0/11240000.msdc1* auto vfat defaults voldmanaged=sdcard1:auto,encryptable=userdata
/devices/soc/11270000.usb3_xhci* auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvram /nvram emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/proinfo /proinfo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk /bootloader emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk2 /bootloader2 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/para /misc emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot /boot emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo /logo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/expdb /expdb emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/secro /secro emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/seccfg /seccfg emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1img /md1img emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1dsp /md1dsp emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1arm7 /md1arm7 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md3img /md3img emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/ppl /ppl emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee1 /tee1 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee2 /tee2 emmc defaults defaults
Click to expand...
Click to collapse
fstab.ranchu <- That comes with Oukitel k6000+ TWRP recovery
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/vda /system ext4 ro wait
/dev/block/vdb /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/vdc /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
#/devices/platform/goldfish_mmc.0 auto vfat defaults voldmanaged=sdcard:auto
Click to expand...
Click to collapse
Also fstab.goldfish <- That comes with Oukitel k6000+ TWRP recovery
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mtdblock0 /system ext4 ro,barrier=1 wait
/dev/block/mtdblock1 /data ext4 noatime,nosuid,nodev,barrier=1,nomblk_io_submit wait,check
/dev/block/mtdblock2 /cache ext4 noatime,nosuid,nodev wait,check
/devices/platform/goldfish_mmc.0* auto auto defaults voldmanaged=sdcard:auto,noemulatedsd
Click to expand...
Click to collapse
Ulefone Power2 volte is getting enabled.
I am not able to enable volte flag in ulefone power2... Does any one see volte flag as enabled. Even i am not able to root this phone
Please help
Dears,
I installed TWRP on SM-A530F/DS and flashed no-verity-opt-encrypt-6.0 and formatted data to let the phone boot.
Well, I'd like to re-encrypt the phone like I've always been doing on sammys after TWRP or Magisk installation, but it doesn't work on this phone.
No matter if it's Nougat or Oreo, applying encryption nothing happens and phone crashes backing to lock screen in a minute.
Any suggestions?
Thanks everybody.
Id like to encrpt mine too. Twrp and rooted with magisk. when i try and encrpt it just reboots after a minute. SMA530W
Dear @jcadduono,
sorry to bother, I think this issue is caused by Samsung's firmwares but, in your opinion, could it be related to no-dm-verity patch?
Or, is it possible to edit the patch in order to not to disable encryption?
There's a modification (red color in code), I think operated by the patch, to ramdisk's fstab.
Stock fstab:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# system and vendor partition will be early-mounted by kernel
/dev/block/platform/13500000.dwmmc0/by-name/SYSTEM /system ext4 ro,errors=panic wait,verify
/dev/block/platform/13500000.dwmmc0/by-name/CACHE /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/platform/13500000.dwmmc0/by-name/USERDATA /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,[COLOR="Red"]forceencrypt=footer[/COLOR],quota
/dev/block/platform/13500000.dwmmc0/by-name/EFS /efs ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/platform/13500000.dwmmc0/by-name/CPEFS /cpefs ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,nofail
# VOLD
/dev/block/platform/13500000.dwmmc0/by-name/HIDDEN /preload ext4 defaults voldmanaged=preload:auto
/devices/platform/13550000.dwmmc2/mmc_host/mmc1* auto vfat defaults voldmanaged=sdcard:auto
/devices/platform/13600000.usb/13600000.dwc3* auto auto defaults voldmanaged=usb:auto
Patched fstab:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# system and vendor partition will be early-mounted by kernel
/dev/block/platform/13500000.dwmmc0/by-name/SYSTEM /system ext4 ro,errors=panic wait
/dev/block/platform/13500000.dwmmc0/by-name/CACHE /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/platform/13500000.dwmmc0/by-name/USERDATA /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,[COLOR="red"]encryptable=footer[/COLOR],quota
/dev/block/platform/13500000.dwmmc0/by-name/EFS /efs ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/platform/13500000.dwmmc0/by-name/CPEFS /cpefs ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,nofail
# VOLD
/dev/block/platform/13500000.dwmmc0/by-name/HIDDEN /preload ext4 defaults voldmanaged=preload:auto
/devices/platform/13550000.dwmmc2/mmc_host/mmc1* auto vfat defaults voldmanaged=sdcard:auto
/devices/platform/13600000.usb/13600000.dwc3* auto auto defaults voldmanaged=usb:auto
Patch operation sounds correct, but this is the only device that fails in encryption them.
Thank you so much.
It's actually not uncommon for a ROM to not be able to re-enable /data encryption from the regular settings, once disabled manually.
As far as I can tell, no-verity-opt-encrypt-6.0.zip replaces the "must encrypt" flag on /data with a "can encrypt if you want" flag. When you format /data from TWRP after flashing that zip, you obtain a non-encrypted partition, but it should be possible to re-encrypt it.
Have you guys tried encrypting data from the adb shell? Details here: http://niki.hammler.net/wiki/Android_Device_Encryption#Setting_up_encryption
This is also recommended reading: https://source.android.com/security/encryption/full-disk
You should also check the system log to see what goes wrong when you try to activate encryption. This is how: https://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging
Hi! I'm a newbie here. I want to ask if the below code is correct for twrp.fstab? Those are the first 5 lines of twrp.fstab.
I change the following lines instead of ".../11120000.msdc0/by-name/system" to ".../11120000.msdc0/mmcblk0p23" and so on.
/dev/block/platform/mtk-msdc.0/11120000.msdc0/mmcblk0p23 /system ext4 ro wait,recoveryonly
/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/vendor /vendor ext4 ro wait,recoveryonly
/dev/block/platform/mtk-msdc.0/11120000.msdc0/mmcblk0p25 /data f2fs noatime,nosuid,nodev,discard,noflush_merge wait,check,formattable,resize,encryptable=/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/metadata,
/dev/block/platform/mtk-msdc.0/11120000.msdc0/mmcblk0p24 /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
PS. My recovery.img was ported using twrp auto porter but it can't mount system, data and cache.