Database Info

[Completed] I can't make bacon? recovery.fstab error

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

getting stock rooted Calkulin rom converted to data/cache f2fs

@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?

[GUIDE][DEV] How to convert NAND ROM to SD-EXT ROM for MultiBootloader

How to convert NAND ROM to SD-EXT ROM for MultiBootloader​
Code:
After following this guide, your ROM can be use with [URL="http://forum.xda-developers.com/nokia-x2/development/sbl-multibootloader-v1-00-04-10-2015-t3217360"]MultiBootloader[/URL]
THIS GUIDE IS NOT FOR NOOBs
Requirements
Knowledge about Android Image Kitchen
Notepad ++
A nand ROM extracted
Instructions
Delete the RED COLOR
Add the BLUE COLOR
Step 1: Modifying boot.img (FOR STOCK KERNEL ONLY) - Check post #2 to download the modified boot image, you don't need to edit it yourself.
Use Android Image Kitchen's unpackimg command to unpack the boot.img file from the ROM your want to port.
Go to Android Image Kitchen\ramdisk folder, edit these files:
fstab.qcom
Change like this:
Code:
# Android fstab file.
# 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
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
[COLOR="Red"]/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,check,encryptable=footer[/COLOR]
[COLOR="Blue"]/dev/block/platform/msm_sdcc.1/by-name/userdata /nanddata ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,check,encryptable=footer[/COLOR]
/devices/msm_sdcc.2/mmc_host /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard:auto
#/dev/block/mmcblk0p11 /system ext4 ro,barrier=1 wait
#/dev/block/mmcblk0p12 /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc wait,check,encryptable=footer
init.rc
- Find this event:
Code:
on fs
- Change like this:
Code:
on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
[COLOR="Red"]mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
mount yaffs2 [email protected] /data nosuid nodev[/COLOR]
[COLOR="Blue"] mount ext4 /dev/block/mmcblk1p2 /system
mount ext4 /dev/block/mmcblk1p2 /system ro remount
mount ext4 /dev/block/mmcblk1p3 /data nosuid nodev[/COLOR]
mount yaffs2 [email protected] /cache nosuid nodev
[COLOR="Blue"]#mount nand data for sharing data/app
mkdir /nanddate 0771 system system
mount yaffs2 [email protected] /nanddata nosuid nodev
# mount sdcard
wait /dev/block/mmcblk1p1
wait /dev/block/mmcblk1p1
mount vfat /dev/block/mmcblk1p1 /storage/sdcard1[/COLOR]
​
init.target.rc
- Find this event:
Code:
on fs
- Change like this:
Code:
on fs
mount_all fstab.qcom
# Keeping following partitions outside fstab file. As user may not have
# these partition flashed on the device. Failure to mount any partition in fstab file
# results in failure to launch late-start class.
wait /dev/block/platform/msm_sdcc.1/by-name/cache
mount ext4 /dev/block/platform/msm_sdcc.1/by-name/cache /cache nosuid nodev barrier=1
wait /dev/block/platform/msm_sdcc.1/by-name/persist
mount ext4 /dev/block/platform/msm_sdcc.1/by-name/persist /persist nosuid nodev barrier=1
wait /dev/block/platform/msm_sdcc.1/by-name/modem
mount vfat /dev/block/platform/msm_sdcc.1/by-name/modem /firmware ro shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337
[COLOR="Red"] wait /dev/block/platform/msm_sdcc.1/by-name/custom
mount ext4 /dev/block/platform/msm_sdcc.1/by-name/custom /custom nosuid nodev barrier=1 ro[/COLOR]
[COLOR="Blue"] wait /dev/block/mmcblk1p4
mount ext4 /dev/block/mmcblk1p4 /custom nosuid nodev barrier=1 ro[/COLOR]
​
Repack boot.img and copy to the ROM folder.
Step 2: Modifying updater-script
Open ROM-name\META-INF\com\google\android\updater-script
Find:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p19", "/system");
or
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
Add these lines above it:
Code:
[COLOR="blue"]ui_print(" Mounting Partitions ");
mount("ext4", "MMC", "/dev/block/mmcblk1p2", "/system-ext");
mount("ext4", "MMC", "/dev/block/mmcblk1p4", "/custom-ext");
mount("ext4", "EMMC", "/dev/block/mmcblk0p20", "/cache");
mount("ext4", "MMC", "/dev/block/mmcblk1p3", "/data-ext");
ui_print(" Formatting Partitions ");
delete_recursive("/system-ext");
delete_recursive("/custom-ext");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data-ext");[/COLOR]
Find this line:
Code:
package_extract_file("boot.img", "/tmp/boot.img");
Change like this:
Code:
[INDENT][COLOR="Red"]package_extract_file("boot.img", "/tmp/boot.img");
run_program("/system/xbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p10");
delete("/tmp/boot.img");[/COLOR][COLOR="Blue"]
package_extract_file("boot.img", "/emmc/kernels/[I]your_rom_name[/I].img");[/COLOR][/INDENT]
Find and change all /system/ to /system-EXT/
Find and change all /custom/ to /custom-EXT/
Save.
Step 3: Create the ZIP
Make sure you have copy the modified boot.img to the ROM folder
Select all the files and folders in the ROM folder (custom, system, META-INF, boot.img,etc..)
Compress into ZIP file.
Done.
<EDITTING>

I have modifed the boot.img to boot into sdext ROM:
For stock based ROM: stock_ext.img - thanks to @symbuzzer for adding some features and fixing the ril & sdcard bugs
modified_stock_insecure-kernel.img - (Maybe I've made some mistake in this file. I don't recommend to use this, it can cause some bugs with sdcard0. Better modify it yourself.)
For CM11 based ROM: ext_cm11.img

Great ! Im waiting for this

Bro how can intsall the rom
I m try but couldn't with me
Plz help ??

@SonnySimon this method doesnt work on Stock Kernel/Rom. I will attach stock kernel on XDA today. You can compare mine with yours and update this post. Thanks

symbuzzer said:
@SonnySimon this method doesnt work on Stock Kernel/Rom. I will attach stock kernel on XDA today. You can compare mine with yours and update this post. Thanks
Click to expand...
Click to collapse
It works. I tried and it boots successfully into ext stock ROM but have some bugs with ril and sdcard.

SonnySimon said:
It works. I tried and it boots successfully into ext stock ROM but have some bugs with ril and sdcard.
Click to expand...
Click to collapse
I meant yours have bugs Thanks anyway

[HOW TO] BOOT FROM SD CARD [SUCCESSFULLY] on QMobile Z8 with BRICKED/DEAD eMMC
SimonVN said:
How to convert NAND ROM to SD-EXT ROM for MultiBootloader
Click to expand...
Click to collapse
I have been successfully able to boot from SD card on QMobile Z8 by partitioning SD card on a Ubuntu machine using 'parted' and 'fdisk' commands, replicating eMMC partition table and then flashing factory firmware images to these newly created partitions using 'dd' command. Then I modified "fstab.qcom" & "init.tegra.rc" files in kernel (boot.img) and "recovery.fstab" and "uneventd.rc" files in twrp recovery to initiate mounting and booting from sd card instead of internal memory. It was successful after some experiments. Details can be found here:
https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171
But I have still a few queries to be answered. Please have a look. Any help, comments, information or suggestions will be appreciated.

Genius wanted: TWRP for LENOVO TB-X104F

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.

[RECOVERY] [Reno 8 Pro] [MT6572] TWRP 3.x

TWRP 3.X Ported
For
Reno8_Pro MT6572​​This TWRP based from TEch Y2 phone​WHAT 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