[Samsung Galaxy Player 4.0, 5.0] TiMthisIS:
Sorry if my postings are getting wordy, lack of sleep and constant testing and figuring things out are to blame.

I kept getting an error that the download was temporarily restricted due to too much traffic by that user for most of the last week. It just started working again, thanks. When I searched elsewhere by putting the file name into Google a bunch of help guides kept popping up. They are often the same text and offer the same bad links that promise a rom but link to usb drivers. One of the top ones actually had the dropbox link but the high traffic restriction kept dead ending me on that file. They seem to have varying intros and generic pictures but the instructions seems to be copied among them, hence the bad links. Sometimes there are unrelated device videos as part of the walk through.

They all begin with "www" if they don't work. I'm link restricted.

bestandroidblog.com/android-hacks/how-to-unbrick-your-galaxy-player-5/

androidauthority.com/unbrick-samsung-galaxy-player-5-48449/

This Italian one has the same bad links too: androider.it/3289/guida-come-fare-ad-eseguire-lunbrick-sul-samsung-galaxy-player-5/

They seem to be churned out possibly based on that XDA info that was the first source.

I've gotten confused over the bootloaders and partition options at times since some instructions say check the box, others say no. I didn't realize some had bootloaders or pits inside those tars. Especially since there are boxes especially for those right in Odin.

Why is that tar so big when unrar-ed? Is it an uncompressed image? I found another image on an xda topic for an international unit. It was gz compressed and was slightly under 8 gigs too when uncompressed but had no file extension. So I'm trying to hunt that source down again and see what/how I am supposed to use that.

One interesting find over in the Nexus threads over a user with the same /cache errors with cwm. User cjward23 posted "It sound very similar to an issue a range of HTC devices had that contained a Samsung EMMC. What was happening is that EMMC would not allow certain partitions of the device to written to."

That makes sense to me too since the log also shows all those mmc block errors. My thinking now is that the pit and bootloaders I'm using are fine but I have a sort of partial root block even with the cwm either by that EMMC or something else. That would make sense of why the stock restores work if the device is trying to match operations up with stock. CWM's mount and format page can't do much. It won't mount and obviously can't format without the mount. Only the external SD card mounts and the USB mode can then activated.

Playing around with Doomlord or SuperOneClick to see about the root status got me nothing. None would connect.

I think early on with this device I tried a rooting app but I don't think the test was successful after it claimed it had rooted. But I was too nervous about problems and lack of knowledge of roms kept me away until recently.

Problem I have now is getting back to FROYO stock and the 2.2.2 partition. I will be trying that next with the boxes checked on the rom I do have. I may have been mixing that with a GB pit file. G70-recovery.tar is the base GB 2.3.5 Int'l right? That isn't quite stock for me if there is some sort of hardware block that is causing this trouble. Or maybe a locked bootloader but now I just tossing more in since I've just started to consume info on where the rooting mojo happens to see if it matches with what's happened.

Update: There's a few files in the G70XXKD6 rar. One seems a bit more for a "light" flash that keeps the customer's old data. The second one I had a bad hash. I found a new one but it fails out if I select repartition <ID:0/004> Can't open the specified file. (Line: 1876)

That would be nice to work since I believe my partitions are in the wrong format or that I should definitely repartition when going back to FROYO. What were the change between the two releases? I seem to remember some talk about rfs though right now mine show ext4.

I suppose I need to go back to adb and see what I can do with sdparted or fdisk once I figure out which ones need to be manually fixed.

I can't quite follow the official instructions that look like their from Samsumg to flash, if not working, to wipe date/factory reset and flash again since I have a soft brick and can't get to recovery until I toss the bootloader back on it. But then I'll the refusals to mount to format again if I do get there.