[Q] mount points atrix vs dx2 - Motorola Droid X2

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.

Related

[Q] Another bricked Desire X

I will start by excusing for the messed up mail.
Have a HTC Desire X(Y13) that is bricked. It have been unlocked and rooted. Original FW. Got OTA notice yesterday. I reinstalled the recovery and locked it.
After i ran the update and rebooted, it stayed on the welcome/beats screen.
I unlocked it and reinstalled the recovery(CWM).
And now I get the “Can't mount /cache/recovery” ect.
I do have a backup from the CWM. But when trying to restore it. It exits just after it restore the boot.img.
Tried to install different roms. Both cooked and “DesireX1.14.401.1.zip".
Get’s “Installing update”. Assert failed: write_raw_image(“/tmp/boot.img”. “boot”)
I have tried to lock it and restore a stock recovery. And then run the RRU:
RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed”
It starts by erasing the user data. Says Starting and Sending. Updating Signature. And after 1min or so it fails with Error 158:Image error.
But it's a Proto ?
I can lock/unlock it. Flash boot.img and recovery’s. Have tried working with the WINTEAM loader. Same problem.
So no matter what I do, I just cant unbrick it. Any ideas on how to do that ?
Could I do an ADB format of the different partitions and flash them? ANY suggestion are welcome.
Log snippets:
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/mmcblk0p21 (null) 0
2 /boot emmc /dev/block/mmcblk0p22 (null) 0
3 /cache ext4 /dev/block/mmcblk0p27 (null) 0
4 /data ext4 /dev/block/mmcblk0p26 (null) 0
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
6 /system ext4 /dev/block/mmcblk0p25 (null) 0
7 /misc emmc /dev/block/mmcblk0p17 (null) 0
8 /devlog ext4 /dev/block/mmcblk0p28 (null) 0
9 /emmc vfat /dev/block/mmcblk0p31 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
magiske said:
I will start by excusing for the messed up mail.
Have a HTC Desire X(Y13) that is bricked. It have been unlocked and rooted. Original FW. Got OTA notice yesterday. I reinstalled the recovery and locked it.
After i ran the update and rebooted, it stayed on the welcome/beats screen.
I unlocked it and reinstalled the recovery(CWM).
And now I get the “Can't mount /cache/recovery” ect.
I do have a backup from the CWM. But when trying to restore it. It exits just after it restore the boot.img.
Tried to install different roms. Both cooked and “DesireX1.14.401.1.zip".
Get’s “Installing update”. Assert failed: write_raw_image(“/tmp/boot.img”. “boot”)
I have tried to lock it and restore a stock recovery. And then run the RRU:
RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed”
It starts by erasing the user data. Says Starting and Sending. Updating Signature. And after 1min or so it fails with Error 158:Image error.
But it's a Proto ?
I can lock/unlock it. Flash boot.img and recovery’s. Have tried working with the WINTEAM loader. Same problem.
So no matter what I do, I just cant unbrick it. Any ideas on how to do that ?
Could I do an ADB format of the different partitions and flash them? ANY suggestion are welcome.
Log snippets:
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/mmcblk0p21 (null) 0
2 /boot emmc /dev/block/mmcblk0p22 (null) 0
3 /cache ext4 /dev/block/mmcblk0p27 (null) 0
4 /data ext4 /dev/block/mmcblk0p26 (null) 0
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
6 /system ext4 /dev/block/mmcblk0p25 (null) 0
7 /misc emmc /dev/block/mmcblk0p17 (null) 0
8 /devlog ext4 /dev/block/mmcblk0p28 (null) 0
9 /emmc vfat /dev/block/mmcblk0p31 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
Click to expand...
Click to collapse
You need a jb optimized recovery...
Stereo8 said:
You need a jb optimized recovery...
Click to expand...
Click to collapse
Thanks. Now I can get it up and running. Can I downgrade from here ? Would like to be able to restore my backup ??
/Mads
Yes!
Flowed from my HTC branded muffin...
Surely kernel problem
Hahahahha the same here...For that we need RUU JB aways can fix the mess that we make

how to Add New HTC Device to Android Kitchen

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

[Q] Need Assist in defining new device in dsixda's kitchen

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

Problem building CWM recovery for SM-G313H

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

What file system should i use?

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...

Categories

Resources