5,599,677 Members 46,059 Now Online
XDA Developers Android and Mobile Development Forum

[SC-03D] Japan NTT DoCoMo Galaxy S II LTE Users plus FAQ

Tip us?
 
cdep.illabout
Old
(Last edited by cdep.illabout; 2nd December 2011 at 06:55 AM.)
#1  
Junior Member - OP
Thanks Meter 0
Posts: 4
Join Date: Nov 2011
Post [SC-03D] Japan NTT DoCoMo Galaxy S II LTE Users plus FAQ

This is a thread for Docomo's Galaxy S II LTE. Its model number is SC-03D.

FAQ in progress...

Q. Tell me about this phone.
A. This phone was released 2011-11-24 in Japan by Docomo.
nttdocomo.co.jp/product/next/sc03d/
ja.wikipedia.org/wiki/SC-03D

Q. What phones is the SC-03D similar to?
A. It appears to be similar to the AT&T Samsung Galaxy S II Skyrocket (SGH-I727) and T-Mobile Samsung Galaxy S II SGH-T989 (both SGSII phones with 4G support). Other than the modem/baseband, it is also probably similar to the Epic 4G Touch.

Q. What is the model number:
A. SC-03D

Q. What is the stock Android version?
A. 2.3.6

Q. What is the stock baseband version?
A. SC03DOMKK3

Q. What is the stock kernel version?
A. 2.6.35.11-SC03DOMKK3-CL711887se.infra@SEP-40 #2

Q. What is the build number?
A. GINGERBREAD.OMKK3

Q. Let's get our hands dirty. Tell me a little about the mounted filesystems.
A. Okay, but you asked for it...

Here are the mounted filesystems.
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p24 /system ext4 ro,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p26 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p13 /system/etc/firmware/misc vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p27 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:28 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
/dev/block/vold/179:33 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.metago.astro-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
Here is the size of the filesystems (keep in mind I've installed a few applications, so these sizes are very slightly bigger than they would be on a new phone).
Code:
# df
Filesystem                      Size   Used   Free   Blksize
/dev                            380M    76K   380M   4096
/mnt/asec                       380M     0K   380M   4096
/mnt/obb                        380M     0K   380M   4096
/mnt/usb                        380M     0K   380M   4096
/system                         698M   588M   110M   4096
/cache                          297M    10M   286M   4096
/efs                              9M     4M     5M   4096
/data                             1G   214M     1G   4096
/system/etc/firmware/misc       199M    21M   178M   4096
/system/etc/firmware/misc_mdm   199M    26M   173M   4096
/tombstones                      68M     4M    64M   4096
/mnt/sdcard                      11G    92M    11G   16384
/mnt/sdcard/external_sd          29G   140M    29G   32768
/mnt/secure/asec                 29G   140M    29G   32768
/mnt/asec/com.metago.astro-1      3M     1M     1M   4096
#
Here is a listing of the block devices on the phone. There's a lot...
Code:
# ls -l -a /dev/block/
brw------- root     root     179,  17 2011-11-27 12:41 mmcblkOp17
brw------- root     root     179,  13 2011-11-27 12:41 mmcblkOp13
brw------- root     root     179,  23 2011-11-27 12:41 mmcblkOp23
brw------- root     root     179,   8 2011-11-27 12:41 mmcblkOp8
brw------- root     root     254,   0 2011-11-26 00:56 dm-0
drwxr-xr-x root     root              2011-11-26 00:56 vold
brw------- root     root     179,  33 2011-11-26 00:56 mmcblk1p1
brw------- root     root     179,  32 2011-11-26 00:56 mmcblk1
brw------- root     root       7,   7 2011-11-26 00:56 loop7
...
brw------- root     root       1,   0 2011-11-26 00:56 ram0
brw------- root     root     179,  28 2011-11-26 00:56 mmcblk0p28
brw------- root     root     179,  27 2011-11-26 00:56 mmcblk0p27
brw------- root     root     179,  26 2011-11-26 00:56 mmcblk0p26
brw------- root     root     179,  25 2011-11-26 00:56 mmcblk0p25
brw------- root     root     179,  24 2011-11-26 00:56 mmcblk0p24
brw------- root     root     179,  23 2011-11-26 00:56 mmcblk0p23
brw------- root     root     179,  22 2011-11-26 00:56 mmcblk0p22
brw-rw---- system   system   179,  21 2011-11-26 00:56 mmcblk0p21
brw-rw---- system   system   179,  20 2011-11-26 00:56 mmcblk0p20
brw-rw---- system   system   179,  19 2011-11-27 16:06 mmcblk0p19
brw------- root     root     179,  18 2011-11-27 17:06 mmcblk0p18
brw------- root     root     179,  17 2011-11-26 00:56 mmcblk0p17
brw------- root     root     179,  16 2011-11-26 00:56 mmcblk0p16
brw------- root     root     179,  15 2011-11-26 19:07 mmcblk0p15
brw------- root     root     179,  14 2011-11-26 00:56 mmcblk0p14
brw------- root     root     179,  13 2011-11-26 00:56 mmcblk0p13
brw-rw---- root     radio    179,  12 2011-11-26 00:56 mmcblk0p12
brw------- root     root     179,  11 2011-11-26 00:56 mmcblk0p11
brw------- root     root     179,  10 2011-11-26 00:56 mmcblk0p10
brw------- root     root     179,   9 2011-11-26 00:56 mmcblk0p9
brw------- root     root     179,   8 2011-11-26 00:56 mmcblk0p8
brw------- root     root     179,   7 2011-11-26 00:56 mmcblk0p7
brw------- root     root     179,   6 2011-11-26 00:56 mmcblk0p6
brw------- root     root     179,   5 2011-11-26 00:56 mmcblk0p5
brw------- root     root     179,   4 2011-11-26 00:56 mmcblk0p4
brw------- root     root     179,   3 2011-11-26 00:56 mmcblk0p3
brw------- root     root     179,   2 2011-11-26 00:56 mmcblk0p2
brw------- root     root     179,   1 2011-11-26 00:56 mmcblk0p1
drwxr-xr-x root     root              2011-11-26 00:56 platform
br--r----- system   system   179,   0 2011-11-26 00:56 mmcblk0
#
Dumping the block images allows us to see their size.
Code:
$ ls -l image sizes
 104857600  --  dev-block-mmcblk0p1.img
    512000  --  dev-block-mmcblk0p2.img
   1536000  --  dev-block-mmcblk0p3.img
      1024  --  dev-block-mmcblk0p4.img
    512000  --  dev-block-mmcblk0p5.img
   2097152  --  dev-block-mmcblk0p6.img
   2560000  --  dev-block-mmcblk0p7.img
  10485760  --  dev-block-mmcblk0p8.img
    512000  --  dev-block-mmcblk0p9.img
    512000  --  dev-block-mmcblk0p11.img
  10485760  --  dev-block-mmcblk0p12.img
 102760448  --  dev-block-mmcblk0p13_system_etc_firmware_misc.img
   3145728  --  dev-block-mmcblk0p14.img
   3145728  --  dev-block-mmcblk0p15.img
   3145728  --  dev-block-mmcblk0p16.img
 102760448  --  dev-block-mmcblk0p17_system_etc_firmware_misc_mdm.img
   3145728  --  dev-block-mmcblk0p18.img
   3145728  --  dev-block-mmcblk0p19.img
   3145728  --  dev-block-mmcblk0p20.img
  10485760  --  dev-block-mmcblk0p21_efs.img
  10485760  --  dev-block-mmcblk0p22.img
  10485760  --  dev-block-mmcblk0p23.img
 744488960  --  dev-block-mmcblk0p24_system.img
2149580800  --  dev-block-mmcblk0p25_data.img
 316669952  --  dev-block-mmcblk0p26_cache.img
 135266304  --  dev-block-mmcblk0p27_tombstones.img
$ ls -lh image sizes
100M  --  dev-block-mmcblk0p1.img
500K  --  dev-block-mmcblk0p2.img
1.5M  --  dev-block-mmcblk0p3.img
1.0K  --  dev-block-mmcblk0p4.img
500K  --  dev-block-mmcblk0p5.img
2.0M  --  dev-block-mmcblk0p6.img
2.5M  --  dev-block-mmcblk0p7.img
 10M  --  dev-block-mmcblk0p8.img
500K  --  dev-block-mmcblk0p9.img
500K  --  dev-block-mmcblk0p11.img
 10M  --  dev-block-mmcblk0p12.img
 98M  --  dev-block-mmcblk0p13_system_etc_firmware_misc.img
3.0M  --  dev-block-mmcblk0p14.img
3.0M  --  dev-block-mmcblk0p15.img
3.0M  --  dev-block-mmcblk0p16.img
 98M  --  dev-block-mmcblk0p17_system_etc_firmware_misc_mdm.img
3.0M  --  dev-block-mmcblk0p18.img
3.0M  --  dev-block-mmcblk0p19.img
3.0M  --  dev-block-mmcblk0p20.img
 10M  --  dev-block-mmcblk0p21_efs.img
 10M  --  dev-block-mmcblk0p22.img
 10M  --  dev-block-mmcblk0p23.img
710M  --  dev-block-mmcblk0p24_system.img
2.1G  --  dev-block-mmcblk0p25_data.img
302M  --  dev-block-mmcblk0p26_cache.img
129M  --  dev-block-mmcblk0p27_tombstones.img
$
Q. Anything else important?
A. None of the images are completely empty, and dev-block-mmcblk0p16.img is identical to dev-block-mmcblk0p20.img.

Q. Which block image maps to what?
A. I'm not sure. Looking at the `mount` output, it's obvious that mmcblk0p21 is /efs, mmcblk0p13 is /system/etc/firmware/misc, mmcblk0p17 is /system/etc/firmware/misc_mdm, mmcblk0p24 is /system, mmcblk0p25 is /data, mmcblk0p26 is /cache, and mmcblk0p27 is /tombstones.

As far as Heimdall-related things like boot.img, recovery.img, etc... it has not been determined. I believe on the Epic 4g Touch, mmcblock0p8 contains boot.img and mmcblk0p22 contains recovery.img. These are probably the same. What is the kernel (zImage)...?
forum.xda-developers.com/showpost.php?p=19269788&postcount=7

The modem is probably mmcblk0p17 because it is mounted on /system/etc/firmware/misc_mdm or mmcblk0p13 because it is mounted on /system/etc/firmware/misc.

Q. How do I enter download mode and recovery mode?
A. Recovery mode can be entered by holding down both the volume DOWN and volume UP buttons at the same time when pressing the power button. The phone should vibrate once. It is then alright to release the power button.

Download mode can be entered two ways. One way is to just hold down the volume DOWN button when turning on the phone like above. The other way is to remove the battery from the phone and connect the phone to a usb port (or the phone charger). While it is connected hold down volume DOWN. It should go into download mode without even having to press the power button.

Q. I want to void my warranty. How can I root my phone?
A. You can use the zergrush exploit.
(Windows program, I think...) xda-developers.com/showthread.php?t=1320350
(exploit runnable on the device for advanced users) xda-developers.com/showthread.php?t=1296916 (In order to run the binary, put it in /data/local/tmp. It is world-writable. /sdcard and /sdcard/external_sd are mounted noexec, so the binary cannot be run from there.)
(exploit source code) github.com/revolutionary/zergRush

Q. Post the stock kernel config?
A. I have attached it to this post.

Q. How can I get my phone back to stock?
A. There is currently no way to get the phone back to stock yet. But I have created an odin package that contains stock boot.img (/dev/block/mmcblk0p8), stock recovery.img (/dev/block/mmcblk0p22), and /system plus `su` and `busybox` (/dev/block/mmcblk0p24).

WARNING: this has not been tested, so it may brick your phone:

Here is a package that is flashable using ODIN:
72.13.95.4/sc03dsmallkernelstockrootimg.tar.gz
gunzip it and then flash it with ODIN. It may also be wise to add the md5sum to the end of the tar (`md5sum -t sc03smallkernelstockrootimg.tar >> sc03smallkernelstockrootimg.tar ; mv sc03smallkernelstockrootimg.tar sc03smallkernelstockrootimg.tar.md5`).

Q. Help, my filesystem is corrupted! Help, the emmc is corrupted! Help, everything on /block/mmcblk0 is corrupted!
A. Try doing a factory reset in the recovery mode. It may not work if you are using ClockWorkMod, so you may need to flash the stock recovery image. If that doesn't work, try the stock recovery image for the TMobile Galaxy S II 4G.

Q. I feel like I've seen this thread somewhere else?
A. You have, sort of. I'm trying to base this thread off of the thread about the non-LTE Docomo Samsung Galaxy S II: forum.xda-developers.com/showthread.php?t=1126190
Attached Files
File Type: txt sc-03d_stock_kernel_config.txt - [Click for QR Code] (79.5 KB, 1060 views)
 
SocialReject
Old
(Last edited by SocialReject; 28th November 2011 at 08:10 AM.)
#2  
SocialReject's Avatar
Senior Member
Thanks Meter 189
Posts: 978
Join Date: Apr 2011
Location: Everywhere.
What does this have to do with the Epic Touch

Sent from the future.
 
cdep.illabout
Old
#3  
Junior Member - OP
Thanks Meter 0
Posts: 4
Join Date: Nov 2011
Quote:
Originally Posted by SocialReject View Post
What does this have to do with the Epic Touch
The SC-03D is (probably)techinally very similar to the Epic 4G Touch. This phone (probably) won't be able to use ROMs for the normal SGSII, but may be able to use ROMs for the 4G version of SGSII. I thought this forum would be the best place for this thread, but perhaps it belongs in the Galaxy S II General forum? Is there a Galaxy S II 4G General forum?
 
Calkulin
Old
#4  
Calkulin's Avatar
Recognized Developer
Thanks Meter 6423
Posts: 1,393
Join Date: Sep 2008

 
DONATE TO ME
Quote:
Originally Posted by cdep.illabout View Post
The SC-03D is (probably)techinally very similar to the Epic 4G Touch. This phone (probably) won't be able to use ROMs for the normal SGSII, but may be able to use ROMs for the 4G version of SGSII. I thought this forum would be the best place for this thread, but perhaps it belongs in the Galaxy S II General forum? Is there a Galaxy S II 4G General forum?

The LTE S2's are actually Qualcomm chipsets, so that phone is more like the AT&T Skyrocket & T-mobile versions than ours.
If you like my work, donate to buy me a beer or 2

The Following User Says Thank You to Calkulin For This Useful Post: [ Click to Expand ]
 
bbedward
Old
#5  
bbedward's Avatar
Recognized Developer
Thanks Meter 829
Posts: 1,109
Join Date: Jun 2010
Location: Cleveland, OH

 
DONATE TO ME
Maybe ur confusing wimax with LTE. I'd consider the skyrocket

Sent from my SPH-D710 using XDA App
I specialize in software development/engineering. My specialty is Android app development, java web development, and front-end web development. I also develop c++ applications in Linux - as well as participate in some Linux kernel development.
Current devices: Nexus 7 - 2013, Nexus 5
The Following User Says Thank You to bbedward For This Useful Post: [ Click to Expand ]
 
cdep.illabout
Old
(Last edited by cdep.illabout; 29th November 2011 at 07:14 AM.)
#6  
Junior Member - OP
Thanks Meter 0
Posts: 4
Join Date: Nov 2011
Quote:
Originally Posted by Calkulin View Post
The LTE S2's are actually Qualcomm chipsets, so that phone is more like the AT&T Skyrocket & T-mobile versions than ours.
Okay, sorry for the confusion. Let me message a moderator and try to get this thread moved to the T-Mobile Samsung Galaxy S II SGH-T989 General forum...

edit: Just sent jerdog (the moderator of this forum) a message asking for this thread to be moved
 
fifo_thekid
Old
#7  
Junior Member
Thanks Meter 0
Posts: 29
Join Date: Jan 2008
Location: Fukui, Japan

 
DONATE TO ME
where am i supposed to get the drivers for windows 7 64 bit?
i tried kies but it couldn't install all the drivers!
 
AllGamer
Old
(Last edited by AllGamer; 1st December 2011 at 06:07 PM.)
#8  
AllGamer's Avatar
Retired Forum Moderator
Thanks Meter 1571
Posts: 11,516
Join Date: May 2008
Location: buried under loads of work IRL

 
DONATE TO ME
Quote:
Originally Posted by Calkulin View Post
The LTE S2's are actually Qualcomm chipsets, so that phone is more like the AT&T Skyrocket & T-mobile versions than ours.
yup, the only difference really is the exterior shell which is a little bit more square than round, and has a HARD key + 2 capacitive buttons, instead of 4 capacitive buttons found in the American version of the phone

it's like the old I9000 super sized


Donation is appreciated but not required, a cup of Coffee would suffice

Samsung i9000m: on CM10
Samsung Nexus S: on JB 4.2.2
Samsung Galaxy S II SGH-T989: on CM10
Samsung Galaxy NOTE SGH-i717r: on CM10
Samsung Galaxy NOTE 3 SM-N900W8: stock 4.3
 
cdep.illabout
Old
#9  
Junior Member - OP
Thanks Meter 0
Posts: 4
Join Date: Nov 2011
Quote:
Originally Posted by fifo_thekid View Post
where am i supposed to get the drivers for windows 7 64 bit?
i tried kies but it couldn't install all the drivers!
I'm sorry, I'm not very familiar with Windows. In order to use Odin, I am running Windows XP in a VM on Linux.

If you can't figure out your problem, try searching this forum or the AT&T Skyrocket forum for help with Odin and Kies.
 
fifo_thekid
Old
#10  
Junior Member
Thanks Meter 0
Posts: 29
Join Date: Jan 2008
Location: Fukui, Japan

 
DONATE TO ME
lol
that's exactly what i've done yesterday :P

Tags
docomo, japanese, lte, sc-03d, sc03d
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes