Related
Some of you are familiar with the adb install command.
Is there an equivalent of it in the terminal emulator?
Hi,
Adb is used from the computer and terminal emulator is used from the phone.
What are you trying to do?
I'm trying to install an app without using astro.
your best choise would be
cd to the location of the apk file and use
adb install appname.apk
or adb install C:\folder\appname.apk
think thats the correct way im not sure how you can install it in the terminal i knwowho to remove it.. but not install :/
Install .apk via Terminal EMulator
1) Place the .apk on the root of your SD card (for simplicity)
2) Type "su"
3) cd into the destination of your .apk (in this case it will be cd /sdcard)
4) Use "install "name of .apk" /"destination"/"name of .apk"
su
cd /sdcard
install com.makemobile.coursepro.apk /system/app/com.makemobile.coursepro.apk
further example:
install "space" com.makemobile.coursepro.apk "space" /system/app/com.makemobile.coursepro.apk
This will install the app on your phone using the Terminal Emulator. The destination location can change as well.
Additional help: http://www.busybox.net/downloads/BusyBox.html
On the flip side, could you uninstall from the ext2 partition this way?
install on/from ext2
not sure...I'll looks into this. I had my apps and data on my sd however, it seemed a little buggy and inconsistant. It may have been due to using original G1 1gb class 2 card.
-let me know if you find out first.
a1t said:
1) Place the .apk on the root of your SD card (for simplicity)
2) Type "su"
3) cd into the destination of your .apk (in this case it will be cd /sdcard)
4) Use "install "name of .apk" /"destination"/"name of .apk"
su
cd /sdcard
install com.makemobile.coursepro.apk /system/app/com.makemobile.coursepro.apk
further example:
install "space" com.makemobile.coursepro.apk "space" /system/app/com.makemobile.coursepro.apk
This will install the app on your phone using the Terminal Emulator. The destination location can change as well.
Additional help: http://www.busybox.net/downloads/BusyBox.html
Click to expand...
Click to collapse
nevermind..........used astro file manager and it worked fine
help
what's 'cd' ? the emulator is already installed on the phone ?
i'm trying to install an app but i don't understand the adb method. someone can help me ?
thanks
MikeMadden said:
what's 'cd' ? the emulator is already installed on the phone ?
i'm trying to install an app but i don't understand the adb method. someone can help me ?
thanks
Click to expand...
Click to collapse
cd is a command, meaning "change directory". Which is used to move your location on the system.
MikeMadden said:
what's 'cd' ? the emulator is already installed on the phone ?
Click to expand...
Click to collapse
cd is a *nix command , it is short for 'change directory' and it... changes directory
MikeMadden said:
i'm trying to install an app but i don't understand the adb method. someone can help me ?
thanks
Click to expand...
Click to collapse
it depends on what the app is
your best bet would be to get an app called 'Astro file manager' from the market
Its quite easy, so I won't go into further detail
Which to be honest is a fair trade
APrinceAmongMen said:
Some of you are familiar with the adb install command.
Is there an equivalent of it in the terminal emulator?
Click to expand...
Click to collapse
Some people have mentioned the `install' command from BusyBox, but this won't quite do what you probably want. To invoke the full Android package installation experience--the complete equivalent of `adb install'--you're looking for `pm install'. It takes the same arguments that `adb install' does, checks signatures, creates the appropriate user accounts, etc. so the package is installed the Android way. You can also use `pm uninstall' to remove a package (and as with `adb install', the "-k" option keeps its data around).
The `am' and `pm' commands are both underdocumented, but can be terribly useful. `am' can issue arbitrary Intents, including some Extra values. `pm' has other features not mentioned here, but which are shown in the help text.
olearyp said:
Some people have mentioned the `install' command from BusyBox, but this won't quite do what you probably want. To invoke the full Android package installation experience--the complete equivalent of `adb install'--you're looking for `pm install'. It takes the same arguments that `adb install' does, checks signatures, creates the appropriate user accounts, etc. so the package is installed the Android way. You can also use `pm uninstall' to remove a package (and as with `adb install', the "-k" option keeps its data around).
The `am' and `pm' commands are both underdocumented, but can be terribly useful. `am' can issue arbitrary Intents, including some Extra values. `pm' has other features not mentioned here, but which are shown in the help text.
Click to expand...
Click to collapse
'pm install' often fails with [INSTALL_FAILED_INSUFFICIENT_STORAGE]
which used to frustrate me no end ..
simple shell script
Code:
am start -a android.intent.action.VIEW -t application/vnd.android.package-archive -d file://$1
just pass the full path e.g
sh /sdcard/installapk.sh /sdcard/theapp.apk
and it pops up the Android Package installer
Firerat said:
'pm install' often fails with [INSTALL_FAILED_INSUFFICIENT_STORAGE]
which used to frustrate me no end ..
Click to expand...
Click to collapse
Interesting. I wonder if that's related to A2SD or a particular implementation, and pm getting confused as a result? Still, I like the idea of sending the VIEW intent to bring up the package installer. Good snippet.
I just cp the files to /system/sd/app/
from Windows Command prompt, and after switching to the folder containing the .apk file, type:
adb install filename.apk
if it is a reinstall:
adb install -r filename.apk
you could also push the file to the app folder. I use this method to push system apk:
adb remount <<<< you have to remount since you're going to mess with a sys folder
adb push filename.apk /system/app
seriously useful thread... especially after for some weird reason certain apps fail to install using the default Android installer. *cough* Radiant *cough*
Thanks for the help guys. Btw install command doesn't work. To clear things out for some clueless person like I am :
1. Open Terminal Emulator
2. Type -
su
cd /dir
pm install appname.apk
3. Done!
Example -
su
cd /sdcard
pm install AstroFileManager.apk
Hope that can help!
rajasyaitan said:
Thanks for the help guys. Btw install command doesn't work. To clear things out for some clueless person like I am :
1. Open Terminal Emulator
2. Type -
su
cd /dir
pm install appname.apk
3. Done!
Hope that can help!
Click to expand...
Click to collapse
This is very helpful, thanks!
rajasyaitan said:
Thanks for the help guys. Btw install command doesn't work. To clear things out for some clueless person like I am :
1. Open Terminal Emulator
2. Type -
su
cd /dir
pm install appname.apk
3. Done!
Example -
su
cd /sdcard
pm install AstroFileManager.apk
Hope that can help!
Click to expand...
Click to collapse
Thanks big time. Installed perfectly although apk won't open...just got to find one that will.
Ok, I have fedora 11 installed on most of my computers, since i love this distro to death. My big thing was trying to get adb to work. This is my guide to get it to work, for now.
First things first. Navigate to /etc/udev/rules.d as root. Create a rules file called 50-android.rules (touch 50-android.rules). NOTE: You are better off looking at the contents and picking a rules number set other than what is listed. Sometimes udev is picky. For the newbies, so if any rules start with '50', then change the number by one or two, like 51 or 52. Paste this into the file:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
Make sure you use ATTRS, not ATTR or SYSFS, since this is a newer updated udev system.
After that, run udevadm control --reload-rules to reload your rules files. Now just run ./adb devices as root to make sure it recognized your HTC dream. I am working on this fix right now so you don't need to be root, keep patient. Now you can adb shell into your device either as root OR normal user, just as long as you start the server as root. This is a permissions problem, and hopefully I can fix this and/or find a fix soon.
I wrote this because i searched high and low through google, and only found a few good parts as far as a fix. Hopefully this helps a few people out there.
Just wondering if this has helped anyone. If not, delete this thread or do whatever with it....
I have adb on my eeepc 900 with f11 I believe this method works too as well. although it says it has been tested with ubuntu, it works pretty well with f11.
http://www.talkandroid.com/android-sdk-install-guide/
Installing The Android SDK
First you will need to download the Android SDK pack .zip archive, once downloaded find a suitable installation location on your machine and extract the zipped files.
Please note: This installation location will be referred to as $SDK_ROOT from now on through this tutorial
Alternatively you can add /tools to your root path which will prevent the need to specify the full path to the tools directory along with enabling you to run Android Debug Bridge (adb) along with other command line tools.
To add /tools:
Linux
1. Edit the ~/.bash_profile or ~/.bashrc files looking for a line that sets the PATH variable.
2. Add the full path location to your $SDK_ROOT/tools location for the PATH variable.
3. If no PATH line exists you can add the line by typing the following:
4. export PATH=${PATH}:<path to your $SDK_ROOT/tools>
Click to expand...
Click to collapse
It helped me, since the creation of the file my OpenSuSE 11.0 recognizes the phone perfectly
Thanks a lot for your hint.
thanks it helped me. ill be looking forward to getting it to work without root
just use sudo instead
Just a heads up for user's using Ubuntu 9.10, this isn't needed. I connected my G1 to it and ran ADB with no adjustments to udev or anything else.
Pretty much it works out of the box.
Here is my version
download the .tgz file from googlecode
http://developer.android.com/sdk/index.html
sudo tar -xzvf android-sdk_r3-linux.tgz
Click to expand...
Click to collapse
Code:
sudo gedit ~/.bash_profile
heres my bash_profile
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH=$PATH:/android-sdk-linux/tools
Click to expand...
Click to collapse
logout
login
connect android g1 device via usb to pc
open a terminal
Code:
adb devices
if you cant get a device try it with superuser.
Don't you think that this is all just a little bit excessive?
To make it work in F11, just do this;
Download SDK, extract.
To use, type:
/path/to/sdk/tools/adb
Another option is to edit the /etc/profile and add
PATH=$PATH:/<Path to android-sdk>/tools
This option will allow any user to use the adb tools when logged in or if you
su -
into another user
I wrote a short guide as well for Windows and Ubuntu. Might help others.
Unfortunately, as anyone with a passing acquaintence with ADB knows, the scrolling issue can be a killer. I swear the other day I pressed "up" twice and it composed "rm /sdcard/rootfs.img /sdcard/system.ext2" and executed it. We run Android on our SD's btw.. Was not cool. Instead, I use ADB via telnet and it works beautifully. Here's how:
Code:
adb shell telnetd &
adb forward tcp:9999 tcp:23
Now type this: "telnet localhost 9999"
Enter "root" and hit enter
Finally update PATH: "export PATH=/usr/bin:/usr/sbin:/bin:/sbin:/system/sbin:/system/bin:/system/xbin:/system/xbin/bb:/data/local/bin"
Okay, so 4 lines to enter and you have a "regular, sane" shell connection to the phone and you can actually scroll through history and text without it jumbling the text and executing random code. Enjoy.
lbcoder said:
Don't you think that this is all just a little bit excessive?
To make it work in F11, just do this;
Download SDK, extract.
To use, type:
/path/to/sdk/tools/adb
Click to expand...
Click to collapse
that works too as well but i would rather open up a terminal and type
sudo adb devices
sensimila said:
that works too as well but i would rather open up a terminal and type
sudo adb devices
Click to expand...
Click to collapse
WHY would you want to make it *MORE COMPLICATED*??
There is NO NEED for root.
/path/to/adb ...
THATS ALL.
This is kind of funny... i wrote this because i had trouble with it, so i am just sharing my fix...
In case this is interesting to someone:
The fix mentioned in the first post has to be applied to open SuSE x86 and x64 edition to make the G1 work. The external device works without it, but not the adb device.
Thanks again!
Just wanted to come and post that this does work with OpenSUSE 11.2 x86. Did this hoping to get adb to work with my LG Ally and it does. Thanks!
(Still) works for me on 64bit SUSE 11.4.
Before adding this file, I could not access my device with adb, received permissions errors.
Added this file, and I can shell into my device.
Permissions on adb itself was not the problem, it was access to the device when udev found it.
[edit]Actually used the lines from http://developer.android.com/guide/developing/device.html[/edit]
Hello all,
Please find attached the recovery and the ramdisk from the firmware.
I have no language knowledge ( C+, Java ) and hence cant help with getting a root.
Could someone please look at the files and help us achieve a root.
Thanks.
Ramdisk : http://www21.zippyshare.com/v/YI1WNBKI/file.html
Recovery: http://www21.zippyshare.com/v/VffwNEbb/file.html
Anyone here with rooting skills ?
tids2k said:
Anyone here with rooting skills ?
Click to expand...
Click to collapse
not too sure why sdb sdk command "sdb root on" exist if it's always permission denied haha, but i might have something little tricky to get root acces, still on it tought
Root would be awesome. Maybe @cipherswitch can give us some pointers as his Gear S root thread is well put together.
Jhfreeze said:
Root would be awesome. Maybe @cipherswitch can give us some pointers as his Gear S root thread is well put together.
Click to expand...
Click to collapse
I actually just picked up an S3 Frontier last week. I haven't really looked into it and and I'm not 100% sure what rooting will do to Samsung Pay but it's worth taking a look at.
cipherswitch said:
I actually just picked up an S3 Frontier last week. I haven't really looked into it and and I'm not 100% sure what rooting will do to Samsung Pay but it's worth taking a look at.
Click to expand...
Click to collapse
We need to do a insert exploit with a method like Magisk as rooting will trigger will Knox fuse and then Samsung pay will become unusable. Also there is actually an app that checks whether the device has been rooted or not in the watch itself. My suggestion would be to pack a binary with su.apk and then making an Odin flashable package, but then I'm not sure if it will proceed as the signature validation will fail.
tids2k said:
We need to do a insert exploit with a method like Magisk as rooting will trigger will Knox fuse and then Samsung pay will become unusable. Also there is actually an app that checks whether the device has been rooted or not in the watch itself. My suggestion would be to pack a binary with su.apk and then making an Odin flashable package, but then I'm not sure if it will proceed as the signature validation will fail.
Click to expand...
Click to collapse
Im fairly sure it will beacuse its not digitally signed by Sammy.
cipherswitch said:
I actually just picked up an S3 Frontier last week. I haven't really looked into it and and I'm not 100% sure what rooting will do to Samsung Pay but it's worth taking a look at.
Click to expand...
Click to collapse
i got access via sdb sheel to few sbin command like "pivot_root" and "switch_root" if this could help..
and i was able to use initrd scripts
Stupid question.
No idea if allready Gear S3 is rooted...
I was able to successfully root Tizen handsets with same method and same 1 file:
SM-Z130H
SM-Z300H
SM-Z300F
SM-Z200F
Procedure...
Copy file su into bin folder...
Easiest way... modify rootfs.img... then flash result with Odin.
Ehm... not tested with any Gear... but...
Maybe check this special Factory Firmware... aka Combination.
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
Extract rootfs.img ...
You will see su in bin folder:
/bin/su
In theory you could try now to use this su file... and inject in other rootfs.img... then flash.
Own risk!
Only as info.
I am to lazy to buy Gear S3 to check my theory...
Best Regards
adfree said:
Stupid question.
No idea if allready Gear S3 is rooted...
I was able to successfully root Tizen handsets with same method and same 1 file:
SM-Z130H
SM-Z300H
SM-Z300F
SM-Z200F
Procedure...
Copy file su into bin folder...
Easiest way... modify rootfs.img... then flash result with Odin.
Ehm... not tested with any Gear... but...
Maybe check this special Factory Firmware... aka Combination.
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
Extract rootfs.img ...
You will see su in bin folder:
/bin/su
In theory you could try now to use this su file... and inject in other rootfs.img... then flash.
Own risk!
Only as info.
I am to lazy to buy Gear S3 to check my theory...
Best Regards
Click to expand...
Click to collapse
Too bad root checker will spot that su binary and blow warranty void fuse than farewell spay
Too bad root checker will spot that su binary and...
Click to expand...
Click to collapse
Root Checker on Z-Mobiles only disable access to FOTA Server...
Not really deep investigation... but an app could check Root... maybe not Bootlaoder...
Something like this...
com.samsung.rootdetection-syspopup ...
Maybe to remove the "App" which checks if su is present or not...
No idea how much Security inside Gear S3... but maybe if you compare difference between Combination "FTMA" Firmware... and normal...
Otherwise you would also loose warranty blabla with this file?
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
No idea yet. Only theory...
Best Regards
adfree said:
Root Checker on Z-Mobiles only disable access to FOTA Server...
Not really deep investigation... but an app could check Root... maybe not Bootlaoder...
Something like this...
com.samsung.rootdetection-syspopup ...
Maybe to remove the "App" which checks if su is present or not...
No idea how much Security inside Gear S3... but maybe if you compare difference between Combination "FTMA" Firmware... and normal...
Otherwise you would also loose warranty blabla with this file?
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
No idea yet. Only theory...
Best Regards
Click to expand...
Click to collapse
With official firmwares you can't loose warranty. As you mentioned this was an internal build with most of the apps scrapped.
I treid to mount the storage but getting write protection error. Trying to compile TWRP and test but unable to do so. @cipherswitch @DevALT. Some screenshots
I could create rootfs.img with su inside...
su file I would take from combination file...
Code:
COMBINATION-FTMA_R760XXU1APK3.tar.md5
rootfs.img I have at the moment only from this Firmware:
Code:
R760XXU1APK7_R760OXA1APK7.zip
And I have NO Gear Watch to test self.
So I "need" tester with balls and SM-R760 who is able to flash with Odin...
OWN risk!
I could do it and upload...
But to prevent waste my time...
I will try to "explain" first...
Before I was able to root my SM-Z130H...
I have used rooted GT-I9300 to create my modified rootfs.img...
Extracting files from rootfs.img under Windows was easy with Windows Tools...
But creation of valid rootfs.img is better to do with Linux...
Need few minutes to upload extracted su file... and to post few Commands for SDB... or ADB ...
Best Regards
Edit 1.
su added...
Taken from Combination Firmware...
MD5
Code:
B784CC4DBBC86EFCC308D239D1235CE0
Now this file "must" inject into folder bin in rootfs.img
Edit 2.
Here is example how I would do it with my rooted Tizen SM-Z130H... with Batch file... few Commands for SDB:
Code:
sdb root on
sdb push su /opt/usr/media/Others
sdb shell mount -t ext4 -o loop,rw /opt/usr/media/Others/rootfs.img /opt/usr/media/Others/2
sdb shell cp /opt/usr/media/Others/su /opt/usr/media/Others/2/bin
sdb shell cd /opt/usr/media/Others/2
sdb shell sync
pause
sdb shell cd /
sdb shell umount /opt/usr/media/Others/2
rootfs.img I would copy manually to folder Others...
For rooted Android device... replace sdb with adb... and few path changes...
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-R760
For Kernel related study... Source Code is available...
I was only to lazy to download...
But in theory also here in repos...
1 RPM is inside with su...
Will check after Download... "soon"...
Best Regards
Downloaded...
SM-R765_Opensource.zip
Extracted:
SM-R765_repos.tar.gz
Unpack:
coreutils-6.9.rpm
Bingo... su Binary is inside.
But still problem...
I don't know how to install RPM without ROOT access.
I can only install RPM if allready device is rooted...
So I only know this way to inject su into rootfs.img and create then valid TAR file to use with Odin...
Simple Copy and Paste solution.
Best Regards
adfree said:
I could create rootfs.img with su inside...
su file I would take from combination file...
Code:
COMBINATION-FTMA_R760XXU1APK3.tar.md5
rootfs.img I have at the moment only from this Firmware:
Code:
R760XXU1APK7_R760OXA1APK7.zip
And I have NO Gear Watch to test self.
So I "need" tester with balls and SM-R760 who is able to flash with Odin...
OWN risk!
I could do it and upload...
But to prevent waste my time...
I will try to "explain" first...
Before I was able to root my SM-Z130H...
I have used rooted GT-I9300 to create my modified rootfs.img...
Extracting files from rootfs.img under Windows was easy with Windows Tools...
But creation of valid rootfs.img is better to do with Linux...
Need few minutes to upload extracted su file... and to post few Commands for SDB... or ADB ...
Best Regards
Edit 1.
su added...
Taken from Combination Firmware...
MD5
Code:
B784CC4DBBC86EFCC308D239D1235CE0
Now this file "must" inject into folder bin in rootfs.img
Edit 2.
Here is example how I would do it with my rooted Tizen SM-Z130H... with Batch file... few Commands for SDB:
Code:
sdb root on
sdb push su /opt/usr/media/Others
sdb shell mount -t ext4 -o loop,rw /opt/usr/media/Others/rootfs.img /opt/usr/media/Others/2
sdb shell cp /opt/usr/media/Others/su /opt/usr/media/Others/2/bin
sdb shell cd /opt/usr/media/Others/2
sdb shell sync
pause
sdb shell cd /
sdb shell umount /opt/usr/media/Others/2
rootfs.img I would copy manually to folder Others...
For rooted Android device... replace sdb with adb... and few path changes...
Click to expand...
Click to collapse
gonna try that but i'll compile myself, not that I don't trust you but if it breaks my gear s3 i want to be the one who brick it
and also for weird reason sdb root on dosen't want to work on windows (will try on Linux tomorrow, work till very late :'( )
simple curiosity did you use RPM based distro to create your rootfs.img, if not witch distro are you using?
adfree said:
Downloaded...
SM-R765_Opensource.zip
Extracted:
SM-R765_repos.tar.gz
Unpack:
coreutils-6.9.rpm
Bingo... su Binary is inside.
But still problem...
I don't know how to install RPM without ROOT access.
I can only install RPM if allready device is rooted...
So I only know this way to inject su into rootfs.img and create then valid TAR file to use with Odin...
Simple Copy and Paste solution.
Best Regards
Click to expand...
Click to collapse
as i said upthere sdb root on command won't work on my windows and your solution seems to be the one will try everything tomorrow on my Linux pc will give an update right after
Code:
sdb root on
This is only possible, if you have allready su in bin folder:
Code:
/bin/su
For better understanding you could install Tizen Studio for instance...
https://developer.tizen.org/development/tizen-studio/download
It is possible to use SDB with Emulator...
Also Wearable Image available...
So you don't need to buy Tizen Mobile or other real device to test...
Simple study Image in Emulator...
You can delete su from Image and then play again with command:
Code:
sdb root on
simple curiosity did you use RPM based distro to create your rootfs.img, if not witch distro are you using?
Click to expand...
Click to collapse
I am Windows Fan Boy...
So first time... before my SM-Z130H was rooted. I've created rootfs.img with GT-I9300 (Android handset)...
Since my SM-Z130H is rooted... I am using this device.
I've never tried to create rootfs.img with Computer... with handset it was easier for me.
Maybe I find my old post with GT-I9300... to check my ADB Commands... because path could be different...
Best Regards
Edit 1.
2 years ago... I found "inspiration" by Gear Watch Thread...
https://forum.xda-developers.com/showpost.php?p=59457357&postcount=95
Then I did something like this:
https://forum.xda-developers.com/showpost.php?p=59478150&postcount=97
Important is for Odin... TAR file...
I can remember not all Windows TAR Packer were valid...
So I am using since over 2 years only IZArc Tool.
Also important... use only rootfs.img from Firmware which is on your device...
Not mix Firmware parts from different versions... to prevent funny sideeffects.
Best Regards
sorry for late update i couldn't test anything today no free time for me until wednesday but sure will I test everything there :l
DevALT said:
sorry for late update i couldn't test anything today no free time for me until wednesday but sure will I test everything there :l
Click to expand...
Click to collapse
No panic.
For few things I have spend many months... years.
And I understand Gear S3 is at the moment very expensive "test" device...
I can wait. :angel:
Maybe someone have halfdead Gear S3... with brroken display or Water Damage or something similar...
Best Regards
Hi,
After setting up my new Gear Sport I was very disappointed to find that the Samsung Pay app was missing. From what I can tell it should be pre-installed and ready to go. I believe this is because I have purchased a Korean model and activated it in the UK - the first thing it did was update the software, so I think it has taken an international firmware version which doesn't include the Pay app, because the Pay app is region specific? Is there a way to update the software to the correct UK version?
Device info:
Gear Sport SM-R600NZKAKOO (Korean model number)
Tizen 3.0.0.1
Software version R600XXU1AQJS
[edit]
After a quick look at the S3 forums I see some people had similar issues and some were able to flash the ROM with the country version they needed:
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-classic-sm-r770-t3526747
I guess I'll have to wait until the UK ROM for the Sport is available to download somewhere...
Gear Sport SM-R600NZKAKOO (Korean model number)
Click to expand...
Click to collapse
Where do you have this info?
From the Box?
Or is in SM-R600 possible to check this in About device info or via Code?
I have no SM-R600 to check self.
Maybe we have now all incredients... to do something similar on SM-R600...
Like few users did with SM-R760 or SM-R770...
Best Regards
adfree said:
Where do you have this info?
From the Box?
Click to expand...
Click to collapse
Yes it is on the side of the box. In the device information the model is listed simply as SM-R600. I believe the additional letters after specify the colour and the region.
I hoped they made it easier to check if Product Code on Box match written Software data in Gear...
Still for normal end user not visible without using Tools...
SM-R600NZKAKOO
UK Sales Code/CSC is IMHO:
Code:
BTU
Last 3 letter... of Product Code.
On Gear S3 Forum...
Few users changed successfully to Sales Code USA:
Code:
XAR
And Gear S3 started to work with Samsung Pay... in:
India
For instance...
------------------------------------------------------------------------------------------
Code for identify of written/active CSC... Sales Code seems different in Tizen 3
Code:
vconftool get -t string db/csc/salescode
This Command worked on Tizen 2.3... but now Permission...
Strange... now CSA folder readable...
So maybe someone with SM-R600 could check if this work with SDB.
Code:
cat /csa/csc/csc-active-customer.inf
and/or just for fun
Code:
cat /csa/imei/prodcode.dat
-------------------------
These Codes only to find out, what is set/written on device
Best Regards
adfree said:
I hoped they made it easier to check if Product Code on Box match written Software data in Gear...
Still for normal end user not visible without using Tools...
SM-R600NZKAKOO
UK Sales Code/CSC is IMHO:
Code:
BTU
Last 3 letter... of Product Code.
On Gear S3 Forum...
Few users changed successfully to Sales Code USA:
Code:
XAR
And Gear S3 started to work with Samsung Pay... in:
India
For instance...
------------------------------------------------------------------------------------------
Code for identify of written/active CSC... Sales Code seems different in Tizen 3
Code:
vconftool get -t string db/csc/salescode
This Command worked on Tizen 2.3... but now Permission...
Strange... now CSA folder readable...
So maybe someone with SM-R600 could check if this work with SDB.
Code:
cat /csa/csc/csc-active-customer.inf
and/or just for fun
Code:
cat /csa/imei/prodcode.dat
-------------------------
These Codes only to find out, what is set/written on device
Best Regards
Click to expand...
Click to collapse
sh-3.2$ cat /csa/csc/csc-active-customer.inf
SEK
sh-3.2$ cat /csa/imei/prodcode.dat
SM-R600NZBASEK
sh-3.2$
anybody managed to solve the issue? having the same problem with the same Korean watch
We have meanwhile 2 Combination Firmware...
https://forum.xda-developers.com/gear-sport/help/sm-r600-firmware-odin-repair-study-t3688495/page3
Code:
COMBINATION-FT30_R600XXU1[B]AQI6[/B].tar.md5
AQI6 seems no luck to change CSC...
Code:
COMBINATION-FT30_R600XXU1AQL1.tar.md5
I got no feedback... no idea if same result...
Code:
COMBINATION-FT30_R600XXU1AQI4.tar.md5
Also no idea, but this is not yet for free available... only on paid sites..
Best Regards
Only as info. Working solution now also for SM-R600 possible:
https://forum.xda-developers.com/showpost.php?p=76007649&postcount=41
And few posts later... with SDBTool:
Code:
launch_app csc-manager.csc-pre-configuration
SDB + infos how to connect are here:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
Best Regards
Many thanks!! I ran the code and managed to change my configuration to UK region (BTU) and reset the device which installed Samsung Pay!
https://forum.xda-developers.com/showpost.php?p=76007649&postcount=41
A few details as I am very much a novice - others may find useful (edited to add more info):
SDB = Software Development Bridge - it comes with the Tizen development studio. It's an executable that lives in the tizen tools folder and you run using a cmd shell (if on windows)
First I had to install Java SE development kit 8 (8u162 for windows - http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html)
Then I had to add a new windows environment variable called JAVA_HOME which points to the Java install directory (C:\Program Files\Java\jdk1.8.0_162) and reboot before Tizen studio would install
I installed Tizen studio - https://developer.tizen.org/
Now I could run the sdb executable on windows command line from the Tizen install folder
To get the Gear sport to connect to sdb I had to enable debug mode on the gear, disconnect it from my phone, connect to the wifi and run the connect command
Here's all the code I ran in the cmd shell:
Code:
cd "C:\tizen-studio\tools"
sdb connect <[I]gear ip address[/I]>
sdb shell
launch_app csc-manager.csc-pre-configuration
Then the region selection popped up on the Gear screen.
Thanks again! :good:
No ZIP for canada
davesing33 said:
Many thanks!! I ran the code and managed to change my configuration to UK region (BTU) and reset the device which installed Samsung Pay!
https://forum.xda-developers.com/showpost.php?p=76007649&postcount=41
A few details as I am very much a novice - others may find useful (edited to add more info):
SDB = Software Development Bridge - it comes with the Tizen development studio. It's an executable that lives in the tizen tools folder and you run using a cmd shell (if on windows)
First I had to install Java SE development kit 8 (8u162 for windows - http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html)
Then I had to add a new windows environment variable called JAVA_HOME which points to the Java install directory (C:\Program Files\Java\jdk1.8.0_162) and reboot before Tizen studio would install
I installed Tizen studio - https://developer.tizen.org/
Now I could run the sdb executable on windows command line from the Tizen install folder
To get the Gear sport to connect to sdb I had to enable debug mode on the gear, disconnect it from my phone, connect to the wifi and run the connect command
Here's all the code I ran in the cmd shell:
Code:
cd "C:\tizen-studio\tools"
sdb connect <[I]gear ip address[/I]>
sdb shell
launch_app csc-manager.csc-pre-configuration
Then the region selection popped up on the Gear screen.
Thanks again! :good:
Click to expand...
Click to collapse
Thank you very much, that worked like charm ! However, there is just one problem now. When I try to add my VISA card, it wants me to enter the ZIP code (5 digit US code) and I apparently live in canada and have an alphanumeric code. Is there a workaround ?
Rammy_sd said:
Thank you very much, that worked like charm ! However, there is just one problem now. When I try to add my VISA card, it wants me to enter the ZIP code (5 digit US code) and I apparently live in canada and have an alphanumeric code. Is there a workaround ?
Click to expand...
Click to collapse
Yes, there is... Only use the numbers of your postal code and add 2 zeros at the end. For example V6T 1Z4 would be 61400.
Happy to see this is working for others!
Cheers
i get a failed to connect to remote target message. ... any ideas?
any ideas?
Click to expand...
Click to collapse
If you mean SDB...
Then maybe check this:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
If not help...
Then maybe helpfull if you post screenshot... or Copy & Paste of text output...
I mean you see an Error message?
Can you Copy & Paste it...
Best Regards
Hi there, i am right at the end of the process of installing the modded samsung health monitor app and ADB etc but i have an error right at the end which is killing me.
This is it here:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb -s "IP address" install Watch.SHM.MOD.1.1.0.215.dante63.apk
error: device 'IP address' not found
adb: error: failed to get feature set: device 'IP address' not found
- waiting for device -
I think it is probably down to the last instruction which is this one:
Now, set your watch aside, type the following ADB command, and hit Enter to install the modded Samsung Health Monitor app on the watch. For this command to work as intended, you need to have the modded Samsung Health Monitor APK in the same directory as the file labeled cmd-here. Also, replace the X in the command mentioned below with the current version number of the APK.
adb -s "IP address" install Watch.SHM.MOD.X.X.X.XXX.dante63.apk
I have put the version number in as i downloaded it 1.1.0.215
I am unclear though on where i am supposed to make sure the apk is in relation to 1.1.0.215
Am i supposed to make sure the APK on my phone is in the same folder as what????? where does the cmd-here file come from ?
Help would be appreciated before i launch the phone towards a crash landing in mild temper LOL
Did you enable wireless debugging on your watch?
naked123 said:
Did you enable wireless debugging on your watch?
Click to expand...
Click to collapse
yep certainly did, and adb connectee so i allowed it
Try using wear installer 2
Sleepwalker54321 said:
Hi there, i am right at the end of the process of installing the modded samsung health monitor app and ADB etc but i have an error right at the end which is killing me.
This is it here:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb -s "IP address" install Watch.SHM.MOD.1.1.0.215.dante63.apk
error: device 'IP address' not found
adb: error: failed to get feature set: device 'IP address' not found
- waiting for device -
I think it is probably down to the last instruction which is this one:
Now, set your watch aside, type the following ADB command, and hit Enter to install the modded Samsung Health Monitor app on the watch. For this command to work as intended, you need to have the modded Samsung Health Monitor APK in the same directory as the file labeled cmd-here. Also, replace the X in the command mentioned below with the current version number of the APK.
adb -s "IP address" install Watch.SHM.MOD.X.X.X.XXX.dante63.apk
I have put the version number in as i downloaded it 1.1.0.215
I am unclear though on where i am supposed to make sure the apk is in relation to 1.1.0.215
Am i supposed to make sure the APK on my phone is in the same folder as what????? where does the cmd-here file come from ?
Help would be appreciated before i launch the phone towards a crash landing in mild temper LOL
Click to expand...
Click to collapse
Did you use the watches IP address instead of the text "IP address"?
Did you connect your watch via adb first?
Apache config:
adb connect x.x.x.x
Yes and yes
Its easy to make a mistake in the process ( happened to me).
Best is to start from step 1 again and carefully follow all instructions.
Use the TAB key to autocomplete file names and directories in a command line interface.
That way you're sure that it's actually the right name