I have been working on porting CyanogenMod to my phone, the Samsung Galaxy Centura. I've been able to make recoveryimage, make systemimage, and flash with heimdall and all that, but when I try to make bacon I get an error that my recovery.fstab is improperly formatted. It looks OK to me? Am I missing something obvious?
# mount point fstype device [device2]
/recovery emmc /dev/block/mmcblk0p12
/boot emmc /dev/block/mmcblk0p8
/data ext4 /dev/block/mmcblk0p18
/cache ext4 /dev/block/mmcblk0p17
/sd-ext vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system ext4 /dev/block/mmcblk0p16
/sdcard datamedia /dev/null
/efs ext4 /dev/block/mmcblk0p19
/misc emmc /dev/block/mmcblk0p21
Specifically, it says that the first line
/recovery emmc /dev/block/mmcblk0p12
is improperly formatted. What gives? Everything else works.
Sir
I strongly suggest to read carefully this guide :
[GUIDE][CM Port][ MT6589 only] Port CyanogenMod 10.2/11 for all MT6589 devices
http://forum.xda-developers.com/showthread.php?t=2814498
Related
Hi,
I have a Zenithink C-94 tablet running ICS on it. I have compiled a JB rom and a KK rom for it, but have not been able to get the tablet to even come on. I contacted Zenithink and requested the kernel source since it is under GPL, but have had no luck. I managed to come up with the proprietaries (ex. cameras, codecs, etc.) and either obtain or write drivers for them. I have compiled the kernel, but this tablet has two kernels. Yes, two kernels; one for the boot.img and one for the "uImage_update". This writes to the vendor partition (mmcblk0p8). The kernel I have compiled is for the boot.img. I am now working on the uImage_update kernel. This one the CPIO is customized big time. See the ICS_CPIO.zip (attached). I am working on the scripts in this to update them to JB /KK. These scripts involve the partitions and recovery.fstab, etc. The partitions have changed from ICS to JB / KK. ICS was like this:
Code:
mmcblk0p1 ------- BOOT
mmcblk0p2 ------- RECOVERY
mmcblk0p4 ------- MEDIA
mmcblk0p5 ------- SYSTEM
mmcblk0p6 ------- CACHE
mmcblk0p7 ------- DATA
mmcblk0p8 ------- Vender
mmcblk0p9 ------- MISC
JB / KK are like this:
Code:
mmcblk0p1 ------- BOOT
mmcblk0p2 ------- RECOVERY
mmcblk0p4 ------- DATA
mmcblk0p5 ------- SYSTEM
mmcblk0p6 ------- CACHE
mmcblk0p7 ------- DEVICE (AKA Vender)
mmcblk0p8 ------- MISC
Boot, recovery, system, and cache have not changed. Data which was on mmcblk0p7 is now on mmcblk0p4. Device, which was known as vender, was on mmcblk0p8 is now on mmcblk0p7. Misc which was on mmcblk0p9 is now on mmcblk0p8. ICS had Media and Data separate, now they are together on the same partition. I know to change the partitions in the scripts, but I am having trouble with the recovery.fstab part. ISC is like this:
Code:
/boot emmc /dev/block/mmcblk0p1
/recovery emmc /dev/block/mmcblk0p2
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/data ext4 /dev/block/mmcblk0p7
## /misc emmc /dev/block/mmcblk0p9
# UBI support is under below:
#/system ubifs /dev/ubi1_0
#/data ubifs /dev/ubi1_2
#/cache ubifs /dev/ubi1_1
/sdcard vfat /dev/block/mmcblk0p4
JB / KK are like this:
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
/devices/platform/sdhci-esdhc-imx.2/mmc_host/mmc1 /mnt/extsd vfat defaults voldmanaged=sdcard:auto
/devices/platform/fsl-ehci /mnt/udisk vfat defaults voldmanaged=sdcard:auto
/dev/block/mmcblk0p5 /system ext4 ro wait
/dev/block/mmcblk0p4 /data ext4 nosuid,nodev,nodiratime,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic wait,encryptable=footer
/dev/block/mmcblk0p6 /cache ext4 nosuid,nodev,nomblk_io_submit wait
/dev/block/mmcblk0p7 /device ext4 ro,nosuid,nodev wait
/dev/block/mmcblk0p1 /boot emmc defaults defaults
/dev/block/mmcblk0p2 /recovery emmc defaults defaults
/dev/block/mmcblk0p8 /misc emmc defaults defaults
In the sbin folder of the CPIO is the "product_tool.sh". It has this line:
Code:
if mount -t vfat /dev/block/mmcblk1p1 /sdcard
How would I rewrite this for JB / KK according to the recovery.fstab? Would this stay the same? Please help.
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
Could a genius with some time on there hands make TWRP for this device, its driving me insane, everything provided below.
Android 8.1
2GB RAM
Snapdragon 210
MSM8909
GPU Adreno 304
Times like these i wish i could follow a tutorial correctly.
Thanks in advance!
I had to archive the recovery as the IMG was over 8MB.
frankieuk said:
Could a genius with some time on there hands make TWRP for this device, its driving me insane, everything provided below.
Android 8.1
2GB RAM
Snapdragon 210
MSM8909
GPU Adreno 304
Times like these i wish i could follow a tutorial correctly.
Thanks in advance!
I had to archive the recovery as the IMG was over 8MB.
Click to expand...
Click to collapse
I know this reply is a little late... but have you tried twrp builder app? Search xda... got a working recovery for an obscure UMX budget phone... I have this tablet but I haven't bothered trying to do anything with it.
i have ported the Lenovo Tab 10 TB-X103F twrp to {TB-X104F}
tdawgg777 said:
I know this reply is a little late... but have you tried twrp builder app? Search xda... got a working recovery for an obscure UMX budget phone... I have this tablet but I haven't bothered trying to do anything with it.
Click to expand...
Click to collapse
i have ported the Lenovo Tab 10 TB-X103F twrp to {TB-X104F}but.... i having problems with partitions when i boot into it
i think my problems has to do with recovery.FSTAB file
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
heres my current recovery.fstab for twrp
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
#device mount point fstype [device2] [length=]
/boot emmc /dev/block/bootdevice/by-name/boot flags=display="Boot";backup=1
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=display="Recovery";backup=1
/system ext4 /dev/block/bootdevice/by-name/system flags=display="System";backup=1;wipeingui
/misc emmc /dev/block/bootdevice/by-name/misc flags=display="Misc";backup=0
/cache ext4 /dev/block/bootdevice/by-name/cache flags=display="Cache";backup=1;wipeingui;wipeduringfactoryreset
/data ext4 /dev/block/bootdevice/by-name/userdata flags=display="Data";backup=1;wipeingui;wipeduringfactoryreset;length=-16384
/sdcard0 vfat /dev/block/mmcblk1p1 flags=display="Micro SDCard";storage;wipeingui;removable;backup=0
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
______________________________________________________________________________________________________________________
heres he stock recovery.fstab
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
#device mount point fstype [device2] [length=]
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc wait,check,encryptable=footer
/dev/block/mmcblk1p1 /sdcard vfat nosuid,nodev wait
/dev/block/bootdevice/by-name/boot /boot emmc defaults defaults
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
none of the partitions show up except (microsd card)
what am i doing wrong
Interested in recovery for this tablet also. Any luck?
Sent from my SM-N960U using Tapatalk
Hello Good People,
Is there a working TWRP for this tablet?
T.I.A.
Hello again,
Is there any working recovery for this tablet.
Its very very difficult to find a custom ROM.
Are people using LineageOS ?
T.I.A.
TWRP 3.X Ported
For
Reno8_Pro MT6572This TWRP based from TEch Y2 phoneWHAT WORK?
BACKUP/RESTORE
INSTALL ZIP/IMAGE
FILE MANAGER
COPY FILE
NOT WORK?
Move FIle
Another? Tell me!
TOOL TO FLASH
SP FLASH TOOL
FLASHIFY(root required)
IMPORTANT THING!!!
1.MAKE BACKUP YOUR ROM AND RECOVERY TO PROCEED
2.Before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
3.I have same device with different mount point.Make sure check on your phone first using Diskinfo apps
HERE Link
recovery.img
drive.google.com
HERE THIS RECOVERY MOUNT POINT
/boot emmc /dev/bootimg flags=display="Boot";backup=1
/logo emmc /dev/logo flags=display="Logo";backup=1
/cache ext4 /dev/block/mmcblk0p5 flags=display="Cache";wipeingui;backup=1
/data ext4 /dev/block/mmcblk0p6 flags=display="data";storage;wipeingui;backup=1
/nvram emmc /dev/nvram flags=display="Nvram";backup=1
/recovery emmc /dev/recovery flags=display="Recovery";backup=1
/system ext4 /dev/block/mmcblk0p4 flags=display="System";wipeingui;backup=1
/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD";storage;wipeingui;removable
/uboot emmc /dev/uboot flags=display="uboot";backup=1
/sd-ext auto /dev/block/mmcblk1p2