Related
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. [email protected] #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
What does this have to do with the Epic Touch
Sent from the future.
SocialReject said:
What does this have to do with the Epic Touch
Click to expand...
Click to collapse
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?
cdep.illabout said:
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?
Click to expand...
Click to collapse
The LTE S2's are actually Qualcomm chipsets, so that phone is more like the AT&T Skyrocket & T-mobile versions than ours.
Maybe ur confusing wimax with LTE. I'd consider the skyrocket
Sent from my SPH-D710 using XDA App
Calkulin said:
The LTE S2's are actually Qualcomm chipsets, so that phone is more like the AT&T Skyrocket & T-mobile versions than ours.
Click to expand...
Click to collapse
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
where am i supposed to get the drivers for windows 7 64 bit?
i tried kies but it couldn't install all the drivers!
Calkulin said:
The LTE S2's are actually Qualcomm chipsets, so that phone is more like the AT&T Skyrocket & T-mobile versions than ours.
Click to expand...
Click to collapse
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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fifo_thekid said:
where am i supposed to get the drivers for windows 7 64 bit?
i tried kies but it couldn't install all the drivers!
Click to expand...
Click to collapse
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.
lol
that's exactly what i've done yesterday
back on topic
there's additional info in Wikipedia that points the same http://en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
HP TouchPad, T-Mobile Galaxy S II, Galaxy S II Skyrocket, HTC Vivid, NTT DoCoMo, Galaxy S II LTE, LG Nitro HD
Click to expand...
Click to collapse
basically all the Apps/Games running on those devices should be compatible with each other
and here's a side by side compare from gsmarena http://www.gsmarena.com/compare.php3?idPhone1=4129&idPhone2=4124
Calkulin said:
The LTE S2's are actually Qualcomm chipsets, so that phone is more like the AT&T Skyrocket & T-mobile versions than ours.
Click to expand...
Click to collapse
Hi, I've just bought a Korean Galaxy S2 4G LTE (SHV-E110S) he looks exactly like the japaneese LTE, and have the same specifications. Do you things that the roms of skyrocket works on it?
you will need to extract the stock kernel, of the SHV-E110S or SC-03D,
make a full nandroid backup
install CWR
then flash the ROM you want, and flash back the stock Kernel
and possibly other minor updates/fixes
there's a good guide over at the Skyrocket forum about how to use Tmo ROMs on ATT Skyrocket, so just replace all those steps with the Korean / Japan version http://forum.xda-developers.com/showthread.php?t=1337311
thank you for the quick reply.
I have a small problem, I don't know if it's the right place to ask, this morning I flashed CW recovery and the capacitive touches dosen't work anymore, if I find the stock kernel it would resolve my pb?
AllGamer said:
you will need to extract the stock kernel, of the SHV-E110S or SC-03D
Click to expand...
Click to collapse
How I extract the stock kernel?
PS: I Can't send donations because of my country money regulation but if you come in Tunis I'll be happy to pay you a coffe
Same thing happened to me
However, after restarting two three times it worked again. Albeit, without haptic feedback
Are you guys flashing on t989?
Sent from my SGH-T989 using XDA App
Are there any stock roms for this phone
Sent from my 丅-爪◯阝工しモ ム丹し丹メㄚ ち 工工 w/ Cyanogen Mod 7.2 ツ using XDA Premium App
Does this have Swype in Japanese? If there is...is there anyway to port it in the languages for our Swype keyboard for the languages?
fifo_thekid said:
Same thing happened to me
However, after restarting two three times it worked again. Albeit, without haptic feedback
Click to expand...
Click to collapse
I'm in the korean version and I restarted many times but nothing changes, when I enter the recovrery and when I have the message "back menu button disabled" the recovery freezes!
I think that there is a compatibility problem or something like, so I want to find the original recovery for my phone but I didn't found it
I tried to change the touch key light duration just to see if something happens, but the delay never changes, the keys lights at the same time of the screen
I found the original firmware of the E110S in a chinese forum and I flashed it with odin but the capacitive touches still don't work
any help?
PS: if someone is searching for the firmware I posted the link http://115.com/file/cljkbns3#
Hello, can anybody with a rooted Gio point me out to the /dev/block files for /system , /data , /cache ?
For example for GSII is /dev/block/mmcblk0p24 25 26
At us i think it should be something with 12/13/14
I need the correct filenames from our Gio. Only names i don`t actually need the files
Thank u in advance
I have CyanogenMod 7.2 installed with ext4 partition on SD.
Here's what "mount" says on my phone (stripped the mounts for individual apps).
I decided to leave other non-/dev/block entries here, too, just in case
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl12 on /system type ext4 (ro,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/stl13 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/stl14 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p2 on /data/app type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p2 on /data/data type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p2 on /cache/download type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
BML partition layout of the Samsung Galaxy Gio GT-S5660:
bml0: contents of the entire flash
bml1: mibib
bml2: qcsbl
bml3: oemsbl
bml4: amss
bml5: block level representation of /dev/stl5 (efs)
bml6: block level representation of /dev/stl6 (empty)
bml7: arm11boot
bml8: boot image
bml9: recovery image
bml10: unknown
bml11: empty (contains only 0xff bytes)
bml12: block level representation of /dev/stl12 (/system)
bml13: block level representation of /dev/stl13 (/data)
bml14: block level representation of /dev/stl14 (/cache)
STL partition layout of the Samsung Galaxy Gio GT-S5660:
stl5: /efs
stl6: empty partition (contains only 0xff bytes)
stl12: /system
stl13: /data
stl14: /cache
Partition layout used by ODIN (GIO_v1.0.ops):
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,
Available partitions according to /proc/partitions:
major minor size device
137 0 513024 bml0/c
137 1 1536 bml1
137 2 512 bml2
137 3 768 bml3
137 4 25600 bml4
137 5 9216 bml5
137 6 5120 bml6
137 7 2048 bml7
137 8 8192 bml8
137 9 8192 bml9
137 10 768 bml10
137 11 6144 bml11
137 12 222464 bml12
137 13 192768 bml13
137 14 29696 bml14
138 12 214784 stl12
138 13 185600 stl13
138 14 25856 stl14
particle.blurringexistence.net/samsung-gt-s5660/partition-layout
Sent from my GT-S5660 using XDA Premium App
Thank u both ! I wanted to try to port DARKSIDE::SUPER::WIPE but it formats in Ext4 and i need in rfs because atm i only use stock rom
Note that my output is from CM which uses ext4, too. No rfs there, sorry
hsrars-d said:
BML partition layout of the Samsung Galaxy Gio GT-S5660:
bml0: contents of the entire flash
bml1: mibib
bml2: qcsbl
bml3: oemsbl
bml4: amss
bml5: block level representation of /dev/stl5 (efs)
bml6: block level representation of /dev/stl6 (empty)
bml7: arm11boot
bml8: boot image
bml9: recovery image
bml10: unknown
bml11: empty (contains only 0xff bytes)
bml12: block level representation of /dev/stl12 (/system)
bml13: block level representation of /dev/stl13 (/data)
bml14: block level representation of /dev/stl14 (/cache)
STL partition layout of the Samsung Galaxy Gio GT-S5660:
stl5: /efs
stl6: empty partition (contains only 0xff bytes)
stl12: /system
stl13: /data
stl14: /cache
Partition layout used by ODIN (GIO_v1.0.ops):
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,
Available partitions according to /proc/partitions:
major minor size device
137 0 513024 bml0/c
137 1 1536 bml1
137 2 512 bml2
137 3 768 bml3
137 4 25600 bml4
137 5 9216 bml5
137 6 5120 bml6
137 7 2048 bml7
137 8 8192 bml8
137 9 8192 bml9
137 10 768 bml10
137 11 6144 bml11
137 12 222464 bml12
137 13 192768 bml13
137 14 29696 bml14
138 12 214784 stl12
138 13 185600 stl13
138 14 25856 stl14
particle.blurringexistence.net/samsung-gt-s5660/partition-layout
Sent from my GT-S5660 using XDA Premium App
Click to expand...
Click to collapse
Sorry to bring the thread back up from the ground but i need some info on how to rebuild/force format on block stl13.
Have tried multiple CWM flashes now and stock rom flashes via Odin but stilll no good
Here you can download a kernel with ClockworkMod Recovery built into it, which allows you to flash zips and to make and restore backups.
This version of ClockworkMod Recovery is the ICS version, so it is the latest (until there is a jellybean one).
Nickholtus has prepared for you an easy to flash package here for you:
Xperia P: http://forum.xda-developers.com/showthread.php?p=28778819
Xperia U: http://forum.xda-developers.com/showthread.php?p=28819512&postcount=282
Xperia Sola (working external sdcard): http://forum.xda-developers.com/showthread.php?p=28957468&postcount=412
To flash this recovery, download the kernel, put it in your fastboot folder and name it kernel.elf.
Then open up a command prompt and in that folder do:
Code:
fastboot flash boot kernel.elf
This is a joint effort of I, nickholtus, K900 and championswimmer, our sources are at https://github.com/AOKPXperia, our main aim is to make trees that will build on AOSP and any other android source tree (AOKP - unicorns).
Thanks to Arakmar for clearing things up for me on how to individually compile the recovery binary.
Keiran
Nice to say devs coming up...Thank you for your efforts ..
Edit: Thank you Thank you Thank you...
Woah!
By the end of the week? That's fast
Do help Kieran get his phone here
Sent from my ST25i using xda premium
Wow !!!!
Thanks For Ur Efforts
Thanks bro!!!
Inviato dal mio LT22i con Tapatalk 2
That would be awesome Hoply we will see some rom development then
Sent from my LT22i using xda premium
Here is my progress:
Got minimal device tree set up for kumquat (ST25i, Xperia U)
All I need now is to make recovery.fstab, can people post mount info for P, U and Sola?
Then after that I edit ram disk to allow booting into recovery and I will post it on this thread.
hi,
here is the /proc/mount file of my xperia sola.
i hope it is what you need?
greetings
Progress:
Got minimal device tree done - check
Compiled recovery - check
Now all we need to do is inject recovery into boot image, then you can have recovery on stock kernel
Our sources are at https://github.com/AOKPXperia
Current repo I am using is device_sony_kumquat
Keiran
Edit: from above info /sdcard is at /dev/block/vold/179:14
Awsome!!! I will wait this...
Code:
C:\Program Files\Android\android-sdk\platform-tools>Adb shell cat /proc/partitio
ns
major minor #blocks name
7 0 10427 loop0
7 1 4190 loop1
7 2 4190 loop2
179 0 7757824 mmcblk0
179 1 1023 mmcblk0p1
179 2 512 mmcblk0p2
179 3 128 mmcblk0p3
179 4 1 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 3072 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 1048576 mmcblk0p10
179 11 2097152 mmcblk0p11
179 12 256000 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 4173824 mmcblk0p14
254 0 10426 dm-0
254 1 4189 dm-1
254 2 4189 dm-2
C:\Program Files\Android\android-sdk\platform-tools>
here u go again xperia U mounts....
---------- Post added at 04:10 PM ---------- Previous post was at 04:05 PM ----------
Code:
# mount
mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p10 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /modemfs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p11 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,
noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p8 /data/idd ext4 rw,nosuid,nodev,noatime,barrier=0,data=order
ed 0 0
/dev/block/vold/179:14 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:14 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.trust5.odp-1 vfat ro,dirsync,nosuid,nodev,relatime
,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mix
ed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/teenpatti.com.ibibo-1 vfat ro,dirsync,nosuid,nodev,rel
atime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortnam
e=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/play.ibibo.rummy.cash-1 vfat ro,dirsync,nosuid,nodev,r
elatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortn
ame=mixed,utf8,errors=remount-ro 0 0
#
should help u too
Yeah I got that
/cache is mmcblk0p12
/data is mmcblk0p11
/system is mmcblk0p10
/sdcard is mmcblk0p14
/boot is mmcblk0p9
Can anyone verify this for me?
Keiran
Keiran can you make this possible for Locked bootloaders btw ?
DeanBoro said:
Keiran can you make this possible for Locked bootloaders btw ?
Click to expand...
Click to collapse
Do this for me,
adb shell "cd /dev/block ; ls ;"
And post here the output
If this device gets root on locked boot loader, maybe.
Keiran
KeiranFTW said:
Do this for me,
adb shell "cd /dev/block ; ls ;"
And post here the output
If this device gets root on locked boot loader, maybe.
Keiran
Click to expand...
Click to collapse
Here is the output you requested
Code:
* daemon started successfully *
vold
mmcblk0p14
mmcblk0p13
mmcblk0p12
mmcblk0p11
mmcblk0p10
mmcblk0p9
mmcblk0p8
mmcblk0p7
mmcblk0p6
mmcblk0p5
mmcblk0p4
mmcblk0p3
mmcblk0p2
mmcblk0p1
mmcblk0
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram15
ram14
ram13
ram12
ram11
ram10
ram9
ram8
ram7
ram6
ram5
ram4
ram3
ram2
ram1
ram0
DeanBoro said:
Here is the output you requested
Code:
* daemon started successfully *
vold
mmcblk0p14
mmcblk0p13
mmcblk0p12
mmcblk0p11
mmcblk0p10
mmcblk0p9
mmcblk0p8
mmcblk0p7
mmcblk0p6
mmcblk0p5
mmcblk0p4
mmcblk0p3
mmcblk0p2
mmcblk0p1
mmcblk0
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram15
ram14
ram13
ram12
ram11
ram10
ram9
ram8
ram7
ram6
ram5
ram4
ram3
ram2
ram1
ram0
Click to expand...
Click to collapse
You have p9, p9 is visible, is boot partition... don't know if you can flash to it though, may be protected on locked bl - anyway you need root first.
KeiranFTW said:
You have p9, p9 is visible, is boot partition... don't know if you can flash to it though, may be protected on locked bl - anyway you need root first.
Click to expand...
Click to collapse
I cant unlock the bootloader as the fastboot is locked unfortunately (N) . Do you have any suggestions on how I could attempt to gain ROOT on it, or maybe even possibly Temp ROOT?
DeanBoro said:
I cant unlock the bootloader as the fastboot is locked unfortunately (N) . Do you have any suggestions on how I could attempt to gain ROOT on it, or maybe even possibly Temp ROOT?
Click to expand...
Click to collapse
No idea but recovery isn't working, bootrec won't execute
KeiranFTW said:
No idea but recovery isn't working, bootrec won't execute
Click to expand...
Click to collapse
ahhh that sucks!
S1 apparently doesnt enable Fastboot for the new Xperia line atm so I cant really do much development
Okay, so from some hard work and testing from nickholtus (hats off to him) we have fixed up bootrec and he is currently using a recovery compiled by me on his P
With this you can even back up boot/kernel partition on the go! No need for fastboot!
Not working:
Mass storage (we are using ICS recovery sources, with different USB gadget implementation to gingerbread)
Everything else works for now
We will post recovery when we have patched stock kernel ram disk for the devices.
Keiran
Trying to start a first port of call for a General & Development Thread for these phones and to make things a little more organised so here we are links provided below a for a range of mods and development that's started and by the look of how it's going its gonna be really busy full of development so please be nice here and if you have any suggestions or tips or hints please feel free to add them in here for our fellow M/M Dual users and developers to see.
Links will be updated on a regular basis
Xperia M Regional Codes (provided by SharpnShiny)
http://forum.xda-developers.com/showthread.php?t=2456622
Full Root for Xperia M (credits to xzn and team for this)
http://forum.xda-developers.com/showthread.php?t=2457174
Root For c2004/2005 models (dual SIM) thanks ernvs
http://forum.xda-developers.com/showthread.php?t=2477254 or http://forum.xda-developers.com/showthread.php?t=2479359 guide by waledac
Stock firmware thread (by Doomlord) and Recovery Test (thanks to alivanov79 on page 12)
Firmware Version: 15.1.A.1.9
customization ID: 1274-3888_IN
model: C1904
http://forum.xda-developers.com/showthread.php?t=2410913
Stock Firmware 15.1.C.1.17 C1904 (Tutorial within thread on how to flash it and thanks to jeremarfil24)
http://forum.xda-developers.com/showthread.php?t=2463870
Stock Xperia M Kernel (thanks n1kolaa)
https://github.com/n1kolaa/andorid_kernel_sony_Nicki
Full internal dump and stock kernel (thanks alvinhochun)
https://dl.dropboxusercontent.com/u/39080136/c1905/loop0p17.img
https://dl.dropboxusercontent.com/u/39080136/c1905/probably_stock_kernel.bin
Bootloader Unlocking (provided by Sony) *WARNING* Will erase everything on phone and set back to factory so backup apps etc
http://unlockbootloader.sonymobile.com
AOSP File/Build by Sony of first firmware
http://developer.sonymobile.com/dow...ves/open-source-archive-for-build-15-1-a-1-9/
Thanks to cian for sharing the links and thanks to jeremarfil24 for these mods
Honami Settings For Xperia M
http://forum.xda-developers.com/showthread.php?p=46042519
Honami SystemUI for Xperia™ M
http://forum.xda-developers.com/showthread.php?p=46042247
Stock kernel with cwm recovery (thanks to alvinhochun)
http://forum.xda-developers.com/showthread.php?t=2480556
Tool to add CWM recovery to any kernel including Xperia M(thanks to alvinhochun)
http://forum.xda-developers.com/showthread.php?t=2481864
Few links for Mods and guide to flashing 4.2.2 dual SIM firmware to c1904/1905 and rooting guide (thanks to jeremarfil24)
http://forum.xda-developers.com/showthread.php?p=46427950
Sent from My Sony Xperia M C1905
Good thread, there's a lot tutorial out there for xperia M
Sent from my C1905 using xda app-developers app
I've currently just removed full root from my phone as I noticed stamina mode was not working so it was either the root or busybox or possibly the rootfix not 100% sure if this was the cause but I've reverted back to factory and stamina is now working
Thought I would share this info
Sent from my C1905 using xda app-developers app
i shered xperia m kernel on github! https://github.com/n1kolaa/andorid_kernel_sony_Nicki
Not my work but i found these too,
Honami Settings For Xperia M
http://forum.xda-developers.com/showthread.php?p=46042519
Honami SystemUI for Xperia™ M
http://forum.xda-developers.com/showthread.php?p=46042247
dunc4n88 said:
I've currently just removed full root from my phone as I noticed stamina mode was not working so it was either the root or busybox or possibly the rootfix not 100% sure if this was the cause but I've reverted back to factory and stamina is now working
Thought I would share this info
Sent from my C1905 using xda app-developers app
Click to expand...
Click to collapse
What do u mean? My stamina mode still work after root and remount reboot fix, u mean estimated time? If so the estimated time always recalibrated depend user usage time
Sorry for my bad englisj
Sent from my C1905 using xda app-developers app
Partitions information of internal storage
I dumped the internal storage (`cat /dev/block/mmcblk0 > full.img`) and tried to get some useful information from that. Took me ages to do that. Since I dumped the file on-line, userdata and cache partitions are dirty, but that doesn't affect much, does it huh?
Strangely both the GPT partition tables have corrupted CRC, but they looks fine so I just used it.
Anyway I don't have any experience hacking emmc devices, but let's see if I'm helpful:
Code:
GPT fdisk (gdisk) version 0.8.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk full.img: 7733248 sectors, 3.7 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Partition table holds up to 28 entries
First usable sector is 34, last usable sector is 7733214
Partitions will be aligned on 256-sector boundaries
Total free space is 107998 sectors (52.7 MiB)
Number Start (sector) End (sector) Size Code Name
1 256 4351 2.0 MiB FFFF TA
2 4352 4607 128.0 KiB FFFF sbl1
3 4608 5119 256.0 KiB FFFF sbl2
4 5120 5631 256.0 KiB FFFF s1sbl2
5 5632 6655 512.0 KiB FFFF sbl3
6 6656 7679 512.0 KiB FFFF aboot
7 7680 8703 512.0 KiB FFFF tz
8 8704 8959 128.0 KiB FFFF alt_sbl1
9 8960 9471 256.0 KiB FFFF alt_sbl2
10 9472 9983 256.0 KiB FFFF alt_s1sbl2
11 9984 11007 512.0 KiB FFFF alt_sbl3
12 11008 12031 512.0 KiB FFFF alt_aboot
13 12032 13055 512.0 KiB FFFF alt_tz
14 13056 14079 512.0 KiB FFFF rpm
15 14080 15103 512.0 KiB FFFF alt_rpm
16 16384 49151 16.0 MiB 8300 LTALabel
17 49152 90111 20.0 MiB FFFF boot
18 90112 221183 64.0 MiB 0700 modem
19 221184 227327 3.0 MiB FFFF modemst1
20 229376 235519 3.0 MiB FFFF modemst2
21 237568 243711 3.0 MiB FFFF fsg
22 243712 253951 5.0 MiB FFFF ramdump
23 253952 286719 16.0 MiB FFFF FOTAKernel
24 286720 294911 4.0 MiB 8300 persist
25 294912 2752511 1.2 GiB 8300 system
26 2752512 3264511 250.0 MiB 8300 cache
27 3268608 7634910 2.1 GiB 8300 userdata
Partitions content attempt to be identified with `file`:
Code:
full.img: x86 boot sector; partition 1: ID=0xee, starthead 0, startsector 1, 7733247 sectors, extended partition table (last)\011, code offset 0x0
loop0p1.img: DOS executable (block device driver)
loop0p2.img: data
loop0p3.img: data
loop0p4.img: data
loop0p5.img: data
loop0p6.img: Hitachi SH big-endian COFF object, not stripped
loop0p7.img: data
loop0p8.img: data
loop0p9.img: data
loop0p10.img: data
loop0p11.img: data
loop0p12.img: Hitachi SH big-endian COFF object, not stripped
loop0p13.img: data
loop0p14.img: data
loop0p15.img: data
loop0p16.img: Linux rev 1.0 ext4 filesystem data, UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (extents) (large files)
loop0p17.img: ELF 32-bit LSB executable, ARM, version 1, statically linked, stripped
loop0p18.img: x86 boot sector, code offset 0x3c, OEM-ID "MSDOS5.0", sectors/cluster 32, root entries 512, Media descriptor 0xf8, sectors/FAT 17, heads 255, sectors 131072 (volumes > 32 MB) , serial number 0xbc614e, unlabeled, FAT (16 bit)
loop0p19.img: data
loop0p20.img: data
loop0p21.img: data
loop0p22.img: ELF 32-bit LSB executable, ARM, version 1, statically linked, stripped
loop0p23.img: ELF 32-bit LSB executable, ARM, version 1, statically linked, stripped
loop0p24.img: Linux rev 1.0 ext2 filesystem data (mounted or unclean), UUID= xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (extents) (large files) (huge files)
loop0p25.img: Linux rev 1.0 ext4 filesystem data, UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (extents) (large files)
loop0p26.img: Linux rev 1.0 ext4 filesystem data, UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (needs journal recovery) (extents) (large files)
loop0p27.img: Linux rev 1.0 ext4 filesystem data, UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (needs journal recovery) (extents) (large files)
Meaningful guess of what the partitions may contain (actually pretty obvious):
p17 (boot) - Kernel? Binary code which starts the kernel? vmlinux? (*) My copy: https://dl.dropboxusercontent.com/u/39080136/c1905/loop0p17.img
p23 (FOTAKernel) - Same as above, but downloaded by FOTA for update purpose
p24 (persist) - Mounted as `/persist`, ext2
p25 (system) - System partition, mounted as `/system`, ext4
p26 (cache) - Cache partition, mounted as `/cache`, ext4
p27 (userdata) - Data partition, mounted as `/data`, ext4
(*) For my firmware 15.1.C.1.17, at offset 0x3db7 you can find "Uncompressing Linux...", and at offset 0x4053 you can find the gzip magic number. So...
Code:
$ tail -c +16468 loop0p17.img |gunzip > blah.bin
gzip: stdin: decompression OK, trailing garbage ignored
... I think this dumped the stock kernel. Uploaded it here: https://dl.dropboxusercontent.com/u/39080136/c1905/probably_stock_kernel.bin
The partition is probably the vmlinux.
I hope I can do something to find the initrd, can't find it yet...
ariw182 said:
What do u mean? My stamina mode still work after root and remount reboot fix, u mean estimated time? If so the estimated time always recalibrated depend user usage time
Sorry for my bad englisj
Sent from my C1905 using xda app-developers app
Click to expand...
Click to collapse
I've re-rooted the phone now just me thinking it wasn't working but after re-root it does still work, im glad the system dumps are coming in mine failed dumping to sdcard and havent had time to try through adb
Sent from my C1905 using xda premium
Oh I am such an idiot... the initrd is just also inside the boot partition...
Found yet another gzip magic number at 0x55aadc, so extract it:
Code:
$ tail -c +5614301 loop0p17.img |gunzip > second.bin
gzip: stdin: decompression OK, trailing garbage ignored
$ file second.bin
second.bin: ASCII cpio archive (SVR4 with no CRC)
So here is the CPIO file: https://dl.dropboxusercontent.com/u/39080136/c1905/initrd.cpio
The ramdisk content in tar format if you need: https://dl.dropboxusercontent.com/u/39080136/c1905/initrd.tar
I believe this is enough to build a bootable image for fastboot for unlocked bootloader, isn't it?
Anyone who has installed the test cwm recovery try downloading an app from play market called X-parts and use the option to reboot to recovery, try and report please
Sent from my C1905 using xda premium
Just a thought for cwm recovery what about trying to use ROM Manager to install cwm recovery, would this work?
Edit
Doesn't work just tried
Sent from my C1905 using xda premium
For the recovery, i think this link (http://forum.xda-developers.com/showthread.php?t=2075562) will be useful :silly:
and since our device's specs are almost identical with xperia L which gets CM 10.2 (cmiiw), i think there is a chance that xperia L's CM 10.2 can be ported to our device, we just need an experienced developer who want to help or a noob who want to learn :silly: huehuehhehuhe
DPI
Hi,
I was wonering if i could change the Dpi in the prop build??
And is there going to be a Full Thread for Xperia M? (please)
My Phone-Xperia M
Build-15.1.B.0.2
Status-Unlocked/Rooted
Loads of Apps removed (184 Remaining)
gavanid said:
Hi,
I was wonering if i could change the Dpi in the prop build??
And is there going to be a Full Thread for Xperia M? (please)
My Phone-Xperia M
Build-15.1.B.0.2
Status-Unlocked/Rooted
Loads of Apps removed (184 Remaining)
Click to expand...
Click to collapse
Hi and welcome, there are requests put in for a thread but nothing yet so I made this one to try and organise things abit,
Dpi probably could be changed in build prop, look for the line that has dpi in it and change the value can't remember if it's the higher their value the more smaller the screen goes but back up your build prop before editing it try rom toolbox to edit the build prop, also did you do a full root with the root fix after installing busybox?
Sent from my C1905 using xda premium
DPI
dunc4n88 said:
Hi and welcome, there are requests put in for a thread but nothing yet so I made this one to try and organise things abit,
Dpi probably could be changed in build prop, look for the line that has dpi in it and change the value can't remember if it's the higher their value the more smaller the screen goes but back up your build prop before editing it try rom toolbox to edit the build prop, also did you do a full root with the root fix after installing busybox?
Sent from my C1905 using xda premium
Click to expand...
Click to collapse
There is no DPI in the prop build but it doesn't matter
the dpi is at 240 anyway. i used the android hardware info app to find all info
OK, so I've been trying to boot/reflash the dumped stock kernel as a test, but all I've got is failure. Here're some notes I've taken:
About the kernel cmdline:
Kernel cmdline:
- As seen in boot.elf:
Code:
console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3
- As seen in /proc/cmdline:
Code:
console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter androidboot.emmc=true androidboot.bootloader=s1 oemandroidboot.s1boot=1271-1024_S1_Boot_MSM_8227_5 androidboot.serialno=********** ta_info=1,16,256 startup=0x00000001 warmboot=0x77665502 oemandroidboot.imei=**************** oemandroidboot.phoneid=0000:**************** oemandroidboot.babe1234=00000000 androidboot.baseband=msm
(IMEI and serial censored)
What? `r=0x3F ehci-hcd.park=3` is gone?
Click to expand...
Click to collapse
About attempting to use `fastboot boot` to boot the dumped kernel (may be invalid, so if someone want to try it just try):
Enter fastboot: Hold `Volume Up` when connecting USB cable, OR use `adb reboot-bootloader`
Visual identification: Blue LED on
version-bootloader: S1_Boot_MSM_8227_5
version-baseband: 1272-2325_15.1.C.1.17
product: C1905
Tried commands:
Code:
fastboot boot boot.elf
> Blue LED stays on, no response to power button, need to remove battery.
Code:
fastboot boot probably_stock_kernel.bin initrd.cpio
> Blue LED stays on, no response to power button, need to remove battery.
Code:
fastboot boot boot.elf -c "console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3"
> Blue LED stays on, no response to power button, need to remove battery.
Code:
fastboot boot probably_stock_kernel.bin initrd.cpio -c "console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3"
> Blue LED stays on, no response to power button, need to remove battery.
Code:
fastboot boot boot.elf -c "console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3" -b 0x80208000
> Blue LED stays on, no response to power button, need to remove battery.
Code:
fastboot boot probably_stock_kernel.bin initrd.cpio -c "console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3" -b 0x80208000
> Blue LED stays on, no response to power button, need to remove battery.
Click to expand...
Click to collapse
About attempting to flash the dumped kernel back to the device:
Code:
fastboot flash boot boot.elf
> FAILED (remote: image is not a boot image)
OMG I really don't want to make a boot image with `mkbootimg`, even though soft bricks can be fixed with a reflash, that means I'll need to restore all my userdata once again.
Click to expand...
Click to collapse
Can anyone help me?
alvinwong_1234 said:
OK, so I've been trying to boot/reflash the dumped stock kernel as a test, but all I've got is failure. Here're some notes I've taken:
About the kernel cmdline:
About attempting to use `fastboot boot` to boot the dumped kernel (may be invalid, so if someone want to try it just try):
About attempting to flash the dumped kernel back to the device:
Can anyone help me?
Click to expand...
Click to collapse
When I check for updates on my phone via pc update service it tells me to connect phone with volume down pressed for fastboot have you tried that? But the led doesn't go blue it flashes red then Amber when I do it could this be flashmode on these devices?
Sent from my C1905 using xda premium
dunc4n88 said:
When I check for updates on my phone via pc update service it tells me to connect phone with volume down pressed for fastboot have you tried that? But the led doesn't go blue it flashes red then Amber when I do it could this be flashmode on these devices?
Sent from my C1905 using xda premium
Click to expand...
Click to collapse
Yes this is flash mode!
Sent from my C1904 using xda app-developers app
alvinwong_1234 said:
Can anyone help me?
Click to expand...
Click to collapse
Are you checked this? http://forum.xda-developers.com/showthread.php?t=2334045
As I saw through fastboot can flash only .img not .elf image file
Boot image with CWM recovery (need to be flashed, unlocked bootloader only)
http://forum.xda-developers.com/showthread.php?t=2473813
Hey guys!
I'm searching around and I couldn't find a way to root SM-R500 Samsung Galaxy Watch Active (Tizen 4.0.0.3). I found a lot of firmware on different websites, but I couldn't find a rooted one. Any suggestions ...
Thanks
Depend what you expect...
Factory/Service Firmware called Combination Firmware is rooted...
I am using Combination Firmware as base... as Engineer sboot.bin (Bootloader) Engineer Kernel is inside...
From Stock Firmware only rootfs.img is modified... to have su Binary...
Problem...
SM-R500 nor other Galaxy variant tested...
Sugestion for you...
Flash Combination Firmware to see what kind of Root you can expect...
I could help you to modify Firmware Files... but OWN RISK...
Best Regards
adfree said:
Depend what you expect...
Factory/Service Firmware called Combination Firmware is rooted...
I am using Combination Firmware as base... as Engineer sboot.bin (Bootloader) Engineer Kernel is inside...
From Stock Firmware only rootfs.img is modified... to have su Binary...
Problem...
SM-R500 nor other Galaxy variant tested...
Sugestion for you...
Flash Combination Firmware to see what kind of Root you can expect...
I could help you to modify Firmware Files... but OWN RISK...
Best Regards
Click to expand...
Click to collapse
I don’t mind to give it a try. Please share what you have?
Sorry.
I waste tooo much time with Tizen...
I have limited time... and energy...
The long way is here:
https://forum.xda-developers.com/smartwatch/gear-s3/gear-s3-android-wear-port-wip-t3584588
Somewhere inside this Thread are infos how to play with rootfs.img...
The "faster" way for you or both of us... is.
Flash Combination Firmware for SM-R500 to see if this is what you want...
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
COMBINATION-FT40_R500XXU1ASG1.tar.md5
These 2 FT40 seems leaked and available... maybe somewhere in public...
I am too lazy to search for you.
TRy hard enough and in 2 days you can pm me... if you not able to find it...
Maybe I will upload for you...
But again.
What kind of magic you expect from Rooting of your SM-R500?
So I can make decission to help you... or maybe waste my time with other things.
Best Regards
Edit 1.
Code:
COMBINATION-FT40_R500XXU1[B]ASA5[/B].tar.md5
ASA5 I have on my HDD... I could upload...
Edit 2.
Uupsi.. I have both FT40...
Still no idea if somewhere public Link available...
Edit 3...
Lesson 1.
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You "need" netOdin Tool for Flashing Firmware...
I will upload for you:
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
Need some time for upload...
Plese remember:
Own risk!
Best Regards
---------- Post added at 04:28 AM ---------- Previous post was at 03:35 AM ----------
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
https://www.file-upload.net/download-13786815/COMBINATION-FT40_R500XXU1ASA5.tar.md5.7z.html
Own risk!
Best Regards
adfree said:
Sorry.
I waste tooo much time with Tizen...
I have limited time... and energy...
The long way is here:
https://forum.xda-developers.com/smartwatch/gear-s3/gear-s3-android-wear-port-wip-t3584588
Somewhere inside this Thread are infos how to play with rootfs.img...
The "faster" way for you or both of us... is.
Flash Combination Firmware for SM-R500 to see if this is what you want...
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
COMBINATION-FT40_R500XXU1ASG1.tar.md5
These 2 FT40 seems leaked and available... maybe somewhere in public...
I am too lazy to search for you.
TRy hard enough and in 2 days you can pm me... if you not able to find it...
Maybe I will upload for you...
But again.
What kind of magic you expect from Rooting of your SM-R500?
So I can make decission to help you... or maybe waste my time with other things.
Best Regards
Edit 1.
Code:
COMBINATION-FT40_R500XXU1[B]ASA5[/B].tar.md5
ASA5 I have on my HDD... I could upload...
Edit 2.
Uupsi.. I have both FT40...
Still no idea if somewhere public Link available...
Edit 3...
Lesson 1.
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You "need" netOdin Tool for Flashing Firmware...
I will upload for you:
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
Need some time for upload...
Plese remember:
Own risk!
Best Regards
---------- Post added at 04:28 AM ---------- Previous post was at 03:35 AM ----------
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
https://www.file-upload.net/download-13786815/COMBINATION-FT40_R500XXU1ASA5.tar.md5.7z.html
Own risk!
Best Regards
Click to expand...
Click to collapse
Sorry for the late reply and thank you adfree for your effort, but I already have and tested the combination firmware and It is not what I'm looking for! Now I'm trying to figure the pinout so I can connect it directly.
Done first attempt with DSL1 Firmware...
Waiting for feedback...
Meanwhile...
A
To enable Root access... SDB Tool required...
Code:
sdb root on
A.1
To enable su from Shell...
Additional steps required...
Code:
sdb root on
sdb shell
mount -vo remount,rw /
chmod -v +sx /usr/bin
Code:
sdb root off
Then you can su from shell...
Code:
su
then it asks for password... password is:
Code:
tizen
B
To check if you can now play with rootfs.img "on the fly"...
Code:
sdb root on
Or you have enbled the other way...
Code:
sdb shell
Code:
mount -vo remount,rw /
Now you can for instance delete poweron poweroff Animation... you can do more but this is safe... nothing will explode.
Code:
sdb root on
Switched to 'root' account mode
sdb shell
sh-3.2# cd /usr/share/edje
sh-3.2# ls -a1l
total 1280
drwxr-xr-x 5 root root 4096 Jun 27 2019 .
drwxr-xr-x 131 root root 4096 Jun 27 2019 ..
-rw-r--r-- 1 root root 322470 Apr 19 2019 360x360_PowerOff.edj
-rw-r--r-- 1 root root 227171 Apr 19 2019 360x360_PowerOn.edj
-rw-r--r-- 1 root root 6065 Apr 19 2019 csc-ani.edj
-rw-r--r-- 1 root root 6221 Apr 19 2019 factory-reset-util.edj
drwxr-xr-x 2 root root 4096 Jun 27 2019 images
drwxr-xr-x 2 root root 4096 Jun 27 2019 include
-rw-r--r-- 1 root root 295340 Apr 19 2019 poweroff.edj
-rw-r--r-- 1 root root 411726 Apr 19 2019 poweron.edj
-rw-r--r-- 1 root root 5656 Apr 19 2019 voice-control-elm.edj
drwxr-xr-x 2 root root 4096 Jun 27 2019 xwalk
Code:
rm poweron.edj
and/or
Code:
rm poweroff.edj
Be carefully what you remove or replace...
Best Regards
Seems to work... DSL1 rooted... tested in coop with:
Code:
COMBINATION-FT40_R500XXU1[B]ASL2[/B]
For some dump action I need some infos about partition layout...
Code:
[B]cat /proc/partitions[/B]
Example output from SM-Z130H and SM-R760...
Code:
major minor #blocks name
7 0 10052 loop0
7 1 17408 loop1
254 0 146152 zram0
179 0 3817472 mmcblk0
179 1 1024 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 9216 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2048 mmcblk0p12
179 13 2048 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 4096 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 32768 mmcblk0p21
179 22 131072 mmcblk0p22
179 23 2641920 mmcblk0p23
179 24 917504 mmcblk0p24
179 96 512 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 7749632 mmcblk1
179 129 7748608 mmcblk1p1
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Apr 6 09:52 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Apr 6 09:52 csc -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Apr 6 09:52 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Apr 6 09:52 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Apr 6 09:52 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 steady -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Apr 6 09:52 system-data -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 15 Apr 6 09:52 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Apr 6 09:52 user -> ../../mmcblk0p13
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 16 Apr 6 09:52 modules -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 10 Apr 6 09:52 ramdisk -> ../../ram0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk-recovery -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 tizen -> ../../mmcblk0p13
Code:
sh-3.2# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 320K 1 loop /opt/share/zoneinfo
loop1 7:1 0 13.6M 1 loop /usr/share/locale
zram0 254:0 0 279.3M 0 disk [SWAP]
mmcblk0rpmb 179:24 0 512K 0 disk
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
mmcblk0 179:0 0 3.7G 0 disk
|-mmcblk0p1 179:1 0 32M 0 part
|-mmcblk0p2 179:2 0 8M 0 part /csa
|-mmcblk0p3 179:3 0 2M 0 part
|-mmcblk0p4 179:4 0 20M 0 part
|-mmcblk0p5 179:5 0 8M 0 part
|-mmcblk0p6 179:6 0 8M 0 part
|-mmcblk0p7 179:7 0 3M 0 part
|-mmcblk0p8 259:0 0 16M 0 part
|-mmcblk0p9 259:1 0 16M 0 part
|-mmcblk0p10 259:2 0 16M 0 part /usr/lib/modules
|-mmcblk0p11 259:3 0 190M 0 part /opt/system/csc
|-mmcblk0p12 259:4 0 158M 0 part /opt
|-mmcblk0p13 259:5 0 1.9G 0 part /opt/usr
|-mmcblk0p14 259:6 0 1.3G 0 part
| `-rootfs 253:0 0 1.2G 1 crypt /
`-mmcblk0p15 259:7 0 256K 0 part
Thanx in advance.
Best Regards
Here the answer.
Thanx. :good:
SM-R500 DSL1
Code:
sh-3.2# cat /proc/partitions
major minor #blocks name
1 0 20480 ram0
1 1 20480 ram1
7 0 34240 loop0
7 1 384 loop1
254 0 284980 zram0
179 0 3817472 mmcblk0
179 1 8192 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 28160 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 2048 mmcblk0p9
259 2 6144 mmcblk0p10
259 3 3072 mmcblk0p11
259 4 18432 mmcblk0p12
259 5 18432 mmcblk0p13
259 6 10240 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 194560 mmcblk0p16
259 9 172032 mmcblk0p17
259 10 1873408 mmcblk0p18
259 11 1439744 mmcblk0p19
259 12 256 mmcblk0p20
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 16 Feb 8 11:11 afpc -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Feb 8 11:11 boot -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Feb 8 11:11 cm -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 15 Feb 8 11:11 csa -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Feb 8 11:11 csc -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 15 Feb 8 11:11 module -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 16 Feb 8 11:11 nad_fw -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 15 Feb 8 11:11 nad_refer -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Feb 8 11:11 param -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk2 -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 16 Feb 8 11:11 recovery -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Feb 8 11:11 rootfs -> ../../mmcblk0p19
lrwxrwxrwx 1 root root 15 Feb 8 11:11 smsn -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Feb 8 11:11 steady -> ../../mmcblk0p20
lrwxrwxrwx 1 root root 16 Feb 8 11:11 system-data -> ../../mmcblk0p17
lrwxrwxrwx 1 root root 15 Feb 8 11:11 tup -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Feb 8 11:11 tyd -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Feb 8 11:11 up_param -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 16 Feb 8 11:11 user -> ../../mmcblk0p18
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk-recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-csc -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-rootfs -> ../../mmcblk0p19
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-system-da -> ../../mmcblk0p17
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-user -> ../../mmcblk0p18
Code:
sh-3.2# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 33.4M 1 loop /usr/share/locale
loop1 7:1 0 384K 1 loop /opt/share/zoneinfo
mmcblk0 179:0 0 3.7G 0 disk
|-mmcblk0p1 179:1 0 8M 0 part /csa
|-mmcblk0p2 179:2 0 2M 0 part
|-mmcblk0p3 179:3 0 1M 0 part
|-mmcblk0p4 179:4 0 512K 0 part
|-mmcblk0p5 179:5 0 512K 0 part
|-mmcblk0p6 179:6 0 27.5M 0 part
|-mmcblk0p7 179:7 0 20M 0 part
|-mmcblk0p8 259:0 0 8M 0 part
|-mmcblk0p9 259:1 0 2M 0 part
|-mmcblk0p10 259:2 0 6M 0 part
|-mmcblk0p11 259:3 0 3M 0 part
|-mmcblk0p12 259:4 0 18M 0 part
|-mmcblk0p13 259:5 0 18M 0 part
|-mmcblk0p14 259:6 0 10M 0 part
|-mmcblk0p15 259:7 0 4M 0 part
|-mmcblk0p16 259:8 0 190M 0 part /opt/system/csc
|-mmcblk0p17 259:9 0 168M 0 part /opt
|-mmcblk0p18 259:10 0 1.8G 0 part /opt/usr
|-mmcblk0p19 259:11 0 1.4G 0 part /
`-mmcblk0p20 259:12 0 256K 0 part
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
mmcblk0rpmb 179:24 0 512K 0 disk
zram0 254:0 0 278.3M 0 disk [SWAP]
Code:
mmcblk0p1 CSA
mmcblk0p2 TYD
mmcblk0p3 NAD_REFER
mmcblk0p4 SMSN
mmcblk0p5 MODULE
mmcblk0p6 TUP
mmcblk0p7 RAMDISK-RECOVERY
mmcblk0p8 RAMDISK
mmcblk0p9 PARAM
mmcblk0p10 UP_PARAM
mmcblk0p11 CM
mmcblk0p12 BOOT
mmcblk0p13 RECOVERY
mmcblk0p14 NAD_FW
mmcblk0p15 AFPC
mmcblk0p16 CSC
mmcblk0p17 SYSTEM-DATA
mmcblk0p18 USR
mmcblk0p19 ROOTFS
mmcblk0p20 STEADY
mmcblk0boot0 BOOT0
mmcblk0boot1 BOOT1
mmcblk0rpmb RPMB --->protected... NOT readable
mmcblk0 Full 4 GB eMMC
Best Regards
SM-R500 DSL1 summary for dd action... dump partitions... :angel:
We have 20 partitions p1 - p20
+ 3 additional
We are writing to USR partition p18... remember limited space... ca, 1500 MB free
Code:
dd if=/dev/mmcblk0boot0 of=/opt/usr/media/bootloader0.bin
dd if=/dev/mmcblk0boot1 of=/opt/usr/media/bootloader1.bin
[COLOR="Red"][B]dd if=/dev/mmcblk0rpmb of=/opt/usr/media/rpmb.bin[/B][/COLOR]
dd if=/dev/mmcblk0p1 of=/opt/usr/media/csa.bin
dd if=/dev/mmcblk0p2 of=/opt/usr/media/tyd.bin
dd if=/dev/mmcblk0p3 of=/opt/usr/media/nad_refer.bin
dd if=/dev/mmcblk0p4 of=/opt/usr/media/smsn.bin
dd if=/dev/mmcblk0p5 of=/opt/usr/media/module.bin
dd if=/dev/mmcblk0p6 of=/opt/usr/media/tup.bin
dd if=/dev/mmcblk0p7 of=/opt/usr/media/ramdisk-recovery.bin
dd if=/dev/mmcblk0p8 of=/opt/usr/media/ramdisk.bin
dd if=/dev/mmcblk0p9 of=/opt/usr/media/param.bin
dd if=/dev/mmcblk0p10 of=/opt/usr/media/up_param.bin
dd if=/dev/mmcblk0p11 of=/opt/usr/media/cm.bin
dd if=/dev/mmcblk0p12 of=/opt/usr/media/boot.bin
dd if=/dev/mmcblk0p13 of=/opt/usr/media/recovery.bin
dd if=/dev/mmcblk0p14 of=/opt/usr/media/nad_fw.bin
dd if=/dev/mmcblk0p15 of=/opt/usr/media/afpc.bin
dd if=/dev/mmcblk0p16 of=/opt/usr/media/csc.bin
dd if=/dev/mmcblk0p17 of=/opt/usr/media/system-data.bin
[COLOR="Red"][B]dd if=/dev/mmcblk0p18 of=/opt/usr/media/usr.bin[/B][/COLOR]
[COLOR="Red"][B]dd if=/dev/mmcblk0p19 of=/opt/usr/media/rootfs.bin[/B][/COLOR]
dd if=/dev/mmcblk0p20 of=/opt/usr/media/steady.bin
Red marked Commands...
rootfs to dump is not really usefull... remember free space...
usr is written to usr partition... so never possible to dump in 1 step...
rpmb read protected,,, found no way on Wearables...
To pull all files from Media folder...
Code:
sdb pull /opt/usr/media/
Or pull file by file with filename... example:
Code:
sdb pull /opt/usr/media/[B]csa.bin[/B]
Best Regards
To dump "whole" eMMC...
Limitation we have only maximum 1,8 GB... so we have tiny problem to put whole 4 GB...
To check free space...
Example taken from my SM-R760...
Code:
sh-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 1.1G 200M 84% /
devtmpfs 340M 0 340M 0% /dev
/dev/mmcblk0p14 1.3G 1.1G 200M 84% /
/dev/mmcblk0p12 139M 85M 51M 63% /opt
/dev/mmcblk0p10 14M 253K 13M 2% /usr/lib/modules
tmpfs 352M 24K 352M 1% /dev/shm
tmpfs 352M 2.6M 349M 1% /run
tmpfs 352M 0 352M 0% /sys/fs/cgroup
tmpfs 352M 60K 352M 1% /tmp
/dev/loop0 384K 384K 0 100% /opt/share/zoneinfo
/dev/loop1 34M 34M 0 100% /usr/share/locale
/dev/mmcblk0p11 183M 101M 80M 56% /opt/system/csc
/dev/mmcblk0p2 6.8M 1.2M 5.0M 20% /csa
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr
tmpfs 71M 80K 71M 1% /run/user/5001
tmpfs 71M 0 71M 0% /run/user_ext/5001
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/media
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/apps
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/home/owner/media
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/media
sh-3.2# df -a
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1298824 1064480 204612 84% /
devtmpfs 347224 0 347224 0% /dev
none 0 0 0 - /proc
sysfs 0 0 0 - /sys
/dev/mmcblk0p14 1298824 1064480 204612 84% /
/dev/mmcblk0p12 141376 86868 51276 63% /opt
/dev/mmcblk0p10 13847 253 13287 2% /usr/lib/modules
securityfs 0 0 0 - /sys/kernel/security
smackfs 0 0 0 - /sys/fs/smackfs
tmpfs 359712 24 359688 1% /dev/shm
devpts 0 0 0 - /dev/pts
tmpfs 359712 2628 357084 1% /run
tmpfs 359712 0 359712 0% /sys/fs/cgroup
cgroup 0 0 0 - /sys/fs/cgroup/systemd
pstore 0 0 0 - /sys/fs/pstore
cgroup 0 0 0 - /sys/fs/cgroup/net_cls
cgroup 0 0 0 - /sys/fs/cgroup/cpu,cpuacct
cgroup 0 0 0 - /sys/fs/cgroup/freezer
cgroup 0 0 0 - /sys/fs/cgroup/memory
debugfs 0 0 0 - /sys/kernel/debug
tmpfs 359712 60 359652 1% /tmp
configfs 0 0 0 - /sys/kernel/config
/dev/loop0 384 384 0 100% /opt/share/zoneinfo
/dev/loop1 34176 34176 0 100% /usr/share/locale
/dev/mmcblk0p11 187373 102462 81020 56% /opt/system/csc
/dev/mmcblk0p2 6907 1218 5117 20% /csa
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr
tmpfs 71940 80 71860 1% /run/user/5001
tmpfs 71940 0 71940 0% /run/user_ext/5001
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/media
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/apps
vip_cgroup 0 0 0 - /sys/fs/cgroup/vip
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/home/owner/media
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/media
Taken from here:
https://opensource.com/article/18/7/how-check-free-disk-space-linux
First attempt:
Code:
dd if=/dev/mmcblk0 of=/opt/usr/media/full4GB_eMMC.bin
dd stopps if usr partition is full...
Could lead to sideeffect...
But could be enough to pull result...
Code:
sh-3.2# dd if=/dev/mmcblk0 of=/opt/usr/media/full4GB_eMMC.bin
dd: writing to `/opt/usr/media/full4GB_eMMC.bin': [COLOR="Red"][B]No space left on device[/B][/COLOR]
3596569+0 records in
3596568+0 records out
1841442816 bytes (1.8 GB) copied, 151.265 s, 12.2 MB/s
Code:
sh-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 1.1G 200M 84% /
devtmpfs 340M 0 340M 0% /dev
/dev/mmcblk0p14 1.3G 1.1G 200M 84% /
/dev/mmcblk0p12 139M 83M 53M 61% /opt
/dev/mmcblk0p10 14M 253K 13M 2% /usr/lib/modules
tmpfs 352M 24K 352M 1% /dev/shm
tmpfs 352M 2.5M 349M 1% /run
tmpfs 352M 0 352M 0% /sys/fs/cgroup
tmpfs 352M 60K 352M 1% /tmp
/dev/loop0 384K 384K 0 100% /opt/share/zoneinfo
/dev/loop1 34M 34M 0 100% /usr/share/locale
/dev/mmcblk0p11 183M 101M 80M 56% /opt/system/csc
/dev/mmcblk0p2 6.8M 1.2M 5.0M 20% /csa
[COLOR="Red"][B]/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr[/B][/COLOR]
tmpfs 71M 80K 71M 1% /run/user/5001
tmpfs 71M 0 71M 0% /run/user_ext/5001
[COLOR="Red"][B]/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/media
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/apps
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/home/owner/media
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/media[/B][/COLOR]
Code:
sdb pull /opt/usr/media/full4GB_eMMC.bin
pulled full4GB_eMMC.bin 100% 1756MB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/media/full4GB_eMMC.bin 552 KB/s (1841442816 bytes in 3255.896s)
Pull seems 1 hour...
Best Regards
Code:
sh-3.2# dd if=/dev/mmcblk0 | gzip > /opt/usr/media/full4GB_eMMC.bin.gz
gzip: stdout: No space left on device
Creates corrupt/unfinished archive file... but have 2200 MB inside... few more as uncompressed...
Better we split... and find other way for user partition...
.
.
.
Best Regards
Maybe found something...
Code:
sdb shell dd if=/dev/mmcblk0boot1>testme11.bin
sdb shell dd if=/dev/mmcblk0boot0>testme11more.bin
sdb shell dd if=/dev/mmcblk0rpmb>testme11moreAA.bin
Now need more time for next attempt...
Code:
sdb shell dd if=/dev/mmcblk0>FULLeMMCoverSDB_WiFi.bin
4 GB !
IMHO 1 - 2 hours...
Best Regards
Rooted SM-R500 DSL1 Firmware is here:
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
If Questions... better ask BEFORE...
Best Regards
Hmmm... I don't know why...
But if I direct dump to PC... then additional crap is written...
2 Bytes...
Code:
0D0D
I have Tizen handset... SM-Z130H... with Tizen 2.4...
Here this work as it seems, tested with Command:
Code:
sdb shell dd if=/dev/mmcblk0boot1>Z1_boot1.bin
This partition is ever empty... contains only 00... so IMHO good reference...
But my Z1 is connected via USB cable...
No idea if 0D0D cames because some TCP problem...
Best Regards
With SM-R760 we have luck...
Combination Firmware not mandatory for Tizen 4 Root...
Only RAMDISK taken from Combination Firmware...
Maybe this is also working for SM-R500... need to be tested.
Attached is ramdisk.img from FT40 ASL2 for SM-R500...
Best Regards
I0T said:
Hey guys!
I'm searching around and I couldn't find a way to root SM-R500 Samsung Galaxy Watch Active (Tizen 4.0.0.3). I found a lot of firmware on different websites, but I couldn't find a rooted one. Any suggestions ...
Thanks
Click to expand...
Click to collapse
Hey there! Could you finally root the SM-R500? Is it still alive? Have the same model here... I used to root all Samsung I had but this is my very first watch so I do not want to mess it yet without anyone proofs
Your Firmware Version?
I have only rooted DSL1 for SM-R500...
Best Regards
adfree said:
Your Firmware Version?
I have only rooted DSL1 for SM-R500...
Best Regards
Click to expand...
Click to collapse
Hi adfree, It seems DSL1, lastest Samsung update.. I have read about combination firmwares etc.. but not tired anything without being sure cause is the most expensive watch i ever bought..
The most combinations firms seems for others than R500, I don't know either about knox on watch if will be tripped too and will left samsung pay useless or it works different than phones..
Yesterday I downloaded all tizen SDK tools etc... and sideloaded tpk apps to watch, they install but could not run them propperly.. but I guess all this is about to test yet as it is a "new watch" ...sorry my ignorance but I come from a LG watch from 2015 omg I had to update myself... xD
Thank you and have a nice day !
@Albayeah
Sorry.
In main I am talking with my self... about Rooting...
No idea why user not confirm in public...
I know he used the old method with Combination Firmware first... then my rooted rootfs,img...
The new way... is to flash only RAMDISK from Combination Firmware, then my rooted files.
So Round 1:
with netOdin
https://forum.xda-developers.com/showpost.php?p=81799723&postcount=15
Round 2.
with netOdin
IGNORE the Combination Firmware files
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
Only this:
https://www.file-upload.net/download-13891175/2020_DSL1_smR500_ROOT_v1.7z.html
Own Risk!
But I am 99,9 % sure this is working. :angel:
Best Regards
adfree said:
@Albayeah
Sorry.
In main I am talking with my self... about Rooting...
No idea why user not confirm in public...
I know he used the old method with Combination Firmware first... then my rooted rootfs,img...
The new way... is to flash only RAMDISK from Combination Firmware, then my rooted files.
So Round 1:
with netOdin
https://forum.xda-developers.com/showpost.php?p=81799723&postcount=15
Round 2.
with netOdin
IGNORE the Combination Firmware files
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
Only this:
https://www.file-upload.net/download-13891175/2020_DSL1_smR500_ROOT_v1.7z.html
Own Risk!
But I am 99,9 % sure this is working. :angel:
Best Regards
Click to expand...
Click to collapse
Many thanks! I am going to save your files by the moment because I am still afraid of messing something definetly on the watch with no reverse..
Maybe I have to do more research..
I hope I dont bother you with my questions but if you already rooted.. could you use samsung apps as usual..? Like samsung health, samsung pay.. won't prompt a security message or disable any functions, any apps..?
Sorry cause i am kinda confused with that details..
On phone I use Samsung apps hiding with magisk etc... cause it is rooted but it is Android, but what about watch with tizen and no magisk..? Will disable the apps just like in the phone, or is it knox unrecoverable? :silly:
Sorry for my inexperience maybe all this sounded silly to you XDD
Best wishes to all on these hard times :good: