yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S2] adfree:
Today I was drunken enough to try "few" repair attempts...

Problem 1.

Lost... SMD part for WiFi... :rolleyes:

https://xdaforums.com/showpost.php?p=72238914&postcount=138

[B]C108[/B] --->	2203-006556 C108 C-CERAMIC	---->	2203-006556 C-CER,CHIP;0.047nF,5%,25V,C0G,0603 (CAPACITOR FOR MOBILE PHONE)

I have desoldered C196 from GT-I9300 PCB...

This is so f&$ing tiny...

I was not able to fix this little tiny thing to solder in correct position on my SM-R732...

I gave up... :o :(

Problem 2.

Ripped off TP... Gold pad... :rolleyes:

I've killed the white cable... Data -

Long time ago...

This was the reason why nothing more posted...

But WiFi is f.ing slow and Range so short...

Anyway... tried with screwdriver to scratch little bit on green paint... to solder again wire...

Will later check if I scratched on correct position... :D :rolleyes: :o

Maybe I can again solder wires for USB...

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

Tried today few attempts to solder again wires...

But no luck...

TP for white cable is dead...

WiFi is still half dead... and nearly unusable... for "short tests"...

Maybe somewhere is alternate TP...

:confused:

Best Regards
[Samsung Gear S2] adfree:
For tests and repair attempts...

I will add Bootloader sboot.bin only TARs for use with ODIN... or study or what ever...

R732XX[B]E[/B]2BOJ2

Taken from Combination Firmware...

Later I will add more...

Best Regards
[Samsung Gear S2] adfree:
Here is example how to use ODIN protocol over Wifi...

In theory more possible... at the moment I have only dump partition.pit (PIT) from device:

https://xdaforums.com/showpost.php?p=75571582&postcount=455

At the moment I have only tested with my;

SM-R732
SM-R760

But should also work with:

SM-R600
SM-R360
SM-R765
SM-R730

All Gear devices which can be updated with netOdin.

Best Regards
[Samsung Gear S2] simonberger:
Hi, I'm new here. I'm a bit confused after Reading this thread. Is There a way to get Android Wear on the Gear S2? Or what is the progress?
[Samsung Gear S2] adfree:
Nobody is helping...

nobody do research...

nobody support nor somebody is testing something...

And we have no Kernel Developer nor any other Developer... :rolleyes:

Btw.

Same situation for Gear S3. :D

Wir sind nicht mal in der Lage... ein bissel Source Code zusammenzubasteln... :rolleyes:

Eigentlich ne ganz schwache Nummer...

Aber in den + 4 Jahren bin ich nix anderes gewohnt. :D

Entweder sie wollen nicht... oder können es ganz einfach nicht.

Schon alleine das die meisten Tizen User Schweißausbrüche bei dem Wort Root bekommen... :rolleyes:

:eek:

This is actual status. ;)

Best Regards
[Samsung Gear S2] simonberger:
OK danke :)

Bin am überlegen meine Gear S2 zu verkaufen und mir stattdessen eine Fossil Q Explorer 3 zu kaufen, auch wenn ich da keinen Pulssensor hab :mad:
[Samsung Gear S2] adfree:
[MENTION=8523776]simonberger[/MENTION]

Danke für Info.

Leider wird es weder bei den Gear S3 Geräten noch der neuen SM-R600... der Sport besser...

Samsung bekleckert sich nicht gerade mit Ruhm... was die da mit Tizen 3 verzapfen. :(

Es werden zwar noch Gear S2 Updates von Samsung kommen... aber sie stümpern jetzt einfach nur noch vor sich hin...

Die Gear S3 User sind über Tizen 3 auch nicht alle unendlich begeistert...

Die Tizen Handys haben sie "liebevoll" wie bada schon an die Wand gefahren... :mad:

Solche Fan Projekte wie Android auf ein nicht Android Gerät prügeln... erfordert meist mehr als nur 1 Person.

Wie Du in diesem Thread sehen kannst...

Kann ich mich nicht erinnern das da mehr als Geschwafel zustande kam...

Schade...

Meine SM-R732 hab ich leider bissel mehr putt gespielt... als sie vorher scheinbar war...

WiFi Reichweite ist unterirdisch...

Ich bekommen teilweise keinen Empfang, wenn die Uhr auf dem Notbook liegt... :rolleyes:

Mir ist beim Löten ein klitzkleines Teil weggeflogen... :crying:

Den Rest hab ich der Platine gegeben, als ich diesen Goldkontakt abgerissen hatte... :crying:

Somit kann ich auch keine Unsinn mehr mit Tizen 3 4 und 5 machen... mit USB Kabel...

Naja, was solls.

MfG
[Samsung Gear S2] toypoi:
JIG

Hi.

How to connect usb to the spots. Can you share diagram of some sort?

Best Regards

Tom
[Samsung Gear S2] adfree:
param.bin only TAR for Odin...

To enable Upload Mode...

Debug MIDdle

Attached for SM-R720...

Later I will add for SM-R732 too...

(in theory for both...)

Useable for instance for RDX Tool...

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

You can find Logs... and dump PIT partition.pit for instance...

Best Regards
[Samsung Gear S2] adfree:
http://dl.pars-hamrah.com/index.php...XXU2FRC1+R720OXX2FRC1+3File+ORginal+Firmware/

AP_R720XXU2FRC1_usr.tar.md5
BL_R720XXU2FRC1_usr.tar.md5
CSC_OXX_R720OXX2FRC1_usr.tar.md5
[B]TizenSecKeystringW-20160202.zip[/B]
sdb_2.2.67_windows-32.zip

SDB sure I know...

But what is TizenSecKeystringW-20160202.zip ?

:confused:

Any ideas or maybe somebody can download please.

Thanx in advance.

Best Regards
[Samsung Gear S2] TheMadScientist:
If it's anything like android. The keystrings are what bassicly like hidden menus. And other hidden data and settings
[Samsung Gear S2] adfree:
Oh, surprice... :D

Today I was drunken enough to flash EQJ2 OXA to my halfdead SM-R732... with success. :cool:

Tested on other Notebook with Windows 8.1

<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> zImage
<ID:0/001> NAND Write Start!!
<ID:0/001> zImage-recovery
<ID:0/001> param.bin
<ID:0/001> modules.img
<ID:0/001> sboot.bin
<ID:0/001> ramdisk-recovery.img
<ID:0/001> ramdisk.img
<ID:0/001> user.img
<ID:0/001> system-data.img
<ID:0/001> rootfs.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)

It was faster... 9 minutes needed... :good: :cool:

Before on my older Notebook with Windows Vista... :o

Anyway... I can do some stupid tests...

1 of it is to install:

TizenSecKeystringW-20160202.zip

:D

Best Regards

Edit 1.

sdb install signed_org.tizen.tizenseckeystringW-2.2.2-160202-arm.tpk
pulled signed_org.tizen.tizenseckeystringW-2.2.2-160202-arm.tpk 100% 66KB
1 file(s) pulled. 0 file(s) skipped.
signed_org.tizen.tizenseckeystringW-2.2.2-160202-arm.tpk 193 KB/s (68267 bytes in 0.343s)
path is /opt/usr/apps/tmp/signed_org.tizen.tizenseckeystringW-2.2.2-160202-arm.tpk
__return_cb req_id[21640002] pkg_type[tpk] pkgid[org.tizen.tizenseckeystring] key[start] val[update]
__return_cb req_id[21640002] pkg_type[tpk] pkgid[org.tizen.tizenseckeystring] key[install_percent] val[30]
__return_cb req_id[21640002] pkg_type[tpk] pkgid[org.tizen.tizenseckeystring] key[error] val[34] error message: Certificate is expired or not yet valid. Update your certificate or device date
__return_cb req_id[21640002] pkg_type[tpk] pkgid[org.tizen.tizenseckeystring] key[end] val[fail]
processing result : CERTIFICATE_EXPIRED [34] failed
spend time for pkgcmd is [5167]ms

Need to check something, as i started Gear S2 with tapping trick instead f.&%$ing Gear Manager... :rolleyes:

Edit 2.

sh-3.2$ date --set="26 Feb 2016 03:02:00"
date: cannot set date: Operation not permitted
Fri Feb 26 03:02:00 KST 2016

sh-3.2$ date --rfc-2822
Wed, 18 Apr 2018 07:46:15 +0900

I hate it without ROOT... :D :rolleyes:
[Samsung Gear S2] adfree:
I have successfully downgraded from FRC1 back to my beloved BOKK Firmware...

<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> 192.168.49.1
<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> zImage-recovery
<ID:0/001> NAND Write Start!!
<ID:0/001> sboot.bin
<ID:0/001> param.bin
<ID:0/001> zImage
<ID:0/001> modules.img
<ID:0/001> user.img
<ID:0/001> system-data.img
<ID:0/001> ramdisk-recovery.img
<ID:0/001> ramdisk.img
<ID:0/001> rootfs.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)

Now I can use my rooted Version...

Only as info...

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

This would be so much fun. :cyclops:

But too expensive for me...

https://www.ebay.de/itm/14-x-Samsun...M-R732-Smartwatch-Schwarz-Posten/282955664295

Best Regards
[Samsung Gear S2] Ph3arr3t:
I personally am upset that can't get AW or Google apps to run on the s2. Bought the watch expecting to be able to run Ingress.
[Samsung Gear S2] lmore377:
Have you made any progress?
[Samsung Gear S2] adfree:
Memo to me...

Linaro GCC 4.6-2013.05

This seems Toolchain for Linux Kernel...

Taken from zImage...

COMBINATION-FTMA_R732XXU2CPC1

Will check to find Linaro Toolchain for Compiling Source...

Best Regards

Edit 1.

Maybe from here:

https://releases.linaro.org/archive/13.05/components/toolchain/gcc-linaro/4.6/

or

https://launchpad.net/gcc-linaro/4.6/4.6-2013.05

Edit 2.

Hunt for Binaries... instead Source... or Qemu...

http://releases.linaro.org/archive/13.01/components/toolchain/binaries/

Maybe this 4.7...

gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux.tar.bz2

Edit 3.

Unmodified WRONG template...

export CROSS_COMPILE="/opt/toolchain-aarch64/bin/aarch64-tizen-linux-gnu-"

Modified for me...

export CROSS_COMPILE="/home/gcc47/bin/arm-linux-gnueabihf-"
[Samsung Gear S2] Akio_horri:
I have the Verizon 3G with the Qualcom processor, I'm open to helping test any apps.
[Samsung Gear S2] sqerk:
I've got a SM-R730A that I'm willing to use as a guinea pig
[Samsung Gear S2] TheMadScientist:
WE are now 2

My primary gear s2 is a verizon version and i slightly damaged it and Had a bit od water ingress It has been acting up and I dont feel it has much life left in it,Testing would be the best thing for it now before total failure
[Samsung Gear S2] adfree:
LD drivers/built-in.o
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 9 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
GZIP arch/arm/boot/compressed/piggy.gzip
AS arch/arm/boot/compressed/head.o
CC arch/arm/boot/compressed/misc.o
CC arch/arm/boot/compressed/decompress.o
CC arch/arm/boot/compressed/string.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
SHIPPED arch/arm/boot/compressed/ashldi3.S
AS arch/arm/boot/compressed/lib1funcs.o
AS arch/arm/boot/compressed/ashldi3.o
AS arch/arm/boot/compressed/piggy.gzip.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
System_wc1_20181214-.tar

My first success to compile Kernel...

./release.sh wc1

Toolchain used:

gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux.tar.bz2

From here:

http://releases.linaro.org/archive/13.01/components/toolchain/binaries/

At the moment I have no idea... if wc1 or this:

./release.sh hwp

:confused:

Maybe more later...

Best Regards

Edit 1.

LD vmlinux.o
MODPOST vmlinux.o
[COLOR="Red"]WARNING: modpost: Found 9 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'[/COLOR]
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
GZIP arch/arm/boot/compressed/piggy.gzip
AS arch/arm/boot/compressed/head.o
CC arch/arm/boot/compressed/misc.o
CC arch/arm/boot/compressed/decompress.o
CC arch/arm/boot/compressed/string.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
SHIPPED arch/arm/boot/compressed/ashldi3.S
AS arch/arm/boot/compressed/ashldi3.o
AS arch/arm/boot/compressed/lib1funcs.o
AS arch/arm/boot/compressed/piggy.gzip.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready

No idea if I can ignore this...

:confused:
[Samsung Gear S2] iesous-kurios:
I'd love to see wear on my gear s2 classic. Willing to test out if we ever get bootable OS.

I have the T-Mobile version with standalone 4g capability.
[Samsung Gear S2] adfree:
Hmmmmmm...

If Google for:

tizen_wc1_defconfig

I can find 2 hits...

No idea what kind of infos inside this eBook...

If I search for this:

tizen_b2_defconfig

https://xdaforums.com/gear-2/development/please-help-kernel-compiling-android-t2992953/page7

I have NO idea why never tried to contact him...

[MENTION=803006]biktor_gj[/MENTION]

And now seems tooo late as he is since monthS... offline...

Best Regards
[Samsung Gear S2] Kyrat:
The model I need to run AW is 3G/4G right? That's the only model with Qualcomm processor
[Samsung Gear S2] natalia86:
Glad to see this is still active! I own a Gear S2 Classic SM-R732. The Android Wear models sold where I live are nothing compared to the Samsung Smartwatches, as far as quality is concerned. Needless to say I would love to see Android Wear working on my S2 Classic. Happy to help test, once a working ROM is ready. Keep up the good work!
[Samsung Gear S2] Carlinyos18:
Thank you for all the testing and work you've done! I've managed to install a rooted version (COMB FTMA_R720XXU2AOJ2) over wifi on my SM-R720. What should the next steps be?
[Samsung Gear S2] adfree:
[MENTION=3068311]Carlinyos18[/MENTION]

Sorry I have limited time... :o

... and my SM-R732 not used since monthS...

No idea how to help you.... Maybe give more details what you are trying to achieve...

[MENTION=9350973]All[/MENTION]

R720XXU2FSD1
R732XXU2FSD1

New Firmware... no idea about changelog...

Best Regards
[Samsung Gear S2] Carlinyos18:
Trying to boot android wear on the gear s2, if possible. For the fact, the gear 2 and 2 neo share the same processor so im not sure how hard could be to change the already existent android kernel and install android on our rootfs partition
[Samsung Gear S2] Carlinyos18:
[MENTION=9350973]All[/MENTION]

FIY: If you want to use USB download with Odin without soldering, you can try to buy a Gear S USB charging base and connect it to the gear S2. Same pinout https://youtu.be/oQNOaZ8-BTQ?t=267
[Samsung Gear S2] bbsc:
Do you have any links, please?
[Samsung Gear S2] adfree:
R732XXU2FSD1

https://www.file-upload.net/download-13602698/R732XXU2FSD1.7z.html

Untested... own risk.

Best Regards
[Samsung Gear S2] Carlinyos18:
Any change you've got the firmware for the R720?
[Samsung Gear S2] yanzi:
new here :) sorry if i sound pretty newbie

plz let me know if you got a brief guide on compilation and how-to flash it to the watch [MENTION=1030585]adfree[/MENTION] (if you got a git etc.)

i'd be happy to dig around and port yours to 730A that I owned after the end of this month
[Samsung Gear S2] NEPAT989:
If needing Gear S2 Guinea Pig

I have the ATT Gear S2 with Esim 3G/4G Qualcomm if this is what you needed.
[Samsung Gear S2] adfree:
At the moment i am trying to prepare some Bootloader action... to remove Warranty Void 1...

I am not sure if eFuse... :D

Tests with my SM-R760... eFuse... :o

Result of today:

sh-3.2# dd if=/dev/mmcblk0boot0 of=/opt/usr/media/bootloader0.bin
dd: reading `/dev/mmcblk0boot0': Input/output error
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.0233555 s, 0.0 kB/s

:confused:

:eek:

After reboot...

sh-3.2# dd if=/dev/mmcblk0boot0 of=/opt/usr/media/bootloader0.bin
8192+0 records in
8192+0 records out
4194304 bytes (4.2 MB) copied, 0.279837 s, 15.0 MB/s

Need to check result...

sdb pull /opt/usr/media/bootloader0.bin

Some additional infos... SM-R720...

https://xdaforums.com/showpost.php?p=81853799&postcount=29

I have SM-R732...

Writing to mmcblk0boot0 is dangerous... can kill device for long time or forever... :D

Later more...

Best Regards

Edit 1.

Found my SM-R760 posts:

https://xdaforums.com/showpost.php?p=78582677&postcount=691

https://xdaforums.com/showpost.php?p=78530937&postcount=683

Edit 2.

https://xdaforums.com/showpost.php?p=78514927&postcount=680

No idea, maybe SM-R732 allow this funny force Command...

sh-3.2# [COLOR="Red"][B]echo 0 > /sys/block/mmcblk0boot0/force_ro[/B][/COLOR]
sh-3.2# dd if=/opt/usr/media/Music/mmcblk0boot0.bin of=/dev/mmcblk0boot0
8192+0 records in
8192+0 records out
4194304 bytes (4.2 MB) copied, 0.456286 s, 9.2 MB/s
[Samsung Gear S2] bbsc:
720 and 732 are identical and can be transformed one to another relatively easy.
[Samsung Gear S2] adfree:
[MENTION=682658]bbsc[/MENTION]

You are the perfect person to try boot0 writing. :angel:

To nuke Warranty Void 1... attempt

SM-R760 eFuse yes...

But no idea if SM-R720/SM-R732 fully secured... :confused:

Best Regards
[Samsung Gear S2] bbsc:
I do not promise anything but I'll see what I can do.

There was a spare mobo somewhere in the drawer... Seems it has bad sensors and it boots only when it wants.

I did not follow the discussion so we have to plan the experiment.

So I have to:

1. Flash something (what?) and confirm "good" status (how?)

2. Flash something (what?) and confirm "bad" status (how?)

3. Pull the /dev/mmcblk0boot0 and correct some bits there, than flash it back to the watch and confirm that it is really flashed (how?)

4. Confirm "good" status (how?)

Well, I know the answers but we really need a plan for not to miss anything. Because I'm not going to waste more than 1 watch on this experiment :D
[Samsung Gear S2] adfree:
Will test first my halfdead SM-R732...

Attached files for compare...

Result later...

Best Regards

Edit 1.

First attempt with Combination Firmware

COMBINATION-FTMA_R732XXU2AOJ2.tar.md5

:D

SM-R732 still alive...

... NO effect...

Damn. So I need to prepare Tizen 3 or 4 with WiFi driver...

Steps I made:

sdb root on
sdb push resetAttempt.bin /home
sdb shell
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=/home/resetAttempt.bin of=/dev/mmcblk0boot0
reboot

Edit 2.

Tested with zImage only from Tizen 3...

alive... but no effect...

Next attempt with RAMDISK...

Edit 3.

+ RAMDISK...

alive + no effect...

Puhhhh... so I need to prepare whole Tizen 3... with WiFi Driver...
[Samsung Gear S2] adfree:
Meanwhile we have success to dump whole eMMC direct to PC:

https://xdaforums.com/showpost.php?p=81872965&postcount=848

Tested devices with success:

SM-Z130H
SM-R760
SM-R732
SM-R500 rooted DSL1 Tizen 4

:cowboy:

"Limitation"...

I have only success with Tizen 2.3 with my SM-R760...

Tizen 3 and 4 failed... :(

Maybe again some SMACK Rules... :eek:

Only as info.

With my SM-R732 and Combination Firmware AOJ2 tested:

COMBINATION-FTMA_R732XXU2AOJ2.tar.md5

dd if=/dev/mmcblk0 | /home/[B]netcat[/B] -vv 123.123.123.23 1234

or

dd if=/dev/mmcblk0 | /home/[B]nc-arm-static[/B] -vv 123.123.123.23 1234

As example...

Best Regards
[Samsung Gear S2] adfree:
For "our" boot0 Knox 1 project...

I need to inject files into rootfs.img from Tizen 3:

tizen-wearable_20170403.2.20170404.044936_wearable-wayland-armv7l-tw1.tar.gz

largo-dsp3-ez2-control.wmfw
mdnie
nvram_mfg_bcm4334w_semco.txt
nvram_mfg_bcm4334w_semco3rd.txt
nvram_mfg_bcm4343w_murata_r720.txt
nvram_mfg_bcm4343w_semco.txt
nvram_mfg_bcm4343w_semco_r720.txt
nvram_net_bcm4334w_semco.txt
nvram_net_bcm4334w_semco3rd.txt
nvram_net_bcm4343w_murata_r720.txt
nvram_net_bcm4343w_semco.txt
nvram_net_bcm4343w_semco_r720.txt
wlan_apsta_bcm4343w.bin
wlan_mfg_bcm4334w.bin
wlan_mfg_bcm4343w.bin
wlan_net_bcm4334w.bin
wlan_net_bcm4343w.bin

wifi-loader
wlan.sh
wifi-module-check.service

Not impossible... but I have to move my lazy a...

Best Regards

Edit 1.

My old Adventure with Tizen 3 and 4...

https://xdaforums.com/showpost.php?p=72480651&postcount=165

Strange, here iread something about DL wireless alos not work... this is not good for me... I can not connect again with USB...

https://xdaforums.com/showpost.php?p=72550888&postcount=170

Uooo... this could be bad if I have to start Shell script manually:

https://xdaforums.com/showpost.php?p=72567943&postcount=173

Hmmm... here ended Tizen 3 and 4 adventure...

https://xdaforums.com/showpost.php?p=72967791&postcount=193
[Samsung Gear S2] adfree:
:rolleyes:

I am out of luck... Tizen curse...

My SM-R732 not accept any new Firmware...

Like these Threads:

https://xdaforums.com/smartwatch/gear-s2/fail-to-hard-softreset-t3746359

https://xdaforums.com/smartwatch/gear-s2/gear-s2-wont-perform-factory-reset-t3737448

:(

The only good thing is...

I am on Combination Firmware...

So I can try few ideas... to find reason for "write protection"...

Best Regards

Edit 1.

First check with full dump... if zImage or Ramdisk written... no...

So my Tizen 3 attempts...

Next I will check if I can do this:

https://xdaforums.com/showpost.php?p=72467226&postcount=164

sh-3.2# reboot fota_bl
Rebooting with argument 'fota_bl'.
[Samsung Gear S2] adfree:
:crying:

Looks really like Hardware damage to eMMC...

First check with

badblocks -v /dev/mmcblk0

I have cancelled because many Errors...

Second attempt with:

sh-3.2# e2fsck -vfcy /dev/mmcblk0p13
e2fsck 1.42.13 (17-May-2015)
Resize inode not valid. Recreate? yes

Error reading block 95 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps. Ignore error? yes

Force rewrite? yes

Checking for bad blocks (read-only test): 19.10% done, 6:45 elapsed. ([COLOR="Red"][B]51623[/B][/COLOR]/0/0 errors)

19 %...

Need to wait for 100 % result... :o

Best Regards
[Samsung Gear S2] adfree:
At the moment I am trying to find Tool for GPT partitions...

Memo to me...

https://www.linux-community.de/ausgaben/easylinux/2013/02/shell-tools-fuer-gpt-partitionstabellen/

I have tried to use ARM parted binary,,, but hard to find all correct depencies...

Bad is... i can remount rootfs.img and cp to /bin and /usr/lib

But after reboot also these files are gone.... :eek:

Next attempts to make read only again rootfs.img before reboot...

Best Regards