This MultiROM trying to install but I get the following error:
Log
Installing '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Installing MultiROM for condor
Extracting binaries...
about to run program [/sbin/busybox] with 3 args
mount: mounting /dev/block/mmcblk0p36 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/busybox] with 3 args
minzip: Extracted 40 file(s)
minzip: Extracted 6 file(s)
about to run program [/tmp/extract_multirom.sh] with 1 args
mkdir: can't create directory '/data/media/0/multirom': Permission denied
chown: /data/media/0/multirom: No such file or directory
chmod: /data/media/0/multirom: No such file or directory
mkdir: can't create directory '/data/media/0/multirom/roms': No such file or directory
chown: /data/media/0/multirom/roms: No such file or directory
chmod: /data/media/0/multirom/roms: No such file or directory
touch: /data/media/0/multirom/.nomedia: No such file or directory
chown: /data/media/0/multirom/.nomedia: No such file or directory
rm: can't remove '/data/media/0/multirom/boot.img-ubuntu*': No such file or directory
rm: can't remove '/data/media/0/multirom/infos/*': No such file or directory
rm: can't remove '/data/media/0/multirom/res/*': No such file or directory
cp: can't create '/data/media/0/multirom/adbd': No such file or directory
cp: can't create '/data/media/0/multirom/busybox': No such file or directory
cp: can't create '/data/media/0/multirom/exfat-fuse': No such file or directory
cp: can't create '/data/media/0/multirom/fw_mounter': No such file or directory
cp: can't create directory '/data/media/0/multirom/icons': No such file or directory
cp: can't create '/data/media/0/multirom/kexec': No such file or directory
cp: can't create '/data/media/0/multirom/lz4': No such file or directory
cp: can't create '/data/media/0/multirom/mrom.fstab': No such file or directory
cp: can't create '/data/media/0/multirom/multirom': No such file or directory
cp: can't create '/data/media/0/multirom/ntfs-3g': No such file or directory
cp: can't create directory '/data/media/0/multirom/res': No such file or directory
cp: can't create '/data/media/0/multirom/trampoline': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-init': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-touch-init': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-touch-sysimage-init': No such file or directory
chmod: /data/media/0/multirom/multirom: No such file or directory
chmod: /data/media/0/multirom/busybox: No such file or directory
chmod: /data/media/0/multirom/trampoline: No such file or directory
chmod: /data/media/0/multirom/kexec: No such file or directory
chmod: /data/media/0/multirom/ntfs-3g: No such file or directory
chmod: /data/media/0/multirom/exfat-fuse: No such file or directory
chmod: /data/media/0/multirom/lz4: No such file or directory
chmod: /data/media/0/multirom/ubuntu-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-init/local: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-init/scripts/touch: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-sysimage-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-sysimage-init/scripts/touch: No such file or directory
chmod: /data/media/0/multirom: No such file or directory
chown: /data/media/0/multirom: No such file or directory
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/extract_multirom.sh") == 0
assert failed: run_program("/tmp/extract_multirom.sh") == 0
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip'
Error flashing zip '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip
Now edit the build.prop but I get the same error also delete the first lines of updater.script and follows me out the same. I just worked with me but I want to install cm11 in stock
Sorry for my bad English
Which rom you are using as a primary rom
prajapati ravi said:
Which rom you are using as a primary rom
Click to expand...
Click to collapse
I'm using the stock
Then whats the problem add the cm11 and reboot
---------- Post added at 01:20 AM ---------- Previous post was at 01:16 AM ----------
magdeoz said:
I'm using the stock
Click to expand...
Click to collapse
If you use stock as primary rom then will not get any issue's if still get it then you doing something wrong with your hand
Hi
I have problem with using AdAway on my Z3TC.
I have successfully rooted my device. Now I'm on stock KK with root and locked back BL.
I installed AdAway but it doesn't want to work. There is problem with hosts file.
I found that I have to change permissions for /system to -rw-rw-rw and for file host too. But the problem is I can't. When I'm trying to change permissions I got info: Changing permissions was not successful. And it doesn't matter what Explorer I use.
Any ideas? Of course there is root permission for explorer... May the locked Bootloader be the problem (I doubt...)
To write in system you have to install from the recovery ricdefeat
https://github.com/dosomder/SonyRICDefeat/blob/master/RICDefeat.zip
I didn't installed TWRP after relocking BL.
I tried now and there is another problem (looks similar)
Code:
##########################################################
#
# Installing XZDR version 2.8.3 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
mount: permission denied (are you root?)
mount: permission denied (are you root?)
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.philz.cpio.lzma': Read-only file system
chmod: /system/bin/recovery.twrp.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.cwm.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.philz.cpio.lzma: No such file or directory
Rename stock mr
mv: can't rename '/system/bin/mr': Read-only file system
Rename stock chargemon
mv: can't rename '/system/bin/chargemon': Read-only file system
Copy chargemon script to system.
cp: can't create '/system/bin/chargemon': File exists
chmod: /system/bin/chargemon: Read-only file system
Copy dualrecovery.sh to system.
cp: can't create '/system/bin/dualrecovery.sh': Read-only file system
chmod: /system/bin/dualrecovery.sh: No such file or directory
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': Read-only file system
chmod: /system/bin/rickiller.sh: No such file or directory
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': Read-only file system
chmod: /system/app/NDRUtils.apk: No such file or directory
Copy disableric to system.
cp: can't create '/system/xbin/disableric': Read-only file system
chmod: /system/xbin/disableric: No such file or directory
Creating /system/.XZDualRecovery to store a backup copy of busybox.
mkdir failed for /system/.XZDualRecovery, Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': Read-only file system
cp: can't create '/system/.XZDualRecovery/': Is a directory
chmod: /system/xbin/busybox: No such file or directory
chmod: /system/.XZDualRecovery/busybox: No such file or directory
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event3!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
/system/bin/sh: /system/xbin/busybox: not found
=============================================
Installation finished. Enjoy the recoveries!
ADB asked for root permission during installation, I agreed.
And after all recovery is not installed...
I see where the problem is. You can not write in system because you need ricdefeat, but to install XZDualRecovery and flash from there ricdefeat need to write in "system"
I'm afraid you have to start over. Is necessary Flash Ricdefeat from the TWRP recovery before it is erased.
Read here (where it says "To install rooted Stock"):
http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534 (relatively speaking there nicely explains the steps to take and what order , replace firmware sgp621 -> sgp611)
or my tutorial in Spanish I did not know if you know the language:
http://www.htcmania.com/showthread.php?t=966040 (Part B)
---
I will try to explain what I would do, I'm using google translator if not understood:
1- unlock bootloader
2- install advanced stock kernel
3- Now there are two options:
** 3A) Create pre-rooted firmware. Copy firmware pre-rooted and ricdefeat.zip on the tablet. Login to TWRP and flash firmware then ricdefeat, and restart at the end.
** 3B) Copy to tablet the ricdefeat file. Go to TWRP recovery, flash ricdefeat and restart. With flashtool , install on the tablet only the kernel, using the original firmware.
4- Start android and restore TA
5- Install XYDualRecovery to have a custom recovery
I tried rooting my phone with kingoroot bit found it was to buggy then I installed it and factory reset my phone now when I press power the phone does not.go into sleep mode even if timmed.
No of blocks updated = 0
sbl1 update success.
start to update splash.diff ...
splash.diff not found
Verifying current system...failed to stat "system/app/Drive/Drive.apk": No such file or directory
failed to stat "system/app/Drive/lib/arm/libdocscanner_image.so": No such file or directory
failed to stat "system/app/Drive/lib/arm/librectifier.so": No such file or directory
failed to stat "system/app/Drive/lib/arm/libwebp_android.so": No such file or directory
failed to stat "system/app/GooglePinyinIME/GooglePinyinIME.apk": No such file or directory
failed to stat "system/app/GooglePinyinIME/lib/arm/libpinyin_data_bundle.so": No such file or directory
failed to stat "system/app/GoogleTTS/GoogleTTS.apk": No such file or directory
failed to stat "system/app/Hangouts/Hangouts.apk": No such file or directory
failed to stat "system/app/Hangouts/lib/arm/libcronet.so": No such file or directory
failed to stat "system/app/Hangouts/lib/arm/libframesequence.so": No such file or directory
failed to stat "system/app/Hangouts/lib/arm/libvideochat_jni.so": No such file or directory
failed to stat "system/app/KoreanIME/KoreanIME.apk": No such file or directory
failed to stat "system/app/LatinImeGoogle/LatinImeGoogle.apk": No such file or directory
failed to stat "system/app/Maps/Maps.apk": No such file or directory
failed to stat "system/app/Maps/lib/arm/libgmm-jni.so": No such file or directory
failed to stat "system/app/Photos/lib/arm/libfilterframework_jni.so": No such file or directory
failed to stat "system/app/Photos/lib/arm/libmoviemaker-jni.so": No such file or directory
failed to stat "system/app/PlusOne/PlusOne.apk": No such file or directory
failed to stat "system/app/PlusOne/lib/arm/libphotoeditor_native.so": No such file or directory
failed to stat "system/app/YouTube/YouTube.apk": No such file or directory
file "/system/bin/bootanimation" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/bootanimation" has unexpected contents.
"/system/bin/bootanimation" has unexpected
Hi all,
Im trying to root my Doogee T3 but haven't been sucessfull so far. Seems like no one tried before or posted about it.
It has a
Mediatek MT6753,
so MTKdroidTools should work but it gives a few errors:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
I tried to install twrp but it doesnt seem to work on this device. Happy if you prove me wrong.
I found a guide to root a Doogee F5, same chipset as the T3 so I gave it a shot.
(adb_log at the end, obviously a disaster)
Maybe there is a way to use the User2Root option of the MTK Engineer Mode? Like used in the F5 guide but I dont really understand what it actually does. I understand that its trying to change the linux-like persmissions and that it doesn't find anything, but thats it.
Lets skip this stuff:
-Yes, USB debugging and OEM unlocking are enabled
-Yes, I do have adb and fastboot
-Yes, I do have the drivers
-I already tried previous MTKdroidTools Versions
-KingRoot doesn't work
-RootGenius doesn't work
-Framaroot doesn't work
-I wasn't able to create a scatter file but found one for MT6753 online
adb log of Doogee F5 method:
Code:
Drcken Sie eine beliebige Taste . . .
mount: Read-only file system
/system/bin/sh: can't create /system/toolbox: Read-only file system
chmod: /system/toolbox: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/toolbox: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/toolbox: No such file or directory
mkdir: '/system/bin/.ext': Read-only file system
chown: /system/bin/.ext: No such file or directory
chown: /system/bin/.ext: No such file or directory
chmod: /system/bin/.ext: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
mkdir: '/system/app/SuperSU': Read-only file system
rm: /system/bin/.ext/.su: No such file or directory
failed to copy 'su_bin/su' to '/system/bin/.ext/.su': Read-only file system
chown: /system/bin/.ext/.su: No such file or directory
chown: /system/bin/.ext/.su: No such file or directory
chmod: /system/bin/.ext/.su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext/.su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext/.su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/su: No such file or directory
failed to copy 'su_bin/su' to '/system/xbin/su': Read-only file system
chown: /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
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/daemonsu: No such file or directory
failed to copy 'su_bin/su' to '/system/xbin/daemonsu': Read-only file system
chown: /system/xbin/daemonsu: No such file or directory
chown: /system/xbin/daemonsu: No such file or directory
chmod: /system/xbin/daemonsu: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/daemonsu: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/daemonsu: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/sugote: No such file or directory
failed to copy 'su_bin/su' to '/system/xbin/sugote': Read-only file system
chown: /system/xbin/sugote: No such file or directory
chown: /system/xbin/sugote: No such file or directory
chmod: /system/xbin/sugote: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote: No such file or directory
rm: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: can't create /system/xbin/sugote-mksh: Read-only file system
chown: /system/xbin/sugote-mksh: No such file or directory
chown: /system/xbin/sugote-mksh: No such file or directory
chmod: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/supolicy: No such file or directory
failed to copy 'su_bin/supolicy' to '/system/xbin/supolicy': Read-only file system
chown: /system/xbin/supolicy: No such file or directory
chown: /system/xbin/supolicy: No such file or directory
chmod: /system/xbin/supolicy: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/supolicy: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/supolicy: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/lib64/libsupol.so: No such file or directory
failed to copy 'su_bin/libsupol.so' to '/system/lib64/libsupol.so': Read-only file system
chown: /system/lib64/libsupol.so: No such file or directory
chown: /system/lib64/libsupol.so: No such file or directory
chmod: /system/lib64/libsupol.so: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/lib64/libsupol.so: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/lib64/libsupol.so: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
chown: /system/app/SuperSU: No such file or directory
chown: /system/app/SuperSU: No such file or directory
chmod: /system/app/SuperSU: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/app/SuperSU/SuperSU.apk: No such file or directory
failed to copy 'su_bin/Superuser.apk' to '/system/app/SuperSU/SuperSU.apk': Read-only file system
chown: /system/app/SuperSU/SuperSU.apk: No such file or directory
chown: /system/app/SuperSU/SuperSU.apk: No such file or directory
chmod: /system/app/SuperSU/SuperSU.apk: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU/SuperSU.apk: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU/SuperSU.apk: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/etc/install-recovery.sh: No such file or directory
failed to copy 'su_bin/install-recovery.sh' to '/system/etc/install-recovery.sh': Read-only file system
chown: /system/etc/install-recovery.sh: No such file or directory
chown: /system/etc/install-recovery.sh: No such file or directory
chmod: /system/etc/install-recovery.sh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/install-recovery.sh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/install-recovery.sh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
/system/bin/sh: /system/toolbox: not found
ln: no such tool
ln: cannot create symbolic link from '/system/etc/install-recovery.sh' to '/system/bin/install-recovery.sh': File exists
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/install-recovery.sh' to u:object_r:system_file:s0: Read-only file system
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/install-recovery.sh' to u:object_r:system_file:s0: Read-only file system
rm: /system/bin/app_process: Read-only file system
/system/bin/sh: /system/toolbox: not found
ln: no such tool
ln: cannot create symbolic link from '/system/xbin/daemonsu' to '/system/bin/app_process': File exists
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process' to u:object_r:system_file:s0: Read-only file system
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process' to u:object_r:system_file:s0: Read-only file system
mv: bad '/system/bin/app_process64': Read-only file system
/system/bin/sh: /system/toolbox: not found
ln: no such tool
ln: cannot create symbolic link from '/system/xbin/daemonsu' to '/system/bin/app_process64': File exists
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process64' to u:object_r:system_file:s0: Read-only file system
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process64' to u:object_r:system_file:s0: Read-only file system
rm: /system/bin/app_process_init: No such file or directory
/system/bin/sh: can't create /system/bin/app_process_init: Read-only file system
chown: /system/bin/app_process_init: No such file or directory
chown: /system/bin/app_process_init: No such file or directory
chmod: /system/bin/app_process_init: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/app_process_init: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/app_process_init: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/etc/init.d/99SuperSUDaemon: No such file or directory
failed to copy 'su_bin/99SuperSUDaemon' to '/system/etc/init.d/99SuperSUDaemon': Read-only file system
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chmod: /system/etc/init.d/99SuperSUDaemon: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/init.d/99SuperSUDaemon: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/init.d/99SuperSUDaemon: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
{
"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.