yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S2] adfree:
<ID:0/001> 192.168.49.1
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/001> Odin engine v(ID:1.0000)..
<ID:0/001> File analysis..
<ID:0/001> SetupConnection..
<ID:0/001> Initialzation..
<ID:0/001> Set PIT file..
<ID:0/001> DO NOT TURN OFF TARGET!!
<ID:0/001> Get PIT for mapping..
<ID:0/001> Get PIT Transmission
<ID:0/001> Firmware update start..
<ID:0/001> SingleDownload.
<ID:0/001> param.bin
<ID:0/001> NAND Write Start!!
<ID:0/001> modules.img
<ID:0/001> zImage
<ID:0/001> sboot.bin
<ID:0/001> zImage-recovery
<ID:0/001> rootfs.img
<ID:0/001> system-data.img
<ID:0/001> ramdisk.img
<ID:0/001> ramdisk-recovery.img
<ID:0/001> user.img
<ID:0/001> csc.img
<ID:0/001> RQT_CLOSE !!
<ID:0/001> RES OK !!
<ID:0/001> Remain Port .... 0
<ID:0/001> Removed!!
<OSM> All threads completed. (succeed 1 / failed 0)

My Logfile from Odin... and attached Screenshot of Record time... :rolleyes: :eek:

------------

Next problem... :rolleyes:

I have only old outdated Android handsetS... like GT-I9300 with oldest Firmware... :rolleyes: :rolleyes:

First attempt with SM-Z130H and Gear Manager BETA fails...

As this useless S... not work with R732XXU2AOJ3... :rolleyes:

I can not finish "first init" setup... nor I can enter Download Mode menu to check if Bootloader is downgraded or not... :rolleyes:

Again 3 hours for Flashing other Firmware... :rolleyes: :rolleyes: :rolleyes:

So I need some time to flash/update my GT-I9300... or find other working solution for Gear Manager...

WHY the h. Samsung have no PC Tool like Kies/ Smart Switch or any other to interact with this f. Watch...

Ti... s u c k s

Nothing is normal working... :silly: :eek:

But the good news... for me.

My cheap Gear S2 is alive. :cool:

Best Regards
[Samsung Gear S2] adfree:
No idea how or why... :confused:

But after many attempts with Gear Manager Beta and my SM-Z130H I was able to bypass first Init setup...

:cyclops: :highfive: :victory:

Also it looks like sboot is downgraded... maybe also by luck... :D

Next step is to connect with SDB... to log something and to check really sboot version...

Command is this:

cat /proc/cmdline

But I will go better now sleep little bit... before my little brain explode... for today. :D

No idea how many years I need to connect with SDB... :D :o :rolleyes:

Best Regards

Edit 1.

Fastest part to configure WiFi for SDB... result of Bootloader check:

bootloader.ver=R732XXU2AOJ3
bootloader.fb=0x48000000
bootloader.log=0x10bc@0x46000000
bootloader.elapsed=2110

Nice, so I have flashed sboot.bin... :good:

So next attempt is to root R732XXU2AOJ3...

But first I have to think about it... maybe I make new TAR without sboot.bin and cm.bin ...

:confused:

Also I have to improve my WiFi Odin Hardware constellation... to flash in less time... not again 3 hours...

Edit 2.

sh-3.2$ screenshot --help
mkdir: cannot create directory `/opt/usr/media': Permission denied
chown: cannot access `/opt/usr/media/Screenshots': Permission denied
chmod: cannot access `/opt/usr/media/Screenshots': Permission denied
/opt/usr/media/Screenshots: Permission denied
Screenshot Error: fail to createScreenShot!
/usr/bin/screenshot: line 27: mediadb-update: command not found
/opt/usr/media/Screenshots/Screen-20170427105951.bmp: Permission denied
"/opt/usr/media/Screenshots/Screen-20170427105951.bmp" saved
screenshot success

Screenshot function require also root... :rolleyes:

So I need to learn this swipe thing...

Edit 3.

sh-3.2$ cat /proc/partitions
major minor #blocks name

7 0 39308 loop0
254 0 98016 zram0
179 0 3817472 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 16384 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 276480 mmcblk0p10
259 3 131072 mmcblk0p11
259 4 2209792 mmcblk0p12
259 5 1081344 mmcblk0p13
259 6 256 mmcblk0p14
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0

Edit 4.

My fault... I have started the shell script... not the Binary... :o

sh-3.2$ screenshot-arm --help
Usage: screenshot-arm -w <width> -h <height> -f <filepath>

Later I will try with correct w and h... and valid accessable path...
[Samsung Gear S2] adfree:
sh-3.2$ screenshot-arm -w 360 -h 360 -f /opt/usr/media/Screenshots
[UTILX] fail : initialize screenshot.
Screenshot Error: fail to createScreenShot!

Hmmm, attempt 1...

attempt 2...

sh-3.2$ screenshot-arm -w 360 -h 360 -f /opt/usr/media/Images
[UTILX] fail : initialize screenshot.
Screenshot Error: fail to createScreenShot!

:rolleyes:

attempt 3...

sh-3.2$ screenshot-arm -w 360 -h 360 -f /home/developer
[UTILX] fail : initialize screenshot.
Screenshot Error: fail to createScreenShot!

attempt 4...

sh-3.2$ screenshot-arm -w 360 -h 360 -f /tmp
[UTILX] fail : initialize screenshot.
Screenshot Error: fail to createScreenShot!

:rolleyes:

Okidoki... no fun without ROOT... in "User Mode" only pain to play with...

So "next goal" is ROOT R732XXU2AOJ3...

Theory is clear... :angel:

Take su Binary from Combination file... put into rootfs.img:

/bin/su

Create valid TAR for action with Odin...

Now only little question... what is valid... :o

For SM-Z130H, SM-Z300H, SM-Z300F and SM-Z200F ---> all Mobiles... worked only to put modified rootfs.img into TAR and flash with Odin...

"My" first attempt with SM-R760 ends in Bootloop/Cycle and repair in Service Center... :o

I hope this time with SM-R732 and Firmware R732XXU2AOJ3 more luck, maybe not so strong "protected"... :cyclops:

Best Regards

---------- Post added at 05:42 PM ---------- Previous post was at 05:00 PM ----------

Usefull PDF document about connect Gear Sx with Tool SDB over WiFi:

http://developer.samsung.com/technical-doc/view.do?v=T000000251

For me my beloved SDB Version 2.2.60 work with R732XXU2AOJ3

sdb version
Smart Development Bridge version 2.2.60

I am using this Version since months/years with my SM-Z130H... :cool: :good:

In newer versions it is not possible easy to Copy & Paste text...

Btw... new Version...

Only reason is this undocumented Command:

sdb capability

Result later...

Best Regards
[Samsung Gear S2] adfree:
For my tiny little brain...

BL_R732XXU2AOJ3_usr.tar.md5

sboot.bin

AP_R732XXU2AOJ3_usr.tar.md5

rootfs.img

CSC_R732OXX2AOJ3_usr.tar.md5

csc.img

Later more... need new haircut... :D

Best Regards
[Samsung Gear S2] adfree:
I am lazy...

And I want to see Combination Firmware on Gear... :D :cyclops: :cowboy:

So I will try:

COMBINATION-FTMA_R732XXXU2AOI8.tar.md5

More as it will explode... :D :D :D

Maybe I need again 3 hours for Flashing...

Best Regards

Edit 1.

Oh, this time faster as my first attempt... :good:

Oh2...

Not realized before...

But Bootloader from AP_R732XXU2AOJ3 shows also Upload and Upload (wifi) in menu...

Edit 2.

Uh Oh.. Game over after 8 minutes... :D :rolleyes: :o

But now I understand what happens...

I mean in F%& red lettern we can see the reason:

Custom binary blocked

by Reactivation Lock

In Download Mode menu nearly all menus are blocked... only these without wifi:

Upload
Download (usb)

Interesting... in Download menu I can see...

K: Custom
P: Official

So if K is Kernel... then P means maybe Platform...

Okidoki... next step is to open SM-R732 and to make my little USB cable... :D :rolleyes: :o

Edit 3.

Maybe something like this:

https://xdaforums.com/showpost.php?p=70449052&postcount=15

https://xdaforums.com/showpost.php?p=70451487&postcount=19

Edit 4.

Added Log and Screenshot... How I killed my Wearable... :o :crying:

<ID:0/001> 192.168.49.1
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/001> Odin engine v(ID:1.0000)..
<ID:0/001> File analysis..
<ID:0/001> SetupConnection..
<ID:0/001> Initialzation..
<ID:0/001> Set PIT file..
<ID:0/001> DO NOT TURN OFF TARGET!!
<ID:0/001> Get PIT for mapping..
<ID:0/001> Get PIT Transmission
<ID:0/001> Firmware update start..
<ID:0/001> SingleDownload.
<ID:0/001> sboot.bin
<ID:0/001> NAND Write Start!!
<ID:0/001> param.bin
<ID:0/001> zImage
<ID:0/001> zImage-recovery
<ID:0/001> modules.img
<ID:0/001> rootfs.img
<ID:0/001> system-data.img
<ID:0/001> user.img
<ID:0/001> ramdisk-recovery.img
<ID:0/001> csc.img
<ID:0/001> ramdisk.img
<ID:0/001> RQT_CLOSE !!
<ID:0/001> RES OK !!
<ID:0/001> Remain Port .... 0
<ID:0/001> Removed!!
<OSM> All threads completed. (succeed 1 / failed 0)
[Samsung Gear S2] adfree:
Puh... Searching since hour... if I have an Y Screwdriver at home... or I have to buy one to open SM-R732...

I need 4 Screws to remove...

I found my old Torx and many other old Tools... :D

Many tiny Screw Drivers... BUT...

Best Regards

Edit 1.

Damn... I have no Triwing Screwdriver at home...

So I have to buy 1... :rolleyes:

I hope not more as 10 - 15 Euro... maybe for Screwdriver set...
[Samsung Gear S2] tids2k:
I see you are making great progress there. All the best.
[Samsung Gear S2] Antish12:
Though I understand only about 20% of what you all saying, I want to say thanks for putting so much time in this. If it happens really, it's going to be a major breakthrough.
[Samsung Gear S2] adfree:
Tried few Shops in Germany... to find Triwing Screwdriver in tiny size...

No luck.

I am trying today at Conrad...

https://www.conrad.de/de/elektronik...g-pentalobe-627426.html?sc.ref=Search Results

Maybe something like this... for 12 Euro...

Maybe if I solder wires or not... I need fixture...

To prevent loosing connection... :D

First problem I have solved by Youtube Videos... how to remove bands... :D

This video is nice...

https://www.youtube.com/watch?v=ySpoJzu1vlE

Idea 1... is using Band.... maybe I have something to replace...

Or I can find PINs like in Video...

Later more...

Best Regards

Edit 1.

After I saw this Picture...

https://postimg.org/image/7hob7hidr/

Maybe I have an idea...

Maybe I can use Screws... to fix something between this "2 points"...

Pinout with Screws are on an "line/row"...

Maybe then solderless possible connect wires...

Edit 2.

painted "idea" added... :D

I hope imagination is big enough...
[Samsung Gear S2] adfree:
I have some time, before Conrad will open...

So I am seaching little bit around...

Usefull Videos:

How to open after water damage...

https://www.youtube.com/watch?v=DNeE_vks8kY

:D

https://www.youtube.com/watch?v=2bVpAItyzWE

This seems cool... so if I can repair... then next first Init will be maybe easier...
[Samsung Gear S2] tids2k:
https://youtu.be/c0OF_Ux9XVE maybe this will help you.
[Samsung Gear S2] adfree:
Little progress...

Thanx to Conrad... perfect Tool set with Triwing Screwdriver (Y)... for 10 Euro. :good:

Removed 4 Screws...

Then need some time to remove rear...

First attempt with my finger nails... :o

No chance...

Second attempt... "carefully"... you need little bit power... as rear plate is "glued"...

I have "Open Tool"... visible in Photos

In theory Test Points are big enough... to solder wires... with touching other SMD parts...

:cool: :good:

Thanx Samsung for this PCB design. :good:

Now I need little bit time...

I want not solder in first attempt...

I have enough screws... and also 1 old Polar "Watch"...

To play around and find maybe stable incredients...

I hope before I will start to "press the Button".... somebody can confirm Pinout and also driver problem is clear... before I will start.

Best Regards
[Samsung Gear S2] adfree:
Few hours later... and after I "cut" my Finger with Knife... :rolleyes:

No panic, all 10 fingers on my 2 hands... :D

But I remember now, why I am soldering wires... because all these stuff so little tiny small...

With my 2 left hands and limited skills I can never create JIG with 4 Pins... without destroying me, my Gear S2...

I have Pins with 1 mm...

Pinout for 4 Pins are maximum 5 mm...

So risk to short circuit...

Solder wires is much easier... in theory. :D :o

Best Regards

Edit 1.

No idea how easy it is with such part... if it really fits...

https://xdaforums.com/showpost.php?p=71190103&postcount=26
[Samsung Gear S2] adfree:
I have soldered wires...

Boah, I need more practice or I am really old and blind... anyway.

Windows can not find Driver...

Something like here:

https://xdaforums.com/galaxy-gear/help/dead-gear-t2836697/page2

Will attach Picture from my construction...

Best Regards

Edit 1.

RX and TX switched... Odin worked... Gear S2 alive. :victory:

Photo added
[Samsung Gear S2] adfree:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> param.bin
<ID:0/003> modules.img
<ID:0/003> zImage
<ID:0/003> sboot.bin
<ID:0/003> zImage-recovery
<ID:0/003> rootfs.img
<ID:0/003> system-data.img
<ID:0/003> ramdisk.img
<ID:0/003> ramdisk-recovery.img
<ID:0/003> user.img
<ID:0/003> csc.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/008> Added!!

My SM-R732 is alive again...

The good old trick... check RX and TX... and if Picture is from UART Prolific team... switch... :rolleyes:

Now I can go to my bed...

Best Regards
[Samsung Gear S2] adfree:
Without Combination Firmware I stuck... :o

Meanwhile infos about Upload Modes...

Upload USB working... :good:

Screenshots and Ramdump RDX are here:

https://xdaforums.com/showpost.php?p=72110199&postcount=45

param.bin file from Firmware can control visible menu...

I have enabled Upload and Upload wifi via param.bin from Combination package...

Best Regards
[Samsung Gear S2] adfree:
:cyclops:

100000000 x thanx for helping me with Combination file. :cool:

Result for today.

COMBINATION-FTMA_R732XXU2AOJ2.tar.md5

Successfully flashed and work.

I have no ROOT. :cool: :angel:

Look at Screenshots... Combination Firmware shows only stuff for Testing and other "Factory" stuff...

Screebshots now easy with Command:

screenshot

:D

I have dumped few MB with dd...

sh-3.2# dd if=/dev/mmcblk0boot0 of=/opt/usr/media/Others/boot0.bin
8192+0 records in
8192+0 records out
4194304 bytes (4.2 MB) copied, 0.238197 s, 17.6 MB/s
sh-3.2# dd if=/dev/mmcblk0boot1 of=/opt/usr/media/Others/boot1.bin
8192+0 records in
8192+0 records out
4194304 bytes (4.2 MB) copied, 0.211381 s, 19.8 MB/s
sh-3.2# dd if=/dev/mmcblk0 bs=512 count=1000000 of=/opt/usr/media/Others/d1.bin
1000000+0 records in
1000000+0 records out
512000000 bytes (512 MB) copied, 113.603 s, 4.5 MB/s

Partition:

sh-3.2# cat /proc/partitions
major minor #blocks name

7 0 26908 loop0
254 0 97968 zram0
179 0 3817472 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 16384 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 276480 mmcblk0p10
259 3 131072 mmcblk0p11
259 4 2209792 mmcblk0p12
259 5 1081344 mmcblk0p13
259 6 256 mmcblk0p14
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0

Now need some... how I will process... to get root access also in normal Firmware...

Best Regards
[Samsung Gear S2] Stjin:
Holy cow, progress is actually being made? Good Job on everyone working on this project.

I thought this was a dead project
[Samsung Gear S2] tids2k:
with the last part, anything you flash will not boot and will go in bootloops. missing bootloader entry and signature check, you are right about the SBBK. userdata can be written to the sboot but it also needs to be checked by trust zone that is the TEE OS you mentioned above in the partitions and the files and subdirectories. the file under ./tee could be auth token that it used to verify the image being written. more later on. im going to start building twrp for gear s3. my jig has been shipped and i will have it in 2-3 days.
[Samsung Gear S2] adfree:
First success for today.

Rooted Firmware R732XXU2AOJ3.

Successfully accomplished. :victory:

So I was able to leave Combination Firmware... now I can proceed with "Custom" Firmware...

"Short summary"...

STILL under construction and ONLY with soldered Wires tested... NO idea if with WiFi possible.

Step 1.

[COLOR="Red"][B]COMBINATION[/B][/COLOR]-FTMA_R732XXU2[B]AOJ2[/B].tar.md5

Combination Firmware have ROOT access "preinstalled".

Step 2.

sh-3.2[B][COLOR="Red"]#[/COLOR][/B] dd if=/opt/usr/media/Others/rootfs.img of=/dev/mmcblk0p13
1863288+1 records in
1863288+1 records out
954003712 bytes (954 MB) copied, 408.361 s, 2.3 MB/s

dd my modified rootfs.img

rootfs.img is taken from Firmware R732XXU2AOJ3...

Only "magic" at the moment:

/bin/su

Added su to bin folder... NOTHING else

su is taken from Combination Firmware...

Step 3.

Create with files from 3 part Firmware R732XXU2AOJ3 an SINGLE TAR with only these files:

csc.img
modules.img
ramdisk-recovery.img
ramdisk.img
system-data.img
user.img
zImage
zImage-recovery

If somebody want try...

PM me, I could upload my result... for SM-R732

WARNING!!!

Maybe it depend on Bootloader Version...

Maybe newer Bootloader can detect this...

For instance...

My Recover seems not to start... or I did something wrong...

Also, NO idea if I have luck, with soldered wires... and USB cable...

Maybe way with WiFi only much harder...

Only as info.

Best Regards
[Samsung Gear S2] adfree:
If somebody need... for study.

Source Code(S) for SM-R732 and SM-R720

https://xdaforums.com/showpost.php?p=72124639&postcount=121

Gear & MP3 Player	SM-R720
SM-R732	R720XXU2BOKK,
R732XXU2BOKK	SM-R720_Opensource.zip
Mobile Phone	SM-R720
SM-R732	R720XXU2AOIA,
R732XXU2AOIA	SM-R720_Opensource.zip
Mobile Phone	SM-R720
SM-R732	R720XXU2AOJ3,
R732XXU2AOJ3	SM-R720_Opensource.zip

Best Regards
[Samsung Gear S2] tids2k:
thats very good news. but has it tripped the knox counter when you enter download mode ?
[Samsung Gear S2] adfree:
If you mean W/V Counter? Warranty Void is 1...

But this happens by "accident" with the wrong Combination from SM-R732X

Meanwhile I can remember more about my little exercises with Knox and GT-I9300 and GT-I9305...

Seems similar to work... :D

I would really laugh, if also the old Linux Command work to Reset/Erase Knox... :angel:

Best Regards
[Samsung Gear S2] adfree:
My edited fingerprint seems to work...

I can install apps... also modifed and self signed apps. :D

For fully use of my SM-R732... I will for now desolder the 4 wires...

So I can better move and interact and try few things...

Next plans...

- Play with every apps I can find... :D

- check testmode Codes...

- playing with Shell Scripts...

Later... if I have more time... study of Source Codes:

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-R732

Inside Kernel Sources and few RPM from "repos"...

Compiling Kernel could be not impossible for me... I was able to do this with SM-Z130H and SM-Z300H Kernel...

Only problem... I am not sure if Kernel is also protected against Flashing?

:confused:

Screenshot script work... very helpfull...

Maybe I can find solution for Video capture of Screen...

Best Regards
[Samsung Gear S2] adfree:
:o :crying:

Stupid me damaged WiFi / BT Antenna... :rolleyes:

Little bit luck, it is not complete dead, but range is much much lower...

No idea when exact it happens...

During my first soldering...

or

During my second soldering as 1 Wire ripped off...

or

During my desoldering...

My Solder skills are very bad... :eek:

Please, I need all aparts of SM-R732 (or SM-R720)... found only 1 part.

[B]SM-R732-TSHOO-7.pdf[/B]
SM-R732-PSPEC-2.pdf
SM-R732-EVAPL-3.pdf
SM-R732-EPLIS-11.pdf
SM-R732-Direy-6.pdf
SM-R732-COVER-1.pdf

Strange...

I am pretty sure I have started with 2 litte tiny SMD "pieces"... and lost only 1

But in SM-R732-TSHOO-7.pdf I can read:

Resolder or replace L105, C108, C111

According to this info, my SM-R732:

L105 seems still in position... but I have hit it... :D :o :rolleyes:

C108 is Missing in action.. :rolleyes: :rolleyes:

C111 I never had... it is free/empty

Pictures from FCC and so on are very bad... to see if 3 SMD parts soldered or only 2...

Strange, on this Pic I can see only L105...

https://postimg.org/image/7hob7hidr/

:confused:

On the attached Picture... L015 AND C108 is visible... look at white line...

Maybe if I know what it is...

Maybe I can find replacement for it...

And maybe I can solder it, without killing the whole Gear S2... :D :o

Best Regards

Edit 1.

Seems I found all files from Service Manual :victory:

http://www.mediafire.com/file/vdo0v8t0n4h8gf3/Samsung_SM-R732_Schematic.rar

Thank you very much for sharing d-artigo. :good:
[Samsung Gear S2] adfree:
sh-3.2# testmode *#1234#
[libtbm:4904] bufmgr init: fd=18
[libtbm:4904] duplicate the drm_fd(18), bufmgr use fd(19).
[libtbm:4904] TBM module exynos4412: vendor="Samsung" ABI=1,1
[libtbm:4904] cache_crtl:TBM lock_crtl:TBM
[libtbm:4904] Success to load module(libtbm_default.so)
[libtbm:4904] create tizen bufmgr: ref_count:1
ERR<4904>:ecore_evas ecore_evas_extn.c:2202 ecore_evas_extn_plug_connect() Extn plug failed to connect:ipctype=0, svcname=elm_indicator_portrait, svcnum=0, svcsys=0

We all know the Code *#1234# I hope...

With ROOT you can fire up also the hidden/blocked Codes... with simple Command testmode as "prefix"...

Interesting Codes we can find in Binary testmode...

Need some time to find something more "amazing"... :D

Later more...

Best Regards

Edit 1.

Added few Screenshots... few more inside ZIP...

testmode Binary added from SM-R732 AOJ3 Firmware...

Here you can find few codes... is from:

/usr/bin/testmode
[Samsung Gear S2] tids2k:
put some solder on the chip that you hit. if u need indivisual chip ill see if i can get.
[Samsung Gear S2] adfree:
Chip is ripped off... lost... no idea when or where...

I hope with help of SM-R732 Schematics... and especially this part list:

SM-R732-EPLIS-11.pdf

Maybe I have spare part or can "desolder" from other PCB...

From GT-I9300 and few other old Mobiles I have enough SMD parts...

I have only no idea what I have killed... resistor or something more "magically"...

In SM-R770 I can find:

Then I look into part list...

2703-004038
C635
INDUCTOR-SMD
--------------
2203-005736
C637
C-CER,CHIP
------------
2203-005736
C638
C-CER,CHIP
------------
2904-002323
F600
FILTER-SAW
------------
1001-002026
U601
IC-RF SWITCH

And then with Google for instance... more infos to find...

But I need SM-R732-EPLIS-11.pdf or from SM-R720 please. :angel:

My SM-R732 is alive and WiFi is working... BT not tested...

I only play at the moment with SDB connections...

But the range between my Access Point and SM-R732 is very very short... :o :( :crying:

1 or 2 meters... :D :rolleyes: :( :crying: :eek:

Best Regards
[Samsung Gear S2] adfree:
Playing with Port Scan...

Open "WiFi" Ports on my SM-R732:

Port 21 FTP;transfer

Port 53 DNS

Port 8080 HTTP;Alternativer HTTP-Port, oft von Proxyservern verwendet

Port 26101 SDB connection

Hmmm, tried few things with 8080... but no luck yet...

The idea... maybe with PC or other Device have easier access folders... for data transfer...

Long time ago I have checked my SM-Z130H... to find maybe open port for SDB action... but no...

Port 21 FTP;transfer

Port 53 DNS

Port 6269

Port 6271

Only as info...

Maybe someone have an idea or have Tools or Commands to use open Ports on Gear...

If I have time, will check Tizen Studio... maybe it connects not only over SDB...

Best Regards