Amazfit watch diswarn - connection lost notifications on the watch - Amazfit

Hi! I came from 4pda.ru and want to introduce my own shell script that notificates you if the watch losts connect with smartphone.
It can be installed at watch with unlocked bootloader.
In my tests it has no effect on the battery lifetime.
Script can be customized via diswarn_scenario.txt that stored at watch in the root of sdcard memory and can be edited with Notepad.
For use it you have to unrar attachment at C:\ and run diswarn_installer.cmd
UPD: file reloaded with install issue fix
UPD2: Added new version 4.1. More compatibility with newest roms

kenas said:
Hi! I came from 4pda.ru and want to introduce my own shell script that notificates you if the watch losts connect with smartphone.
It can be installed at watch with unlocked bootloader.
In my tests it has no effect on the battery lifetime.
Script can be customized via diswarn_scenario.txt that stored at watch in the root of sdcard memory and can be edited with Notepad.
For use it you have to unrar attachment at C:\ and run diswarn_installer.cmd
Click to expand...
Click to collapse
Hi buddy, I'm having some trouble with your script. This is what I get on last step when autorun_patch.sh starts:
PHP:
/system/bin/autorun_patch.sh[5]: cat: /system/bin/lmkd.sh: No such file or directory
Initial state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 0
/system/bin/autorun_patch.sh[58]: stat: not found
/system/bin/autorun_patch.sh[58]: [: 60000: unexpected operator/operand
Final state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 0
Autorun patch ERROR. Contact with Kenas at 4pda.ru
remount succeeded
Pacefied rom v1.2.41 Rel.30 and unlocked BL. Any clue?

Saratoga79 said:
Hi buddy, I'm having some trouble with your script. This is what I get on last step when autorun_patch.sh starts:
PHP:
/system/bin/autorun_patch.sh[5]: cat: /system/bin/lmkd.sh: No such file or directory
Initial state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 0
/system/bin/autorun_patch.sh[58]: stat: not found
/system/bin/autorun_patch.sh[58]: [: 60000: unexpected operator/operand
Final state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 0
Autorun patch ERROR. Contact with Kenas at 4pda.ru
remount succeeded
Pacefied rom v1.2.41 Rel.30 and unlocked BL. Any clue?
Click to expand...
Click to collapse
Oh, looks like you haven't necessary utility stat in your watch kernel. I used it for prevent damage original system files while patching.
Thank you fr your feedback i'll resolve it soon.
If you are familiar with adb and shell commands you can run this commands sequence for activate autorun my script:
PHP:
mv "/system/bin/logwatch" "/system/bin/logwatch_orig"
echo '#!/system/bin/sh' > "/system/bin/logwatch"
echo "# patch for diswarn script by Kenas @ 4pda" >> "/system/bin/logwatch"
echo "nohup diswarn < /dev/null > /dev/null 2>/dev/null &" >> "/system/bin/logwatch"
echo "exec logwatch_orig [email protected]" >> "/system/bin/logwatch"
As you can see, we rename original bin file logwatch and place instead of it small shell script.

I changed algorithm and reload install pack. Please try it.

kenas said:
I changed algorithm and reload install pack. Please try it.
Click to expand...
Click to collapse
Thanks for your work.
This is my output now:
PHP:
remount succeeded
Remove old files...
Some errors with it are allowed
rm failed for /system/bin/diswarn_daemon, No such file or directory
rm failed for /system/bin/diswarn_message, No such file or directory
rm failed for /system/bin/msg, No such file or directory
[100%] /mnt/shell/emulated/0/diswarn_scenario.txt
Copying new files...
INSTALL_FAILED_ALREADY_EXISTS error is allowed
[100%] /system/bin/diswarn
[100%] /system/bin/autorun_patch.sh
[100%] /mnt/shell/emulated/0/diswarn_scenario.txt
[100%] /data/local/tmp/msg.apk
pkg: /data/local/tmp/msg.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Set permissions...
Patch watch for autorun
/system/bin/autorun_patch.sh[5]: cat: /system/bin/lmkd.sh: No such file or directory
Initial state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 0
/system/bin/autorun_patch.sh[58]: [: /system/bin/logwatch: unexpected operator/operand
Final state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 0
Autorun patch ERROR. Contact with Kenas at 4pda.ru
remount succeeded
Watch is rebooting
Seems better than my last output but still no success.

Saratoga79 said:
still no success.
Click to expand...
Click to collapse
Try one more time. I hope, I catch what was wrong.

kenas said:
Try one more time. I hope, I catch what was wrong.
Click to expand...
Click to collapse
Sorry but no luck :crying:
PHP:
remount succeeded
Remove old files...
Some errors with it are allowed
rm failed for /system/bin/diswarn_daemon, No such file or directory
rm failed for /system/bin/diswarn_message, No such file or directory
rm failed for /system/bin/msg, No such file or directory
[100%] /mnt/shell/emulated/0/diswarn_scenario.txt
Copying new files...
INSTALL_FAILED_ALREADY_EXISTS error is allowed
[100%] /system/bin/diswarn
[100%] /system/bin/autorun_patch.sh
adb: error: cannot stat '.\diswarn_scenario.txt': No such file or directory
[100%] /data/local/tmp/msg.apk
pkg: /data/local/tmp/msg.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Set permissions...
Patch watch for autorun
/system/bin/autorun_patch.sh[5]: cat: /system/bin/lmkd.sh: No such file or directory
Initial state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 0
/system/bin/autorun_patch.sh[58]: cut: not found
/system/bin/autorun_patch.sh[58]: [: 60: unexpected operator/operand
Final state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 0
Autorun patch ERROR. Contact with Kenas at 4pda.ru
remount succeeded
D:\AMAZFIT_PACE\MODs\diswarn_4.2_eng\diswarn_4.0_eng\\tools\adb reboot
Watch is rebooting
Also found a typo in line 44
PHP:
echo %~dp0\tools\adb reboot

Saratoga79 said:
Sorry but no luck
Click to expand...
Click to collapse
Holy ****. I've replaced missing stat with cut, but it's not present too. :crying::crying::crying:
Wait, i'm trying resolve it and thanks for your patience

kenas said:
Holy ****. I've replaced missing stat with cut, but it's not present too. :crying::crying::crying:
Wait, i'm trying resolve it and thanks for your patience
Click to expand...
Click to collapse
Take your time my friend.

Try again uploaded version.
For clearance, it's no errors in main diswarn script, it's only some fails in installation sequence. I made some checks before patch the watch for prevent damage it with wrong patch

kenas said:
Hi! I came from 4pda.ru and want to introduce my own shell script that notificates you if the watch losts connect with smartphone.
It can be installed at watch with unlocked bootloader.
In my tests it has no effect on the battery lifetime.
Script can be customized via diswarn_scenario.txt that stored at watch in the root of sdcard memory and can be edited with Notepad.
For use it you have to unrar attachment at C:\ and run diswarn_installer.cmd
UPD: file reloaded with install issue fix
Click to expand...
Click to collapse
Now seems to be correct!! Thanks!
PHP:
remount succeeded
Remove old files...
Some errors with it are allowed
rm failed for /system/bin/diswarn, No such file or directory
rm failed for /system/bin/diswarn_daemon, No such file or directory
rm failed for /system/bin/diswarn_message, No such file or directory
rm failed for /system/bin/msg, No such file or directory
adb: error: remote object '/mnt/shell/emulated/0/diswarn_scenario.txt' does not exist
rm failed for /mnt/shell/emulated/0/diswarn_scenario.txt, No such file or directory
Copying new files...
INSTALL_FAILED_ALREADY_EXISTS error is allowed
[100%] /system/bin/diswarn
[100%] /system/bin/autorun_patch.sh
[100%] /mnt/shell/emulated/0/diswarn_scenario.txt
[100%] /data/local/tmp/msg.apk
pkg: /data/local/tmp/msg.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Set permissions...
Patch watch for autorun
/system/bin/autorun_patch.sh[5]: cat: /system/bin/lmkd.sh: No such file or directory
Initial state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 0
Patching logwatch ...
Final state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 1
Autorun patched succesful
remount succeeded
Still reboot bug at the end of the sctipt.

New version 4.1 uploaded. Fixed some troubles with new rom versions.

And that's a perfect example for two devs collaboration
Thanks to you both!

kenas said:
Hi! I came from 4pda.ru and want to introduce my own shell script that notificates you if the watch losts connect with smartphone.
It can be installed at watch with unlocked bootloader.
In my tests it has no effect on the battery lifetime.
Script can be customized via diswarn_scenario.txt that stored at watch in the root of sdcard memory and can be edited with Notepad.
For use it you have to unrar attachment at C:\ and run diswarn_installer.cmd
UPD: file reloaded with install issue fix
UPD2: Added new version 4.1. More compatibility with newest roms
Click to expand...
Click to collapse
Hi, I love your idea, but somehow it's not working on my watch. It's in PACEfied Rel 34 (1.2.48), and the installation process seems to work, but I don't receive any message when the watch disconnects from my device. Here's the installation info:
Code:
Presione una tecla para continuar . . .
remount succeeded
Remove old files...
Some errors with it are allowed
rm failed for /system/bin/diswarn, No such file or directory
rm failed for /system/bin/diswarn_daemon, No such file or directory
rm failed for /system/bin/diswarn_message, No such file or directory
rm failed for /system/bin/msg, No such file or directory
[100%] /mnt/shell/emulated/0/diswarn_scenario.txt
Copying new files...
INSTALL_FAILED_ALREADY_EXISTS error is allowed
[100%] /system/bin/diswarn
[100%] /system/bin/autorun_patch.sh
[100%] /mnt/shell/emulated/0/diswarn_scenario.txt
[100%] /data/local/tmp/msg.apk
pkg: /data/local/tmp/msg.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Set permissions...
Patch watch for autorun
/system/bin/autorun_patch.sh[5]: cat: /system/bin/lmkd.sh: No such file or directory
Initial state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 0
Patching logwatch ...
Final state:
Lmkd.sh found: 0, patched: 0
Logwatch found: 1, patched: 1
Autorun patched succesful
remount succeeded
C:\diswarn_4.1_eng\\tools\adb reboot
Watch is rebooting
If you have iPhone, you must activate IPHONE=1= option in diswarn_scenario.txt according with diswarn_scenario iphone example.txt
I placed the folder in C:\ and my diswarn_scenario.txt is in /sdcard. This is how I setup it:
Code:
#Vibration scenario for diswarn 4.0
#Reboot the watch after changing this scenario.
#Use the syntax: PARAMETER_NAME=parameters values divided space=
DISCONNECT_VIB=600 600=
CONNECT_VIB=300=
SHOW_MESSAGE=1=
CONNECT_TEXT=Установлена связь со смартфоном=
DISCONNECT_TEXT=Потеряна связь со смартфоном=
WARNING_TEXT=Работа сервиса уведомлений о потере связи со смартфоном прекращена=
DELAY_IN_SEC=10=
#Uncomment and use next option for detecting only one device. For android: with device ID, device name, device serial number or bluetooth MAC. For iPhone: with bluetooth MAC. Useful for prevent notification about headset status.
#DEVICE_ID=MI 4W=
#use next option for user-friendly name of your smartphone in notifications
#DEVICE_NAME=MI 4W=
#use next option only if you have iPhone connected
#IPHONE=1=
I don't know what's going wrong, because the whole proccess succeeds and I tried many times uninstalling and installing this mod. Please help!
Thank you very much for your work, I found you in 4pda but I'm not Russian. Thanks in advance and happy new year.

Log is normal. Did you have iPhone or Android phone? I haven't iPhone for a full testing.
Also you can try delete diswarn_scenario.txt from watch and reboot watch.

Hello,
I tried to install diswarn on my pace (rom pacefied 1.2.50h) several time, 4.0 and 4.1, but no positive results, feedbacks on video seem ok (only reboot doesn't work, but this isn't a problem ) and I don't know what new action is possible to try, for me.
Thanks

Related

[Q] Need help downgrading.

Trying to downgrade...
C:\Program Files (x86)\Android\android-sdk\platform-tools>crackin.bat
"Copying tools"
cannot stat 'busybox': No such file or directory
cannot stat 'flash_image': No such file or directory
cannot stat 'misc1-2.img': No such file or directory
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/flash_image: No such file or directory
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, No such file or directory
rmdir failed for /data/DxDrm/fuse/, No such file or directory
cannot create /data/DxDrm/fuse: directory nonexistent
Unable to chmod /data/DxDrm/fuse: No such file or directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, No such file or directory
rmdir failed for /data/DxDrm, No such file or directory
link failed Permission denied
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, No such file or directory
link failed File exists
link failed Permission denied
"Rebooting to normal mode to downgrade ROM"
/dev/mtd/mtd0: Permission denied
/data/local/busybox: not found
/data/local/flash_image: not found
"Freeing links"
rm failed for /data/DxDrm, No such file or directory
rm failed for /data/dontpanic, Permission denied
PATH: C:\Program Files (x86)\Android\android-sdk\tools
Copied the hack4legend files to C:\Program Files (x86)\Android\android-sdk\platform-tools & C:\Program Files (x86)\Android\android-sdk\tools
Following this guide:
http://forum.xda-developers.com/showthread.php?t=725430
You have your adb and crackin.bat in the folder " /android-sdk/platform-tools"
And it looks like the other files (line 3 - 5) are in another folder.
Assuming you followed the instructions exactly, you probably extracted those files into "/android-sdk/tools"?
If so, just copy all files from "/android-sdk/platform-tools" to "/android-sdk/tools" and it should work.
Also, do i need to root HBOOT first?
New error:
C:\Program Files (x86)\Android\android-sdk\tools>crackin.bat
"Copying tools"
1364 KB/s (698452 bytes in 0.500s)
608 KB/s (76044 bytes in 0.122s)
1438 KB/s (655360 bytes in 0.445s)
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, No such file or directory
rmdir failed for /data/DxDrm/fuse/, No such file or directory
cannot create /data/DxDrm/fuse: directory nonexistent
Unable to chmod /data/DxDrm/fuse: No such file or directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, No such file or directory
rmdir failed for /data/DxDrm, No such file or directory
link failed Permission denied
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, No such file or directory
link failed File exists
link failed Permission denied
"Rebooting to normal mode to downgrade ROM"
/dev/mtd/mtd0: Permission denied
cr--rw---- 1 1001 2002 90, 0 Mar 9 14:13 /dev/mtd/mtd0
error writing misc: Permission denied
"Freeing links"
rm failed for /data/DxDrm, No such file or directory
rm failed for /data/dontpanic, Permission denied
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
After that you should be able to run the 1.31 RUU
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
# adb push flash_image /data/local/
adb push flash_image /data/local/
adb: not found
#
Edit:
Is this what suppose to happen?
C:\Program Files (x86)\Android\android-sdk\tools>adb shell
$ su
su
# /data/local/flash_image misc /data/local/misc1-2.img
/data/local/flash_image misc /data/local/misc1-2.img
#
kmtse1 said:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
# adb push flash_image /data/local/
adb push flash_image /data/local/
adb: not found
#
Edit:
Is this what suppose to happen?
C:\Program Files (x86)\Android\android-sdk\tools>adb shell
$ su
su
# /data/local/flash_image misc /data/local/misc1-2.img
/data/local/flash_image misc /data/local/misc1-2.img
#
Click to expand...
Click to collapse
From what I remember, yes it is.
You can now continue the guide in your first post from the point where you have to insert your gold card into your phone.
Still the same errors...
kmtse1 said:
Still the same errors...
Click to expand...
Click to collapse
Which errors?
The errors you posted in your first post were from running crackin.bat.
That is not necessary after running the steps I posted.
You can skip to the part where you insert your goldcard into your phone and then run the 1.31 RUU.
I get stuck at step 6 http://theunlockr.com/2010/06/07/how-to-load-a-custom-rom-on-the-htc-legend/
No menus load.
So if I understand correctly, you have now already succesfully downgraded (Link as in your first post) and rooted (Link)your phone? Since the link you gave in your last post is for flashing a custom rom, which is the last step in the process.
Oops, no, not downgraded yet - I lost my patience, I will try properly again.
Azaruc said:
So if I understand correctly, you have now already succesfully downgraded (Link as in your first post) and rooted (Link)your phone? Since the link you gave in your last post is for flashing a custom rom, which is the last step in the process.
Click to expand...
Click to collapse
How do I install the RUU to downgrade? I get an error if I run the .exe on my laptop.
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
PAPP:
PVENDOR:
PGUID:
$
@Windows 7 / Server 2008 R2 Service Pack 1 (7601)
IE Version: 8.0.7601.17514
Have you installed HTC Sync v2.0.33 ?
Download here
You need this version of HTC Sync, so if you have a newer version, uninstall that version first.
Once installed, run the RUU again (you might need to run it as admin).
Azaruc said:
Have you installed HTC Sync v2.0.33 ?
Download here
You need this version of HTC Sync, so if you have a newer version, uninstall that version first.
Once installed, run the RUU again (you might need to run it as admin).
Click to expand...
Click to collapse
Yes I have that specific version.
Tried run as admin.
Just to be sure, you still have your phone connected in charge only state right?
If so, are you sure you didn't get any error in the earlier steps?
I downgraded using the exact same method and didn't get this error (recognized all of the others), so I'm not sure what might cause this otherwise.
Azaruc said:
Just to be sure, you still have your phone connected in charge only state right?
If so, are you sure you didn't get any error in the earlier steps?
I downgraded using the exact same method and didn't get this error (recognized all of the others), so I'm not sure what might cause this otherwise.
Click to expand...
Click to collapse
I showed you what I got from following your steps earlier. You said it looked ok, then I went to downgrade with the RUU.
Is the RUU compatible with 64bit Windows 7?
Looking at your other post, it looks like you managed to complete the downgrading?
What turned out to be the problem with the second step?
Azaruc said:
Looking at your other post, it looks like you managed to complete the downgrading?
What turned out to be the problem with the second step?
Click to expand...
Click to collapse
The downgrade guide doesn't work for me - I followed this instead: http://android.modaco.com/content/h...-r4-htc-legend-rooting-guide-now-with-1-31-x/
But now, I still can't delete widgets/apps. http://forum.xda-developers.com/showthread.php?t=987023
Azaruc said:
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
After that you should be able to run the 1.31 RUU
Click to expand...
Click to collapse
Mate, just wanted to let you know I was having the exact same issues under Win7 x64 and after trying your Visionary+ and manually executing adb commands method, I was able to run RUU successfully.
My Legend is now 1.3.1 and Im performing the root as I type.
Thanks for your help and contritubtion.
Error 170: Usb connection error
Tried to downgrade many time using guides on the forum but when running RUU always get:
ERROR 170: USB CONNECTION ERROR
- downloaded the drivers with HTC SYNC (phone shows up at device manager)
- made the gold card (with two different cards 2GB Kingston, 8GB SanDisc)
- ran ADB ended up with: cr--rw----
- did a temproot, ran adb shell .... su and so on
but still get:
ERROR 170: USB CONNECTION ERROR
Have no clue what to do now whatsoever. Any suggestions?

Anyone wanna test a one root script for me?

Found a one root script. Just need to see if it'll work on the Amaze. If it does, I'll add it in my tool and give proper credits as always. If not, I'll look into it myself.
Prerequisites?
_________________________
Am I on Candid Camera?
Same as usual. S-off or unlock boot loader.
I will be able to help after work in few hours if still needed. Unless I don't need a computer, in which if that's the case, I'll help ya out now
_________________________
Am I on Candid Camera?
You need a computer, I just need a few testers. Thanks GG!
hasoon2000 said:
You need a computer, I just need a few testers. Thanks GG!
Click to expand...
Click to collapse
I'm home I'm an hour and half... I'll ccheck in then. No prob
_________________________
Am I on Candid Camera?
replacement is due in an hour or two so I will test it then.
zPacKRat said:
replacement is due in an hour or two so I will test it then.
Click to expand...
Click to collapse
Before you s-off/unlock your boot loader, run the script. Tell me if it works. If it does, reboot the phone twice and see if it is a perm root or temp root.
Wife says I'm busy :banghead:
Sorry 4 now
_________________________
Am I on Candid Camera?
hasoon2000 said:
Before you s-off/unlock your boot loader, run the script. Tell me if it works. If it does, reboot the phone twice and see if it is a perm root or temp root.
Click to expand...
Click to collapse
first attempt it hangs:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
749 KB/s (2005736 bytes in 2.613s)
640 KB/s (91980 bytes in 0.140s)
713 KB/s (570342 bytes in 0.781s)
REBOOT
cannot create /data/local.prop: permission denied
AGAIN REBOOT
After rebooting from power button it provided the following:
AGAIN!?
mount: Operation not permitted
mount: Operation not permitted
cannot create /system/xbin/busybox: read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
busybox: permission denied
busybox: permission denied
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
Unlock your boot loader and try it.
hasoon2000 said:
Unlock your boot loader and try it.
Click to expand...
Click to collapse
same!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
4544 KB/s (2005736 bytes in 0.431s)
3592 KB/s (91980 bytes in 0.025s)
2978 KB/s (570342 bytes in 0.187s)
REBOOT
cannot create /data/local.prop: permission denied
AGAIN REBOOT
AGAIN!?
mount: Operation not permitted
mount: Operation not permitted
cannot create /system/xbin/busybox: read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
busybox: permission denied
busybox: permission denied
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
Flash a recovery. Boot into recovery, run the command. Sorry for all this lol
from 4ext nothing, just hangs.
Hold on, adb is giving me issues.
Alright. Try CWM
no go from cwm
it seems that in recovery it hangs a "@adb wait-for-device"
below is what happened when I removed the wait for device command and changed reboot to reboot recovery.
I had dropped the last part of the script in manually to finish the process.
* server not running *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
788 KB/s (2005736 bytes in 2.483s)
747 KB/s (91980 bytes in 0.120s)
704 KB/s (570342 bytes in 0.791s)
mv: can't rename '/data/local/tmp': No such file or directory
REBOOT
error: device offline
AGAIN REBOOT
error: device offline
AGAIN!?
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "echo ro.kernel.qemu=1 > /data/local.prop"
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>ECHO
AGAIN REBOOT
AGAIN REBOOT
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
reboot recovery
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mount -wo remount rootfs /"
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mount -o remount,rw -t ext4
/dev/block/mmcblk0p30 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1
,data=ordered)
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/dev
/block/mmcblk0p33 /system"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "cat /data/local/busybox >
/sbin/sh: syntax error: unexpected end of file
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/xbin/busybox"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 777 /system/xbin/busybox"
chmod: /system/xbin/busybox: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "/system/xbin/busybox --install -s
/sbin/sh: /system/xbin/busybox: not found
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/xbin"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "busybox cp /data/local/Superuser.apk
BusyBox v1.19.3-cm9 static (2011-11-20 14:44 +0100) multi-call binary.
Usage: cp [OPTIONS] SOURCE DEST
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY
-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/app/Superuser.apk"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "busybox cp /data/local/su /system/xbin/su"
cp: can't stat '/data/local/su': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chown 0.0 /system/xbin/su"
chown: /system/xbin/su: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 06755 /system/xbin/su"
chmod: /system/xbin/su: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 644 /system/app/Superuser.apk"
chmod: /system/app/Superuser.apk: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "rm /data/local.prop"
rm: can't remove '/data/local.prop': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "rm /data/local/tmp"
rm: can't remove '/data/local/tmp': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mv /data/local/tmp.bak /data/local/tmp"
mv: can't rename '/data/local/tmp.bak': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
try this. It will reboot you in recovery
Just a heads up, I've s-offed and am upgrading to ICS because I have to get it ready for work tomorrow. let me know if there is any other way I can help.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Wait til you are in recovery, then press a button
Press any key to continue . . .
6359 KB/s (2005736 bytes in 0.308s)
6416 KB/s (91980 bytes in 0.014s)
5460 KB/s (570342 bytes in 0.102s)
mv: can't rename '/data/local/tmp': No such file or directory
mount: mounting /dev/block/mmcblk0p33 on /system failed: Invalid argument
/sbin/sh: can't create /system/xbin/busybox: nonexistent directory
chmod: /system/xbin/busybox: No such file or directory
/sbin/sh: /system/xbin/busybox: not found
cp: can't create '/system/app/Superuser.apk': No such file or directory
cp: can't create '/system/xbin/su': No such file or directory
chown: /system/xbin/su: No such file or directory
chmod: /system/xbin/su: No such file or directory
chmod: /system/app/Superuser.apk: No such file or directory
mv: can't rename '/data/local/tmp.bak': No such file or directory
C:\Users\user.account\Desktop\Oneclickroot>
I wouldn't recommend running this batch script on Amaze.
It doesn't even know where our system partition is mounted.
And if my memory is correct, we won't have root previledge to do much with adb shell right after unlocking the bootloader; we need to flash su binary using updater-script to begin with. As for the busybox, just install the 'busybox installer' so that users can run it in Android.
BTW, your all-in-one tool is very handy. Why no 4EXT recovery, though...
ringochan said:
I wouldn't recommend running this batch script on Amaze.
It doesn't even know where our system partition is mounted.
And if my memory is correct, we won't have root previledge to do much with adb shell right after unlocking the bootloader; we need to flash su binary using updater-script to begin with. As for the busybox, just install the 'busybox installer' so that users can run it in Android.
BTW, your all-in-one tool is very handy. Why no 4EXT recovery, though...
Click to expand...
Click to collapse
His tool does have ext4... You just have to get the full version from android-dev
Sent from my HTC_Amaze_4G using Tapatalk 2

sed Permission denied and No such file or directory errors while building CWMR

I've been looking around and i can't fix this. My cm10 source is all updated and before I did this i entered
Code:
sudo apt-get update
so everything is up to date
i've been following this guide: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device but im stuck on step 3 when I enter
Code:
build/tools/device/mkvendor.sh samsung_aegis2vzw /your/path/to/the/boot.img (yes i changed this to my boot.img path)
i get this as the outcome:
Code:
build/tools/device/mkvendor.sh: line 83: /sedcommand: Permission denied
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
sed: -e expression #1, char 15: unknown option to `s'
sed: couldn't open file /sedcommand: No such file or directory
Any help is much appreciated.
bump
Bump
Bump
Okay I now believe this is occurring because I don't have the file sedcommand. Is this file in the root of everyone's cm10 source?
bump

Tizen.NET vs Tizen Studio

Can you tell me the difference between Tizen.NET and Native Applications development with Tizen Sudio? Are there any limitations if, for example, I use Visual Studio and C # respect to Tizen Studio and C++ ?
Inviato dal mio EVR-L29 utilizzando Tapatalk
Maybe lost in Translation... or I am not sure enough what you try to achieve...
Tizen dotNet stuff is on REAL Hardware in commercial Area only since 4.0... maybe...
Tizen 4.0 devices have dotNet...
Maybe try to read here:
https://developer.tizen.org/forums/tizen-.net/active
Best Regards
Code:
sdb shell rpm -Uvh --force /tmp/corefx-managed-ref-2.1.4-3.10.noarch.rpm
Preparing... ################################# [100%]
Updating / installing...
1:corefx-managed-ref-2.1.4-3.10 ################################# [100%]
sdb shell rpm -Uvh --force /tmp/dotnet-build-tools-2.1.502-8.1.armv7l.rpm
Preparing... ################################# [100%]
No manifest in this package. Creating default one
Updating / installing...
1:dotnet-build-tools-2.1.502-8.1 ################################# [100%]
I am too lazy to install all necessary files on my PC...
So attempt with SM-R760 and Tizen 5.5...
Maybe these 2 RPMs enough to build dotNet stuff with Command line...
In theory these files also for Emulator... exists...
Best Regards
Can somebody help me to compile this Themes example?
Please.
Taken from here:
https://github.com/Samsung/xamarin-forms-samples/tree/master/Themes/ThemesDemo
Attached as Zip...
I mean with this:
Code:
sh-3.2# dotnet-build -h
/usr/bin/dotnet-build: illegal option -- h
usage:
/usr/bin/dotnet-build restore <project> [-s <source>] ...
/usr/bin/dotnet-build build <project> [-c <configuration>] ...
/usr/bin/dotnet-build pack <project> [-c <configuration>] [-v <version>] ...
/usr/bin/dotnet-build install <project> [-t <type>]
sh-3.2# /usr/bin/dotnet-build build <project> [-c <configuration>] ...
sh: project: No such file or directory
sh-3.2# /usr/bin/dotnet-build build test
----------------------------------------------
CMD=build
PROJECT=test
SOURCE=
CONFIGURATION=
VERSION=
TYPE=
REST ARGS=
----------------------------------------------
+ dotnet restore test
/usr/bin/dotnet: line 9: /usr/share/dotnet-build-tools/cli/dotnet: cannot execute binary file
(Failed! Retry 2/3) /usr/share/dotnet-build-tools/timeout.sh 600 dotnet restore test /nologo
/usr/bin/dotnet: line 9: /usr/share/dotnet-build-tools/cli/dotnet: cannot execute binary file
(Failed! Retry 3/3) /usr/share/dotnet-build-tools/timeout.sh 600 dotnet restore test /nologo
/usr/bin/dotnet: line 9: /usr/share/dotnet-build-tools/cli/dotnet: cannot execute binary file
Error 126
Any ideas?
Thanx in advance.
Best Regards
Edit 1.
Code:
sh-3.2# dotnet-build build ThemesDemo.Tizen
----------------------------------------------
CMD=build
PROJECT=ThemesDemo.Tizen
SOURCE=
CONFIGURATION=
VERSION=
TYPE=
REST ARGS=
----------------------------------------------
+ dotnet restore ThemesDemo.Tizen
/usr/bin/dotnet: line 9: /usr/share/dotnet-build-tools/cli/dotnet: cannot execute binary file
(Failed! Retry 2/3) /usr/share/dotnet-build-tools/timeout.sh 600 dotnet restore ThemesDemo.Tizen /nologo
/usr/bin/dotnet: line 9: /usr/share/dotnet-build-tools/cli/dotnet: cannot execute binary file
(Failed! Retry 3/3) /usr/share/dotnet-build-tools/timeout.sh 600 dotnet restore ThemesDemo.Tizen /nologo
/usr/bin/dotnet: line 9: /usr/share/dotnet-build-tools/cli/dotnet: cannot execute binary file
Error 126

[MOD] Stock Firmware adb root + init.d + SuperSU | Pace | Stratos | Verge | Stratos 3

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does.
Click to expand...
Click to collapse
Unlocked Bootloader
Only for Stock Firmware
Supported devices:
Pace​
A1602/CN
A1612/US
Stratos​
A1609/CN
A1619/US
A1609S/CN (Probably too but not tested)
A1619S/US (Probably too but not tested)
Verge​
A1801/CN
A1811/US
Stratos 3​
A1928/CN
A1929/US
Properly installed ADB and Fastboot drivers as system wide
Watch battery >40% (50% recommended)
Click to expand...
Click to collapse
For anyone interested on installing adb root, init.d support and SuperSU binary on Stock Firmware.
You don't need to install this on any of my rooted custom ROMs.
Note that this mod will break official OTA updates and you will need to update to new firmware using the installers for each device. So don't take any OTA just in case.
Install on your own risk.
Click to expand...
Click to collapse
Used boot.img for adb root and init.d support are based on latest firmware version for each device.
SuperSU binary is based on v2.82SR5.
Click to expand...
Click to collapse
@Neur_User
@Cracklydisc
@Ranomez
@1immortal
Click to expand...
Click to collapse
Windows .bat installation:
Download and unzip the .zip
Connect your watch
Go into unzipped folder
Run installer .bat depending on your watch (Pace/Stratos/Verge) and the Stock Firmware you are running (CN/US):
pace_cn_root.bat = For Pace running Stock CN Firmware
pace_us_root.bat = For Pace running Stock US Firmware
stratos_cn_root.bat = For Stratos running Stock CN Firmware
stratos_us_root.bat = For Stratos running Stock US Firmware
verge_cn_root.bat = For Verge running Stock CN Firmware
verge_us_root.bat = For Verge running Stock US Firmware
stratos_3_cn_root.bat = For Stratos 3 running Stock CN Firmware
stratos_3_us_root.bat = For Stratos 3 running Stock US Firmware
Linux .sh installation:
Download and unzip the .zip file
Connect your watch
Go into unzipped folder
Open Terminal and run the script depending on your watch (Pace/Stratos/Verge) and the Stock Firmware you are running (CN/US):
pace_cn_root.sh = For Pace running Stock CN Firmware
pace_us_root.sh = For Pace running Stock US Firmware
stratos_cn_root.sh = For Stratos running Stock CN Firmware
stratos_us_root.sh = For Stratos running Stock US Firmware
verge_cn_root.sh = For Verge running Stock CN Firmware
verge_us_root.sh = For Verge running Stock US Firmware
stratos_3_cn_root.sh = For Stratos 3 running Stock CN Firmware
stratos_3_us_root.sh = For Stratos 3 running Stock US Firmware
Example output log:
*****************************
CONNECT YOUR WATCH TO BEGIN
*****************************
* daemon not running; starting now at tcp:5037
* daemon started successfully
***********************
INSTALLATION FEATURES
***********************
BATTERY LEVEL: 100
DETECTED WATCH MODEL: A1619 - Amazfit Stratos
INSTALLED ROM VERSION: everestUS-2.3.10.4
STOCK US/INTERNACIONAL STRATOS ROM
**********************************
REBOOTING WATCH IN FASTBOOT MODE
**********************************
********************************************
FLASHING ROOTED boot.img FOR US Stratos
********************************************
< waiting for any device >
Sending 'boot' (5462 KB) OKAY [ 0.354s]
Writing 'boot' OKAY [ 0.531s]
Finished. Total time: 0.912s
********
REBOOT
********
Rebooting
Finished. Total time: 0.020s
****************************
WAITING FOR adb CONNECTION
****************************
remount succeeded
*************************
ENABLING init.d SUPPORT
*************************
files\init.d\.\: 1 file pushed. 0.0 MB/s (87 bytes in 0.007s)
files\xbin\.\: 1 file pushed. 3.2 MB/s (1576152 bytes in 0.468s)
*********************
SETTING PERMISSIONS
*********************
********************
INSTALLING SuperSU
********************
files\supersu\supersu\: 6 files pushed. 2.6 MB/s (710149 bytes in 0.258s)
============= INSTALLING SuperSU v2.82-SR5 ===============
============= SuperSU v2.82-SR5 INSTALLED ===============
********
REBOOT
********
**************************
INSTALLATION IS FINISHED
**************************
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
Manual installation commands:
Open a terminal or CMD window on the unzipped folder.
Variables will have one of these values depending on your watch and Stock Firmware version, so replace with correct value if you don't want to brick your watch:
%VER% = Pace/Stratos/Verge/Stratos3
%INST% = CN/US
Run these commands:
Code:
[B]# Reboot into fastboot[/B]
adb -d kill-server
adb -d start-server
adb -d shell reboot bootloader
[B]# Flash rooted boot.img[/B]
fastboot flash boot files\[B][COLOR="blue"]%VER%[/COLOR][/B]\[B][COLOR="Red"]%INST%[/COLOR][/B]\boot-[B][COLOR="Red"]%INST%[/COLOR][/B]-adb-root.img
fastboot reboot
[B]# Install init.d files[/B]
adb -d root
adb -d remount rw
adb -d shell mkdir /system/etc/init.d
adb -d push files\init.d\. /system/etc/init.d/
adb -d push files\xbin\. /system/xbin/
[B]# Set init.d permissions[/B]
adb -d shell chmod 0755 /system/etc/init.d
adb -d shell chmod -R 0755 /system/etc/init.d
adb -d shell chmod -R 0755 /system/xbin
[B]# Install SuperSU[/B]
adb -d push files\supersu\supersu\ /sdcard/
adb -d shell cd /sdcard/supersu/; sh root_amazfit.sh
adb -d shell rm -r /sdcard/supersu/
[B]# Reboot[/B]
adb -d reboot
adb -d kill-server
[B]# Done[/B]
Let me know about any issue or mistake I made.
Click to expand...
Click to collapse
Installer downloads
Stock Firmware adb root + init.d + SuperSU installer | Mirror | More info
Click to expand...
Click to collapse
If you like my work you can buy me a beer herehttp://paypal.me/Saratoga79
Click to expand...
Click to collapse
Mio1
Mio1
Thanks!!! with this can i use AmazBoost on stock ROM ?
saarakura said:
Thanks!!! with this can i use AmazBoost on stock ROM ?
Click to expand...
Click to collapse
I think so, but I didn't test it.
Give some feedback if you try it.
Thanks for all the great work OP!!!! Can you acces music while doing a workout in the verge? multitasking?
Thank you very much, i'll test it soon on my verge. I have custom ROM at this moment, but i believe it's gonna work.
Saratoga79 said:
I think so, but I didn't test it.
Give some feedback if you try it.
Click to expand...
Click to collapse
Tried today, the installer works fine...but i dont know how to check if AmazBoost is working
Hello, this is compatible with the new FW 2.3.10.5 ?
saarakura said:
Hello, this is compatible with the new FW 2.3.10.5 ?
Click to expand...
Click to collapse
I think so.
It should work for every old/new version.
Installer update to v1.1
Installer update to v1.1
Updated boot.img to:
Stratos
US: 2.3.10.5
CN: 2.0.70.1​
Verge
CN: 3.0.37.0​
Installer update to v1.2
Installer update to v1.2
Updated boot.img to:
Verge
US: 3.2.4.0​
Just got my Stratos and was trying to root it but when I get to install Superuser it says the above:
adb -d shell cd /sdcard/supersu/; sh root_amazfit.sh
sh: 0: Can't open root_amazfit.sh
Yes, I am using terminal to install as my SO is Linux... Does anyone had this issue?
mrps2 said:
Just got my Stratos and was trying to root it but when I get to install Superuser it says the above:
adb -d shell cd /sdcard/supersu/; sh root_amazfit.sh
sh: 0: Can't open root_amazfit.sh
Yes, I am using terminal to install as my SO is Linux... Does anyone had this issue?
Click to expand...
Click to collapse
Try to write that command in 2 different shell commands, one for cd and the other one for sh.
Saratoga79 said:
Try to write that command in 2 different shell commands, one for cd and the other one for sh.
Click to expand...
Click to collapse
Thank you mate! Will try it tonight... Hope it works??
This time the command worked but I think it wasnt installed:
adb -d shell cd /sdcard/supersu/; sh root_amazfit.sh
============= INSTALLING SuperSU v2.82-SR5 ===============
cp: cannot create regular file '/system/etc/install-recovery.sh': No such file or directory
chmod: cannot access '/system/etc/install-recovery.sh': No such file or directory
chcon: invalid context: ‘ubject_r:toolbox_exec:s0’: No such file or directory
rm: cannot remove '/system/bin/install-recovery.sh': No such file or directory
ln: failed to create symbolic link '/system/bin/install-recovery.sh': No such file or directory
cp: cannot create regular file '/system/xbin/su': No such file or directory
chmod: cannot access '/system/xbin/su': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
cp: cannot create regular file '/system/xbin/daemonsu': No such file or directory
chmod: cannot access '/system/xbin/daemonsu': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
cp: cannot create regular file '/system/xbin/supolicy': No such file or directory
chmod: cannot access '/system/xbin/supolicy': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
cp: cannot create regular file '/system/lib/libsupol.so': No such file or directory
chmod: cannot access '/system/lib/libsupol.so': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
cp: cannot create regular file '/system/etc/init.d/99SuperSUDaemon': No such file or directory
chmod: cannot access '/system/etc/init.d/99SuperSUDaemon': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
cp: cannot stat '/system/bin/app_process32': No such file or directory
chown: invalid group: ‘root:shell’
chmod: cannot access '/system/bin/app_process32_original': No such file or directory
chcon: invalid context: ‘ubject_r:zygote_exec:s0’: No such file or directory
cp: cannot stat '/system/bin/app_process32': No such file or directory
chown: invalid group: ‘root:shell’
chmod: cannot access '/system/bin/app_process_init': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
rm: cannot remove '/system/bin/app_process': No such file or directory
ln: failed to create symbolic link '/system/bin/app_process': No such file or directory
rm: cannot remove '/system/bin/app_process32': No such file or directory
ln: failed to create symbolic link '/system/bin/app_process32': No such file or directory
root_amazfit.sh: 35: root_amazfit.sh: /system/xbin/su: not found
============= SuperSU v2.82-SR5 INSTALLED ===============
So many "invalid" and "No's", what I am doing wrong?
mrps2 said:
This time the command worked but I think it wasnt installed:
adb -d shell cd /sdcard/supersu/; sh root_amazfit.sh
============= INSTALLING SuperSU v2.82-SR5 ===============
cp: cannot create regular file '/system/etc/install-recovery.sh': No such file or directory
chmod: cannot access '/system/etc/install-recovery.sh': No such file or directory
chcon: invalid context: ‘ubject_r:toolbox_exec:s0’: No such file or directory
rm: cannot remove '/system/bin/install-recovery.sh': No such file or directory
ln: failed to create symbolic link '/system/bin/install-recovery.sh': No such file or directory
cp: cannot create regular file '/system/xbin/su': No such file or directory
chmod: cannot access '/system/xbin/su': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
cp: cannot create regular file '/system/xbin/daemonsu': No such file or directory
chmod: cannot access '/system/xbin/daemonsu': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
cp: cannot create regular file '/system/xbin/supolicy': No such file or directory
chmod: cannot access '/system/xbin/supolicy': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
cp: cannot create regular file '/system/lib/libsupol.so': No such file or directory
chmod: cannot access '/system/lib/libsupol.so': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
cp: cannot create regular file '/system/etc/init.d/99SuperSUDaemon': No such file or directory
chmod: cannot access '/system/etc/init.d/99SuperSUDaemon': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
cp: cannot stat '/system/bin/app_process32': No such file or directory
chown: invalid group: ‘root:shell’
chmod: cannot access '/system/bin/app_process32_original': No such file or directory
chcon: invalid context: ‘ubject_r:zygote_exec:s0’: No such file or directory
cp: cannot stat '/system/bin/app_process32': No such file or directory
chown: invalid group: ‘root:shell’
chmod: cannot access '/system/bin/app_process_init': No such file or directory
chcon: invalid context: ‘ubject_r:system_file:s0’: No such file or directory
rm: cannot remove '/system/bin/app_process': No such file or directory
ln: failed to create symbolic link '/system/bin/app_process': No such file or directory
rm: cannot remove '/system/bin/app_process32': No such file or directory
ln: failed to create symbolic link '/system/bin/app_process32': No such file or directory
root_amazfit.sh: 35: root_amazfit.sh: /system/xbin/su: not found
============= SuperSU v2.82-SR5 INSTALLED ===============
So many "invalid" and "No's", what I am doing wrong?
Click to expand...
Click to collapse
I think SuperSU stuff has to be installed right after the watch boots and adb gets enabled, if you wait too long some permission errors will prompt there.
I will take a look to commands in my VM, maybe there is something wrong too, and I will try to write a .sh script for non Windows users.
Saratoga79 said:
I think SuperSU stuff has to be installed right after the watch boots and adb gets enabled, if you wait too long some permission errors will prompt there.
I will take a look to commands in my VM, maybe there is something wrong too, and I will try to write a .sh script for non Windows users.
Click to expand...
Click to collapse
That would be awesome, I have Linux right now and most of things are made for Windows and I still in the process of learning how to work stuff in Linux as well...
After reading a little I think that you are totally right, my problem started at the rooting process, I think that the tempory root did not work and I didn't notice and kept going.
Now got to wait for some free time to try it again as it takes a little time to write this typing line by line...
Thanks for the help! And I would be glad to try yours batch script for Linux. :good:
mrps2 said:
That would be awesome, I have Linux right now and most of things are made for Windows and I still in the process of learning how to work stuff in Linux as well...
After reading a little I think that you are totally right, my problem started at the rooting process, I think that the tempory root did not work and I didn't notice and kept going.
Now got to wait for some free time to try it again as it takes a little time to write this typing line by line...
Thanks for the help! And I would be glad to try yours batch script for Linux. :good:
Click to expand...
Click to collapse
I think I got it, maybe it's not perfect but seems to work:
Code:
*****************************
Pace US ROOT INSTALLER
*****************************
******************************
CONNECT YOUR WATCH TO BEGIN
******************************
cannot connect to daemon at tcp:5037: Connection refused
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
be601824 device
****************
WATCH FEATURES
****************
DETECTED WATCH MODEL: Amazfit Pace (A1612)
INSTALLED ROM VERSION: huangheUS-2.8.4.0
ROM STOCK INTERNACIONAL FOUND
********************************
FLASHING ROOTED boot.img ROOT
********************************
< waiting for any device >
Sending 'boot' (5458 KB) OKAY [ 0.762s]
Writing 'boot' OKAY [ 1.052s]
Finished. Total time: 1.931s
***********
REBOOTING
***********
Rebooting
Finished. Total time: 0.270s
****************************
WAITING FOR adb CONNECTION
****************************
adbd is already running as root
remount succeeded
*************************
ENABLING init.d SUPPORT
*************************
mkdir failed for /system/etc/init.d, File exists
files/init.d/: 1 file pushed. 0.0 MB/s (87 bytes in 0.011s)
files/xbin/: 1 file pushed. 0.9 MB/s (1576152 bytes in 1.651s)
*********************
SETTING PERMISSIONS
*********************
********************
INSTALLING SuperSU
********************
files/supersu/: 6 files pushed. 0.8 MB/s (710149 bytes in 0.888s)
============= INSTALLING SuperSU v2.82-SR5 ===============
============= SuperSU v2.82-SR5 INSTALLED ===============
***********
REBOOTING
***********
**************************
INSTALLATION IS FINISHED
**************************
Now i will create scripts for all watches and variants, and I will update the mod with latest CN Verge boot.img.
I recommend you flashing stock firmware as re-installing SuperSU again will throw a lot of errors, it can be flashed just once per fresh firmware.
Saratoga79 said:
I think I got it, maybe it's not perfect but seems to work:
Now i will create scripts for all watches and variants, and I will update the mod with latest CN Verge boot.img.
I recommend you flashing stock firmware as re-installing SuperSU again will throw a lot of errors, it can be flashed just once per fresh firmware.
Click to expand...
Click to collapse
Fantastic! I would be happy to try it for you... Will get the stock firmware ready to install as soon as you release it.
Cheers mate!
Installer update to v1.3
Installer update to v1.3
Updated boot.img to:
Verge
CN: 3.0.40.0
Added new Linux .sh script installers.

Categories

Resources