Develop Bugs

[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. [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#

S4 I9500 partitions and CPU info

[email protected]:/dev/block/platform/dw_mmc.0/by-name $ ls -la
ls -la
lrwxrwxrwx root root 2013-03-26 16:07 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-03-26 16:07 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-03-26 16:07 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-03-26 16:07 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-03-26 16:07 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-03-26 16:07 CDMA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-03-26 16:07 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-03-26 16:07 HIDDEN -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-03-26 16:07 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-03-26 16:07 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-03-26 16:07 PERSDATA -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-03-26 16:07 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-03-26 16:07 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-03-26 16:07 RESERVED2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-03-26 16:07 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-03-26 16:07 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-03-26 16:07 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-03-26 16:07 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-03-26 16:07 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-03-26 16:07 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-03-26 16:07 m9kefs3 -> /dev/block/mmcblk0p6
[email protected]:/ $ cat /proc/cpuinfo
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 3 (v7l)
processor : 0
BogoMIPS : 1590.88
processor : 1
BogoMIPS : 1590.88
processor : 2
BogoMIPS : 1590.88
processor : 3
BogoMIPS : 1590.88
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva id
ivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc0f
CPU revision : 3
Hardware : UNIVERSAL5410
Revision : 0009
Serial : xxxxxxxxxxx4d00ee10
Build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=JDQ39.I9500XXUAMC6
ro.build.version.incremental=I9500XXUAMC6
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Mon Mar 11 22:42:39 KST 2013
ro.build.date.utc=1363009359
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-127
ro.build.tags=release-keys
ro.product.model=GT-I9500
ro.product.brand=samsung
ro.product.name=ja3gxx
ro.product.device=ja3g
ro.product.board=universal5410
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos5
# ro.build.product is obsolete; use ro.product.device
ro.build.product=ja3g
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=ja3gxx-user 4.2.2 JDQ39 I9500XXUAMC6 release-keys
ro.build.fingerprint=samsung/ja3gxx/ja3g:4.2.2/JDQ39/I9500XXUAMC6:user/release-keys
ro.build.characteristics=lightTheme
# Samsung Specific Properties
ro.build.PDA=I9500XXUAMC6
ro.build.hidden_ver=I9500XXUAMC6
ro.build.changelist=265143
ro.product_ship=true
ro.chipname=exynos5410
# end build properties

This is the 16gb model if I am correct? Interesting it's ext4.
Sent from my HTC One S using xda app-developers app

Closed Source Project said:
This is the 16gb model if I am correct? Interesting it's ext4.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Why is that interesting?

Toss3 said:
Why is that interesting?
Click to expand...
Click to collapse
+1 :angel:

Samsung has been on EXT4 after the S1. Google forced them over. Its not surprising.

I want to ask you, to do into terminal
Code:
su
cd dev/block/platform/dw_mmc/by-name
ls -l
and upload result..
after this, if you can, make dump partitions: boot, recovery, system, cache, hidden, modem, param
Code:
su
dd if=dev/block/mmcblk0p[partition number] of=sdcard/[image file]
Then I will try make ROM for flash via odin

my S4 not have root！ Can you ROOT my S4?

zhangqip said:
my S4 not have root! Can you ROOT my S4?
Click to expand...
Click to collapse
But for this i need any stock rom or system dump from cwm
p.s.
try load phone into recovery mode, connect to kies and choose restore device, kies must download 3th files service ROM, on PC

zhangqip said:
my S4 not have root！ Can you ROOT my S4?
Click to expand...
Click to collapse
If you want it to root plant it in the ground and water it...
Sent from my HTC One S using xda app-developers app

Here are more details extracted from Screener device, credits goes to him.
Partition sizes:
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 90112 mmcblk0p13
259 6 262144 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 573440 mmcblk0p16
259 9 12288 mmcblk0p17
259 10 4096 mmcblk0p18
259 11 2121728 mmcblk0p19
259 12 2830336 mmcblk0p20
259 13 9379840 mmcblk0p21
and Mount points:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0

[/COLOR]wanam you're a genius, finally, today I will make system.img... with root for Odin
well done
http://forum.xda-developers.com/showthread.php?t=2213775

Closed Source Project said:
If you want it to root plant it in the ground and water it...
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Hahahahaha rooting made simple lol
Sent from my GT-I9500 using xda app-developers app

wanam said:
Here are more details extracted from Screener device, credits goes to him.
Partition sizes:
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 90112 mmcblk0p13
259 6 262144 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 573440 mmcblk0p16
259 9 12288 mmcblk0p17
259 10 4096 mmcblk0p18
259 11 2121728 mmcblk0p19
259 12 2830336 mmcblk0p20
259 13 9379840 mmcblk0p21
and Mount points:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
Click to expand...
Click to collapse
with this in future can have more space in internal card??

e
GT-I9500 cihazımdan Tapatalk kullanılarak gönderildi

Deleted because I found what I was looking for :thumbup:
Sent from my GT-I9500

[Q] Widget/script for properly mounting/unmounting external sd card

Hey, I'm trying to create two shortcuts on my home launcher to unmount the sdcard and the other one to mount it for safe eject purposes. I have a galaxy s3 sgh-i747 at&t running AOKP 4.4.4 rooted/busyboxed. I am trying to create two scripts that i can simply run with a click of the SManager widget instead of having to go through all the settings and unmounting it from there.
Partitions:
Code:
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 32 7761920 mmcblk1
179 33 7757824 mmcblk1p1
Mounts:
Code:
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,fmask=0177,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:33 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
The sdcard is mount # 33 located at block mmcblk1p1
The location of the mount is /storage/sdcard1 or /mnt/media_rw/sdcard1 (looks like the one in /storage is just a link to the real one in /mnt)
I am aware of the commands mount/umount.
Please help me out. Thanks!

[REF] partition layout

Output from cat /proc/partitions, names shown in red do not appear, they have been taken from different files in the system, they could be wrong!
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
31 0 1024 mtdblock0
179 0 3866624 mmcblk0
179 1 128 mmcblk0p1
179 2 512 mmcblk0p2 [COLOR="Red"] mbm[/COLOR]
179 3 512 mmcblk0p3
179 4 1 mmcblk0p4 [COLOR="Red"] ebr[/COLOR]
179 5 512 mmcblk0p5 [COLOR="Red"] cdt[/COLOR]
179 6 4096 mmcblk0p6 [COLOR="Red"] pds[/COLOR]
179 7 1536 mmcblk0p7
179 8 1024 mmcblk0p8 [COLOR="Red"] logo.bin[/COLOR]
179 9 16384 mmcblk0p9[COLOR="Red"] boot[/COLOR]
179 10 16384 mmcblk0p10[COLOR="Red"] recovery[/COLOR]
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 262144 mmcblk0p14 [COLOR="Red"] system[/COLOR]
179 15 262144 mmcblk0p15 [COLOR="Red"] cache[/COLOR]
179 16 131072 mmcblk0p16 [COLOR="Red"] customize[/COLOR]
179 17 3160064 mmcblk0p17 [COLOR="Red"] data[/COLOR]
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
To encourage more research and developments, use the donate button on the right! thanks!

in case needed, heres output for mount
Code:
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
/dev/block/mmcblk0p14 /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,data=ordered 0 0
/dev/block/mmcblk0p17 /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p6 /pds ext4 rw,seclabel,nosuid,nodev,noatime,discard 0 0
/dev/block/mmcblk0p16 /customize ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime,mode=755 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

Rooting Samsung Galaxy Watch Active

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: