[Samsung Galaxy Player 4.0, 5.0] TiMthisIS:
Alrighty, I took the NOOB video to heart and have spent a pantsload of time trying to unbrick my Galaxy S WiFi 5.0 that I got from woot.com that I mucked up with some bad files/bad settings on Odin, I don't really remember what I did anymore. I love the video, very well done.

My sgp has the physical home button but unlike all the other releases, it started out with Froyo. The box it came in says it's a YP-G70CW/TTT though there is some dispute where these were destined and I've seen conflicting info on the TTT. Probably doesn't matter. The fact is it started out with Froyo and I think everybody else started with Gingerbread.

Using various Adam Outler threads, I was able to get it out of hard brick using Unbrickable, then I got the Samsung logo back with the bootloader, and back into recovery/normal download mode using the G70-GalaxyPlayer5.0-8gig-Inter_model_2.3.5.pit

But then I'm stuck at a bunch of mount errors. Here's a screenshot I took with Droid Explorer: i42.tinypic.com/34g0ehc.jpg (sorry, can't post full links)

Applying the ROM from Eryigit-GB-2.3.6 G70ZCKPA release 3 gets me a nice little CWM recovery, the error list is shorter unless I look at the log. If I plug in a USB when the device is off, I get the "working" star with no animation and shortly after the empty battery icon appears and the player reboots, repeating the same routine. Unplugged it boots into CWM recovery.

i39.tinypic.com/i2lnnl.jpg

Here is a somewhat cleaned up formatting of the log I got off the player.

Starting recovery on Wed Mar 7 13:32:21 2012

framebuffer: fd 4 (480 x 800)

CWM-based Recovery v5.0.2.7

recovery filesystem table

=========================

0 /tmp ramdisk (null) (null)

1 /efs rfs /dev/block/mmcblk0p10 (null)

2 /system ext4 /dev/block/mmcblk0p13 (null)

3 /cache ext4 /dev/block/mmcblk0p15 (null)

4 /data ext4 /dev/block/mmcblk0p16 (null)

5 /datadata ext4 /dev/block/mmcblk0p14 (null)

6 /emmc vfat /dev/block/mmcblk0p17 (null)

7 /sdcard vfat /dev/block/mmcblk1p1 (null)

8 /boot emmc /dev/block/mmcblk0p11 (null)

9 /recovery emmc /dev/block/mmcblk0p12 (null)

W:Unable to get recovery.fstab info for /sd-ext during fstab generation!

I:Completed outputting fstab.

I:Processing arguments.

W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)

mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory

W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)

E:Can't mount /cache/recovery/command

I:Checking arguments.

I:device_recovery_start()

Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=c0890801ac378bd
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdkc110
ro.revision=0
init.svc.recovery=running
init.svc.adbd=running
ro.build.product=herring
ro.product.device=herring
ro.radio.noril=yes
ro.bt.bdaddr_path=/efs/bluetooth/bt_addr
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
ro.telephony.call_ring.multiple=0
ro.nfc.port=I2C

I:Checking for extendedcommand...

I:Skipping execution of extendedcommand, file not found...

W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)

mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory

W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)

mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory

W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)

mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory

W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)

W:Can't unlink /cache/recovery/command

And this is what things looked like with Adroid Commander:

i41.tinypic.com/14aga2r.jpg

I'm not sure if the lack of device info nor space used is due to the program not having access or just a better look at what the log is saying that there is squat there.

I'm not sure, but it seems like I am not able to browse into those problematic folders. At one point in one program (I think it was Adroid Commander) the cache, data, sdcard, etc had a different icon and from some more reading, seemed to be the behavior of the program not having root access to those folders (or are they really partitions?). But I should be especially with that cwm ROM. I'm not really clear what is going on here.

So I have been learning and poking around with adb and dbparted since I was trying to see if there were problems with the partitions though I couldn't get print to cooperate. I think the data from the log and those other programs were what I needed.

What I've seen in tons of reading on some of those "can't mount /cache" errors is the advice to restore to factory as the cure. I don't think I've seen anything specific of what the problem is that causes this but I don't think anyone has put up the original pit/boatloader/rom I would need to get to my factory setup.

Or I'm doing something wrong getting to a base Gingerbread with the 2.3.5 pit and the roms I tried. It seems my partitions are messed up but I'm not quite sure what they should be for me to modify them with sdparted. There seems to a variety going on with the partition types.

Still getting nowhere though I figured out how to make Heimdall download the pit from my player once I got past the lib error.

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Checking if protocol is initialised...
Protocol is initialised.

Beginning session...
Session begun with device of type: 0

Downloading device's PIT file...
PIT file download sucessful

Entry Count: 14
Unknown 1: 15718400
Unknown 2: 1
Unknown 3: 0
Unknown 4: 0
Unknown 5: 7703
Unknown 6: 237
Unknown 7: 62704
Unknown 8: 18

--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: IBL+PBL
Filename: boot.bin

--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: YPG70_8G-0304.pit

--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL
Filename: Sbl.bin

--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 6226025
Unknown 3: 7143533
Partition Name: SBL2
Filename: Sbl.bin

--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs

--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 40
Unknown 2: 39021280
Unknown 3: 7143533
Partition Name: EFS
Filename: efs.rfs

--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 36662408
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage

--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 6684793
Unknown 3: 3014771
Partition Name: RECOVERY
Filename: zImage

--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1160
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.rfs

--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 536
Unknown 2: 6684780
Unknown 3: 115
Partition Name: DBDATAFS
Filename: dbdata.rfs

--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 256
Unknown 2: 115
Unknown 3: 115
Partition Name: CACHE
Filename: cache.rfs

--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 7696
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: datafs.rfs

--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20516
Unknown 2: 0
Unknown 3: 0
Partition Name: USERFS
Filename: userfs_8G.rfs

--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: inand_8G.bin

I threw different 5.0 pit files from different sgp's at it to see the result. It still booted into recovery with the same can't mount errors no matter if it was the Korean one with the larger memory or the US pit. Everything got messed up again when I tried the 4.0 pits out. Adroid Commander and Droid Explorer also don't seem happy with the stock recovery mode, I can't see anything on the player. With the cwm recovery, both are browsable in those programs except for some partitions. I get fewer boot errors with the cwm/eryigit rom. It seems like the bootloaders don't have permission to get at the important partition folders during boot. Is that the problem.? How is that fixed if so?