yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S2] adfree:
https://xdaforums.com/showpost.php?p=56281758&postcount=69

For rootfs.img I am using since years successfully

ext2explore.exe :good:

http://www.droidviews.com/extract-system-img-files-or-system-dump-of-android-devices-on-windows/

For other *.img... I am using:

ext4_unpacker.exe

WinHex can also extract, but seems for me not perfect solution... depend on WinHex Version...

Best Regards
[Samsung Gear S2] adfree:
Interesting:

https://de.ifixit.com/Guide/Samsung+Gear+S2+Classic+Disassembly/63009

Meanwhile I investigate Gear Manager Beta for Tizen... the 1 year old version 0.0.8...

Playing around with my SM-Z130H and SM-R732...

Best Regards
[Samsung Gear S2] adfree:
Example from Log file... Kernel Panic/Ramdump/Upload related... taken with RDX Tool:

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

My log_0x46000000--0x461fffff.lst

Currejt SBOOT version : VERSION_-+B2

Samsung S-Boot 4.0 for SM-R732 (Oct 5 2015 - 06:18:52)

EXYNOQ3250(EVT 0.0) / 506MB / #728MB / Rev 12 / R732XXU2AOJ3 /(PKE_AD 0xB0d0808!

BOOTHOADER VERSION : R712XU2AOJ3
pit_update_partinFo: try to load pit
pit_updata_partinfm: try to cheak sifnature
- re`d_bl1
pit_check_siglature (PIT) valid.
initialize_dd)_dat`: usable! (1:0x0
ZRPIB] e-mc_rpmb_open*
e4 DATA success.

[BPMB] emmc_2plb_clo3e:
initialize_rpmb_data8 usable! (SM-R532:VERSION_$+B2)
PARAM ENV VERSAON: v1.0..
SECURE O FERSION: P-Base v30 RaL (MiB)
init_chargar: max14577 detecded
init_pre_feeh_gauge mo@e=0x1 00
init[pre]fuelgaugd: hibrt 0000) =, 0x0
muic_api_interrupt_reg_clear: INTR[1:0x00, 2:0x02, 3:0x02]
AP_PMIC_SDA 5 2
PMIC_ID

No idea why corrupted data inside...

Maybe bad soldered wires or RDX Version is outdated...

Best Regards
[Samsung Gear S2] adfree:
Here are few Shell scripts inside... for study...

Taken from AOJ3 Firmware... rootfs.img

Searching for an way for WiFi Direct... for instance...

Best Regards
[Samsung Gear S2] adfree:
At the moment I 'm stuck... slowest progress...

I have different problems and no easy solution yet... :rolleyes: :o :(

Problem 1.

For playing with Firmware I need Firmware... :D

But... :cyclops:

[B][COLOR="Red"]FACTORY/SPECIAL/COMBINATION[/COLOR][/B]	I have
COMBINATION-FTMA_R732XXU2AOJ2	[B]Yes[/B]
COMBINATION-FTMA_R732XXU2AOL4	[B]Yes[/B]
COMBINATION-FTMA_R732XXU2CPC1	[B]Yes[/B]

"NORMAL" Firmware package for Odin
R732_XXU2AOIL_OXA2AOIL_OXX2AOIL	Oh [COLOR="Red"][B]NO[/B][/COLOR]
R732_XXU2AOJ3_OXA2AOJ3	[B]Yes[/B]
R732_XXU2BOKK_OXA2BOKK	[B]Yes[/B]
R732_XXU2BOKK_OXX2BOKK	OH [COLOR="Red"][B]NO[/B][/COLOR]
R732_XXU2CPB7_OXA2CPB7	OH [COLOR="Red"][B]NO[/B][/COLOR]
R732_XXU2DPFB_OXX2DPFB	OH [COLOR="Red"][B]NO[/B][/COLOR]
R732_XXU2EPK5_OXA2EPK5_OXX2EPK5	[B]Yes[/B]
R732XXU2EQC1/R732OXA2EQC1	[B]Yes[/B]
R732XXU2EQH1/R732OXA2EQH1	[B]Yes[/B]
R732XXU2EQJ2/R732OXA2EQJ2	[B]Yes[/B]

Maybe somebody can help me to find the "missing" Firmware packages...

If somebody need Combination Firmware... PM me... I can share.

Problem 2.

To play with TPK and WGT...

I have only few... 3 or 4 or 5...

Main problem... :rolleyes:

I have no supported smartphone only dumboldphones... and kastrierte old Beta Version for Tizen...

To prevent to buy new Samsung phone... I am trying few "Hacking" attempts to run Gear Manager...

First idea is this:

https://xdaforums.com/showpost.php?p=72208056&postcount=135

Still not solved... I do something wrong or I am only too stupid to sign proper APK... :rolleyes:

So I have to solve first problem 1 and/or 2 to proceed...

Only as info.

Best Regards

Edit 1.

Here are few Packages... at bottom... :good:

http://4pda.ru/forum/lofiversion/index.php?t687583-1060.html

Need some time for download...

Edit 2.

https://www.tapatalk.com/topic/2844...pk5_tizen_2-3-2-1_factory_firmware_05_12_2016

So I have now BOKK, EPK5 and few more from older AOJx... :cool:

Edit 3.

EQC1 for SM-R732... OXA

https://www.file-upload.net/download-12636189/EQC1_OXA_smR732.zip.html

Edit 4.

EQH1 for SM-R732 AND SM-R720 :cool: :good:

https://xdaforums.com/gear-s2/general/gear-s2-firmwares-r720-r732-t3684789
[Samsung Gear S2] adfree:
Spend few hours to find solution for F%& Gear Manager App...

But no luck. :rolleyes:

Now I need few hours for Backup my old GT-I9300 with Android 4.1...

Maybe I have more luck with Android Version 4.3...

First attempts will be with Original Stock crap...

Also all attempts to find solution to see Gear Apps without... failed...

I was never able to find all... only few...

:confused:

More luck with SM-R732 Service Manual and search for spare part... :D

L105 sieht Scheisse aus	---	2703-003004 L105 INDUCTOR-SMD	---->	2703-003004 INDUCTOR-SMD;47nH,5%,0603,2.8Ohm,50mA,4/ (INDUCTANCE COIL FOR MOBILE PHONE)
C108 fehlt durch mich	---	2203-006556 C108 C-CERAMIC	---->	2203-006556 C-CER,CHIP;0.047nF,5%,25V,C0G,0603 (CAPACITOR FOR MOBILE PHONE)
C111 war scheinbar schon weg...	---	no hits

I have added Link in older post... for complete Service Manual

It could be, the part I need is also on GT-I9300...

From GT-I9300 I have few PCBs... :cowboy:

Only my Solder skills are still sh... it...

So I have first to increase my Solder skills...

I have Hot Air Station and Microscope...

Best Regards
[Samsung Gear S2] adfree:
Puh...

After little mistake to backup my GT-I9300 Android 4.1 with RootExplorer and only 4 GB SD card inside... :D :D

I have also tried to ZIP data folder... :D :D :D :D and after 13 hours fail... :D :D :D :rolleyes:

But I was able to install now Gear Manager on GT-I9300 Android 4.3...

Before I was not able to find compatible APK... ever Parse Error...

GT-I9300 now successfully connected with my SM-R732... and bam... now I understand what the f%&$ Reactivation Lock means...

It is impossibe for me to use Android Gear Manager with my SM-R732...

I have bought this watch from Ebay... in used condition and half damaged, because not booting... reason unknown.

Nice... I got this info about Reactivation Lock and mandatory Samsung Account... AFTER I was forced again to Factory Reset...

:eek: :mad: :crying:

Okidoki... I thought I don't need to erase this RL...

But I have an idea...

Maybe it is like in old times stored in boot0... after sboot.bin...

Maybe I can force to NULL...

Maybe my SM-R732 will servive...

Oterwise I kill Bootloader... then maybe also soldered wires useless for Odin... :o

We will see...

Best Regards

Edit 1.

Need to prepare few things... and study... maybe alternate way exists...

Before I kill SM-R732...

I have rooted my GT-I9300 to work with Root Explorer... now I have copied data folders for investigate *.xml file and *.db

Maybe it is possible to bypass via Gear Manager App "mod"...

Edit 2.

Uupsi...

With paired SM-R732 and open Gear Manager app... it is possible to open Galaxy Apps app... and to explore Gear apps...

I was able to download 1... and... :angel:

Found location where it is temporary stored... ;)

Need to check if decrypted or...

I have short searched for text string:

file

And all File Manager or Transfer related files are not for free... only paid apps... :rolleyes:

Puh... this is really hard...

Edit 3.

Found also other method to explore Gear Apps on my SM-Z130H... :cool:

Also it seems I can bypass really this forced Init process at first time...

So I don't need Gear Manager... at the moment... :cyclops:

Maybe later for catching FOTA update packages...
[Samsung Gear S2] adfree:
Bootloader (sboot.bin)... Reactivation Lock... Crypto crap... Knox related...

Little exercise for today...

sdb shell
sh-3.2# cd opt/usr/media
sh-3.2# mkdir Others
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.185075 s, 22.7 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.222447 s, 18.9 MB/s
sh-3.2# exit
exit

sdb pull /opt/usr/media/Others
pulled boot1.bin 100% 4MB
pulled boot0.bin 100% 4MB
2 file(s) pulled. 0 file(s) skipped.
/opt/usr/media/Others 223 KB/s (8388608 bytes in 36.686s)

boot1.bin should be empty...

but boot0.bin contains Bootloader sboot.bin

model name... i.e. SM-R732

and some cryptokaka :D

Will compare dump from today with older dump...

Maybe I can see crypto area...

Later more...

Best Regards

Edit 1.

Short analyze... damn, all my boot0 dumps are 1:1 same... so I have nothing really to compare...

boot0 contains this:

0x0	sboot.bin	1:1 no additional data
0x158500	crypto stuff/Knox	seems 256 Byte	last 16 Byte looks like MD5
0x1FFC10	Model Name	+ few Bytes additional data
[Samsung Gear S2] adfree:
About FOTA... Delta... incremental update of Firmware...

https://xdaforums.com/showpost.php?p=63299323&postcount=1

:good:

So valid FOTA Binaries are:

---oldest
R732XXU2AOIL/R732OXA2AOIL
R732XXU2AOJ3/R732OXA2AOJ3
R732XXU2BOKK/R732OXA2BOKK
R732XXU2BOL6/R732OXA2BOL6
R732XXU2CPB7/R732OXA2CPB7
R732XXU2CPC5/R732OXA2CPC5
R732XXU2DPFB/R732OXA2DPFB
R732XXU2EPK5/R732OXA2EPK5
---latest
R732XXU2EQC1/R732OXA2EQC1

Maybe somebody have the other FOTA Links...

:confused:

Thanx in advance.

Best Regards
[Samsung Gear S2] adfree:
With Google search power... :D

I have now 2 more "official" Firmware packages for Odin:

R732XXU2BOKK/R732OXA2BOKK
R732XXU2EPK5/R732OXA2EPK5

Links are in this Thread... older post...

So next attempt is to root BOKK... :)

I have only Combination Firmware with .C. to prevent problems if I need to repair...

For study and prepare few other things... I think I need 1 week...

I will test first few other stupid things, before I will proceed with Firmware updates...

No idea yet, if BOKK is worth to try...

I "need" this Samsung apps app inside...

Will investigate and extract rootfs.img first...

Other "projects" for this week...

Compiling Samsung Accessory SDK Examples... to learn about BT Connection... :D

Maybe with luck I can connect SM-Z130H with SM-R732...

Tizen vs. Tizen :D

Best Regards
[Samsung Gear S2] adfree:
https://xdaforums.com/showpost.php?p=67311795&postcount=12

Ah, found Thread about Gear Manager APK "Hacking"... :good:

Somebody told me today... 7zip is able to extract files from Firmware *.img

:good:

Thanx for this nice hint.

I have not tested if all files proper extracted, but very usefull for easy extract all files for short investigation. :cool:

About my dream next Firmware to flash with Odin...

BOKK seems not interesting enough... as this "Gear Store" app is not inside...

So I think I will proceed soon with:

EPK5

Puh... now I will try few tests with Tizen Studio / SDK and Samsung Accessory SDK examples...

Best Regards

Edit 1.

Compile part 1 for Gear...

Receiver created form Tizen native folder...

sdb install org.tizen.filetransferreceiver-1.0.0-arm.tpk
pulled org.tizen.filetransferreceiver-1.0.0-arm.tpk 100% 45KB
1 file(s) pulled. 0 file(s) skipped.
org.tizen.filetransferreceiver-1.0.0-arm.tpk 392 KB/s (46294 bytes in 0.115s)
path is /opt/usr/apps/tmp/org.tizen.filetransferreceiver-1.0.0-arm.tpk
__return_cb req_id[187840002] pkg_type[rpm] pkgid[org.tizen.filetransferreceiver] key[start] val[install]
__return_cb req_id[187840002] pkg_type[rpm] pkgid[org.tizen.filetransferreceiver] key[install_percent] val[30]
__return_cb req_id[187840002] pkg_type[rpm] pkgid[org.tizen.filetransferreceiver] key[install_percent] val[60]
__return_cb req_id[187840002] pkg_type[rpm] pkgid[org.tizen.filetransferreceiver] key[install_percent] val[100]
__return_cb req_id[187840002] pkg_type[rpm] pkgid[org.tizen.filetransferreceiver] key[end] val[ok]
spend time for pkgcmd is [96972]ms

App is able to start on my SM-R732...

I have tried just for one 1 APK from ... as Sender... seems not to work... tried with SM-Z130H on ACL...

-----------

Okidoki... need Sender App...

Maybe with luck I can create for mobile... and test with SM-Z130H or RD-PQ...

Edit 2.

Puh... I have to update Tizen Studio... because 2.3.1 Mobile Profile missing...

Meanwhile I found this, and will try again with SM-Z130H and ACL:

https://xdaforums.com/showpost.php?p=69438815&postcount=27

Edit 3.

Argh...

Seems not for Tizen Mobile... only for Tizen Wearable

http://developer.samsung.com/onlinedocs/native_sap/group__SAMSUNG__ACCESSORY__PROTOCOL.html
[Samsung Gear S2] Daiskei:
I've been watching your progress and I just want to say, this is amazing! Thank you for your hard work.
[Samsung Gear S2] adfree:
[MENTION=1568167]Daiskei[/MENTION]

Thanx. I am trying only to learn.

Best Regards

Puh... still nothing is really easy on Tizen/Gear...

Samsung Accessory related... yesterday no luck... :rolleyes:

Today somebody posted this. Thanx:

http://img-developer.samsung.com/co...ting_Gear_applications_using_the_Emulator.pdf

Puhhhh...

I think easiest thing to me is prepare EPK5 Firmware with root on weekend...

And then maybe monday flash result...

So I have 2 days to play little bit around...

Maybe with EPK5 more luck...

I have for instance big problems to follow this Instruction...

:confused:

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

:confused:

I was only 1 time able to bypass this forced menu... by luck.

I can remember I craweled with 2 Fingers... :D

So still I can only use Tizen Beta Gear Manager for Init...

Meanwhile I know how to use...

But I can not switch to German Language as SM-Z130H has no German language... :D :rolleyes:

Maybe this feature is Firmware Version related... and with EPK5 easier to do...

Best Regards
[Samsung Gear S2] adfree:
Preparing EPK5 for root

First I have checked via Odin to be sure files are not damaged/corrupted...

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_R732XXU2EPK5_usr.tar.md5 is valid.
<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> AP_R732XXU2EPK5_usr.tar.md5 is valid.
<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> CSC_OXA_R732OXA2EPK5_usr.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..

Looks good... so I can now modify rootfs.img and create TAR package...

Best Regards

Edit 1.

part 1 done...

I have zipped rootfs.img to transfer to my SM-R732... via SDB...

ZIP size is 500 MB...

No idea how long this will be...

I hope enough space to unzip...

Edit 2.

I am trying to transfer 500 MB file via BT and Gear Manger Beta Tizen Version...

Fail after 70 % ... 30 minutes...

Now trying again...

Edit 3.

Boah ey... no idea if WiFi is more stable... to transfer thiss huge file

But failed after 90 % with BT + GM

40 minutes... :rolleyes:

So I think 60 minutes for 500 MB transfer via BT... 1 hour is easier to handle with my brain.

Screenshot is earlier taken...

Edit 4.

Transfer maybe successfully done... after 99 % no confirmation... but less storage...

Also part 2 meanwhile created... TAR is ready for Odin

Edit 5.

Hmmmm... at the moment I am not sure if lost WiFi connection again... or it takes more time... :rolleyes:

sh-3.2# cd opt/usr/media
sh-3.2# ls
Downloads Images Music Sounds
sh-3.2# cd Images
sh-3.2# ls
4rootfs.zip.png
sh-3.2# mv 4rootfs.zip.png 1.zip
sh-3.2# ls
1.zip
sh-3.2# unzip 1.zip
Archive: 1.zip
inflating: rootfs.img

Blinking Cursor only... since 50 minutes...

Damn... maybe with -v more visible... like progressbar...

Edit 6.

Maybe done successfully... not 100 % sure as connection interrupted after I saw # again...

sh-3.2# cd /opt/usr/media/Images
sh-3.2# ls
1.zip rootfs.img
sh-3.2# ls -a -1 -l
total 1397992
drwxrwxrwx 2 app app 4096 May 13 18:23 .
drwxrwxrwx 7 root root 4096 Oct 6 2015 ..
-rw-r--r-- 1 app app 473142631 May 13 17:51 1.zip
-rw-rw-rw- 1 root root 958378240 May 13 14:35 rootfs.img

Edit 7.

Hmmmm... no idea if finished correct... or interrupted...

In theory rootfs.img is now written to p13...

This time this mixed Firmware not work...

But I can see Logo Screen...

Recovery attempt leads also to Logo...

For Flashing with Odin the second part... I need more time.

My Notebook is not here yet...

But short tested Download (usB) and also Download (wifi) starts... so I hope it work.

Maybe only Kernel and some other stuff is too much different to mix AOJ3 with rootfs.img from EPK5
[Samsung Gear S2] adfree:
After several attempts to transfer zipped 500 MB...

Maybe this time success..

:confused:

I have to check result and unzip on SM-R732...

Time needed for this attempt:

ca. 45 minutes

I have disabled Screenlock and forced always on Display... maybe this helped little bit...

Or I had simple luck. :D

Menu to disable Screenlock
testmode *#7594#

and

Always on display...
testmode *#251#

Now I have to check result over WiFi and SDB...

But first...

Eating... I am so hungry... :eek:

Best Regards
[Samsung Gear S2] adfree:
First Rooting attempt with EPK5 failed...

No idea where exactly...

First Flash with Odin failed short before ending... I will later add Log File...

Second attempt with Odin flash success... But only Logo...

Odin Download (usb) is stable... all wifi menus are very very short visible... then black...

I will try with Video... maybe then I can see what is on Screen...

So I have solder again wires. :D

No idea if problem is Firmware related... or best first step is Combination Firmware... then modified stuff...

Generally it looks like to me... with wifi you can flash every crap you want... without warning... :cyclops:

Detailed Errors are only possible with USB cable connected.

I am busy now.

I need to look Prison Break... :good:

Later today I will solder wires again...

And maybe first attempt is to catch Log with Upload mode... and Ram dump extractor Tool...

Best Regards
[Samsung Gear S2] adfree:
Still I am very bad in soldering wires... :o

After 1 hour I have soldered those 4 wires again...

1.

I have dumped with Upload usb... to RDX Tool... will later check result...

2.

Flashed with Odin successfully AOJ2 Combination Firmware...

SM-R732 alive again...

3.

Now I will try again... same steps like before with EPK5...

Only difference... faster possible as USB cable attached...

So hopefully this time more luck... or more output/log possible...

Later more...

Best Regards

Edit 1.

Strange... after my "part 1" and "part" EPK5 comes up...

But in russian language...

I can see near Gear Logo little tiny lock and funny long text...

I can only identify something seems Reactivation Lock related...

Strange... MTP is on... I can access filesystem...

SDB is not on...

Will check if I can see BT or pair... with Gear Manager...

BT seems on I can pair

Now I have to fight again with incompatible Gear Manager and Reactivation Lock...

Nice... :D :rolleyes:

Best Regards

Edit 2.

Big sorry.

The beta Gear Manager from Tizen is my best friend at the moment. :cyclops: :angel:

It is the only chance for me to bypass Reactivation Lock...

And many thanx... it work also with EPK5. :good: :cool:

So I have now rooted EPK5 Firmware on my SM-R732. :victory:

Best Regards
[Samsung Gear S2] adfree:
I was able to remove Reactivation Lock... :victory: :angel:

So I was able to use my GT-I9300 with "normal" Gear Manager... instead my Tizen SM-Z130H with Tizen Beta GM...

Now I can also easy install apps from Store. :cowboy:

Btw.

I was wrong with boot0 partition... RL is somewhere else... :o

Now I will add my certs to my rooted EPK5...

Then after sleep few hours... I will desolder the wires for USB... I hope this time not kill again something... :D

Best Regards
[Samsung Gear S2] ddaggebi:
Hello,

I have throughly read all your posts from start. Looks like you've done a bunch:eek: achieving root on tizen!! Thanks for your great works!

I have some questions, though.

1. What can you do by having root on tizen wearable? Is there anything fun to do if it is rooted?

2. Can this be (any chance) related to developing AW for Gear S2?

Again, thanks for your hard work on this old device!
[Samsung Gear S2] adfree:
Greetings to Seoul. :D

I hope you are not Samsung R&D... ;)

I'm trying in my bad English.

1.

SM-R732 and SM-R720 = same or very similar...

They are heavily secured against any kind of changing Software or manipulation of Firmware...

I have no idea if the other devices with Qualcomm chipset are easier to play with...

2.

I have also no idea yet, if it is possible to flash Open Source Kernel and/or Platform from here:

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

Without having same problems with Security...

3.

In theory all Sources are given... to do Port to something...

Android Wear or what ever you want... BUT Security.

But all attempts with Odin wifi or simple dd if you have root leads to "soft bricked" device...

For the most users of us this means "hard bricked"... as they NOT solder wires...

4.

Summary... all attempts leads to this result:

https://xdaforums.com/showpost.php?p=72097974&postcount=113

Look at this Picture with soldered wires to PCB.

:o

Gear Sx series Wearables are not very Porting friendly... :D :(

No USB cable....

I hope now little bit more clear... why I am far away from testing ready Android wear... :D :D :D

Feel free to find better way, easier and more safe...

Every contribution... also in theory is welcome. :good:

Best Regards
[Samsung Gear S2] ddaggebi:
[MENTION=1030585]adfree[/MENTION]

Aha... If I am understanding you correctly, everything we want can be done IF the security problem can be solved, right?

And the security problem is the f$%king 'Reactivation lock' thingy that blocks wifi odin, so if we encounter one, we have no choice but to solder wires into our Gear to establish a usb connection between PC and gear.

And in some of your last posts, you found a way to unlock RL by flashing a certain firmware?

Am I correct?

If I'm right, then you have my utmost respect:good::good: All these figured out by you...wow
[Samsung Gear S2] adfree:
Reactivation Lock is only 1 part of Security...

It prevented me to use Gear Manager fully to install Apps...

But this word/text Reactivation Lock also Odin spit out very often...

As I have played with Odin USB... and attached USB cable... Look here as example:

https://xdaforums.com/showpost.php?p=72061374&postcount=104

Custom binary blocked

by Reactivation Lock

These messages you are not seeing in "wifi mode"... only if you have attached USB cable.

If it would be more safe to try something, then maybe more users and also Android Developers would try something...

But for now every attempt leads to this result.

You have to connect mandatory via USB cable to repair... Flash again... :eek:

I have removed Reactivation Lock ... this thing where device is locked to old Samsung Account...

With Tool + USB cable... because you need mandatory USB cable + Download Mode.

1 click done. :D

But this is not my solution. I have only simple used existing solution.

But it also required soldered wires or this Factory JIG...

With wifi only impossible. :(

Still all things not very easy... nor very safe...

Best Regards