yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] Col.Kernel:
You fanbois need to quit being so touchy. The lot of you are almost emo at this point. If anyone dares to post anything less than lauding Asus to the skies praise one of you has to jump in with the obligatory "Quit being so negative" whine.

Asus screwed the pooch on the product launch, and this forum was quite verbal about it. They're trying to recover from it, and doing a half way decent job. Now enough, knock it off, let it go.

The poster you quote voiced an OPINION. It's his opinion and it is a valid position. It's not an opinion I agree with, but it's a very far cry from being the negative lambasting you seem to think it is.

We've had multiple ICS patches in the past 3 weeks. While some of the issues I'd like to see addressed aren't at the top of the list (or fixed yet) at least my Prime is functional. It's looking like acceptable support to me.
[Asus  Eee Pad Transformer Prime] stretchwookie:
i dont know, i kinda like it. they are stupid names, but its always fun. heres what you can do though

if it's Cupcake, call it 1.5

if it's Donut, call it 1.6

if it's Eclair, call it 2.0, 2.0.1, or 2.1

if it's Froyo, call it 2.2, 2.2.1, 2.2.2, or 2.2.3

if it's Gingerbread, call it 2.3, 2.3.3, 2.3.4, 2.3.5, 2.3.6, or 2.3.7

if it's Honeycomb, 3.0, 3.1, 3.2, 3.2.1, or 3.2.2

if it's Ice Cream Sandwich, call it 4.0, 4.0.1, 4.0.2, or 4.0.3

that may save you some frustration? hope that helps!
[Asus  Eee Pad Transformer Prime] Keion:
Asus,
[Asus  Eee Pad Transformer Prime] Wordlywisewiz:
I'm just happy its not demandarin posting all the news thanks :)

But anyways no jelly Bean is gonna integrate google @ home and personal assistant into it! Maybe even have a mode that supports mouse and keyboard better to compete with windows 8 and maybe replace desktops :p Hopefully it will require all phones to have NFC
[Asus  Eee Pad Transformer Prime] stretchwookie:
its ok demandarin, i still love you :p
[Asus  Eee Pad Transformer Prime] demandarin:
;) ..........kinda mad I can still see people posts that I ignored when other people quote them. lol that wordgirl kid needs to grow up ..lol
[Asus  Eee Pad Transformer Prime] stretchwookie:
Awww! That sucks! Sorry dood
[Samsung Galaxy Player 4.0, 5.0] tdm:
WARNING:

For devs and experts ONLY!

This is not fully functional and it is not well tested yet!

This is an unofficial port of CM7 to the Galaxy Player 4.0 (USA and EUR).

Known Issues

Deep sleep is disabled because it crashes the device

Cameras are upside down

Camcorder may crash

Bluetooth turns on but doesn't seem to scan

External sdcard isn't mounted by default

USB storage does not work

Preparation

DO A FULL BACKUP! Make sure you can recover from nothing using odin/heimdall

Make sure you have a known good kernel handy, Steve's is good

Backup /system using "dd" use with odin/heimdall, just in case:

dd if=/dev/block/stl9 of=/mnt/sdcard/system.img bs=512

Backup your apps if you care about them

Installation

Download the ROM for your device

Verify MD5 on the device

Boot into recovery and install the ROM

Do a full wipe. Wipe data, cache, dalvik, everything

Reboot and hopefully you should have a CM7 system! :D

Issues?

Post any other issue here and I will respond when I get a chance. Please do NOT send me PM's.

Download

USA: update-cm-7.2.0-RC0-YPG1-USA-KANG-signed.zip md5=4ebe819524a5a5e4e68913d1156e0961

EUR: update-cm-7.2.0-RC0-YPG1-EUR-KANG-signed.zip md5=ce77cb63512bfe224ea2e19eb23e15e9

Note: gapps is not currently included in the ROM.
[Samsung Galaxy Player 4.0, 5.0] minimeofctown:
device is bricked, why not? lol
[Samsung Galaxy Player 4.0, 5.0] klin1344:
Also, camera zoom doesn't seem to work.
[Samsung Galaxy Player 4.0, 5.0] tdm:
At least two people have had successful installs.

What happened during the install?

Can you connect via adb?
[Samsung Galaxy Player 4.0, 5.0] minimeofctown:
okay no i really need some help to unbrick my device. i really thought this would do it. it just boots straight into CWM.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Use odin/heimdall to flash Steve's kernel and system image that you made.

You did backup your system partition, right?
[Samsung Galaxy Player 4.0, 5.0] minimeofctown:
your rom didnt brick my device. it was already bricked. and yes i can connect to adb

---------- Post added at 12:45 AM ---------- Previous post was at 12:43 AM ----------

this is what happened, i flashed klins rom, worked fine. went back to wipe dalvik and cache. then it started bootlooping. me being dumb didnt do a backup before hand. i did a back up of the bootlooping but thats it. since then ive been trying to unbrick.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Well that's OT then. I think there are other threads that detail how to unbrick your device.

FYI, I've had my device completely fubar'd including the kernel and all of the partitions after playing with the partition table and raw MTD, and I managed to restore it every time. It's just a matter of finding the right pieces and flashing them.
[Samsung Galaxy Player 4.0, 5.0] minimeofctown:
flashed steves on top of your rom and now i get a bunch of mount errors in CWM

---------- Post added at 12:49 AM ---------- Previous post was at 12:47 AM ----------

ive tried the partitions and tried flashing stock and klins and steves. dont know what to do now man. its frustrating
[Samsung Galaxy Player 4.0, 5.0] tdm:
Assuming you have a good partition table, a good efs partition, and a good param (lfs) partition, this is pretty easy to recover from.

Download a good clean factoryfs

Flash Steve's kernel and factoryfs using odin/heimdall

Delete everything on /dbdata, /cache, and /data

When you are booted into recovery and /system is mounted, you can also try to use newfs_msdos on the /dbdata, /cache, and /data partitions.

Note Steve's kernel is not compatible with my CM7 ROM and my kernel is not compatible with the stock ROM. The kernel itself is the same but the embedded initramfs is different for CM7.
[Samsung Galaxy Player 4.0, 5.0] klin1344:
wait...I thought it was because you used the wrong PIT file for your device that is causing it to be bricked.
[Samsung Galaxy Player 4.0, 5.0] minimeofctown:
it was stuck in boot looping before that. sorry i forgot to mention:o

---------- Post added at 12:58 AM ---------- Previous post was at 12:57 AM ----------

okay, how do i flash the factoryfs with odin? sorry for being a noob. its not in a zip file so i dont know how to flash it
[Samsung Galaxy Player 4.0, 5.0] klin1344:
... Maybe you should ask in a different thread. This thread is for the OP's CM7.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Sorry I use Linux and heimdall.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
There's the gapps if you want them. Flash with CWM. :D

Gapps Download
[Samsung Galaxy Player 4.0, 5.0] Zyxxeil:
Wow Nice.

First time flashing it did it in like 4 seconds and i was like WTF. I tried turning on but it was stuck on the samsung logo.

After the second time, idk what i did but it did take like a min to flash and it booted up pretty quick for first time.

So far pretty happy with it. But thats just me i've only had it for like 10 min. :D

Ill keep you updated.

For the meantime i can confirm it works..

Also can confirm gapps work to. Thanks.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Thanks. I have seen the fast flash also, I think it's because /system is (or isn't) mounted in recovery.

Unfortunately, Samsung has to be different from every other standard Android device. They use a single image for kernel, recovery, and normal boot. So you're stuck with my recovery files for CM7. I'm still learning the details of how the recovery is supposed to work...
[Samsung Galaxy Player 4.0, 5.0] Zyxxeil:
NP Man

As long as i have a stable CM7 Im good.. :D

Yeah really stable. Though the launcher is kinda slow other than that everything is snappy really ♥ the theme option. Well anyways man good job. Best rom ever. Now i guess since we have a cm7 rom we can start building a miui. :)
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
We have indeed a cm7 rom but we need a more stable rom. I'll try this weekend to make MIUI and during next week too. (spring break! :D)
[Samsung Galaxy Player 4.0, 5.0] Zyxxeil:
Not trying to sound kinda... you know, but i found a bug.

1. The soft keys at the bottom dont light up nor vibrate.

I also got some positive.

1. Some of the apps that didnt show for the SGP even with the klasic rom now show up such as go locker and a few more apps.

Ill keep you updated.

Our spring break is till next week :D
[Samsung Galaxy Player 4.0, 5.0] tdm:
You have a modem partition. I don't think I have that. So you have one more partition than me and you need one more device node. This is probably why it says that it cannot open mtd8. I'll get you a custom boot image later today.

Are you sure that the modem partition is from the factory on your device?
[Samsung Galaxy Player 4.0, 5.0] klin1344:
I'll download it now and see if there are the same problems on my US player.

---------- Post added at 08:52 AM ---------- Previous post was at 08:12 AM ----------

I can't seem to install it...

It keeps giving error assert failed: run_program("/tmp/convert_to_mtd.sh")

I thought it was because I was using EXT4, so I completely repartitioned my player and then flashed. It flashed and rebooted, and using adb shell I saw that the partitions were correctly yaffs2. But I tried flashing the second time, and it gives me the same error as above.

Also I noticed something strange that in the root of my sd card there is a file ".convert_to_mtd.sh"

I tried downloading the ROM again and reflashing, but still no luck. I tried removing the assert in that line, but it still failed.
[Samsung Galaxy Player 4.0, 5.0] tdm:
zac, try flashing this for your kernel.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Yeah it's not expecting ext4.

If you have everything converted to yaffs2 (or if you just wipe those partitions manually) you can remove the touchfile /sdcard/.convert_to_mtd and the script will skip the conversion.

edit: I'll try to add support for ext4 on monday.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Thanks. I can get at least to recovery now but I have the same errors as klin's
[Samsung Galaxy Player 4.0, 5.0] tdm:
Can I get a copy of /tmp/convert.debug after it fails?
[Samsung Galaxy Player 4.0, 5.0] tdm:
New test ROM here (md5=96581817df515f9270c4676ec0251e21).

Changes since yesterday:

* Added more mtd nodes to /dev for devices with modem partitions.

* Cleaned up the convert_to_mtd.sh script. Maybe it will work better now.
[Samsung Galaxy Player 4.0, 5.0] klin1344:
Thank you for your work. I will flash this in a few and tell you how it goes...

Sent using Tapatalk
[Samsung Galaxy Player 4.0, 5.0] daniel644:
Just flashed this on my 4.0 US model and my home button isn't working, any ideas?
[Samsung Galaxy Player 4.0, 5.0] Gigadroid:
You have flashed the international version of my LeWa ROM.

I think CM 7 now recognizes your device as the international variant. If you flash the first US Alpha, the error should be corrected
[Samsung Galaxy Player 4.0, 5.0] tdm:
The buyer code is not set. What is the contents of /efs?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Sorry about the late reply for modem. Yes it is factory and now CM7 is running good. Thanks!

EDIT: I think we should change the vold.fstab in order to get it working with the external sd card. I can get my thumbnails but not my music.
[Samsung Galaxy Player 4.0, 5.0] Tcollins412:
currently, whats working and what isnt working?
[Samsung Galaxy Player 4.0, 5.0] daniel644:
aside from knowing how to flash ROMs i'm still a newb, how do I get that info for you, Also I can't seam to go back to any other ROM other then Klin's R5, after flashing any other ROM I get stuck in a bootloop and when flashing back to stock ROM and booting into recovery I'm getting a bunch of cannot mount errors. Even when on Klin's R5 ROM US my home button doesn't work, I know the button isn't the problem because when I flashed back to a earlier ROM with Steves 2.1 kernel the home button works for navigating in that version of CWM.

Is there someway to reverse the MTD conversion that seems to be what is causing my problems trying to revert?
[Samsung Galaxy Player 4.0, 5.0] klin1344:
You would have to use the PIT file and check repartition in odin or heimdall. You have to flash zaclimon's US recovery, as it includes all the partitions needed.
[Samsung Galaxy Player 4.0, 5.0] tdm:
The pit should not be needed. But a full restore of everything else will: efs, factoryfs, dbdata, cache, data, and kernel.
[Samsung Galaxy Player 4.0, 5.0] klin1344:
I just installed this and it seems to work fine. I reverted to rfs though before flashing.

Thanks for your work.

Sent using Tapatalk
[Samsung Galaxy Player 4.0, 5.0] tdm:
Honestly you should not be flashing this. You are in way over your head. Wait until I stabilize the mtd conversion at least.

Did you do a full backup like the op says in red text? That is how you go back. If you don't have a backup of efs, some data (your device mac addrs for wifi and bt) may be lost forever.
[Samsung Galaxy Player 4.0, 5.0] klin1344:
I can confirm that your new zip also works on EXT4. I went back to my EXT4 setup and then flashed again, and it worked. I think I might stay on CM7 and not revert back, since I don't need bluetooth and no deep sleep isn't a big issue for me.

EDIT:

Actually wait, I just noticed that the home button doesn't work. In efs there is only a lost+found folder, and there is nothing in it. Should I try restoring my efs data from the efs.tar backup?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
It seems that I got an error about not mounting efs in stock kernel. So it seems that I need to flash (re-partition) the efs.tar
[Samsung Galaxy Player 4.0, 5.0] daniel644:
I've already used heimdall to flash back using Zaclimon's method (as per Klin's recommendation) and I'm back to stock till you get this more hammered out. My wifi is working fine and I did use CWM to make a backup but when restoring it I was having issues (no home button amongst them). I have a few issues but I posted about them on the thread for his restore method so as to not hijack your thread.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Okay so it looks like I have more work to do on the convert script. I'll make a new build before noon tomorrow, Seattle time.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Ok cool. Just want to make sure your efs is safe.

The only reason I can see for your home button not working is that it's still using my kernel, or an intl kernel.
[Samsung Galaxy Player 4.0, 5.0] daniel644:
using the method I mentioned in my last post got the home working on the stock kernel.

Also I had flashed several Rom and kernels while trying to get back to normal, and the reason I wanted to try yours is because I have played with literally every other rom available so far.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Okay here is another test ROM. md5=d45b2fbfa236813cad3d45e04f23e434.

Changes:

* Hopefully fixed the convert script

* Should reboot back into recovery after the first install

* Got rid of the no-signal indicator in the status bar (but lockscreen text remains)
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Hmm I need some help here. I deleted my backup of efs.tar and it seems that my /efs is mounted yaffs2 or mtd. So for result I can't flash CM7 anymore as I got an error about the script. The script can detect efs in ext4 or rfs but not in yaffs2. I know this is stupid I didin't flashed efs but I forgot to do it so.
[Samsung Galaxy Player 4.0, 5.0] tdm:
If the efs data exists in yaffs2 format, you can retrieve it.

Get an adb shell with the new kernel running in recovery and do this:

mount /sdcard

mount /efs

cd /efs

tar -c -f /sdcard/efs.tar .

cd /

umount /efs

Now, if you want to back it up again in rfs format, you would go back to an RFS based recovery and do something like this:

mount /system

/system/bin/newfs_msdos /dev/block/stl3

mount -t rfs /dev/block/stl3 /efs

cd /efs

tar -x -f /sdcard/efs.tar

cd /

umount /efs

dd if=/dev/block/stl3 of=/sdcard/efs.img
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Ok so the msdos thing is to convert it back to stl/rfs partition right?
[Samsung Galaxy Player 4.0, 5.0] tdm:
Yes that's correct.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
But then if it's the case what happens to the mtdblock? (sorry for asking these questions but I want to learn more about this.)

EDIT: Ok I understand now the /efs switch place so it can be in stl3 and mtdblock0 gets deleted.
[Samsung Galaxy Player 4.0, 5.0] tdm:
The device names change with the kernel. A kernel that supports MTD will show your efs partition as /dev/block/mtdblock0. A kernel that supports BML will show it as /dev/block/bml3 and /dev/block/stl3 (almost). It is possible for one kernel to support both so that all three devices exist and refer to the same partition. But obviously that is confusing and dangerous.

This is not an exact description though. MTD devices are "raw" devices.

BML devices go through the block mapping layer, which maps bad blocks to the reservoir partition so that BML devices never appear to have bad blocks. If there are no bad blocks, MTD == BML. If there are, MTD != BML. BML is understood and could be implemented in a Free kernel.

STL devices go through an additional translation layer, which is proprietary and I don't know anything about it. But it's almost surely a wear levelling implementation. It uses roughly 10% to 15% of the BML device in overhead (mapping tables of some sort). This is why a Free kernel cannot use STL nor mount /efs.

And finally, of course, there is rfs. This is vfat plus some proprietary extensions to handle Unix file permissions, symlinks, and such. Nasty stuff, but at least you can mount and view the data.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I did try this but I got an error when trying to mount rfs:

~ # mount -t rfs /dev/block/stl3 /efs
mount: mounting /dev/block/stl3 on /efs failed: Invalid argument
~ #
[Samsung Galaxy Player 4.0, 5.0] tdm:
Did you retrieve your data? You might need to reinitialize the stl device with heimdall. Create an empty file with dd that is say 1k and flash it as efs. Then try to create the rfs file system and mount it. But make sure you have the data recovered first!
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
And how I'm supposed to create the 1k file? I thought I can retrieve the efs.tar and repartition it with heimdall.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Okay so I'll assume you have efs.tar saved away (and several copies of it just to be safe) ;)

This will create an empty file of the same size as my stl3, 6553600 bytes:

dd if=/dev/zero of=blank.img bs=65536 count=100

If you don't have a Linux computer, you can do that on your player with adb. You can put that file in the root directory (which is ram, and so it is volatile) or you can put it on your /sdcard if you want to use it again. Pull the file to your PC with adb.

Now flash it to your device to reset/reinitialize the STL data:

heimdall flash --efs blank.img (or whatever the odin equivalent is)

Now boot into a BML/STL recovery and create the filesystem:

mount /system

/system/bin/newfs_msdos /dev/block/stl3

Mount it and extract your data:

mount -t rfs /dev/block/stl3 /efs

cd /efs

tar -x -f /sdcard/efs.tar

Hopefully that will work...
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Woah this is bad. I tried to make a backup of efs with the tar but when I came to make the tar. it says that it's a empty archive. Hopefully I made a backup of efs using root manager before so I didin't lost it. Well does your config of efs.tar is different (does it has a folder before? or something like that?) I'll restore the efs using my folder.

I tried your suggestion but I got these things again:

isaac@isaac-P:~$ adb shell
~ # mount /system
~ # /system/bin/newfs_msdos /dev/block/stl3
/system/bin/newfs_msdos: warning, /dev/block/stl3 is not a character device
/system/bin/newfs_msdos: Skipping mount checks
Error getting gemoetry (Not a typewriter) - trying sane values
/system/bin/newfs_msdos: trim 11 sectors from 12800 to adjust to a multiple of 63
/dev/block/stl3: 12744 sectors in 1593 FAT12 clusters (4096 bytes/cluster)
bps=512 spc=8 res=1 nft=2 rde=512 sec=12789 mid=0xf0 spf=5 spt=63 hds=64 hid=0
~ # mount -t rfs /dev/block/stl3 /efs
mount: mounting /dev/block/stl3 on /efs failed: Invalid argument
~ #

I think It has found it I'll try to just copy my things over and see if it works.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Hmm ... ok, well, let me know if you can't get it fixed. Maybe I can create a blank vfat filesystem image and send it to you.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
As I tought it's not working. But I can't get efs formatted as rfs too so I don't know what to do now. (Sorry to clutter up your thread though. :D)
[Samsung Galaxy Player 4.0, 5.0] klin1344:
Do you have a backup of stl3 efs.rfs?

I flashed that and that's how I converted to rfs.

Sent using Tapatalk
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Nope I just made a backup of my efs folder with root explorer. I made this a long time ago. I thought efs would be restored without anything like my modem partition.

EDIT: Wait I have an idea I don't know if you would like it through. Can you send me your efs.rfs so it can be re-partitionned and after I erase your items and replace it with mine?
[Samsung Galaxy Player 4.0, 5.0] tdm:
I'll try to get you an empty rfs image of the proper size tomorrow.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Oh alright thanks! :D
[Samsung Galaxy Player 4.0, 5.0] tdm:
Sorry I got busy yesterday. I tried making RFS images using various tools, both on the device and on my Linux workstation. None seem to mount as RFS properly. :/

So I took a different approach. I hex edited my efs image and zeroed everything except the superblock and FAT tables. As such, it may not show the correct amount of free space (eg. it may think some blocks are in use when they are actually not). But that's not a big deal. The filesystem only holds a couple kb of data anyway.

I tested it on my device and it seems to work. So here it is, attached and gzipped.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Ok I will try it right now.

EDIT: WOOOOOOOOTTT it's working!! Thanks a lot :D (I also got my lockscreen working now!!!!!!!!!!!!!) This is a lesson I have to learn from.
[Samsung Galaxy Player 4.0, 5.0] daniel644:
Hey Zac, as you know I am in the same boat as you were, how can I use that file to fix the issue?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I'll send you a PM, I don't want to make a big post and cluttering tdm's thread. However if many people are getting these issues, I should put them in the recovery thread.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Glad you got it working. Congratulations! Now save off that image in at least 3 places. ;)
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Yeah don't worry about that :p I'm actually surprised by the size (7 KO and 6 MO when unpacked.)
[Samsung Galaxy Player 4.0, 5.0] tdm:
Well the image is just a super block and lots of zero bits. The uncompressed size is fixed of course.

Anyway how is the latest test image installing? I think it's working well now.

And since there seem to be few takers, I'll probably use what I've learned here and start focusing on ics now.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Oh and btw I have been working on a ROM manager/updater app and it should be included in future roms, both cm7 and ics.
[Samsung Galaxy Player 4.0, 5.0] GalaxySwifi4.0:
So you're working on an update offre CM7?

Will Bluetooth work fine? Do you think the battery will be better?
[Samsung Galaxy Player 4.0, 5.0] klin1344:
@ tdmcode:

I just flashed your beta 3 of CM7, and it it flashed successfully and the home button works now. I guess you got the MTD convert script correct. Nice work!

It is really smooth and I will probably stay on CM7 for a while.

Also, could you push your recent changes to github? I'd like to poke around and see what I could do to try to fix some of the bugs. But don't count on it though :p
[Samsung Galaxy Player 4.0, 5.0] tdm:
Thanks. I'll see about pushing code tomorrow.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Me too but it's for the ICS branch I would like to test it on my device. :D