Hello, my device is not defined in dsixda's kitchen. And i could not define my device on my own in kitchen. I need some help in defining my device. Please , help me. i will provide with all the information required about my device please build it for me..
Here are the information i get when i open recovery.fstab
# mount point fstype device [device2]
#Gionee lingfen 20120716 add for CR00651943 start
#this is map from /proc/dumchar_info
/boot emmc boot
/cache ext4 /dev/block/mmcblk0p7
/data ext4 /dev/block/mmcblk0p8
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sdcard2 vfat /dev/block/mmcblk0p9
/system ext4 /dev/block/mmcblk0p6
#Gionee lingfen 20120716 add for CR00651943 end
Related
Here is the recovery.fstab for the atrix
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p11
/cache ext4 /dev/block/mmcblk0p15 NULL ext3
/data ext4 /dev/block/mmcblk0p16 NULL ext3
/sdcard vfat /dev/block/mmcblk1p1
/emmc vfat /dev/block/mmcblk0p18
/system ext4 /dev/block/mmcblk0p12 NULL ext3
/recovery emmc /dev/block/mmcblk0p10
/osh ext3 /dev/block/mmcblk0p13
/preinstall ext3 /dev/block/mmcblk0p17
And here the dx2
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system auto /dev/block/mmcblk0p12
/cache ext3 /dev/block/mmcblk0p15
/data ext3 /dev/block/mmcblk0p16
#/misc mtd misc
#/boot mtd boot
#/recovery mtd recovery
/pds ext3 /dev/block/mmcblk0p3
#/preinstall ext3 /dev/block/mmcblk0p17
/emmc vfat /dev/block/mmcblk0p18
I am trying to find the err in the mongrel cwr. More: log from this: cwr 5025 + oly recovery(sbin) + oly etc( recovery.fstab ). See thread cwr hacking.
It backsup but adv restore fails.
Do you mean you can make a backup nandRoid but it wont restore it?
---------- Post added at 09:37 PM ---------- Previous post was at 09:35 PM ----------
Cuz Dragonz made it that far before... Restore fails because /system can't unmount because there is processes using it...
Yes here is my latest mongrel cwr.
But the full restore will never untill we get a UL boot loader so use adv restore for testing or find a work around.
I already get the recovery.fstab as following
# mount point fstype device [device2]
/boot emmc boot
/cache ext4 cache
/data ext4 userdata
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 system
/devlog ext4 devlog
/internal_sdcard vfat /dev/block/mmcblk0p35
to add new device create file in edify_defs with the same of device, as above listed mount point how can I edit the new file
Thanks for help
Hey guys, I was recently given a Galaxy Tab 3 Lite (SM-T110) and have found very little roms considering its an old tablet and none are with my latest stock firmware. That said, I'm trying to implement this tablet into dsixda's kitchen but am having a little bit of trouble.
I have set up the kitchen successfully on Windows 10 using cygwin and have even complied a rom successfully but the problem is when I flash it it gives me errors about boot.img mounting points. I pretty much have 3 questions:
1. Cant find my boot mnt point and was wondering if someone can help me find it? (ill attach my recovery.fstab file in the bottom for you to see)
2. Dont really know if I need that "fix_boot2=yes" line? "fix_boot=yes" line? Or none? How can I tell if i need it?
3. Since boot mount point is not inside recovery.fstab file, does that mean it is not need to be mentioned?
I made a file called "goyawifi" inside the edify_defs folder with the following info inside it:
# Samsung Galaxy Tab 3 Lite SM-T110
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p15
cache_mnt=\/dev\/block\/mmcblk0p14
boot_mnt=\/dev\/block\/mmcblk0p15
data_mnt=\/dev\/block\/mmcblk0p16
sdcard_mnt=\/dev\/block\/mmcblk1p1
fix_boot2=yes
And this is my recovery.fstab info:
#mount point fstype device [device2]
/mrd emmc /dev/block/mmcblk0p1
/mrd1 emmc /dev/block/mmcblk0p2
/mep2 emmc /dev/block/mmcblk0p3
/efs ext4 /dev/block/mmcblk0p4
/dtim emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p9
/kernel emmc /dev/block/mmcblk0p10
/radio emmc /dev/block/mmcblk0p11
/custom ext4 /dev/block/mmcblk0p12
/preload ext4 /dev/block/mmcblk0p13
/cache ext4 /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p16 length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/mnt/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Can anyone please help me to start customizing/flashing my rom? Thanks in advance...
FWI: When I say "successfully compiled a rom" I mean that the kitchen makes a rom, but upon flashing it, it gives me an error. Something about boot.img not mounted right
Bump! 45 views and no replies? So many developers here, surely someone knows the answer to my problems
Tried again to build a rom using dsixda's Android Kitchen, would like to find boot mount points... can anybody help?
Sorry, I don't have this device to test, but I think you should check "/kernel emmc /dev/block/mmcblk0p10"
Here should be the kernel image and maybe not the whole boot.img !
As you already know , boot.img have a kernel image and a ramdisk .... but on your device , ramdisk may be under /system ... I'm not 100% sure ... but from what you've posted so it seems !
So, there is no partition on your device for boot.img ... anyway you can make a custom rom also in this case, but you should know how to flash the new kernel image and also the ramdisk !
Unfortunately Samsung has made this device quite difficult for development, but not impossible .
Good luck !
Hello all,
I'm new to the world of ROMS and custom recoveries, I've rooted my phone and for educational purposes, I wanted to build CWM 6 but I have trouble with my recovery.fstab or something because I only get a blank screen flashing periodically.
Here's the stock recovery.fstab of the recovery.img
Code:
/dev/block/platform/sprd-sdhci.0/mmcblk1p1 /sdcard vfat default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/HIDDEN /preload ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 default wait,length=-16384
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/PRODNV /productinfo ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/KERNEL /boot emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/RECOVERY /recovery emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/modem /modem emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/DSP /modem2 emmc default recoveryonly
I've also tried this version (after changing the names with partitions)
Code:
# mount point fstype device
/system ext4 /dev/block/mmcblk0p18
/preload ext4 /dev/block/mmcblk0p19
/data ext4 /dev/block/mmcblk0p20
/cache ext4 /dev/block/mmcblk0p17
/efs ext4 /dev/block/mmcblk0p7
/productinfo ext4 /dev/block/mmcblk0p5
/boot emmc /dev/block/mmcblk0p11
/recovery emmc /dev/block/mmcblk0p12
/modem emmc /dev/block/mmcblk0p13
/modem2 emmc /dev/block/mmcblk0p14
/sdcard vfat /dev/block/platform/sprd-sdhci.0/mmcblk1p1
but to no avail, the only result that I got was when I used the fstab of the boot.img
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
# <src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
#/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 ro,barrier=1 wait
#/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit wait,encryptable=footer,check
#/dev/block/platform/sprd-sdhci.3/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit wait,check
#/dev/block/platform/sprd-sdhci.3/by-name/prodnv /productinfo ext4 noatime,nosuid,nodev,nomblk_io_submit wait,check
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 ro,noatime,errors=panic wait
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check,encryptable=footer
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/dev/block/platform/sprd-sdhci.3/by-name/PRODNV /productinfo ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/devices/platform/sprd-sdhci.0/mmc_host/mmc1 auto vfat defaults voldmanaged=extSdCard:auto,noemulatedsd
would you please tell me what I'm missing here ?
Just want to know
Could you tell me how you got root for this phone..? Been searching all over with no luck
Edit: I found solution
ext4 according to TWRP fstab
https://twrp.me/samsung/samsunggalaxya32017.html
Code:
/boot emmc /dev/block/platform/13540000.dwmmc0/by-name/BOOT
/cache ext4 /dev/block/platform/13540000.dwmmc0/by-name/CACHE
/data ext4 /dev/block/platform/13540000.dwmmc0/by-name/USERDATA length=-16384
/recovery emmc /dev/block/platform/13540000.dwmmc0/by-name/RECOVERY
/system ext4 /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM
/efs emmc /dev/block/platform/13540000.dwmmc0/by-name/EFS flags=display="EFS";backup=1
/radio emmc /dev/block/platform/13540000.dwmmc0/by-name/RADIO flags=display="Modem";backup=1
/cpefs emmc /dev/block/platform/13540000.dwmmc0/by-name/CPEFS flags=display="CPEFS";backup=1
/system_image emmc /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM
/cache_image emmc /dev/block/platform/13540000.dwmmc0/by-name/CACHE
/radio_image emmc /dev/block/platform/13540000.dwmmc0/by-name/RADIO
/hidden_image emmc /dev/block/platform/13540000.dwmmc0/by-name/HIDDEN
/external_sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable
/usb-otg vfat /dev/block/sdd1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
Nothing to learn here... F... I hate these.. "I found solution".
Me, me, me,,, and then comes another asking for the same...