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
Related
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
I try to install ubuntu on my i9300
I have an issue in terminal when i write the code: sh ubuntu.sh
Its appear an error..
Code:
[email protected]:/ $ su
[email protected]:/ # cd sdcard/ubuntu
cd sdcard/ubuntu
[email protected]:/sdcard/ubuntu # sh ubuntu.sh
sh ubuntu.sh
mkdir failed for /data/local/mnt, File exists
mount: Operation not supported on transport endpoint
mount: Operation not supported on transport endpoint
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: mounting /sdcard on /data/local/mnt/sdcard failed: No such file or directory
net.ipv4.ip_forward = 1
ubuntu.sh[30]: can't create /data/local/mnt/etc/resolv.conf: No such file or directory
ubuntu.sh[31]: can't create /data/local/mnt/etc/resolv.conf: No such file or directory
ubuntu.sh[32]: can't create /data/local/mnt/etc/hosts: No such file or directory
ubuntu is configured with SSH and VNC servers that can be accessed from the IP:
eth0: No such device
BusyBox v1.21.1-jb bionic (2013-07-25 21:23 +0100) multi-call binary.
Usage: chroot NEWROOT [PROG ARGS]
Run PROG with root directory set to NEWROOT
Shutting down ubuntu ARM
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
losetup: /dev/loop7: No such file or directory
1|[email protected]:/sdcard/ubuntu #
Sent from my GT-I9300 using Tapatalk 4
This is the wrong forum .
See third post down.
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
Please confirm that Flashfire work on the latest firmware for Verizon Galaxy S4 SCH-I545...
I don't want to risk it.
I guess I bricked it now that I tried...
FlashFire works fine as long as you're rooted.
Don't know how you'd brick it.
Well Flashfire requires SuperSU for the most part.
If I can remember, I tried "replace Kinguser with SuperSU" when i was on OF1, and it failed. It rebooted and SuperSU failed to install. I guess I can't take any more risks...
Here's what it says:
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
Failure - not installed for 0
Failure [DELETE_FAILED_INTERNAL_ERROR]
rm: /system/app/Kinguser.apk: No such file or directoryFailure - not installed for 0
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
pkg: /sdcard/mrw/superuser.apk
Failure [INSTALL_FAILED_USER_RESTRICTED]
rm: /dev/reportroot: No such file or directory
chattr: stat /system/etc/install_recovery.sh: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
Error type 3
Error: Activity class {eu.chainfire.supersu/eu.chainfire.supersu.MainActivity} does not exist.
I guess it's the bootloader.
Kotetsukun said:
Well Flashfire requires SuperSU for the most part.
If I can remember, I tried "replace Kinguser with SuperSU" when i was on OF1, and it failed. It rebooted and SuperSU failed to install. I guess I can't take any more risks...
Here's what it says:
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
Failure - not installed for 0
Failure [DELETE_FAILED_INTERNAL_ERROR]
rm: /system/app/Kinguser.apk: No such file or directoryFailure - not installed for 0
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
pkg: /sdcard/mrw/superuser.apk
Failure [INSTALL_FAILED_USER_RESTRICTED]
rm: /dev/reportroot: No such file or directory
chattr: stat /system/etc/install_recovery.sh: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
Error type 3
Error: Activity class {eu.chainfire.supersu/eu.chainfire.supersu.MainActivity} does not exist.
I guess it's the bootloader.
Click to expand...
Click to collapse
It isn't the bootloader, it means your root access didn't implement correctly... something is wrong with your kinguser.
{
"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.