KB6 ROM (Android 2.2.1) @ Samfirmware for the GT-P1010 (wifi-only Galaxy Tab)

daniel.weck

daniel.weck

Senior Member
Nov 2, 2010
574
95
0
daniel.weck.free.fr
Feb 20, 2011 at 12:24 PM
NOTE: the log below pertains to KB5...I haven't had time yet to look into KB6.

http://www.samfirmware.com/WEBPROTECT-p1010.htm

ro.build.display.id=FROYO.XWKB5
ro.build.version.sdk=8
ro.build.version.release=2.2.1
ro.build.date=Thu Feb 17 19:34:43 KST 2011

I'm going to unpack the various RFS archives, to see what's new. I've got a GT-P1000 Galaxy Tab (wifi+3G), so I'm not going to flash with Heimdall (let alone Odin :p ).

I made backups for factoryfs.rfs / dbdata.rfs etc. using the usual bit-by-bit "dd" -based method, and I've got a trusty TitaniumBackup archive ready, just in case ;)

I notice that TV-out seems to be gone, and FM radio appears to be available. Hardware DSP support seems more present too. (read content logs below for more information)

TAR contents:

Code: 
p1wifi_20110128_r10_00.pit (4 KB) (see PIT-info dumped below)

GT-P1010-CSC-SERKB3/
    cache.rfs (10.9 MB) (see content listing below)
    movinand.mst (51MB) (can be extracted with [URL="http://movitool.ntd.homelinux.org/trac/movitool/"]MoviTool[/URL], based on [URL="http://forum.xda-developers.com/showpost.php?p=9481702&postcount=30"]Volker1's method[/URL])

P1010XWKB5-REV03-ALL-low-CL913814/
    boot.bin (256 KB)
    cache.rfs (672 KB)
    normalboot.img (4.3 MB)
    param.lfs (612 KB)
    recovery.img (4.3 MB)
    Sbl.bin (1.2 MB)
    system.rfs (331 MB)
    userdata.rfs (1.2 MB)

Output from Volker1's PIT-info utility:

Code: 
Contents of PIT file: p1wifi_20110128_r10_00.pit
---------------------------------------------------------------------------
file magic = 0x12349876  (expected value)
Unknown data: 0 0 0 0 0
Number of partitions = 13  (usual value)

Partition #1
  Usual content: boot.bin, the primary boot loader (low-level hardware initialization)
  partition entry type: 0 0  (normal partition)
  ID = 0;	  flags = 0;	  unknown: 0
  size = 1 blocks of 256 * 512 bytes  = 131072 B = 128 kB = 0 MB
  unknown string: [........]
  partition name = [IBL+PBL.........................]
  file name = [boot.bin........................................................]

Partition #2
  Usual content: partition information table (PIT)
  partition entry type: 0 0  (normal partition)
  ID = 0x1;	  flags = 0;	  unknown: 0
  size = 1 blocks of 256 * 512 bytes  = 131072 B = 128 kB = 0 MB
  unknown string: [........]
  partition name = [PIT.............................]
  file name = [p1wifi.pit......................................................]

Partition #3
  Usual content: efs.rfs
  partition entry type: 0 0  (normal partition)
  ID = 0x14;	  flags = 0x2  (rfs file system);	  unknown: 0
  size = 40 blocks of 256 * 512 bytes  = 5242880 B = 5120 kB = 5 MB
  unknown string: [........]
  partition name = [EFS.............................]
  file name = [efs.rfs.........................................................]

Partition #4
  Usual content: Sbl.bin, the secondary boot loader (loads linux kernel)
  partition entry type: 0 0  (normal partition)
  ID = 0x3;	  flags = 0;	  unknown: 0
  size = 5 blocks of 256 * 512 bytes  = 655360 B = 640 kB = 0 MB
  unknown string: [........]
  partition name = [SBL.............................]
  file name = [sbl.bin.........................................................]

Partition #5
  Usual content: backup of secondary boot loader
  partition entry type: 0 0  (normal partition)
  ID = 0x4;	  flags = 0;	  unknown: 0
  size = 5 blocks of 256 * 512 bytes  = 655360 B = 640 kB = 0 MB
  unknown string: [........]
  partition name = [SBL2............................]
  file name = [sbl.bin.........................................................]

Partition #6
  Usual content: param.lfs /mnt/.lfs j4fs
  partition entry type: 0 0  (normal partition)
  ID = 0x15;	  flags = 0x2  (rfs file system);	  unknown: 0
  size = 20 blocks of 256 * 512 bytes  = 2621440 B = 2560 kB = 2 MB
  unknown string: [........]
  partition name = [PARAM...........................]
  file name = [param.lfs.......................................................]

Partition #7
  Usual content: zImage, the linux kernel
  partition entry type: 0 0  (normal partition)
  ID = 0x5;	  flags = 0;	  unknown: 0
  size = 30 blocks of 256 * 512 bytes  = 3932160 B = 3840 kB = 3 MB
  unknown string: [........]
  partition name = [NORMALBOOT......................]
  file name = [normalboot.img..................................................]

Partition #8
  Usual content: recovery.bin, the backup copy of zImage/initramfs
  partition entry type: 0 0  (normal partition)
  ID = 0x8;	  flags = 0;	  unknown: 0
  size = 30 blocks of 256 * 512 bytes  = 3932160 B = 3840 kB = 3 MB
  unknown string: [........]
  partition name = [RECOVERY........................]
  file name = [recovery.img....................................................]

Partition #9
  Usual content: factoryfs.rfs
  partition entry type: 0 0  (normal partition)
  ID = 0x16;	  flags = 0x2  (rfs file system);	  unknown: 0
  size = 1430 blocks of 256 * 512 bytes  = 187432960 B = 183040 kB = 178 MB
  unknown string: [........]
  partition name = [SYSTEM..........................]
  file name = [system.rfs......................................................]

Partition #10
  Usual content: dbdata.rfs
  partition entry type: 0 0  (normal partition)
  ID = 0x17;	  flags = 0x2  (rfs file system);	  unknown: 0
  size = 302 blocks of 256 * 512 bytes  = 39583744 B = 38656 kB = 37 MB
  unknown string: [........]
  partition name = [USERDATA........................]
  file name = [userdata.rfs....................................................]

Partition #11
  Usual content: cache.rfs
  partition entry type: 0 0  (normal partition)
  ID = 0x18;	  flags = 0x2  (rfs file system);	  unknown: 0
  size = 140 blocks of 256 * 512 bytes  = 18350080 B = 17920 kB = 17 MB
  unknown string: [........]
  partition name = [CACHE...........................]
  file name = [cache.rfs.......................................................]

Partition #12
  Usual content: modem.bin
  partition entry type: 0 2  (unknown value)
  ID = 0x3;	  flags = 0x1;	  unknown: 0
  size = 0 blocks of 0 * 512 bytes  = 0 B = 0 kB = 0 MB
  unknown string: [........]
  partition name = [HIDDEN.D........................]
  file name = [hidden.rfs.t....................................................]

Partition #13
  Usual content: Unknown
  partition entry type: 0 2  (unknown value)
  ID = 0;	  flags = 0x1;	  unknown: 0
  size = 0 blocks of 0 * 512 bytes  = 0 B = 0 kB = 0 MB
  unknown string: [........]
  partition name = [MOVINAND........................]
  file name = [movinand.mst....................................................]
The usual CSC cache.rfs content:

Code: 
/dbdata/svox/de-DE_gl0_sg.bin
/dbdata/svox/de-DE_ta.bin
/dbdata/svox/en-GB_kh0_sg.bin
/dbdata/svox/en-GB_ta.bin
/dbdata/svox/en-US_lh0_sg.bin
/dbdata/svox/en-US_ta.bin
/dbdata/svox/es-ES_ta.bin
/dbdata/svox/es-ES_zl0_sg.bin
/dbdata/svox/fr-FR_nk0_sg.bin
/dbdata/svox/fr-FR_ta.bin
/dbdata/svox/it-IT_cm0_sg.bin
/dbdata/svox/it-IT_ta.bin
/system/csc/feature.xml
/system/csc/contents.db
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/customer.xml
/system/app/MusicODC.apk
/system/T9DB/qwerty_fi.kdb
/system/T9DB/phonepad_cs.kdb
/system/T9DB/qwerty_da.kdb
/system/T9DB/Samsung_400_PLlsUN_xt9.ldb
/system/T9DB/phonepad_lt.kdb
/system/T9DB/Samsung_400_TRlsUN_xt9.ldb
/system/T9DB/Samsung_400_DEusUN_xt9.ldb
/system/T9DB/Samsung_400_ETlsUN_xt9.ldb
/system/T9DB/Samsung_400_ENubUN_xt9.ldb
/system/T9DB/Samsung_400_SVusUN_xt9.ldb
/system/T9DB/qwerty_sv.kdb
/system/T9DB/Samsung_400_DAlsUN.ldb
/system/T9DB/phonepad_uk.kdb
/system/T9DB/phonepad_it.kdb
/system/T9DB/phonepad_el.kdb
/system/T9DB/qwerty_hu.kdb
/system/T9DB/qwerty_es.kdb
/system/T9DB/Samsung_400_UKlsUN_xt9.ldb
/system/T9DB/qwerty_fr.kdb
/system/T9DB/qwerty_et.kdb
/system/T9DB/Samsung_400_SKlsUN_xt9.ldb
/system/T9DB/phonepad_no.kdb
/system/T9DB/qwerty_nl.kdb
/system/T9DB/qwerty_lt.kdb
/system/T9DB/Samsung_400_LVlsUN_xt9.ldb
/system/T9DB/Samsung_400_ITlsUN_xt9.ldb
/system/T9DB/Samsung_400_PTlsUN_xt9.ldb
/system/T9DB/phonepad_da.kdb
/system/T9DB/Samsung_400_HUlsUN_xt9.ldb
/system/T9DB/Samsung_400_ELlsUN_xt9.ldb
/system/T9DB/phonepad_et.kdb
/system/T9DB/Samsung_400_KKlsUN_xt9.ldb
/system/T9DB/phonepad_es.kdb
/system/T9DB/qwerty_sk.kdb
/system/T9DB/phonepad_nl.kdb
/system/T9DB/qwerty_pt.kdb
/system/T9DB/Samsung_400_ESlsUN_xt9.ldb
/system/T9DB/Samsung_400_CSlsUN_xt9.ldb
/system/T9DB/phonepad_ru.kdb
/system/T9DB/phonepad_tr.kdb
/system/T9DB/qwerty_tr.kdb
/system/T9DB/phonepad_de.kdb
/system/T9DB/Samsung_400_FIlsUN_xt9.ldb
/system/T9DB/phonepad_ko.kdb
/system/T9DB/phonepad_fr.kdb
/system/T9DB/phonepad_fi.kdb
/system/T9DB/qwerty_ru.kdb
/system/T9DB/phonepad_en.kdb
/system/T9DB/qwerty_en.kdb
/system/T9DB/qwerty_cs.kdb
/system/T9DB/qwerty_el.kdb
/system/T9DB/Samsung_400_NOlsUN.ldb
/system/T9DB/Samsung_400_RUlsUN_xt9.ldb
/system/T9DB/qwerty_kk.kdb
/system/T9DB/qwerty_no.kdb
/system/T9DB/qwerty_uk.kdb
/system/T9DB/phonepad_lv.kdb
/system/T9DB/phonepad_pl.kdb
/system/T9DB/Samsung_400_NLlsUN_xt9.ldb
/system/T9DB/phonepad_sv.kdb
/system/T9DB/phonepad_sk.kdb
/system/T9DB/Samsung_400_LTlsUN_xt9.ldb
/system/T9DB/qwerty_pl.kdb
/system/T9DB/qwerty_de.kdb
/system/T9DB/Samsung_400_FRlsUN_xt9s.ldb
/system/T9DB/qwerty_ko.kdb
/system/T9DB/qwerty_lv.kdb
/system/T9DB/phonepad_pt.kdb
/system/T9DB/qwerty_it.kdb
/system/T9DB/phonepad_hu.kdb
/system/CSCFiles.txt
/system/SW_Configuration.xml
Changes in /system/app/ :

Removed DailyBriefing, Ebook, Mms, MobileTrackerEngineTwo, MobileTrackerUI, OtaProvisioningService, SamsungWidget_WeatherClock, SoundRecorder, signin, syncmldm, wipereceiver, wssomacp

Added PhoneCrashNotifier, PopupuiReceiverf, qik, qikhelp, skype

Changes in /system/bin/ :

Too many to list, but here are some notable ones:

Removed BCM4329B1_002.002.023.0534.0590.hcd (the driver for the multi-function Broadcom BCM-4329 chipset, also removed in /etc/wifi/ etc.), akmd2 (the multi-sensor driver, now split into several sub-daemons: geomagnetic, gyroscope, temperature, light, orientation, pressure, proximity, etc.)

Notable changes in /system/etc/ :

Added audio/codec/FMRadioEar.ini, audio/codec/FMRadioSpk.ini, and FM-radio stuff in /etc/firmware/ and /lib/libfmradio_jni.so (the Texas Intruments BRF6350 chip supports FM radio...but I don't think that /system/app/ contains an FM tuner application).

Notable addition: /lib/dsp/ + /lib/libOMX*.so + /lib/libVendor_ti_OMX*.so + lib/libaomx_*.so (Texas Intruments OMX/DSP, hardware encoding/decoding of 720p AMR, WB-AMR, AAC, h264, WMA, WMV, MP3, MPEG4, Flac, AC3, S263, etc.)

Code: 
720p_h264vdec_sn.dll64P
720p_mp4vdec_sn.dll64P
720p_mp4venc_sn.dll64P
baseimage.dof
baseimage.map
chromasuppress.l64p
conversions.dll64P
dctn_dyn.dll64P
ddspbase_tiomap3430.dof64P
dfgm.dll64P
dynbase_tiomap3430.dof64P
eenf_ti.l64P
h264vdec_sn.dll64P
h264venc_sn.dll64P
ipp_sn.dll64P
jpegdec_sn.dll64P
jpegenc_sn.dll64P
m4venc_sn.dll64P
monitor_tiomap3430.dof64P
mp3dec_sn.dll64P
mp4v720parcdec_sn.dll64P
mp4varcdec_sn.dll64P
mp4vdec_sn.dll64P
mpeg4aacdec_sn.dll64P
mpeg4aacenc_sn.dll64P
mpeg4aridec_sn.dll64P
nbamrdec_sn.dll64P
nbamrenc_sn.dll64P
postprocessor_dualout.dll64P
qosdyn_3430.dll64P
ringio.dll64P
star.l64P
usn.dll64P
vpp_sn.dll64P
wbamrdec_sn.dll64P
wbamrenc_sn.dll64P
wmadec_sn.dll64P
wmv9dec_sn.dll64P
yuvconvert.l64p
Wifi access point doesn't seem very well protected (/etc/wifi/softap/hostapd.conf):

SSID = AndroidAP (not broadcast)
IP = 192.168.43.1
PASS = "password" (WPA)

By the way, the Wifi interface is different than on the fully-featured Tab: tiwlan0 (the access point is tiap0)
 
Last edited:
  • Like
Reactions: paulshields, fastcx, wallah and 3 others
zyborg

zyborg

Senior Member
Jun 21, 2008
686
32
0
Holmegaard
www.linkedin.com
Feb 20, 2011 at 7:30 PM
Splice/combine the ROM with a P1000 ROM?

Cool. Does this mean that your aim to splice/combine the ROM with a P1000 ROM to create a custom Android 2.2.1 ROM WITH 3G capabilities, that is compatible with P1000?

And in that case, it sure would be nice to keep most of what has been removed from /system/* in the P1010 ROM, of course.
 
Last edited:
Technomancer

Technomancer

Retired Recognized Developer
Feb 15, 2010
562
425
0
SF Bay Area
Feb 21, 2011 at 6:41 AM
Very interesting, thanks for posting the analysis.
I wonder whether GL drivers are any newer than from P1000 ROMs.
And GPS daemon?
Also, interesting about these split sensor drivers.

edit
hmm, interesting, the GL drivers are for SGX530 not 540 like in normal tab.
And the CPU in 1010 is OMAP3 not Hummingbird.
 
Last edited:
himmelhauk

himmelhauk

Senior Member
Mar 19, 2007
170
9
0
Texas
Apr 24, 2011 at 6:10 PM
bthoven said:
Yes. Only differences between 3g and wifi model:

- no 3G radio
- less powerful CPU/GPU on wifi model (thus can't play HD/Full HD video)
- and off course, wifi model is cheaper
Click to expand...
Actually it CAN play HD video. It can record 720p movies so it would only make sense it'd be able to play them. I watch 720p episodes of Breaking Bad on mine.

Sent from my GT-P1010 using XDA Premium App
 
bthoven

bthoven

Senior Member
Jun 28, 2008
350
37
0
Bangkok
Apr 27, 2011 at 3:37 AM
himmelhauk said:
Actually it CAN play HD video. It can record 720p movies so it would only make sense it'd be able to play them. I watch 720p episodes of Breaking Bad on mine.

Sent from my GT-P1010 using XDA Premium App
Click to expand...
Yes, it can play 720p lower bitrate whilst the 3G version can play higher bit rate, and also 1080p.
 
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone