Gear S3 Root and Kernel Source! (Android Wear Port Thread)

Search This thread

adfree

Senior Member
Jun 14, 2008
9,103
5,374
Code:
if [ "${MODEL}" = "galileo" ]; then
    LOCAL_BUILD_SECURE_BOOT=1
    if [ ${v_array[large]} ]; then
        if [ ${v_array[lte]} ]; then
            if [ ${v_array[na]} ]; then
                SECURITY_KEY=SM-R805U_NA_USA_USA0
            elif [ ${v_array[kor]} ]; then
                SECURITY_KEY=SM-R805N_KOR_SKC_KOR0
            elif [ ${v_array[eur]} ]; then
                SECURITY_KEY=SM-R805F_EUR_XX_EUR0
            elif [ ${v_array[chn]} ]; then
                SECURITY_KEY=SM-R8050_CHN_CHN_CHN0
            else
                # default SM-R805U_NA_USA
                SECURITY_KEY=SM-R805U_NA_USA_USA0
            fi
        else
            SECURITY_KEY=SM-R800_NA_USA_USA0
        fi
    elif [ ${v_array[small]} ]; then
        if [ ${v_array[lte]} ]; then
            if [ ${v_array[na]} ]; then
                SECURITY_KEY=SM-R815U_NA_USA_USA0
            elif [ ${v_array[kor]} ]; then
                SECURITY_KEY=SM-R815N_KOR_SKC_KOR0
            elif [ ${v_array[eur]} ]; then
                SECURITY_KEY=SM-R815F_EUR_XX_EUR0
            else
                # default SM-R815U_NA_USA
                SECURITY_KEY=SM-R815U_NA_USA_USA0
            fi
        else
            SECURITY_KEY=SM-R810_NA_USA_USA0
        fi
    fi
elif [ "${MODEL}" = "pulse" ]; then
    if [ ${v_array[lte]} ]; then
        echo "this is lte model"
    else
        LOCAL_BUILD_SECURE_BOOT=1
        SECURITY_KEY=SM-R500_NA_STA_USA0
    fi
elif [ "${MODEL}" = "renaissance" ]; then
    LOCAL_BUILD_SECURE_BOOT=1
    if [ ${v_array[large]} ]; then
        if [ ${v_array[lte]} ]; then
            if [ ${v_array[na]} ]; then
                LOCAL_BUILD_META_DATA=1
                ODIN_META_MODEL_NAME="SM-R825US"
            fi
            SECURITY_KEY=SM-R825US_NA_USA_USA1
        else
            SECURITY_KEY=SM-R820_EUR_XX_EUR0
        fi
    elif [ ${v_array[small]} ]; then
        if [ ${v_array[lte]} ]; then
            if [ ${v_array[na]} ]; then
                LOCAL_BUILD_META_DATA=1
                ODIN_META_MODEL_NAME="SM-R835US"
            fi
            SECURITY_KEY=SM-R835US_NA_USA_USA0
        else
            SECURITY_KEY=SM-R830_EUR_XX_EUR0
        fi
    fi
elif [ "${MODEL}" = "noblesse" ]; then
    LOCAL_BUILD_SECURE_BOOT=1
    if [ ${v_array[large]} ]; then
        if [ ${v_array[lte]} ]; then
            if [ ${v_array[na]} ]; then
                LOCAL_BUILD_META_DATA=1
                ODIN_META_MODEL_NAME="SM-R845U"
            fi
            if [ ${v_array[chn]} ]; then
                SECURITY_KEY=SM-R8450_CHN_CHC_CHN0
            else
                SECURITY_KEY=SM-R845U_NA_USA_USA0
            fi
        else
            SECURITY_KEY=SM-R840_NA_USA_USA0
        fi
    elif [ ${v_array[small]} ]; then
        if [ ${v_array[lte]} ]; then
            if [ ${v_array[na]} ]; then
                LOCAL_BUILD_META_DATA=1
                ODIN_META_MODEL_NAME="SM-R855U"
            fi
            SECURITY_KEY=SM-R855U_NA_USA_USA0
        else
            SECURITY_KEY=SM-R850_NA_USA_USA0

Memo to me...

GWA2 is Renaissance
GW3 is Noblesse

GWA1 is Pulse
GW is Galileo

Edit 1.

Leads to this as config files...
Code:
tizen_noblesse_brcm_defconfig
tizen_noblesse_chub_defconfig
tizen_noblesse_defconfig
tizen_noblesse_large_defconfig
tizen_noblesse_lte_defconfig
tizen_noblesse_small_defconfig
 
tizen_renaissance_brcm_defconfig
tizen_renaissance_chub_defconfig
tizen_renaissance_defconfig
tizen_renaissance_large_defconfig
tizen_renaissance_lte_defconfig
tizen_renaissance_small_defconfig

Hmmmmmmmmmmmmmm...
For SM-R820 IMHO I need:
tizen_noblesse_defconfig

And now no idea...
tizen_noblesse_brcm_defconfig
or
tizen_noblesse_chub_defconfig

:unsure:
 
Last edited:
  • Like
Reactions: rostifaner

adfree

Senior Member
Jun 14, 2008
9,103
5,374
Hmmmmmmmmmmm...

Compiler could be this...

And Command for first attempt could be this... for SM-R820 Kernel:
./release.sh noblesse large

@Shadowkairos

Please need more info what you want... ?

At the moment my brain is empty... and I can not answer your Question... no idea...

Best Regards

Edit 1.

Mistakes like every year...

A
Binaries are here:

B
I wasted my time first with my 32 bit crap Notebook... instead the 64 bit Machine...
 
Last edited:
  • Like
Reactions: rostifaner

adfree

Senior Member
Jun 14, 2008
9,103
5,374
Code:
[email protected]:~/Dokumente/2020/1$ ./release.sh noblesse large
fatal: Not a git repository (or any of the parent directories): .git
Merge tizen_noblesse_large_defconfig to tizen_noblesse_variant_defconfig
Merge tizen_noblesse_brcm_defconfig to tizen_noblesse_variant_defconfig
drivers/sensorhub/brcm/bbdpl/Kconfig:7:warning: choice value used outside its choice group
drivers/sensorhub/brcm_noblesse/bbdpl/Kconfig:7:warning: choice value used outside its choice group
drivers/sensorhub/brcm/bbdpl/Kconfig:13:warning: choice value used outside its choice group
drivers/sensorhub/brcm_noblesse/bbdpl/Kconfig:13:warning: choice value used outside its choice group
drivers/sensorhub/brcm/bbdpl/Kconfig:19:warning: choice value used outside its choice group
drivers/sensorhub/brcm_noblesse/bbdpl/Kconfig:19:warning: choice value used outside its choice group
arch/arm64/configs/tizen_noblesse_defconfig:4132:warning: override: reassigning to symbol IIO_BUFFER
KCONFIG_VARIANT(arch/arm64/configs/tizen_noblesse_variant_defconfig)
#
# configuration written to .config
#
arch/arm64/Makefile:23: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum
./scripts/gcc-version.sh: Zeile 25: /opt/toolchain-aarch64/bin/aarch64-tizen-linux-gnu-gcc: Datei oder Verzeichnis nicht gefunden
./scripts/gcc-version.sh: Zeile 26: /opt/toolchain-aarch64/bin/aarch64-tizen-linux-gnu-gcc: Datei oder Verzeichnis nicht gefunden
make: /opt/toolchain-aarch64/bin/aarch64-tizen-linux-gnu-gcc: Befehl nicht gefunden
make: /opt/toolchain-aarch64/bin/aarch64-tizen-linux-gnu-gcc: Befehl nicht gefunden
scripts/kconfig/conf  --silentoldconfig Kconfig
drivers/sensorhub/brcm/bbdpl/Kconfig:7:warning: choice value used outside its choice group
drivers/sensorhub/brcm_noblesse/bbdpl/Kconfig:7:warning: choice value used outside its choice group
drivers/sensorhub/brcm/bbdpl/Kconfig:13:warning: choice value used outside its choice group
drivers/sensorhub/brcm_noblesse/bbdpl/Kconfig:13:warning: choice value used outside its choice group
drivers/sensorhub/brcm/bbdpl/Kconfig:19:warning: choice value used outside its choice group
drivers/sensorhub/brcm_noblesse/bbdpl/Kconfig:19:warning: choice value used outside its choice group
arch/arm64/Makefile:23: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum
./scripts/gcc-version.sh: Zeile 25: /opt/toolchain-aarch64/bin/aarch64-tizen-linux-gnu-gcc: Datei oder Verzeichnis nicht gefunden
./scripts/gcc-version.sh: Zeile 26: /opt/toolchain-aarch64/bin/aarch64-tizen-linux-gnu-gcc: Datei oder Verzeichnis nicht gefunden
make: /opt/toolchain-aarch64/bin/aarch64-tizen-linux-gnu-gcc: Befehl nicht gefunden

I hate this Linux...
I hate S. for renaming files...

Edit 1.

Bypassed problem by editing file:
export CROSS_COMPILE="/opt/toolchain-aarch64/bin/aarch64-tizen-linux-gnu-"

in release.sh

Now close before finish... my HDD is full &%''''###
:poop:
 
Last edited:
  • Like
Reactions: rostifaner

adfree

Senior Member
Jun 14, 2008
9,103
5,374
Code:
  LD      vmlinux
  SORTEX  vmlinux
  SYSMAP  System.map
  OBJCOPY arch/arm64/boot/Image
DTB combiner:
  Input directory: 'arch/arm64/boot/dts/exynos/'
  Output file: 'arch/arm64/boot/merged-dtb'
Found file: exynos9110-tizen_noblesse_large_bt-r02.dtb ...
chipset: 0x9110, platform: 2, rev: 0
Found file: exynos9110-tizen_noblesse_large_bt-r05.dtb ...
chipset: 0x9110, platform: 5, rev: 0
Found file: exynos9110-tizen_noblesse_large_bt-r08.dtb ...
chipset: 0x9110, platform: 8, rev: 0
=> Found 3 unique DTB(s)
Start EXYNOS magic, version DTB...
Generating master DTB...
(writing 'arch/arm64/boot/dts/exynos/exynos9110-tizen_noblesse_large_bt-r02.dtb' - 143360 bytes)
(writing 'arch/arm64/boot/dts/exynos/exynos9110-tizen_noblesse_large_bt-r05.dtb' - 143360 bytes)
(writing 'arch/arm64/boot/dts/exynos/exynos9110-tizen_noblesse_large_bt-r08.dtb' - 143360 bytes)
Total wrote 432128 bytes
completed
out_name[arch/arm64/boot/dzImage]
kern_name[arch/arm64/boot/Image]
dt_name[arch/arm64/boot/merged-dtb]
272+0 Datensätze ein
272+0 Datensätze aus
272 bytes copied, 0,0228734 s, 11,9 kB/s
signing : start : 2020-12-12 07:27:48
signing : client version : 2.7
warning : Connection to http://165.213.148.120 refused
***** retry [count : 1][code:4] *****
warning : Connection to http://165.213.148.120 refused
***** retry [count : 2][code:4] *****

Seems I have somthing... only unsigned...

Best Regards

Edit 1.

Wow.... seems I am drunken...
First Kernel is for GW3....

My fault.

Code:
warning : Connection to http://165.213.148.120 refused
***** retry [count : 20][code:4] *****
signing : start signing with current client [2]
signing : runtype -> ss_exynos40_all
signing : model -> SM-R840_NA_USA_USA0
signing : inputfile -> arch/arm64/boot/dzImage.u
signing : outputfile -> arch/arm64/boot/dzImage
error : Connection to http://165.213.148.120 refused
[error info] IP :
[error info] MAC :
tar: dzImage: Funktion stat fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
tar: Beende mit Fehlerstatus aufgrund vorheriger Fehler
Failed to tar dzImage

Result of Command:
./release.sh noblesse large


Now will try again with:
./release.sh renaissance large
 
Last edited:
  • Like
Reactions: rostifaner

darkmind21

Senior Member
Mar 1, 2014
876
43
lisbon
Hello guys. How are you all? Hope fine. Tell me what's the advantages to root the s3 frontier? And switching from tizen to android wear?
Could someone please help me understand??
Merry Christmas
 

adfree

Senior Member
Jun 14, 2008
9,103
5,374
CTJ5 Root for SM-R820.


Be sure you have CTJ5 flashed on device, before proceed...


Rooted files for SM-R820 CTJ5 (Tizen 5.5.0.1):




Round 1.

With netOdin

Combination Firmware RAMDISK from SM-R500 to disable Security checks...



Code:
ramdisk_only_smR500_ASL2_FT40.tar


Yes, R500 is no mistake... thanx to "unified"...


Round 2.

With netOdin


Code:
2020_XMAS_smR820_CTJ5_ROOT_v1.tar


OWN RISK!



Best Regards
 

Xaloclaw

New member
Jan 27, 2021
2
0
I'm a noob to flashing, I'm trying to downgrade my S3 Frontier SM-760X, I was wondering if you could link the files I would need again. I'm having trouble finding the bypass knox file
 

adfree

Senior Member
Jun 14, 2008
9,103
5,374

A third codename related to Wear OS was recently discovered by XDA Recognized Developer ivan_meler in the kernel source code for the Galaxy S20 (SM-G980F). The code includes references to a device codenamed Merlot, and it directly links the device with Wear OS. Merlot is described as using a Broadcom BCM43013 chip similar to the Galaxy Watch 3.

Maybe somewhere floating around Android Sources...

Best Regards
 

tin2404

Senior Member
Jan 27, 2007
1,154
258
Zagreb
Checking Knox status could be done on SM-R800 by seven times tapping Knox Enrollement in watch settings device menu-software.If Knox is tripped, there will be standard Samsung root message....Also, Pay, Steps counter and Health will NOT work.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 115
    Hey guys! Some of you might know me from the LG G5 scene, but I have since moved on from there and am hoping to make some progress with the Gear S3 :)

    After doing some digging and paying zero attention in class today, I came across the kernel source files for the Exynos 7270 and the combination firmwares for the Gear 3 Classic and Frontier versions.

    If you don't know what combination files are here is a great explanation but the TL;DR is that this is the internal firmware Samsung uses to reset devices, so it gives you full read/write access to the device including root access. So basically this is a pre-rooted firmware, and I assume that it is bootloader unlocked as it appears to flash an engineer sboot (bootloader), so I believe this would be the first step towards porting Android Wear/TWRP!

    The kernel source is what we will actually use to port over AW/TWRP. It does not seem to have been posted before, and took me a few hours of digging to find. My watch comes in tomorrow, and after I flash this firmware I will pull the boot.img and start making a device/vendor tree to attempt and make a kernel!

    Here is the kernel source for the Exynos 7270: https://github.com/HonestlyAnnoying/tizen_kernel_exynos7270
    Here is the kernel source for the Gear S3 (all versions) (will upload to GitHub in the morning): Samsung Opensource
    Here is the SM-R770 (Classic) combination firmware [R770XXU2BQC2]: link
    Here is the SM-R760 (Frontier) combination firmware [R760XXU2BQC2]: link

    The road to porting Android Wear is going to take a lot of work, and any help developing (not testing for now!) would be EXTREMELY appreciated (looking at you guys @cipherswitch @biktor_gj !;)). If you would like to help with development or would like to contribute in any way, please PM me or hit me up on Skype (honestly.annoying)!

    Here is a Google Drive folder with all files I have for this, it will be updated as new things are found
    23
    Update: have flashed this, can confirm it has root access!! :D Pulling images now
    15
    Code:
    SDB 2.2.60

    Old, but in my eyes best SDB Version... because easy handling with right Mouse Button to mark, copy & paste.

    I have added for few OSes.. with WiFi Instruction...

    Maybe helpfull.

    Btw.
    I have used this Version also with Tizen 3 and Tizen 4...
    For me most main features work. :good:

    Like:
    Code:
    sdb root on
    sdb shell
    sdb pull
    sdb push

    Best Regards

    Edit 1.
    Nice Video for enable Debugging Option... to enable SDB communication... mandatory:
    https://www.youtube.com/watch?v=T_m3wsF7Ozs

    Edit 2.
    Added Video... how to find:
    Code:
    Debugging
    IP address

    Edit 3.
    Added Video... as example.
    How to connect SDB with device...
    Here example how to connect to remote device in RTL service... ;)
    To local device "similar"...

    Edit 4.
    The most important part to connect SDB with device over WiFi is described inside here:
    Code:
    [B][SIZE="3"][COLOR="Green"]Guidelines_on_Connecting_GearS2_device_using_WiFi.pdf
    Guidelines_on_Connecting_GearS2_device_using_WiFi_151222.pdf[/COLOR][/SIZE][/B]
    Please read FIRST! ;)
    12
    1 Way to change CSC... Sales Code.

    Tested by me with my SM-R760 with Wireless/WiFi only.
    NO USB cable required.



    Important.
    Check if Reactivation Lock is OFF...
    Own risk!
    Maybe sideeffects with RL on...



    Step 1.
    Combination Firmware:
    BQC2
    https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3588082


    Step 2.
    Flash CSC only! From Retail/Stock Firmware...
    I have taken from BQH1...
    https://forum.xda-developers.com/gear-s3/development/oxa-rom-gear-s3-r760-t3695150
    Code:
    CSC_OXA_R760OXA2BQH1_usr.tar.md5


    Step 3.
    Factory Reset/Recovery

    To take effect of new CSC...

    Step 4.
    CSC Preconfig
    Code:
    *#272*719434266344#

    Simple enter this Code...

    I have set XAR for US region...
    You can choose what ever you want... own risk.

    Step 5.
    Now flash complete Firmware of your Choice.
    In my case I have now used all files from BQH1.

    BQH1 is at the moment latest Firmware for US regiaon with Sales Code XAR...


    Best Regards
    10
    Example for Rooted Tizen 3 Firmware... CQL1 for SM-R760:
    https://www.file-upload.net/download-13213140/2018_July_rooted_Tizen3_smR760_CQL1_v1.7z.html


    Caution!

    Step 1.
    MANDATORY to flash FIRST Combination Firmware FT30:
    Code:
    CQL1
    https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3746522

    OWN RISK!

    Please NOT try if you NOT understand. ;)

    Best Regards
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone