Originally Posted by jeffcavicchi

Am I wrong that Recovery still sees the external SD card as an internal SD card?

ClockworkMod Recovery, and all CWM-based recoveries mount what what is plugged into a user accessible memory card slot as "/emmc." That, in turn, is called the "internal sd card" within CWM Recovery.

This has historic reasons from what I can tell...

So, these are the partitions that contain user data:

/data - (all android phones have this, even very early android phones.) Used to store user installed programs and data for both system and user installed programs (but not "external" data such as music files.)

/sdcard - This is an optional partition, though nearly all modern phones have it. Unlike /data, there isn't any pre-determinated layout. Usually 8, 16 or 32 GB in size. Back when phones only had /data partitions built in, this storage space might be provided by plugging in an sdcard. In CWM recovery, this is referred to as "sdcard", "the sdcard", etc.

/emmc - (As far as I know, only cyanogenmod (and firmware based on cyanogen) actually mounts to /emmc. Others mount in various other places. The 7+ mounts to /sdcard/extStorages/SdCard) After phones started coming with built-in memory mounted to /sdcard, a different partition was needed for any user-replacable memory card. There really is no standard for this (at this time.) Within CWM recovery, it's referred to as "internal sdcard" (perhaps with the intent of someday supporting an external device for backing up.) Keep in mind that the exact same CWM Recovery source is used for all different versions of android, so the labels might seem a bit strange.

I've seriously considered deviating from the CWM-Recovery source and changing the labels for my recoveries to be more consistant. For example: instead of "sdcard", I'd use "built-in memory." Instead of "internal sdcard", I'd use "user accessible microSD card." The problem with that is that users who are already familiar with CWM Recovery (and accustomed to its quirks) might get confused with different labels.

If I could figure out how to submit a patch for consideration to Koush (the author of CWM Recovery), I would probably submit one that allows the labels for various partitions to be noted in a config file and used from there.

Gary

Awesome explanation - thanks so much! Makes perfect sense now - less of a bug with CWM than an historical anomaly.

Appreciate your taking the time to explain it!

Hi Guys,
I m not sure if anyone encounter the same problem like mine, I tried every ROM out there but somehow cant flash any other ROM than the Malaysia-Dec-2011 ROM.

I doubt it might be the PIT file I need to flash the updated ROM! any help will be appreciated... thanks

Originally Posted by zeeqy

I m not sure if anyone encounter the same problem like mine, I tried every ROM out there but somehow cant flash any other ROM than the Malaysia-Dec-2011 ROM.

How does this relate to the CWM Recovery?

Hi Gary,

We are looking into porting CWM recovery to the 7.7 over in the 7.7 dev thread. The partitioning looks very similar to the 7 plus. Is there a git repo containing your latest version as I think its a great starting point for us.

Thanks

Ddraig

Sent from my GT-P6800 using XDA App

(more time to reply properly now...)

My username on github is garyd9, but I'm not sure how much help my code will be for you.

I don't know how recovery works on the 7.7. It might be similar to how most samsung's work (same kernel partition as a normal boot but with a different boot parameter) or similar to the 7.0 plus (which uses a completely different kernel partition for recovery and normal boots.) That makes a HUGE difference...

I see on the 7.7 forums that you already have people pulling and posting to github the initramfs and kernel stuff - so thats a better place to start than the 7.0plus stuff. You'll probably have to make some adjustments to the kernel source that is posted on opensource.samsung.com. I honestly think they deliberately "tweak" the defconfig's to not work properly on the target device. Unfortunately, I can't predict what changes would be needed for that device.

About the only thing that leaves out is the actual replacement recovery binary, which I compiled from the cyanogenmod sources. You'll probably have to make some changes, but again I can't predict those. You might consider getting the recovery sources from the ICS branch, as they'll likely be more compatible with honeycomb than the gingerbread branch.


Take care and good luck
Gary

Thanks Gary

The 7.7 also uses a completely different kernel partition for recovery and normal boot. Two kernel images with two initramfs. This is why your code will help.

I've extracted both initramfs and compared them so I have a rough idea what the difference is.

Once again, many thanks.

Ddraig

Japan Docomo SC-02D Tab 7.0 Plus

---

FYI for Gary and any Japan users:

The .zip installation does not run on the 7.0 Plus sold in Japan by Docomo. I'm pretty sure the hardware is the same as the GT-P6200, but I guess the ID on the device must be different and blocking your installation, Gary.

Here's some text I got from the recovery screen... important parts only.

Installing Multi-CSC
Can't access to '/system/csc/DCM/system/'.
Successfully applied multi-CSC.
...
(blah blah blah)
...
ERROR: This should only be installed on a Samsung GT-P6200
*******************************************
called abort()
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted"

The model number as listed under "About device" is "SC-02D" (the model number that the carrier, Docomo, has assigned to it.

I'll try and scour Google a bit more to confirm more strongly that its the same hardware as the 6200 or not... (and then you can allow the update.zip to run on it as well). Unless you think the problem is something else entirely based on the errors above.

Thanks
*****************EDIT

Can't find any evidence to suggest that this is NOT the same hardware model for the 3G version sold elsewhere.... but Docomo did disable/remove the TV out function on the previous Tab... This one seems to be functioning and nothing else seems to have been disabled/removed. The only difference that I can see is some extra bloatware from the carrier and language options (can only select English/Japanese/Korean for display... and there is a supplementary Japanese keyboard installed.)

yeah, I'm paranoid... there are SEVERAL different models of this tab, and some are slightly different. For example, some have /system on the 8th partition, some on the 9th. That's a critical thing for the recovery to know about and to get right.

This isn't the thread to discuss it... if you start something in the general subforum (and nag me enough), I'll make you do all kinds of work for me to get the information I need to build a recovery for it. (I need dumps of a few paritions, partition maps, etc.)

I can promise nothing for at least a week and a half, however. Maybe sooner, maybe not. Just depends where my time falls.

Gary

Originally Posted by garyd9

yeah, I'm paranoid... there are SEVERAL different models of this tab, and some are slightly different. For example, some have /system on the 8th partition, some on the 9th. That's a critical thing for the recovery to know about and to get right.

This isn't the thread to discuss it... if you start something in the general subforum (and nag me enough), I'll make you do all kinds of work for me to get the information I need to build a recovery for it. (I need dumps of a few paritions, partition maps, etc.)

I can promise nothing for at least a week and a half, however. Maybe sooner, maybe not. Just depends where my time falls.

Gary

I just bought a GT-P6200 a few days ago and I was happy to find that it has a separate partition for recovery. This is good... much more flexible than the "all in one" boot/recovery on my GT-I9000 (Galaxy S).

Now I want to start porting ICS to the tab.