Samsung Gear 2 / Gear 2 Neo - Firmware



Rep: (17)
Smart watchSamsung Gear 2 / Gear 2 Neo - Firmware
SM-R380 / SM-R381
Discussion | Firmware | [OS] Tizen Wearable - Discussion | [OS] Android Wear

Some information on the OS Tizen

Everything that does not belong to the topic of discussion will be deleted. All questions about connecting watches on TizenOS to other devices are discussed inSamsung Gear 2 / Gear 2 Neo - Discussion. All instructions are in this post.

Drivers and Utilities
ADB driver for Android Wear

Tizen sdk
The Tizen development kit (Tizen SDK) is the most comprehensive set of tools for developing web applications and unmanaged (native) applications for Tizen OS. It consists of an integrated development environment (IDE), an emulator, a set of tools, code samples, and documentation. The Tizen development toolkit runs on Windows *, Ubuntu *, and Mac OS X * operating systems. Tizen applications can be developed without using the official set of development tools, but the layout of the final executable file must comply with the rules for packaging applications for OS Tizen.

Download Tizen 2.2.1 SDK
Download Tizen SDK for Wearable 1.0.0b2

From myself I will add that from the point of view of an ordinary user these kits are of little interest and may be needed only as a source of drivers for communicating with the clock.

Odin v3.09.3
The program is designed firmware Samsung, version 3.09 perfectly sees and flashes Gear 2 / Gear Neo.

DownloadAttached fileOdin3 v3.09.3.zip(972.42 KB)


Samsung Andorid USB Driver for Windows
Universal driver for Samsung mobile devices. On assurances of colleagues with xda-developers.com should work fine with Gear 2 / Gear Neo. The original post confirming the performance of this driver is posted.here.

Download v. 1.3.1500.0 Attached fileSAMSUNG_USB_Driver_for_Mobile_Phones.zip (25.32 MB)

Download v. 1.5.47.0 https://mega.co.nz/#!y…1mqJm5IlbAGWJAu95hiloM

SDB
Attached filesdb.rar(186.47 KB)


adb


Official firmware
Gear 2
R380XXU0BNDD
Update Date : 2014-04-27
CSC : SER
Firmware version : R380XXU0BNDD
OS version : 2.2.1.1
List of changes Unknown
Root : there is

R380XXU0BND8
Update Date : 2014-05-01
CSC : SER
Firmware version : R380XXU0BND8
OS version : 2.2.1.1
List of changes Unknown
Root : Not

R380XXU0BNE5
Update Date : 2014-05-22
CSC : SER
Firmware version : R380XXU0BNE5
OS version : 2.2.1.2
List of changes Unknown
Root : there is

R380XXU0BNK2
Update Date : 2014-11-13
CSC : SER
Firmware version : R380XXU0BNK2
OS version : 2.2.1.2
List of changes Unknown
Root : Not

R380XXU0BNL2
Update Date : 2014-12-08
CSC : SER
Firmware version : R380XXU0BNL2
OS version : 2.2.1.2
List of changes Unknown
Root : Not

R380XXU0BOA2
Update Date : 2015-02-04
CSC : SER
Firmware version : R380XXU0BOA2 POISON
1
OS version : 2.2.1.2
List of changes Unknown
Root : Not



Gear 2 neo
R381XXU0BNDD
Update Date : 2014-04-27
CSC : SER
Firmware version : R381XXU0BNDD
OS version : 2.2.1.1
List of changes Unknown
Root : Not

R381XXU0BNE5
Update Date : 2014-05-22
CSC : SER
Firmware version : R380XXU0BNE5
OS version : 2.2.1.2
List of changes Unknown
Root : there is

R381XXU0BNK2
Update Date : 2014-11-13
CSC : SER
Firmware version : R380XXU0BNK2
OS version : 2.2.1.2
List of changes Unknown
Root : Not

R381XXU0BNL2
Update Date : 2014-12-08
CSC : SER
Firmware version : R380XXU0BNL2
OS version : 2.2.1.2
List of changes Unknown
Root : Not

R381XXU0BOA2
Update Date : 2015-02-04
CSC : SER
Firmware version : R380XXU0BOA2 POISON
Poison 2
OS version : 2.2.1.2
List of changes Unknown
Root : Not



Unofficial firmware
Tizen Mod 3
Based on NE5;
- rooted;
- Scripts for energy saving;
- Removed shutter sounds;
- Added fonts from Android L;
- Added support for third-party icons;
- Added support for third-party fonts, Ringtones, notifications, etc.
- Added support for maximum CPU and governor frequencies (not yet used, because the author needs to tweak something in the scripts);

Mod from our friend* Romeo53, Samsung Gear 2 / Gear 2 Neo - Firmware (Post Romeo53 # 76736061)

Wear Marshmallow & Lollipop
Link toXDA
Installation
Extreme version,Beta6
Downloading the extreme versionMarshmallow Beta 2(dated 03/08/2016).
previous versionLollipopdated September 24th.Mirror 1 Mirror 2
Reboot the clock in Download Mode by holding the power button, and when the "reboot" message appears, we press it three times. After that a small menu appears, the navigation in which is made with the help of short presses on the power button, and the choice of an item by pressing the button for a second or two. After that, we connect the clock to the PC, to ODIN, in the PDA (AP) field, insert the downloaded archive and click Start.
After the reboot, the clock will automatically enter Recovery, in it we go along the Wipe path ->Factory Reset. After we select Reboot - System.

The first download is very long, plus if the programs are already installed, the synchronization will also take enough time.


What does not work in Marshmallow from 18.02:Samsung Gear 2 / Gear 2 Neo - Firmware (Post millifolium # 47237437)
Changelog for version from 24.09
Updated TV remote app
"Soft Mode for Screen Always ON
Added MTP (clock connected as a flash drive to PC)

What works
Works
Sound and microphone
Vibration
Bluetooth
Screen (at 90%. Brightness is not adjustable)
Screen sensor
All sensors and sensors

Does not work
Wi-Fi
IPv6 NAT (apparently it allows applications to go to the Internet without companion applications)
The gesture of turning off the clock by closing the screen with your palm

Return to basics, i.e. to tizen
Samsung Gear 2 / Gear 2 Neo - Firmware (Post dinatron # 41742618)- For now, use this method.

1) DownloadingTizenModFull.tar (Mirror) to where Odin lies.
2) Run Odin and shove it in the PDA fieldTizenModFull.tar .
3) Reboot the watch in Download Mode and connect it to the PC.
4) We are waiting for the inscription "0: COM: $" to appear and then click Start.
5) We are waiting for download.
If the clock has not booted, then we press the button, when Reboot appears, we press the button three times. With a short click, select Recovery, and confirm it with a long one. This will erase all information from the clock, as well as reset them to the factory settings.

Wear 4.4.3W
Instruction (original) to install Test Wear Android Wear:

Video instruction

If you are sure that you need it, and you realize that you can get a brick from your watch, then welcome.
What works and what does not work (May 25)
Works
Touchscreen
Bluetooth
Heart rate sensor
the Internet
Google now


Does not work
Sensors
Wi-Fi
Audio
Camera
Dials



Latest news
June 29
Lolipop appeared. So far, without everything (there is no blues, including, but the video driver works).

May 25
He earned a heart rate sensor, the ability to pass the setup wizard (but with a small crutch). Due to this, the Internet has earned through companion applications.

May 10
biktor_gj launched the firmware / the Internet is still not working - bluetooth falls in a quiet mode, "but at least time is visible" (c). And he can continue to debug the code.

May 7
There is a new problem.biktor_gj , the author of the port, found an error in the PAN, which does not allow to complete the settings wizard. He decided to return to Tizen to search for drivers on Broadom (the chip responsible for bluetooth, Wi-Fi and Radio). If he succeeds, it is likely that Gear 2 will receive Wi-Fi, and at the same time a working Bluetooth.



Installation
1) Download Odin3v3.09.3 Attached fileOdin3 v3.09.3.zip (972.42 KB)
, sdb Attached filesdb.rar (186.47 KB)
and necessary archives:Recovery; [4.4.3W- boot image with the / system partition;kernel_with_Ssp_firmware.tar- Kernel with OpenGL support and heart rate monitor.
recovery- The core with the latest recovery.
2) Unscramble Odin, sdb and * lib into any daddy (c: // sdb / for example) and put the rest of the files there as well.
3) Run Odin on behalf of the Administrator, in the fieldPDA we stuff recovery_fota_cache.tar .
4) Now restart the watch in Dowload mode. We press the button to the splash screen with the inscription "Reboot", and quickly press the button three times. The mode selection menu (Recovery, Download, system) appears. short press on the button select Download, and confirm with long.
5) Connect the watch to the PC. Install the driver (there is a cap) if Odin did not pick up the clock. We are waiting until the field with the inscription "0: COM: $" lights up.
6) In the PDA field we shove the filerecovery_fota_cache.tar and click Start.
7) The clock will automatically reboot, and a bootlap will come out with the artifacts. Reboot back to Download mode.
8) Repeat steps 3-7 with files (in turn)kernel_with_Ssp_firmware.tar , full_06_27_2015.tar and recovery_only_no_kernel.tar .
9) Reboot and use.



I also advise you to install 2 applications:SWApp Launcher WearandWear Mini Launcher

They will allow you to run applications even from under the settings wizard (after reboot), launch Launcher Switcher.


Return to basics, i.e. to tizen
Samsung Gear 2 / Gear 2 Neo - Firmware (Post dinatron # 41742618)- For now, use this method.

1) DownloadingTizenModFull.tar (Mirror) to where Odin lies.
2) Run Odin and shove it in the PDA fieldTizenModFull.tar .
3) Reboot the watch in Download Mode and connect it to the PC.
4) We are waiting for the inscription "0: COM: $" to appear and then click Start.
5) We are waiting for download.
If the clock has not booted, then we press the button, when Reboot appears, we press the button three times. With a short click, select Recovery, and confirm it with a long one. This will erase all information from the clock, as well as reset them to the factory settings.


Extreme Tizen Recovery Version
1) Download allfrom here (TizenModFull.tar You can not download if already downloaded. Mirror
2) Download ADBAttached fileminimal_adb_fastboot_v1.2_setup.exe(2.18 MB)
and install.
3) We do all the points of the usual method of recovery.
4) Sew recovery_fota_cache.
5) Go to the Recovery, connect the clock to the PC and run the ADB.
6) Each line is a new command.
adb shell
umount / data
mount / dev / block / mmcblk0p15 / system
mount / dev / block / mmcblk0p13 / system / opt
mount / dev / block / mmcblk0p14 / system / opt / usr
rm -rf / system / opt
cp /system/usr/system/RestoreDir/opt.zip / system
cd / system
unzip opt.zip
sync
cd /
umount / system / opt / usr
umount / system / opt
umount / system

7) In TWRP, select Reboot - Pover off.
8) Go to the Download Mode and sew firstkernel_tizen.tar , and then tizenmod2.tar


It should be remembered that this is still an alpha build, a lot of things have not been done, and a lot of things may work wrong.
It is also possible to install applications on wear via adb with the command "adb install" the name * .apk ". Of course, the application itself should be located next to adb.

Instructions
To return to the native firmware

Firmware official firmware flasher "Odin3" version 3.09
Attention! All of the following manipulations can lead to a stable “scaling” of the device, so you perform all actions at your own peril and risk. The author of this manual is not responsible for any damage to the device in case of improper use of this manual. Before starting the firmware, the clock battery must be charged up to 100%!
Step One: Preparing the firmware

The official firmware file has a name like R380XXU0BNDD_R380OXA0BNDD_SER.zip (the names of the firmware files will vary depending on the version and build number, so the names given by me are given for example) from which it follows that this is an archive. When you open the archive with any archiver, for example, WinRAR, you will see that it contains two files:
Attached Image

We are interested in a larger file named R380XXU0BNDD_R380OXA0BNDD_HOME.tar.md5, which must be unpacked and left in any convenient folder for you to use later.
Step Two: Prepare the flasher

  1. Download and unpack the Odin3 flasher program in the “Drivers and Utilities” section, or from any other convenient source
  2. Run the Odin3 program (in Winows 7/8 / 8.1 - on behalf of the Administrator!) And see the following window in front of you:
    Attached Image

  3. Put a check in front of the button "PDA"
  4. Click the “PDA” button and in the opened window specify the path to the firmware file, after downloading which, the flasher window will look as follows:
    Attached Image

Step Three: Putting the device into firmware mode

  1. We press and hold the power button, we do not pay attention to the restart window that appears, continue to hold the button, after 5-7 seconds the clock goes off to restart
  2. With the appearance of the logo and the orange inscription "Rebooting ..."
  3. Three times quickly press the power button to go to the boot menu, which looks like this:
    Attached Image

  4. Short press the power button, select the menu item "Downloading"
  5. Press and hold the power button for 3 seconds to go to the selected menu item, after which the clock screen should take the following form:
    Attached Image

  6. Uncheck “Auto Reboot”, if it is installed
  7. The clock is ready for the firmware, we connect it to the computer using a USB cable, if the firmware drivers are correctly installed, the flasher window will take the following form:
    Attached Image

Step Four: Launch the firmware

  1. In the flasher window, press the "Start" button
  2. In case of successful completion of the device firmware, the square in the upper left corner of the flasher window will turn green and “PASS!” Will appear in it, as in the figure below:
    Attached Image

  3. Reboot the clock by long pressing the power button until the word “Rebooting ...” appears

How to connect Galaxy Gear 2 / Neo to a non-Samsung-device (Complete Guide)
Samsung Gear 2 / Gear 2 Neo - Firmware (Post Mag_Alex # 41827840) - Another instruction.
Attention! The efficiency of this material was tested only on HTC (One (M7), One (M8), One DualSim) and Google (Nexus 5) devices! MAYBE, the information given here is applicable to devices from other manufacturers, but neither the authors nor the translator of the article are able to verify this!

What we need:
  • Samsung Galaxy Gear 2 / Neo
  • Having root access to your non-samsung device
  • Presence of custom recovery (CWM / TWRP)

Modify Build.Prop File:

Attention! All the actions described below can lead to a steady “scaling” of your phone, so the author and the translator of this manual strongly recommend making a full backup before starting to manipulate the phone!

Method one (Directly on the phone):
  1. Run any file manager with root support - access to the file system
  2. Go to the directory / System /
  3. Open the file "build.prop"
  4. Edit the following lines:
    ro.product.manufacturer = Samsung
    ro.product.model = GT-I9500
    ro.product.brand = Samsung

  5. Save the modified file
  6. Restart the phone

Method two (Using the command line \ ADB):
  1. Enable USB debugging (Settings>For developers>USB debugging)
  2. We connect the phone to the computer and install the driver if necessary
  3. Run the command line and go to the folder with ADB / Fastboot
  4. Enter “adb remount”
  5. Enter "adb pull /system/build.prop"
  6. Save the old version of the build.prop file (which is copied to the adb / fastboot folder)
  7. Open the file “build.prop” in any text editor (for example, in “Notepad ++”)
  8. Edit the following lines:
    ro.product.manufacturer = Samsung
    ro.product.model = GT-I9500
    ro.product.brand = Samsung

  9. Save the modified file
  10. Enter "adb push build.prop / system /"
  11. Restart the phone

Software installation:

Method one (Directly on the phone):

  1. Download:
    1. Attached fileSamsungservice2_K.apk(6.55 MB)

    2. Attached fileN_SamsungApps_14040104.21.007.0_HHP_TW_newkey_0401.apk(16.74 MB)

    3. Attached fileS-Voice_Android_phone.apk(25.67 MB)

    4. Attached fileGearManagerStub.apk(948.78 KB)

    5. Attached filesvoice-signed.apk(28.69 MB)


  2. We transferN_SamsungApps_14040104.21.007.0_HHP_TW_newkey_0401.apk , svoice-signed.apk and GearManagerStub.apk to the / System / app folder
  3. Change the attributes of copied files -rw-rw-r-- (664) or (644), group 0: root
  4. We transferSamsungservice2_K.apk in the / System / priv-app folder and change the file attributes
  5. Restart the phone
  6. Launch S Voice and agree and accept all license agreements (TOS)
  7. Go to the folder / System / app and delete S Voice
  8. We transferS-Voice_Android_phone.apk in the / System / app folder and change the file attributes
  9. Restart the phone
  10. Open Settings>Accounts and sync and set up a Samsung account
  11. We launch S-Voice, it will fall right after launch - this is normal
  12. Launch the application store Samsung Apps
  13. Find and download Gear Manager
  14. Launch Gear Manager
  15. Set up a connection with the clock

Method two (Using the command line \ ADB):
  1. We include access to settings for developers
  2. Enable USB debugging (Settings>For developers>USB debugging)
  3. Allow downloads from unknown sources (Settings>Security>Unknown sources)
  4. We connect the phone to the computer and install the driver if necessary
  5. Download the archiveAttached fileGear2ADBToolkit.zip(72.82 MB)
    and unpack it
  6. Go to the folder with the unpacked files, right-click with the Shift key held down, select "Open command window" in the pop-up menu
  7. Enter "adb devices" in the command window, a list of connected devices should appear
  8. If the list is empty, then we check the connection and correctness of the driver installation.
  9. Enter “adb remount”
  10. Edit the file "build.prop" in any of the above ways.
  11. Enter "adb push samsungapps.apk / system / app" and press the "Enter" key
  12. Enter "adb push gearmanagerstub.apk / system / app" and press the "Enter" key
  13. Enter "adb push svoice-signed.apk / system / priv-app" and press the "Enter" key
  14. Enter "adb push samsungservice.apk / system / priv-app" and press the "Enter" key
  15. Enter “adb shell” and press the “Enter” key, enter “su” and press the “Enter” key
  16. Enter "chmod 644 /system/app/samsungapps.apk" and press the "Enter" key
  17. Enter "chmod 644 /system/app/GearManagerStub.apk" and press the "Enter" key
  18. Enter "chmod 644 /system/priv-app/svoice-signed.apk", enter "exit" and press "Enter"
  19. Enter "chmod 644 /system/priv-app/samsungservice.apk", enter "exit" and press "Enter"
  20. Enter "adb reboot recovery" and press the "Enter" key (only for custom recovery!)
  21. After launching the recovery tap "Wipe">"Advanced Wipe">choose Dalvik and Cache>We confirm with a swipe, we return to the home screen of recovery
  22. Tap the button "Advanced">Tap "Fix Permissions">we confirm with svaypom, we reboot the phone
  23. Open Settings>Accounts and sync and set up a Samsung account
  24. Launch S Voice and agree and accept all license agreements (TOS)
  25. Enter “adb remount”
  26. Enter “adb shell” and press the “Enter” key, enter “su” and press the “Enter” key
  27. Enter “cd / system / app”, press the “Enter” key, enter “rm svoice-signed.apk”, press the “Enter” key, enter “exit” and press the “Enter” key
  28. Enter "adb push Svoice-Final.apk / system / priv-app" and press the "Enter" key
  29. Enter “adb shell” and press the “Enter” key, enter “su” and press the “Enter” key
  30. Enter "chmod 644 /system/priv-app/Svoice-Final.apk" and press the "Enter" key, enter "exit" and press the "Enter" key
  31. Enter "adb reboot recovery"
  32. After launching the recovery tap "Wipe">"Advanced Wipe">choose Dalvik and Cache>We confirm with a swipe, we return to the home screen of recovery
  33. Tap the button "Advanced">Tap "Fix Permissions">we confirm with svaypom, we reboot the phone
  34. Launch Samsung Apps, find and install the Gear Manager
  35. Launch Gear Manager and set up a connection with the clock
  36. We set up notifications according to the instructions given.

The authors of the material are: Carbonywyre , thesparky007 , mpogr .
Original article is here

Fix "infinite connection with Gear 2 / Neo":
Attention! The efficiency of this material was tested only on HTC (One (M7), One (M8), One DualSim) and Google (Nexus 5) devices! MAYBE, the information given here is applicable to devices from other manufacturers, but neither the authors nor the translator of the article are able to verify this!

The solution to the problem of the "endless" process of binding the clock and the device. Most often it arises because for some reason Gear Manager cannot unpack and install several .apk files inside it. Therefore, a way out of this situation is to manually install the files in the sequence described below:
  1. DownloadingAttached fileConnecting-Fix.zip(17.19 MB)
  2. We transfer to the phone
  3. Unpack the contents
  4. Install all unpacked .apk files
The authors of the material are: Carbonywyre , thesparky007 , mpogr .
Original article is here

Enable notifications
Attention! The efficiency of this material was tested only on HTC (One (M7), One (M8), One DualSim) and Google (Nexus 5) devices! MAYBE, the information given here is applicable to devices from other manufacturers, but neither the authors nor the translator of the article are able to verify this!

  1. Launch “Gear Manager”>Tap "Notifications"
  2. Remove the checkbox "Limit notifications"
  3. Tapnite "1) GENERAL NOTICES"
  4. Tap "Enable"
  5. In the window that opens, check the box next to "Gear Manager"
  6. Return to the Notifications section in Gear Manager
  7. Choose the application whose notifications you want to receive on the clock

The authors of the material are: Carbonywyre , thesparky007 , mpogr .
Original article is here

Pairing watches with Google Nexus 5 with stock firmware (Android KitKat) and other custom firmware based on AOSP 4.4.x
I spent some time and investigated why pairing my watch with my Google Nexus 5 doesn’t go as smoothly as my friend’s HTC One M8.

As far as I know, in systems based on AOSP / Kit Kat 4.4.x, the policy of granting rights at the system level for .apk files has changed in the direction of toughening. Now it is not enough to place the .apk file in the system directory, now it should be located in the / system / priv-app directory. Because of this, when the application tries to install / download additional packages (Note: this means that the main installer of the application is not in the system folder), they are either not installed (silently ignored), or the installation dialog box is displayed, that the application has the permission of INSTALL_PACKAGES and DELETE_PACKAGES. When I installed "SamsungApps" in the \ priv-app \ directory, all the additional downloadable packages (Samsung Billing, In App Purchasing and Push Service) were installed without any problems. However, when these dependent .apk files were installed, they were placed by the installer in the non-system / data / app directory, because of this the signatureOrSystem permission was prohibited.

I hoped that if I moved the “Gear Manager’s” .apk file to / system / priv-app * before * the first launch of the application, this would allow it to install all dependent .apk files without problems. But as it turned out, only four or five dependent files are automatically installed, and on the rest, the installation can “loop” and never complete.

Summing up, I give my version of the pairing procedure:
  1. Download:
    1. Attached fileSamsungservice2_K.apk(6.55 MB)
    2. Attached fileN_SamsungApps_14040104.21.007.0_HHP_TW_newkey_0401.apk(16.74 MB)
    3. Attached fileS-Voice_Android_phone.apk(25.67 MB)
    4. Attached fileGearManagerStub.apk(948.78 KB)
    5. Attached filesvoice-signed.apk(28.69 MB)

  2. We transfer N_SamsungApps_14040104.21.007.0_HHP_TW_newkey_0401.apk, svoice-signed.apk and GearManagerStub.apk to the / system / priv-app folder
  3. Change the attributes of copied files -rw-rw-r-- (664) or (644), group 0: root
  4. We transfer Samsungservice2_K.apk to the / System / priv-app folder and change the file attributes as in the previous paragraph
  5. Restart the phone
  6. Launch S Voice and agree and accept all license agreements (TOS)
  7. Go to the folder / system / priv-app and delete S Voice
  8. We transfer S-Voice_Android_phone.apk to the / system / priv-app folder and change the file attributes
  9. Restart the phone
  10. Open Settings>Accounts and sync and set up a Samsung account
  11. We launch S-Voice, it will fall right after launch - this is normal
  12. Launch the application store Samsung Apps
  13. Find and download Gear Manager
  14. Launch Gear Manager
  15. Run the pairing setting with the clock (it will end with an error, because no additional packages are installed).
  16. Manually install additional packages fromAttached fileConnecting-Fix.zip(17.19 MB)

    • ConnectionManager
    • HostManager
    • SAFTCore,
    • SAFotoProicder,
    • SAccessoryService,
    • Gear2Plugin,
    • goproviders,
    • SANotiProvider,
    • SANSyncProvider,
    • saproviders,
    • SAWeatherProvider (Do not install!),
    • TextTemplateProvider

  17. Start the Gear Manager, set up the pairing with the clock, agree with the licenses
  18. We transfer the following applications to / system / priv-app (You can use the program "/ system / app mover", but you can do it manually):
    • Gear manager
    • Gear2plugin
    • Samsung billing
    • Hostmanager


The last four .apk files contain the permissions INSTALL_PACKAGES and DELETE_PACKAGES in their manifests and most likely should have permissions at the system level. Some of the other .apk files have "non third-party" permissions and may also require increased privileges, but I haven’t figured it out yet.

In the end, I have:
  • Ability to install apps for Gear 2 from Samsung Apps
  • Ability to delete applications without emergency closing Gear2Plugin
  • The ability to pay for applications in Samsung Apps by credit card


I hope that in the new versions of Samsung Apps and Gear Manager, Samsung will correct the errors described above and all additional packages will be installed in the correct directories.

P.S. S-voice did not work for me.

The author of the material is: mpogr .
Original article is here


miscellanea

Changes in the cap
1103.2019 Added a link to install VK on the clock.
07/19/2015 New version of Wear Lollipop
07.13.2015 Update of the caps
06/29/2015 I updated the cap, added the spoiler "Wear Lolipop", and edited the Wear cap (now it's "Wear 4.4.3W", plus updated the instructions)
06/29/2015 Wear News
06/27/2015 I added a video instruction on installing Wear into a spoiler "installation"
05/24/2015 Cap in the process of updating. Added a spoiler with Wear, added links to Tizen firmware for Gear 2 and Gear 2 NEO. A little "combed" hat.
06/17/2014 Updated official firmware for Gear 2
06/17/2014 Updating articles, changing the formatting of the header, editing errors
06/03/2014 Adding articles, creating mirrors of firmware on file sharing
05/26/2014 Section opening, content filling started

Attention: After updating the firmware R380XXUBNK2 the clock shows an hour less (late) . Decision .

Everything that you do - you do at your own peril and risk! Authors of software, instructions and
Manuals are not responsible for the failure of the device in case of your wrong actions!


Also please use more actively.User Moderated Attached ImageAttached Image


For suggestions for improving the theme, updating the caps, please contact me atQMS

Your curatorNospire


Post has been editeddfgigger - 06.05.19, 02:16
Reason for editing: Links to recent unread messages.



Rep: (939)
Something links to firmware from the header do not work ...



Rep: (11)
alex.shastov @ 05/27/2014, 00:30*
Something links to firmware from the header do not work ...

need to be registered onhttp://www.sammobile.com/firmwares/



Rep: (3)
I see no reason for now



Rep: (17)
tango71 @ 06/03/2014, 23:38*
Root did not try on the clock?

Today, I’ll test my performance, if everything “functions”, then I’ll translate the instructions in the next couple of days: happy: After a quick glance at the original, it became clear that the instructions would have to be greatly complemented, I’m very briefly described the comrad with XDA: happy:

Eagleonok @ 06/04/2014 02:24*
I see no reason for now

So far there is really little sense, but in the future you will still have to get root, at least to install custom and "patched" widgets ...

Dr.Di0NiS @ 06/04/2014 08:00*
Today I will test the performance

Tested! The method is quite efficient and I got root rights on my watch without any problems. Everything is quite simple and in order not to be unfounded I provide a screenshot of the process of enabling the root account on the clock from the SDB console. It looks a bit different from the way it looks for a guy with XDA, the reason is that I used the ConEmu console emulator (its window title is visible in the screenshot) and called SDB commands from under Far Manager:
Attached Image

In general, I repeated all the little useless murkiness behind my American colleague, the only thing that really interests us is the result of the "whoami" command. It is he who gives the name of the current user of the system. In my case, as you can see, this is root.

P.S. A little later I will do a full instruction with writing the whole process in order to reduce the number of "bricks";)

Post has been editedRubaka - 04.06.14, 22:12



Rep: (3)
Dr.Di0NiS

Can you try to turn off the sound of the camera?
Muting camera sounds


Post has been editedtango71 - 04.06.14, 20:34



Rep: (17)
Tango71 @ 06/04/2014, 23:31*
Can you try to turn off the sound of the camera?
Muting camera sounds

Easy! : happy: Screenshot of the process of applying the patch on the screen under the spoiler:
Attached Image
The patch works great and jamming the camera completely, a brief report confirming this can be seen onYouTube



Rep: (3)
Full collection of firmware



Rep: (1)
Dr.Di0NiS
Hello! Help, please, tomorrow is a test, I can not make a root to the end. firmware R380XXU0BND8. there is no problem with one. Sdb ran through the command line, but does not see the watch.



Rep: (1)
Attached Image


Post has been editedNospire - 27.01.17, 23:51



Rep: (17)
* saniman may not have installed (or installed crookedly) clock driver. Open the device manager and see if there are any unknown devices, if there is, then it makes sense to install the Samsung Andorid USB Driver for Windows driver from the “Drivers and Utilities” section. The second possible problem: cable glitch ... Is it alive? Do not bend? Not broken?

Add1: Does anything happen when you connect a clock to a computer? MTP device mounted?

Add2: It’s not necessary to launch cmd from Far’s ;-) You can just press Ctrl + O (this is hiding Far’s panels) ...


Post has been editedDr.Di0NiS - 11.06.14, 08:38



Rep: (1)
* Dr.Di0NiS,
cable is flat, ideally. from S4 BE, bought in April. (aware of its fragility)
hours of norms are connected (screenshots of PC and Device Manager)
last night I even managed to reflash them from R380XXU0BND8 to R380XXU0BNDD. also downloaded the corresponding root file. zero results.
There is no information anywhere about sdb. Should the clock be turned on? or in download mode?
Attached Image
Attached Image




Rep: (17)
* saniman judging by the first screenshot, the clock is normally picked up, the MPT device is mounted, which means that the cable is quite lively, if you updated the firmware, that means that the “firmware” drivers were installed exactly ... For the root firmware, the sequence of actions is the same as to upgrade firmware. The clock should be transferred to the "Download" mode from rekoveri, the rootfs.img file is unpacked from the archive and flashed with Odin by analogy with the firmware, with the same exact settings (try disabling the automatic rebooting of the clock with Odin, it causes a steady failure for me Odin'a flash something)!



Rep: (1)
* Dr.Di0NiS,
rootfs.img Odin'om put normally, at the end of the procedure, the clock is restarted, as expected. And then I do not know how to activate the root? When the hours are on, I connect to the PC and go to cmd. I prescribe the sdb devices does not see the clock.



Rep: (17)
* saniman root is activated by the "sdb root on" command, you can verify that you can root using the "whoami" command, it displays the name of the current user.

Hmm ... Interesting situation, the clock is mounted as an MTP device, but sdb cannot communicate with them ... And before updating the firmware and stitching the root, sdb connected to the clock? Tried to execute commands?



Rep: (16)
Dr.Di0NiS @ 06/11/2014, 14:28*
The clock is mounted as an MTP device, but sdb cannot communicate with them.

Is USB debugging enabled?



Rep: (1)
* Dr.Di0NiS,
haven't tried it before. I bought it and immediately threw the root.
I think on the other pc to repeat the whole procedure.
* Tim-Dnepr,
of course included!



Rep: (3)
Has anyone tried to install firmware R380XXU0BNE5 on Gear-2?



Rep: (17)
Tango71 @ 06/11/2014, 21:45*
Has anyone tried to install firmware R380XXU0BNE5 on Gear-2?
I will update on it tomorrow, I will unsubscribe about the results!

Posted 06/11/2014 20:21:

I think on the other pc to repeat the whole procedure.
as an option, you can reset the clock to the factory settings (root will not fly off - checked!), enable USB debugging after resetting, and try to contact the new ...



Rep: (3)
Dr.Di0NiS
Instructions are already in preparation, I'll post it in two or three days ...


I hope the promise is not to wait for three years: blush:

And another question after turning off the sound of the camera, voice control camera remains?



Rep: (17)
And another question after turning off the sound of the camera, voice control camera remains?
Yes, everything remains because You just rename a couple of sounds that mimic the sound of the shutter (the same click of the camera that is heard when shooting) and the camera application “not seeing” files cannot reproduce the sound, it does not affect the rest of the functionality ...

Add: Updated for firmware R380XXU0BNE5 with a Spanish ID, everything works fine, but did not notice the difference, except for the changed lock screen settings icon, at least at first glance. Root also got up without any problems.


Post has been editedDr.Di0NiS - 13.06.14, 04:53


Full version    

Help     rules

Now: 07/20/19, 10:09 PM