Hi guys !
This my first little tool i'm build for resign zipfiles and apkfiles for linux users.
Unzip the testsign_tool.zip to your home directory,inside you will find a little howto.
Sorry for bad english.
Enjoy
1. you can use ~/ instead of /home/username/
2. you can use $USER instead of username
3. you left a hidden file .kopia in the scripts folder.
4. you assume that everybody has testsign.jar in his sdk folder, why not include it with this tool?
other than that, nice tool
Well this is my first script,must start somewhere
thank you .. good work ... it would have bin nice to include the jar file but hey thats what google is for right thanks thou
OK, I'm having a problem getting it to work. Here's what I did: I changed my sdk folder to androidsdk. I unzipped the testsign_tool to my androidsdk/tool folder. I edited the scripts to:
for zipfile script:
Code:
lear
echo
#
#set -x
#
file_date=$(date +%Y%m%d%H%M%S)
# Dir with signed file
working_dir="~/$USER/testsign_tool/update"
# directory that contains update.zip
zip_dir="../working"
jpath="~/$USER/androidsdk/tools/sign/testsign.jar"
cd $working_dir
java -classpath $jpath testsign $zip_dir/update.zip ${file_date}_file-signed.zip
if [ -f $working_dir/${file_date}_file-signed.zip ] ; then
echo "New file signed!"
sleep 2
exit 0
else
echo "Error, please check."
fi
and for apkfile script:
Code:
clear echo
#
#set -x
#
file_date=$(date +%Y%m%d%H%M%S)
# Dir with signed file
working_dir="~/$USER/testsign_tool/update"
# directory that contains update.apk
apk_dir="../working"
jpath="~/$USER/androidsdk/tools/sign/testsign.jar"
cd $working_dir
java -classpath $jpath testsign $apk_dir/update.apk ${file_date}_file-signed.apk
if [ -f $working_dir/${file_date}_file-signed.apk ] ; then
echo "New file signed!"
sleep 2
exit 0
else
echo "Error, please check."
fi
so that $USER will allow anyone to use without modifying the scripts with their own name. I renamed my Launcher.apk to update.apk.
I place the update.apk into the working folder from within the testsign_tool folder. I double click the menu.sh and select option 2 in order to resign/sign my new apk. After this I get a message in terminal saying:
Code:
scripts/do_apkfile: line 13: cd: ~/treken/testsign_tool/update: No such file or directory
Exception in thread "main" java.lang.NoClassDefFoundError: testsign
Caused by: java.lang.ClassNotFoundException: testsign
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Could not find the main class: testsign. Program will exit.
Error, please check.
Press Enter to continue
any insight to my problem as to what I did wrong?
No version for windows? only for linux?
This isn't the first time I've tried to build Cyanogenmod for my i9100 on Ubuntu 12.10; I've done it successfully a few times before. However recently, it has just refused to build.
Code:
lunch cm_i9100-userdebug && mka
gave a bunch of errors: http://pastebin.com/Mn3YLZDY.
Code:
brunch cm_i9100-userdebug
gives different errors: http://pastebin.com/xiv4ettD. Teamhacksung's build script also gives the exact same errors. I tried starting in a new directory from scratch, but I still get the same errors.
The parts that look suspicious to me are
Code:
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
(/home/ari/android/system/external/apache-harmony does exist) and
Code:
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
find: `src': No such file or directory
I think this could be related to a repo sync problem I had/have where it couldn't download anything properly with lots of
Code:
Connection reset by peer
errors, although I think it has now synced (df -h shows 15GB). I also ran
Code:
repo forall -c "git fsck && git gc"
which "repairs" each repository, and that didn't give any errors.
Can anyone help with getting this to build?
EDIT: I found a post on the Android Building mailing list that was similar, and the suggestion to run
Code:
export CDPATH=""
(previously, $CDPATH=".")
got CM to build much further than before. No idea how this works, but it does.
However there are now more errors later during the build, e.g.
Code:
make: *** No rule to make target `/media/build/android/out/system/target/product/i9100/obj/lib/libTVOut.so', needed by `/media/build/android/out/system/target/product/i9100/obj/EXECUTABLES/mediaserver_intermediates/LINKED/mediaserver'. Stop.
It seems to have built a .zip flashable file now:
Code:
Package complete: /media/build/android/out/system/target/product/i9100/cm-10.1-20130121-UNOFFICIAL-i9100.zip
md5: f9fe076a6f0dfe140329e94ce6aa1867
Creating kernel zip...
Bootimage found...
No instructions to create out/target/product/i9100/kernel-cm-10.1-20130121-i9100-signed.zip... skipping.
Elapsed: 47 min(s) 20 sec(s)
but it says it can't create a kernel zip?
The following guide should work for all loki-locked bootloaders, but I can only confirm that it worked on my D800. The problem I was having, was that loki_flash has been replaced with loki_tools, and there arent any guides out for loki_tools.
The right way to flash CWM requires you to generate your own recovery.lok from the aboot.img, and recovery.img (CWM) which you need to use loki_tools for.
PREREQUISITES
Device must be rooted
Device must be in Developer Mode
USB Debugging turned ON
Debugging RSA Signature must be accepted
Download CWM HERE
Download loki_tool HERE
Download ADB HERE
STEP 1 (Getting Files)
Follow this GUIDE to install ADB and FASTBOOT, once its complete, you will have adb installed to C:\adb
Download CWM, rename the file to 'recovery.img' (so its easier to work with) and move it to C:\adb
Download loki_tool and extract the file 'loki_tool' from the bin folder and place it in C:\adb
STEP 2 (Preparing for the Procedure)
Plug in your phone to the computer
In Windows Explorer, navigate to C:\
Shift+Right Click on the 'adb' folder, select 'Open command window here'
Type "adb devices" you should see:
Code:
C:\adb>adb devices
List of devices attached
<devid> device
If not, go back and turn on Develper Mode, USB Debugging, and accept the RSA Signature
STEP 3 (Flashing process)(note: I copied everything from the cmd prompt and edited it as a text file before thinking to post my procedure here, thats why it looks different)
In ADB type the following commands each step is commented out with what it does (someone could make it into a bat, but I'm too lazy.
Code:
// Sending recovery.img to device
C:\adb>adb push recovery.img /data/local/tmp/recovery.img
---------------
3456 KB/s (10510336 bytes in 2.969s)
---------------
// Sending loki_tool to device
C:\adb>adb push loki_tool /data/local/tmp/loki_tool
---------------
2777 KB/s (379248 bytes in 0.133s)
---------------
// entering Android Linux environment
C:\adb>adb shell
// sudo
[email protected]:/ $ su
// generating aboot.img
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
---------------
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.072 secs (14563555 bytes/sec)
---------------
// changing permissions on aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
// exiting Android Linux environment
[email protected]:/ # exit
[email protected]:/ $ exit
// saving aboot.img locally in case you need it again.
C:\adb>adb pull /data/local/tmp/aboot.img
---------------
2992 KB/s (1048576 bytes in 0.342s)
---------------
// entering Android Linux environment
C:\adb>adb shell
// changing directory
[email protected]:/ $ cd /data/local/tmp
// ls should list the following 3 files, if not, you are missing them and need to push them, or generate another aboot.img
[email protected]:/data/local/tmp $ ls
---------------
aboot.img
loki_tool
recovery.img
---------------
// changing the permissions of the files so loki_tool can use them
[email protected]:/data/local/tmp $ chmod 755 /data/local/tmp/loki_tool
[email protected]:/data/local/tmp $ chmod 755 /data/local/tmp/recovery.img
// executing loki_tool to generate the recovery.lok file
[email protected]:/data/local/tmp $ ./loki_tool patch recovery aboot.img recovery.img recovery.lok
---------------
Loki tool v2.1
[+] Detected target AT&T LG G2 build D80010o
[+] Original kernel address: 00008000
[+] Original ramdisk address: 05000000
[+] Writing device tree.
[+] Output file written to recovery.lok
---------------
// exiting Android Linux environment
[email protected]:/data/local/tmp $ exit
// Saving recovery.lok locally in case you need it again
C:\adb>adb pull /data/local/tmp/recovery.lok
---------------
2939 KB/s (10512384 bytes in 3.493s)
---------------
// entering Android Linux environment
C:\adb>adb shell
// sudo
[email protected]:/ $ su
// changing directory
[email protected]:/ $ cd /data/local/tmp
// flashing recovery.lok with loki_tool
[email protected]:/data/local/tmp # /data/local/tmp/loki_tool flash recovery /data/local/tmp/recovery.lok
---------------
Loki tool v2.1
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!
---------------
// exiting Android Linux environment
[email protected]:/data/local/tmp # exit
[email protected]:/ $ exit
// reboot device into recovery
C:\adb>adb reboot recovery
---------------------------------
At this point your device should reboot into CWM, Congrats!
I know it's been 7 years, but this helped me get Magisk working on a locked bootloader. Thanks!
Platypus Enthusiast said:
I know it's been 7 years, but this helped me get Magisk working on a locked bootloader. Thanks!
Click to expand...
Click to collapse
I'm getting a "
Platypus Enthusiast said:
I know it's been 7 years, but this helped me get Magisk working on a locked bootloader. Thanks!
Click to expand...
Click to collapse
I keep getting "failed to find function to patch" error. Any thoughts?
Jackspsychosis said:
I'm getting a "
I keep getting "failed to find function to patch" error. Any thoughts?
Click to expand...
Click to collapse
I can do it for you if you like. I just need the aboot.img and the boot.img (or recovery.img) you're trying to patch.
Could I use this method to put a recovery on my lg g2 d802 (lollipop) on which it seems not to be any recovery (no command, when I press power+vol. down buttons) ?
TapaSte said:
Could I use this method to put a recovery on my lg g2 d802 (lollipop) on which it seems not to be any recovery (no command, when I press power+vol. down buttons) ?
Click to expand...
Click to collapse
I'm not sure if this is a good source, but maybe this might work:
Recovery Mode LG D802 G2, how to - HardReset.info
The Recovery mode it is the hidden feature which will enable a lot of useful operation.
www.hardreset.info
Platypus Enthusiast said:
I'm not sure if this is a good source, but maybe this might work:
Recovery Mode LG D802 G2, how to - HardReset.info
The Recovery mode it is the hidden feature which will enable a lot of useful operation.
www.hardreset.info
Click to expand...
Click to collapse
Like said, I've not recovery and if I press volume down + power I get "no command" screen.
I have european version t6 16gb. Can someone give me a mmcblk0 dump, i have brick my phone hard, service center can't help. I think the dump, you can to make so
( i found this instruction on ru thread, but nobody has uploaded a dump
In general, you first need to put the Root and Busybox Pro. Then observe and record Root explorer path where installed. It so happens that is placed in / system / bin / busybox and sometimes in the / system / xbin / busybox. Then download Cygwin start the installation, specify the installation path C: \ cygwin64
Further, during the installation himself appears the list of packages in which it is necessary to select the following items:
- In paragraph Devel all sub-items whose name begins with the letters gcc (they go in a row = 10 pieces)
- In paragraph Debug sub pv-debugininfo
- In paragraph Utils sub pv
Download the add-on for Cygwin, which is called Netcat here:
unzip all the files in the directory C: \ cygwin. The main thing that would be located in the archive, in the bin folder, file nc.exe
move to the folder C: \ cygwin \ bin. I took the version 1.12 Then download the ADB
Unpack the archive in the folder C: \ cygwin \ bin in the folder C: \ cygwin create a folder called, for example, the VHD.
Download the file VHDtool.exe https: //drive.google.c...hGeEE/view usp = sharing?
Copy it into the folder C: \ cygwin \ VHD This initial training is completed.
Connect your phone to a computer and run Cygwin.bat
Next, enter the following text line by line (Note:
In order to avoid being tortured on the clave, you can copy-paste to copy this sdes line and Cygwin-e klatsat on cap
window, right-click - edit - paste)
adb forward tcp: 5555 tcp: 5555
adb shell
su
/ System / xbin / busybox nc -l -p 5555 -e / system / xbin / busybox dd if = / dev / block / mmcblk0 (and here we must remember where
busybox installed in xbin or bin, which should be the correct.)
This window does not close.
Open another Cygwin terminal (Cygwin.bat) and enter:
adb forward tcp: 5555 tcp: 5555
cd / VHD
nc64 127.0.0.1 5555 | pv -i 0.5> mmcblk0.img
replace 127.0.0.1 ip phone on the network (if connected on Wi-Faya look at the connection properties)
Note: Look carefully at the command input terminal. Sometimes when copying slips such prefix: [Gi EEE should be washed.
After all this is completed will dump up in the folder C: \ cygwin \ VHD. File mmcblk0.img if it enters the 9008 port to write to a micro SD program (run as administrator)
Recording to a USB flash drive. Further instructions on the USB flash drive and then the computer can be formatnut a normal file system only on Linux or formatnut on the phone. Wind will not see her.
{
"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.