yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S3] adfree:
I am on Combination Firmware CQK2... and doing some stupid tests... investigation...

sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 15 Dec 1 02:22 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Dec 1 02:22 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Dec 1 02:22 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Dec 1 02:23 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Dec 1 02:22 csc -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Dec 1 02:22 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Dec 1 02:23 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Dec 1 02:22 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Dec 1 02:22 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Dec 1 02:22 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Dec 1 02:22 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Dec 1 02:22 steady -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Dec 1 02:22 system-data -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 15 Dec 1 02:22 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Dec 1 02:23 user -> ../../mmcblk0p13

My Commands for dump few of these 15 partitions...

sh-3.2# dd if=/dev/mmcblk0p7 of=/home/owner/media/Others/cm.bin
6144+0 records in
6144+0 records out
3145728 bytes (3.1 MB) copied, 0.187943 s, 16.7 MB/s
sh-3.2# dd if=/dev/mmcblk0p3 of=/home/owner/media/Others/cpnvcore.bin
4096+0 records in
4096+0 records out
2097152 bytes (2.1 MB) copied, 0.142777 s, 14.7 MB/s
sh-3.2# dd if=/dev/mmcblk0p2 of=/home/owner/media/Others/csa.bin
16384+0 records in
16384+0 records out
8388608 bytes (8.4 MB) copied, 0.427237 s, 19.6 MB/s
sh-3.2# dd if=/dev/mmcblk0p1 of=/home/owner/media/Others/tup.bin
65536+0 records in
65536+0 records out
33554432 bytes (34 MB) copied, 1.31099 s, 25.6 MB/s
sh-3.2# dd if=/dev/mmcblk0p6 of=/home/owner/media/Others/param.bin
16384+0 records in
16384+0 records out
8388608 bytes (8.4 MB) copied, 0.378626 s, 22.2 MB/s

Goal(S)...

Checking for empty partition sssss

Comparing Images from Firmware packages...

Reason... to prepare few FOTA related stupid tests... :D

Later more...

CSA partition is clear... :D

Its for Backup... NOT play with this Security related partition...

Best Regards

Edit 1.

sdb pull /home/owner/media/Others .\1
pulled cpnvcore.bin 100% 2MB
pulled csa.bin 100% 8MB
pulled param.bin 100% 8MB
pulled tup.bin 100% 32MB
pulled cm.bin 100% 3MB
5 file(s) pulled. 0 file(s) skipped.
/home/owner/media/Others 201 KB/s (55574528 bytes in 269.194s)

cpnvcore.bin is 2 MB empty

cm.bin... looks like additional data is written...

:confused:

Hmmmmmm... Google result for cm.bin:

https://xdaforums.com/galaxy-s6/help/cm-bin-inside-firmware-t3165525
[Samsung Gear S3] adfree:
Maybe tiny success... :D

Tried today Combination Firmware BQC2 + modified rootfs.img.

Changed only text string BQC2 into BQC3 or something like this.

After successfully flashed... Upload Mode...

I have checked if Download Wireless alive = yes.

Then pressed recovery...

After this Watch boot. :cool:

Now under AP something with VX700 visible...

:eek:

So this is first success to modify rootfs.img...

Now I will flash CSC.img from BQC5...

I know this work... since used many times for CSC change...

But new idea is to try now rootfs.img from BQC5...

To check if I can mix Combination BQC2 Firmware with csc.img and rootfs.img from BQC5...

Best Regards
[Samsung Gear S3] adfree:
My Mix of Combination Firmware BQC2 and BQC5 seems to work...

With tiny sideeffect(s)...

Summary:

Round 1.

COMBINATION-FTMA_R760XXU2BQC2.tar.md5

unmodified Original package...

Round 2.

CSC_OXA_R760OXA2BQC5_usr.tar.md5

unmodified Original package...

partition.pit from this CSC is set/written to device...

No idea if "important"...

As I can not decrypt Signature...

Round 3.

From BQC5 only rootfs.img into own TAR file...

rootfs.img -->TAR

In this attempt unmodified Original rootfs.img

Result...

Kernel Panic/Upload Mode...

But I have ignored... hold Power Key... then performed:

Recovery (Factory Reset)

My SM-R760 starts... shows Warning about blabla Unauthorized... See Picture...

But I can ignore it... then I am able to config with my Phone... :cool:

I am able to use the Gear S3...

Need some time to identify what is detecting my "Modification"...

Then next attempt to flash again modified rootfs.img...

Difference to older attempts...

Meanwhole we know sboot.bin from Combination Firmware is special... because Enginiers Variant... not User...

And could be also Kernel is special Factory Variant...

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

Warranty Void is still:

0 (0x0000)

And more important:

Download (Wireless) still working normal. :good: :cool:

Best Regards

Edit 1.

Tested successfully "modified" rootfs.img from BQC5.

Changed 1 Byte...

Next attempt is to insert my Certs... to check if working or not...
[Samsung Gear S3] Juxto2010:
I have a spare T-Mobile s3 classic. If you want anything tested just let me know. Good luck
[Samsung Gear S3] Grimm0878:
flash?

Hey, guys did you manage to flash it to android wear?
[Samsung Gear S3] adfree:
Thanx for offer. :good: :cool:

LTE Versions are harder...

We have not same amount of free Firmware...

SM-R775T available Firmware for free = 0

:(

So you have not the same chance for repair... like SM-R760 and SM-R770 users... if something goes wrong.

No... sorry...

Best Regards
[Samsung Gear S3] marceloanderson:
R760oxa2bqc5 ->r760oxa2cqk3

Hi!

Sorry for this stupid question. I have the version R760OXA2BQC5 installed on my S3. It was bought in Korea. Can I flash the version R760OXA2CQK3? Any suggestion for another rom?

Thanks in advance.

Best Regards,

Marcelo
[Samsung Gear S3] adfree:
[MENTION=8893010]marceloanderson[/MENTION]

If Korea means CSC/Sales Code:

KOO

Then BQC5 is not in database of KOO...

They have BQC8...

But BQH1 and CQK3 is in Korean KOO FOTA database for this device...

And we have BQH1 and CQK3 as Full Firmware for use with netOdin

Suggestion... if you really need Tizen 3...

A.

Update to BQH1... this is Tizen 2.3...

But FOTA update over the air should be possible... if you have KOO as Sales Code/CSC

or

B.

Update to CQK3... this is Tizen 3

FOTA update over the air should be possible... if you have KOO as Sales Code/CSC

Latest Tizen 3 is CQL1... but we have NO Full Firmware...

C.

You could change Sales Code/CSC... if you want....

Best Regards
[Samsung Gear S3] Tyler2265:
Just found this thread. So I have a gear S3 frontier Model SM-R760. Can someone give me clear steps to getting Android Wear on this watch? I desperately need it for Auto wear purposes. Never thought when I bought this watch that tinzen wouldn't be compatible (Stupid me). If it's possible can someone please tell me in detail? Thanks in advance!
[Samsung Gear S3] adfree:
More tiny little progress...

My experiments with BQC5@BQC2 failed... :eek:

Tested few different things but no luck...

Today I flashed from "special" Firmware only rootfs.img and csc.img and it work... :angel:

The interesting thing... IMHO...

Tested CSC and ROOTFS are from Software Revision 1 Firmware...

BQC5 and BQC2 are Software Revision 2... only as info...

Still my Download Wireless is alive... and also Knox not tripped... :cool:

Will try some more and deeper tests...

Best Regards

Edit 1.

First success with modify rootfs.img...

I was able to insert my modified Fingerprint... Cert stuff... :laugh:

Now will test again to insert su Binary...
[Samsung Gear S3] lyvidium:
Is it really that hard to read few posts back? This is still in early development, no android wear for S3 yet.
[Samsung Gear S3] Ansuel:
So benefits of having root?
[Samsung Gear S3] adfree:
Really sorry.

I have no idea how to answer such question...

But I will try. :D

Look at Thread title...

This is really really all I can anwser to you. ;)

Best Regards

Edit 1.

[MENTION=5263199]Ansuel[/MENTION]

I am too lazy to make new post...

Porting is much harder as Farting...

IMHO it is not my fault... that we have no 1 click solution for everyone...

Nor Android Wear Kernel nor platform files.

Feel free to deliver better solution... ;)

Waiting is also not helpfull for any kind of Porting attempts... :rolleyes:

Maybe my results are not giant big... but I try my best.

If you are smarter... then you are welcome to increase my small skills...
[Samsung Gear S3] Ansuel:
You know in phone root it's not equal to aosp... So I repeat by having a rooted ROM what can we to other than wait a very hard port of android wear?
[Samsung Gear S3] adfree:
My rooted LDU rootfs,img... for SM-R760 only:

https://www.file-upload.net/download-12959275/LDU_root_v3.7z.html

WARNING!

experimental... not stable... not for daily use...

Please not use if you not know or not want understand... ;)

Step 1.

BQC2 Combination Firmware required!

MANDATORY!

Step 2.

my TAR file...

Step 3.

After flash... maybe Kernel Panic or Blinking Logo...

No panic...few times hold Power key...

To have Recovery in menu...

So Factory Reset required...

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

Summary:

OWN risk!

Risk to damage your SM-R760...

But this is first evidence we could root and do some custom tweaks...

We have only to find what is inside rootfs.img...

Smack Rules or something else is self checking...

I hope we can find it... if we compare:

BQC5
BQC2
and my LDU rootfs.img

Maybe some ini files with on off flags or something like this...

If Security su cccc kker detected... we can remove... :D

Best Regards
[Samsung Gear S3] lyvidium:
Great news, tnx for the effort. if i get some time i'll thinker around my Frontier.
[Samsung Gear S3] adfree:
My task for the next days, weeks... months...

I know something Security related is inside rootfs.img...

No idea why... but LDU rootfs.img has lowest Security. :good: :good:

So I was able to add su Binary and Certs... :angel:

BQC2 FTMA aka Combination Firmware... su + Certs allready inside... BUT useless for daily action... :rolleyes:

BQC5 rootfs.img...

If I change something... it will be detected...

I have to check 3 x rootfs.img from:

BQC2
BQC5
LDU

My magic Tools:

7Zip to extract files from rootfs.img

Total Commander to compare files or complete folders

Few folders are empty... so I can ignore them. :D

First check up...

Folder	[[SYS]]	bin	csa	etc	lib	mnt	sbin	tmp	usr
BQC2 FTMA	Journal	bash	22	4 or 9	=	=	smack-apps-labels	!!!
BQC5 STOCK	?	or	=	=
LDU	bash	?	64	=	=

So I have to compare many files...

Few are human readable...

Few require maybe more brain as I have... :D

Only as hint...

This is safe work... no risk... only Computer required...

If somebody want help me... feel free to post something usefull.

Thanx in advance.

Best Regards
[Samsung Gear S3] adfree:
Still I need help in case of

PIT dump from alive device... partition.pit
Upload Mode
[B]RDX[/B] Ram Dump eXtractor Tool new Version for support Gear S3

Interesting reading material:

https://saltaformaggio.ece.gatech.edu/publications/DIIN_17.pdf

http://hexdetective.blogspot.de/2017/02/exploiting-android-s-boot-getting.html

leads to some source code...

https://github.com/nitayart/sboot_dump

Also unsolved... why the hell... nobody can tell me part number of Back Cover/Rear Case...

https://xdaforums.com/showpost.php?p=75010692&postcount=383

Maybe somebody could help me.

Thanx in advance.

Best Regards
[Samsung Gear S3] Ansuel:
use win merge

---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------

anyway i wasn't saying that this is useless and you are not smart... i was asking the real benefits of having root... (what can be unlocked for example, custom apk?)
[Samsung Gear S3] tids2k:
I will try to find the part number for u this week.
[Samsung Gear S3] Aashish.007:
Will this work?

https://rounded.com/samsung-gear-s3-frontier-sm-r760-back-cover-gh82-12922a.html?sl=en

https://www.ebay.co.uk/p/Genuine-Sa...m-r765-Rear-Glass-Cover-Gh82-12922a/873737095

https://m.ebay.com/itm/Genuine-Sams...65-Rear-Glass-Cover-GH82-12922A-/352048025930
[Samsung Gear S3] adfree:
The LTE device like SM-R765A have USB Connector inside this Rear Case... Back Cover...

This is why I search for it...

GH82-12922A is wrong :o

Look here:

https://xdaforums.com/gear-s3/help/sm-r765f-teardown-t3659431

Maybe then more clear...

Best Regards

Edit 1.

Looks I come closer...

https://www.samsungparts.com/dcwsearch/models/view/?model=SM-R765

GH98-40714A --->ASSY COVER-POGO

:confused:
[Samsung Gear S3] adfree:
Model	Rear Case	Charger Dock/JIG	Battery	PBA
SM-R720	GH82-10837A/GH82-10790A	GH81-12016G	GH43-04532A	GH82-10769A
SM-R732	GH82-10804A	GH81-12016G	GH43-04532A	GH82-10773A
SM-R730	GH82-10898A	GH81-12016H	GH43-04538A	GH82-10974A	SM-R730A
SM-R760	GH82-12922A	GH81-12016M	GH43-04699A	GH82-13048A
SM-R770	GH82-12954A	GH81-12016M	GH43-04699A	GH82-12948A
SM-R765	[B]???[/B]	GH81-12016L	GH43-04699A	GH82-13016A	SM-R765T

I have corrected few "mistakes"...

I can not find Photos...

GH97-19294A
MEA REAR-SM-R765(BLK)
46 $

or

GH98-40543A
ASSY CASE-REAR(SIL)
25 $

:confused:

But I think more the higher priced part... for 46 $

:confused: :confused:

Best Regards
[Samsung Gear S3] adfree:
18	0.00028013	RDX_5.8_SLP.exe	IRP_MJ_WRITE	ssudserd0000	SUCCESS	Length9:507245614D624C6500
19	0.01958245	RDX_5.8_SLP.exe	IRP_MJ_READ	ssudserd0000	TIMEOUT	Length0:
40	0.00018382	RDX_5.8_SLP.exe	IRP_MJ_WRITE	ssudserd0000	SUCCESS	Length9:507245614D624C6500
41	0.02896423	RDX_5.8_SLP.exe	IRP_MJ_READ	ssudserd0000	TIMEOUT	Length15:41634B6E4F774C6544674D654E7400
42	0.00020973	RDX_5.8_SLP.exe	IRP_MJ_WRITE	ssudserd0000	SUCCESS	Length6:50724F624500
43	0.03086698	RDX_5.8_SLP.exe	IRP_MJ_READ	ssudserd0000	TIMEOUT	Length128:47542D4938383030000000000000000001000000415064756D705F70616E69632D62616E00000040FFFFFF4F01000000415064756D705F70616E69632D62616E00000050FFFFFF5F01000000415064756D705F70616E69632D62616E00000060FFFFFF6F01000000415064756D705F70616E69632D62616E00000070FFFFEF7F

Hmmmm...

Upload Mode related... short sniffed on my old RD-PQ... with RDX 5.8

I will test in next days... if I can use Packet Sender:

https://packetsender.com/documentation

To play over WiFi...

Best Regards
[Samsung Gear S3] tids2k:
[MENTION=1030585]adfree[/MENTION] if you need anything else with RDX just ask. I will try to get it for you.
[Samsung Gear S3] adfree:
Still I wish I have solution for RDX over WiFi...

To read Log files... to dump partition.pit PIT...

Since Tizen 3 it looks like we could also dump partitions...

Combination Firmwares have in Reboot menu:

Upload
Upload (Wireless)

Tizen 3 Combination Bootloader has also:

Partition Dump

RDX 6 seems not compatible... too old...

https://xdaforums.com/showpost.php?p=74776008&postcount=47

I can not test self yet... :o

I am trying as long as I can only to work with WiFi instead USB cable...

Step 1.

To make these Upload menus visible in Stock Firmware...

*#9900#

Debug Mode Setting--->ON

As example look at Video...

Best Regards

Edit 1.

Added Log from SM-R765A... as example... older Tizen 2.3...
[Samsung Gear S3] adfree:
Tiny progress with Upload Mode... RDX over WiFi... :D

From my SM-R760...

I can not check my SM-R732... to have template...

Sniffing Commands via USB is not more possible...

:o :o :o

https://xdaforums.com/showpost.php?p=75486436&postcount=215

Best Regards

Edit 1.

App can handle files... here logfile:

Connect
>>507245614D624C6500
>>507245614D624C6500
<<41634b6e4f774c6544674d654e7400
>>50724F624500
>>50724F624500
>>50724F624500
<<41634b6e4f774c6544674d654e7400
>>50724F624500
>>50724F624500
Disconnect

As text we can read:

PrEaMbLe
PrEaMbLe
AcKnOwLeDgMeNt
PrObE
PrObE
PrObE
AcKnOwLeDgMeNt
PrObE
PrObE
[Samsung Gear S3] tids2k:
This I see as a great achievement. We can now communicate outside samsung propreitery channel. :)
[Samsung Gear S3] Surge1223:
I would absolutely love to help, I have a lot of experience with Kernels, bootloaders, and the boot process in general, just not for the gear devices

I am with the guy who asked earlier It hard to tell what's happening.

instead of complaining I guess I kinda want to know what it takes to get from the picture I have attached, to the point where I can load a custom ramdisk.

In particular I'm interested in the partition table, and the boot process. Idk where to get any official source, all I see is custom made tars and such.

Also just some advice, focus on a bypass and vulnerability not a crypto bypass there are much easier chances there is a workable exploit.

I'm sorry if this sounds like I'm being useless, but it's frustrating as programmer to want to help but not being able to get to where you are.

I think it'd be much more helpful for all of if you take a break from posting your experimental dumps, and maybe do a write up to help us get to where you are at, I mean this in the nicest possible way, and I will help you, just help me help you
[Samsung Gear S3] tids2k:
Dear [MENTION=4939386]Surge1223[/MENTION], I am glad that you are showing your interest in this forum and we need guys like you here. I have read through the prior posts and have realised what has been going on. As you can see this thread has been going past almost a year now. [MENTION=1030585]adfree[/MENTION] have been trying hard to get the boot happen on this device and as you can read through the previous posts as well. I do understand where you are coming from. But [MENTION=1030585]adfree[/MENTION] has been on this forums before even you and me joined the xda.

I know that you are upset that there is not a lot of help around in this area as we dont have good brains like you here in this branch. But at the same time you cant condemn someone who is trying his best to get us results. I totally agree with you on working together. But I think there has been a misunderstanding between you and [MENTION=1030585]adfree[/MENTION].

I would also like to address this to [MENTION=1030585]adfree[/MENTION] that we all here are a developer community lets not forget that. Unless and until we work together we cannot get this to work on our devices.

At the same time like I mentioned before we need to clear this misunderstanding between both of you. [MENTION=1030585]adfree[/MENTION] has been trying all his experiments to get this device to run android. And if you are happy to help, lets try to have a common initiative and get this thread closed as soon as possible and get android booting on this device.

I will also speak to [MENTION=1030585]adfree[/MENTION] as he has very good knowledge around tizen and its environment. Because of lack of expertise here we all are suffering but as I mentioned the more developers jump in we can get this port quicker.

BTW Thank you so much for giving us a helping hand :) . I am posting the CQL1 factory firmware for both of you to work together. I am sure [MENTION=1030585]adfree[/MENTION] will agree with me too on this :)

COMBINATION-FT30_R760XXU2CQL1 -

http://www84.zippyshare.com/v/VaW5koDL/file.html
[Samsung Gear S3] adfree:
[MENTION=4939386]Surge1223[/MENTION]

1.

My English is limited + my time and energy...

2.

Short "summary", why I am doing this.

Maybe then easier to understand.

Please look into these 2 Threads:

https://xdaforums.com/gear-s3/help/wireless-mode-enter-gear-s3-sm-r760-t3710855

https://xdaforums.com/gear-s3/help/sm-r765f-teardown-t3659431

Conclusion... for me.

If Download Wireless (netOdin) is broken... by mistake, accident or Hacking "tests"... then you have an "little tiny" problem.

So you need mandatory USB cable for repair attempts

3.

USB cable... :D :o :crying:

I have damaged my SM-R732 by accident:

https://xdaforums.com/showpost.php?p=75486436&postcount=215

Cost... and lost:

100 Euro from Ebay

I have bought dead, unrepairable SM-R770:

https://xdaforums.com/showpost.php?p=74841897&postcount=375

Lost 140 Euro... from Ebay.

To prevent damage my alive SM-R760... I am not soldering wires as long as I can. :D

Otherwise I would kill again 140 Euro...

I am trying since monthS... to get Rear Case from SM-R765 LTE... with POGO connector inside... but NO luck yet.

https://xdaforums.com/showpost.php?p=75462308&postcount=415

This would increase my Gear S3 tests... :good:

Safer to Hardware...

4.

Maybe, but I have no idea.

If you have Gear for test... safe way to get some Log files:

https://xdaforums.com/showpost.php?p=75472253&postcount=419

*#9900#

Run Log Dump

With SDB or other way you can pull file from device...

I did nearly no tests with ramdisk related files...

ramdisk.img
ramdisk-recovery.img

Reason... to prevent killing Download Wireless... otherwise USB cable needed.

Android Wear... or also Tizen related Source Code/Kernel stuff... we are here:

https://xdaforums.com/showpost.php?p=74757820&postcount=371

NOT tried...

Reason... to prevent killing Download Wireless... otherwise USB cable needed.

About Tizen 3 and your Picture from CQL1...

IMHO Tizen 3 is mor s h i... because more Security... so IMHO not best base for experiments with Custom stuff.

I was only able to break into old rootfs.img from SM-R760X Firmware... aka Live Demo Unit

With BQC2 Combination Firmware as "base"

I am 99,9 % sure.

If you play with Tizen 3... every attempt to do custom stuff... Leads to:

USB cable ;)

I can upload few Log files from different Gear devices for study...

I hope now you understand... where is my status... and why I am soooo slow. :D ;)

Best Regards
[Samsung Gear S3] Ansuel:
Think we first need a working twrp to do all
[Samsung Gear S3] adfree:
:good:

Superb idea.

Please do it.

Seems I am an idot. And I don't know what I am doing. :D

Best Regards
[Samsung Gear S3] tids2k:
ramdisk unzipped
[Samsung Gear S3] adfree:
For Tizen 2.xxx usefull "Weapon" to extract all Image files from Firmware packages is:

[B]7Zip[/B]

Very powerfull. :cool: :good:

But in Tizen 3 Format is changed...

Since CQK3 I have to mount *.img files into Tizen crap Emulator... with Tizen 4 for instance...

Maybe somebody find easier way to extract files from SM-R600... or our Tizen 3 Firmwares like:

CQK3
CQL1

Thanx in advance.

Best Regards
[Samsung Gear S3] Surge1223:
Wow that was awesome response Thanks! Also sorry if I came off rude, and I think your English is good. I'm gonna dig in, so you're saying it's possible to downgrade to a different version? I figured they'd have disallowed that.

I was reading Tizen wiki and gear 2 unlock threads last night. I guess what I was trying to say is I wanted to do some clear set goals.

For me

1. Need to get a custom kernel booted for adb/sdb to get logs

2. From there, we can see what how much control the kernel has and modify it mount another partition or even just alter anything that leads to us able to have a way to recover

---------- Post added at 11:44 AM ---------- Previous post was at 11:43 AM ----------

Ya, now that I know we can flash custom kernels (or at least I think we can) twrp is a priority

---------- Post added at 11:46 AM ---------- Previous post was at 11:44 AM ----------

Nice! But also post the original whenever you can (it's helpful to see how they pack it and try to match)

---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------

I'll see if I can find a solution for that, but overall, unless it's some exotic compression never seen I think we''ll be ok
[Samsung Gear S3] Leinad88:
HI

Hi,

Hab Gelesen das du aus Deutschland bist ? =)

Wollte mal Fragen ob du es villt hinbekommen hast Andrid Wear auf Die Gear s3 zu bekommen und wenn ja ? würde ich mich gerne über eine Antwort freuen.
[Samsung Gear S3] adfree:
[MENTION=4939386]Surge1223[/MENTION]

As example for Log dumps... taken from menu *#9900#

...added 1 from SM-R765A...

https://xdaforums.com/showpost.php?p=75472253&postcount=419

[MENTION=8926168]Leinad88[/MENTION]

Ohne Fleiß... keinen Preis. :D ;)

Best Regards
[Samsung Gear S3] adfree:
Tiny Step forward...

Upload Mode Protocol require TCP Client

Upload (wirelesss)

But ODIN Protocol need TCP Server

Download (wireless)

Easiest way I have found for me... my Phones:

GT-I9300

And this nice Tool from Play Store...

[B]TCP/UDP TEST TOOL[/B]

https://play.google.com/store/apps/details?id=jp.gr.java_conf.tcp_udp_testtool&hl=de

It can also handle HEX... :good: :cool:

Need some time now to figure out...

How I can load and use Text files for sending HEX Commands...

Best Regards