[Galaxy S 5 Q&A, Help & Troubleshooting] davidk21770:
Resolved

Resolved :cool: -- After much more hunting around, I followed the clue in the log and started to umount / fsck -n each partition and found that EFS was hosed. I restored from backup, got a clean e2fsck, and was able to restore my backup and boot. I guess that the process of testing RR hosed it and my repeated attempts to get well just made things worse! :eek:

Thanks godofsalt for your inputs!

Thanks!

I am using odin 3.07 and 3.09. They are different, but the results are the same with either (these are what I used to root the phone). And I'm only using these to install recovery roms until I figured out the the recovery roms would let me install a different version and just chain to it.

I am using TWRP 3.1.0.0 and 3.1.1.0 and both have the same results. Both came from twrp.me and although not listed in the app, appear "official".

My ancient CWM is the last Philz touch version from before he stopped development 6.0.4.8. Since it doesn't talk to the ext sd out of the box I've been avoiding it other than as a double check just to see if I get different results (I figured out how to get to it to talk to the ext sd by using aroma file manager to access the command line to mount and link it to the file system).

I AM using Titanium Backup (Pro) (you're right -- great program)

Is the modem part of EFS? (I have a backup of EFS).

I resisted going back to stock roms, just because of all of the time that would be wasted. I figured (hoped) that I could simply go forward.

The issue has degraded to the point where nothing will boot other than recovery and install. I've continued to research and finally (took me way too long) I dumped and looked at the log.

When I grep on error, these CRC errors look really bad:

<3>[ 7.119548] [c0] dwmmc_exynos 12200000.dwmmc0: data CRC error READ

<6>[ 7.119614] [c5] mmc_host mmc0: Tuning error: cmd.error:0, data.error:-84

<3>[ 7.120317] [c0] dwmmc_exynos 12200000.dwmmc0: data CRC error READ

<6>[ 7.120378] [c5] mmc_host mmc0: Tuning error: cmd.error:0, data.error:-84

<6>[ 7.120519] [c5] mmc_host mmc0: Tuning error: cmd.error:-84, data.error:-115

<3>[ 7.198199] [c0] dwmmc_exynos 12220000.dwmmc2: data CRC error READ

<6>[ 7.198256] [c4] mmc_host mmc2: Tuning error: cmd.error:0, data.error:-84

<3>[ 7.198358] [c0] dwmmc_exynos 12220000.dwmmc2: data CRC error READ

<6>[ 7.198409] [c4] mmc_host mmc2: Tuning error: cmd.error:0, data.error:-84

<4>[ 14.426685] [c5] EXT4-fs warning (device mmcblk0p3): ext4_clear_journal_err:4565: Filesystem error recorded from previous mount: IO failure

<4>[ 14.427518] [c5] EXT4-fs (mmcblk0p3): warning: mounting fs with errors, running e2fsck is recommended

I've been suspicious that somewhere along the line the partition table got hosed, so I looked for that too and found:

<6>[ 7.121748] [c5] mmcblk0: mmc0:0001 V3W00M 14.6 GiB

<6>[ 7.121947] [c7] mmcblk0boot0: mmc0:0001 V3W00M partition 1 4.00 MiB

<6>[ 7.122192] [c4] mmcblk0boot1: mmc0:0001 V3W00M partition 2 4.00 MiB

<6>[ 7.122415] [c7] mmcblk0rpmb: mmc0:0001 V3W00M partition 3 512 KiB

<6>[ 7.126348] [c7] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21

<6>[ 7.131647] [c7] mmcblk0boot1: unknown partition table

<6>[ 7.132609] [c7] mmcblk0boot0: unknown partition table

These both look really bad.

I don't want to run fsck until I'm sure that the partition table's right. AND, I thought that the overwritten partitions got rebuilt every time that I installed a new ROM (at least data, system, cache, preload, and dalvik), so – is my good-old-S5 dieing?

I'm quite comfortable with bash/sh/linux and am a very advanced computer user (30+ years -- yea, way back when an 8 bit 16k computer was the size of a couple of big fridges -- I learned on one ;)), but Android internals are new to me.

Any further suggestions -- or information?

What should the partition table be? (I can provide a dump of /proc/partitions – but I'd really like to see someone else's!) And, if it's wrong, I'll need a little help to fix it! (Or links!)

Thanks!

Edit:

Additional problem with stock firmware. I have no idea of the firmware country and can't figure out how to get it since I'm almost bricked and can't boot! I had SamMobile installed and it told me -- but I can't find a record of it!