How to manually root. Download and unzip the SuperOneClick zip file and...
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
What OS and software are you running? I had the same problem on Ubuntu 10.10 x64, but was able finish the process by completing it by hand. If your brave enough to use the command line to do the process, I can provide the steps.
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
shawnbuck said:
What OS and software are you running? I had the same problem on Ubuntu 10.10 x64, but was able finish the process by completing it by hand. If your brave enough to use the command line to do the process, I can provide the steps.
Click to expand...
Click to collapse
Could you? I have this same problem trying to root on my mac.
Sent from my MB860 using XDA App
I basically have this:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v1 /sdcard/
./adbmac push su-v2 /sdcard/
./adbmac push busybox /sdcard/
./adbmac push Superuser.apk /sdcard/
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
./adbmac remount
./adbmac shell
(the following 3 steps may fail which is OK)
# mv /system/bin/su /system/bin/su.bak
# mv /system/xbin/su /system/xbin/su.bak
# mv /system/xbin/busybox /system/xbin/busybox.bak
# busybox cp /sdcard/su-v* /system/xbin
# cd /system/xbin
(try to execute both su-v*, whichever works keep and renamed to su. For this example we'll assume su-v2 is the correct su)
# rm /system/xbin/su-v1
# mv /system/xbin/su-v2 /system/xbin/su
# busybox cp /sdcard/Superuser.apk /system/app
# busybox cp /sdcard/busybox /system/xbin
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# busybox ln -s /system/xbin/su /system/bin/su
gdanko said:
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
Click to expand...
Click to collapse
In this steps you put up previously, you missed remount the /system partition rw.
Also, what OS & software are you guys using? I'm curious to find out what is causing this problem, so we can correct it in SuperOneClick.
Ubuntu 10.10 x64
shawnbuck said:
In this steps you put up previously, you missed remount the /system partition rw.
# mount -o remount,rw -t yaffs2 /system
Click to expand...
Click to collapse
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p12 /system
shawnbuck said:
In this steps you put up previously, you missed remount the /system partition rw.
# busybox mv /data/local/tmp/su /system/xbin
Click to expand...
Click to collapse
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
gdanko said:
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
Click to expand...
Click to collapse
gdanko said:
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p12 /system
Click to expand...
Click to collapse
Whoops, that slipped by. In any case, you can check what /system is mounted on by checking /etc/mtab.
Still getting permission denied when I type su
How are you using su directly?
Also, have you installed superuser and root checker from the market?
Add these steps to the end:
# chmod 06755 /system/xbin/su
# chmod 0755 /system/xbin/busybox
# reboot
When the phone is up, adb shell back in
Unlock the phone
Type su in the console
Accept the Superuser prompt
I am now rooted
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
I've noticed that the phone doesn't like when you call reboot from the terminal on it.
Also, put the instructions in the first post for anyone in the future.
gdanko said:
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
Click to expand...
Click to collapse
Perfect, thanks!
Might want to update chmod command for /system/xbin/su from 06755 to 6755. I found that after copy 'n pasting these, /system/xbin/su wasn't suid and sgid so it would still give the permission denied error when trying to run su from adb shell.
agentdr8 said:
Might want to update chmod command for /system/xbin/su from 06755 to 6755. I found that after copy 'n pasting these, /system/xbin/su wasn't suid and sgid so it would still give the permission denied error when trying to run su from adb shell.
Click to expand...
Click to collapse
I can confirm this, typing `chmod 06755` doesn't work for me.
Is there a reason we need to set the sgid bit as well?
Probably doesn't need setgid but I left it since it was part of the original instructions.
try with acer liquid mini failed
adb push psneuter /data/local/tmp
adb push su-v2 /data/local/tmp
adb push busybox /data/local/tmp
adb shell
$ busybox chmod +x /data/local/tmp/psneuter
busybox 'permission denied'
what should i do? i am using ubuntu 10.10..thanks for your help...
Related
This guide is for people who want root but want to keep their stock rom, not breaking the warranty, unlocking bootloader etc.
A proud ubuntu user, I am writing this in a new thread purely because the manual rageagainstthecage method and SuperOneClick method did not not work for me, see link to my conclusion below if you care
http://forum.xda-developers.com/showpost.php?p=11305312&postcount=2526
What did work however was via adb shell using psneuter and its fairly simple if you follow the following commands.
This guide assumes you know how to get access to the shell via adb, if you dont then search elsewhere.
OK lets get to business!
1. Download the attached nexus_one_softroot.tar from the bottom of this post and extract contents to the same folder as adb
2. Open up your terminal, cd to the same folder as adb and the extracted files
3. Enter the following commands:
Code:
sudo ./adb push psneuter /data/local/tmp/psneuter
sudo ./adb push busybox /data/local/tmp/busybox
sudo ./adb push su /data/local/tmp/su
sudo ./adb shell chmod 755 /data/local/tmp/psneuter
sudo ./adb shell chmod 755 /data/local/tmp/busybox
sudo ./adb shell chmod 755 /data/local/tmp/su
sudo ./adb shell
After this you should see only a $ which tells us that we at the android command line with user privileges only, lets continue
Code:
$ cd /data/local/tmp
$ ls
busybox
su
psneuter
$ ./psneuter
property service neutered.
killing adbd. (should restart in a second or two)
You will now be kicked out of android shell, lets go back in
Code:
sudo ./adb shell
After this you should see only a # which tells us that we root baby! If you want to double check issue this command
Code:
# id
uid=0(root) gid=0(root)
Lets continue on. From this point we will install busybox and su which will make root permanent
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd /data/local/tmp
# ./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
# busybox cp su /system/bin
# chmod 4755 /system/bin/su
# exit
For some reason I sometimes have to enter exit twice to leave the android shell. Again, re-access the android shell
Code:
sudo ./adb shell
Now in the android shell we can finish up
Code:
# su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
# exit
Lastly we must install Superuser, and I did this from the android market so I knew its the latest version, its simple to get, less command input etc.
Now you have root! I hope this was simple enough to follow, I have not really written a guide before but from lots of searching I just could not find a solution for my Nexus One 2.2.1 FRG83D, especially any guide that uses psneuter.
Anyway, glad to contribute
EDIT - also, being new to starting threads, this may not quite be in the right section of the forum, sorry if thats the case mods
I have an LG Optimus V, which I am trying to root.
My desktop is a Linux Mint 10 LXDE system, and I think ADB is set up properly, because it has been working fine with my nook color.
I was following directions here: http://forum.xda-developers.com/showthread.php?t=935312
When I try to use SUperOneClick, it freezes up at detecting device (I have debugging enabled, and took the sd out.) Since that wasn't working, I tried to root the device manually, following these instructions:
Code:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
When I try to do the step "busybox chmod +x..." I get a permission denied error. I am running as root on my linux box, but obviously just as a regular user in adb. Is there a chmod command I am missing?
Edit: Trying to get more info here: http://forum.xda-developers.com/showthread.php?p=12467368#post12467368
hello at all
i have a little problem. i buyed a used x10i with older firmware but rooted. first of all i only have debian linux 6 64bit and an virtual windows xp. could update to newest firmware 2.1.1.a.0.6 with seus on virtualbox (i did the "repair"). then the root was gone. so i tryed out every version of superoneclick on virtual windows but not working, it freezes everytime. also tried z4mod and flashtool, not working
so i tried manual with adb (i have installed android sdk). i used the binaries from superoneclick 1.9.5. i think the best is when i post my cmd-session:
(i have to replace the shell-prompt from debian with [debian]$, because the forum says me this is an external link...)
Code:
[debian]$ adb push psneuter /data/local/tmp
1635 KB/s (585731 bytes in 0.349s)
[debian]$ adb push su-v1 /sdcard/
430 KB/s (26256 bytes in 0.059s)
[debian]$ adb push su-v2 /sdcard/
579 KB/s (26264 bytes in 0.044s)
[debian]$ adb push su-v3 /sdcard/
437 KB/s (26324 bytes in 0.058s)
[debian]$ adb push Superuser.apk /sdcard/
2063 KB/s (196521 bytes in 0.092s)
[debian]$ adb shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
property service neutered.
killing adbd. (should restart in a second or two)
[debian]$ adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p12 /system
# mv /system/bin/su /system/bin/su.bak
# mv /system/xbin/su /system/xbin/su.bak
# busybox cp /sdcard/su-v* /system/xbin
# cd /system/xbin
# busybox chmod +x su-v*
# su-v1
reloc_library[1245]: 3712 cannot locate '_ZNK7android6Parcel15setDataPositionEj'...CANNOT LINK EXECUTABLE
# exit
[debian]$ adb shell
# su-v2
# exit
# su-v3
# exit
# rm /system/xbin/su-v1
# rm /system/xbin/su-v2
# mv /system/xbin/su-v3 /system/xbin/su
# busybox cp /sdcard/Superuser.apk /system/app
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# su
# exit
# reboot
[debian]$ adb shell
$ su
Permission denied
$
you can see i get a rootshell and mount system, copy su and everything, but when i reboot everything is gone. if i don't reboot and check with "root-checker" it says me that i don't have root access.
what i'm doing wrong? i'm a noob in "hacking" phones but have some knowledge with linux&shells
thanks a lot for some help
could solve it: was using superoneclick on a windows-pc from my friend.works great.. but still iterested in a linux-only solution because i want to develop a shell-script for rooting for linux users
My Kindle fire hdx 8.9 worked normally since I bought it. Yesterday I remove the signature to install google service, and the wrong was it can't restart and I reset it to the factory from recovery. Now it still rest on the colored "kindle fire". But it seems some processes have been loaded because the MTP devices can be found in PC and the adb mode seems work normally. I think some steps losed in the boot. Can I recover it by adb mode or other methods? Thank you.
I reset it to the factory from recovery.
Click to expand...
Click to collapse
very bad, you lost root, so no ideas.
But try:
Code:
adb shell
su
ONYXis said:
very bad, you lost root, so no ideas.
But try:
Code:
adb shell
su
Click to expand...
Click to collapse
Yes , the root tools can work. Input su and display "[email protected]:/#". It seems something different with the bricked in forum.
tianlie said:
Yes , the root tools can work. Input su and display "[email protected]:/#". It seems something different with the bricked in forum.
Click to expand...
Click to collapse
Good.
You need put back original files:
services.odex and any others that you changed
like this:
Code:
adb shell
su
mount -o remount /system
adb push services.odex /data/local/tmp
chmod 755 /data/local/tmp/services.odex
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
or simple
Code:
adb shell
su
mount -o remount /system
rm /system/framework/services.odex
adb push services.odex /system/framework/
chmod 755 /system/framework/services.odex
reboot
ONYXis said:
Good.
You need put back original files:
services.odex and any others that you changed
like this:
Code:
adb shell
su
mount -o remount /system
adb push services.odex /data/local/tmp
chmod 755 /data/local/tmp/services.odex
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
or simple
Code:
adb shell
su
mount -o remount /system
rm /system/framework/services.odex
adb push services.odex /system/framework/
chmod 755 /system/framework/services.odex
reboot
Click to expand...
Click to collapse
"adb push services.odex /data/local/tmp" This command give an error: device not found.
Does it need the file "services.odex"? Where?
Thanks a lot.
The complete response:
D:\win32>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount /system
mount -o remount /system
[email protected]:/ # rm /system/framework/services.odex
rm /system/framework/services.odex
[email protected]:/ # adb push services.odex /system/framework/
adb push services.odex /system/framework/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ # chmod 755 /system/framework/services.odex
chmod 755 /system/framework/services.odex
Unable to chmod /system/framework/services.odex: No such file or directory
10|[email protected]:/ # reboot
reboot
Sorry. Syntax error. I am at gym now. Ill help you when come home. What version of firmware do you use?
ONYXis said:
Sorry. Syntax error. I am at gym now. Ill help you when come home. What version of firmware do you use?
Click to expand...
Click to collapse
It should be 14.3.2.5. OK. I wait you.:good:
https://www.dropbox.com/s/tfd5htc9smt17nx/Desktop.zip?dl=0
Code:
adb push C:\Users\xxx\Desktop\services.odex /sdcard/services.odex
adb shell
su
mount -o remount /system
cp /sdcard/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
If it will not help - try to put back framework-res.apk.
ONYXis said:
https://www.dropbox.com/s/tfd5htc9smt17nx/Desktop.zip?dl=0
Code:
adb push C:\Users\xxx\Desktop\services.odex /sdcard/services.odex
adb shell
su
mount -o remount /system
cp /sdcard/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
If it will not help - try to put back framework-res.apk.
Click to expand...
Click to collapse
That's great! Kindle is upgrading... Select language, register, the desktop come back.
Thank you, ONYXis, you are my god!:good:
To others, don't think the factory set is best.
Thank you again.
fix.bat
Code:
::writable(mount writable)
adb shell < scripts/writeable.sh
::apps remower
adb shell < scripts/mdmkaldir.sh
::dnsconf change
::starting problem here file cant owerwrite.
adb push 20-dns.conf system/etc/dhcpcd/dhcpcd-hooks
::system readonly
adb shell < scripts/readonly.sh
::needed apks
::how i can isntall system app filemanager only
adb install apps/com.rhmsoft.fm-1.apk
adb install apps/com.buak.Link2SD.apk
adb install apps/uk.co.mytechie.setDNS.apk
::(root change)
adb install apps/eu.chainfire.supersu-minAPI7.apk
PAUSE
adb reboot
mdmkaldir.sh
Code:
su
cd system/app
rm EBAMarket.apk
rm EBA_SSO.apk
rm TR_Soft_Keyboard_default.apk
rm FatihMDM_ibnisina.apk
rm MpTest.apk
rm MpTest.odex
rm MpTestGps.apk
rm MpTestGps.odex
exit
exit
writable.sh
Code:
su
mount -o remount,rw /system
exit
exit
please help for this script
adb push 20-dns.conf system/etc/dhcpcd/dhcpcd-hooks
this line not work please help.
gencom said:
fix.bat
Code:
::writable(mount writable)
adb shell < scripts/writeable.sh
::apps remower
adb shell < scripts/mdmkaldir.sh
::dnsconf change
::starting problem here file cant owerwrite.
adb push 20-dns.conf system/etc/dhcpcd/dhcpcd-hooks
::system readonly
adb shell < scripts/readonly.sh
::needed apks
::how i can isntall system app filemanager only
adb install apps/com.rhmsoft.fm-1.apk
adb install apps/com.buak.Link2SD.apk
adb install apps/uk.co.mytechie.setDNS.apk
::(root change)
adb install apps/eu.chainfire.supersu-minAPI7.apk
PAUSE
adb reboot
mdmkaldir.sh
Code:
su
cd system/app
rm EBAMarket.apk
rm EBA_SSO.apk
rm TR_Soft_Keyboard_default.apk
rm FatihMDM_ibnisina.apk
rm MpTest.apk
rm MpTest.odex
rm MpTestGps.apk
rm MpTestGps.odex
exit
exit
writable.sh
Code:
su
mount -o remount,rw /system
exit
exit
please help for this script
adb push 20-dns.conf system/etc/dhcpcd/dhcpcd-hooks
this line not work please help.
Click to expand...
Click to collapse
Why do you need scripts when there are apps that can replace system files easily if rooted?
Dom3616 said:
Why do you need scripts when there are apps that can replace system files easily if rooted?
Click to expand...
Click to collapse
yes rooted all ok only
adb push 20-dns.conf system/etc/dhcpcd/dhcpcd-hooks
this line not work
gencom said:
yes rooted all ok only
adb push 20-dns.conf system/etc/dhcpcd/dhcpcd-hooks
this line not work
Click to expand...
Click to collapse
Just use ES Explorer (it's free) and copy/paste the file.
Dom3616 said:
Just use ES Explorer (it's free) and copy/paste the file.
Click to expand...
Click to collapse
i tryed already rooted device rooted filemanagers not work edit or owerwirite not work.
console log here
Code:
C:\Users\akiyoshi\Desktop\MT\etab4\ADB_Fastboot>adb shell 0<scripts/writeable.sh
su
mount -o remount,rw /system
exit
exit
[email protected]:/ $ su
1|[email protected]:/ $ mount -o remount,rw /system
mount: Operation not permitted
255|[email protected]:/ $ exit
C:\Users\akiyoshi\Desktop\MT\etab4\ADB_Fastboot>adb shell 0<scripts/mdmkaldir.sh
su
cd system/app
rm EBAMarket.apk
rm EBA_SSO.apk
rm TR_Soft_Keyboard_default.apk
rm FatihMDM_ibnisina.apk
rm MpTest.apk
rm MpTest.odex
rm MpTestGps.apk
rm MpTestGps.odex
exit
exit
[email protected]:/ $ su
[email protected]:/ # cd system/app
[email protected]:/system/app # rm EBAMarket.apk
rm failed for EBAMarket.apk, No such file or directory
255|[email protected]:/system/app # rm EBA_SSO.apk
rm failed for EBA_SSO.apk, No such file or directory
255|[email protected]:/system/app # rm TR_Soft_Keyboard_default.apk
rm failed for TR_Soft_Keyboard_default.apk, No such file or directory
255|[email protected]:/system/app # rm FatihMDM_ibnisina.apk
rm failed for FatihMDM_ibnisina.apk, No such file or directory
255|[email protected]:/system/app # rm MpTest.apk
rm failed for MpTest.apk, No such file or directory
255|[email protected]:/system/app # rm MpTest.odex
rm failed for MpTest.odex, No such file or directory
255|[email protected]:/system/app # rm MpTestGps.apk
rm failed for MpTestGps.apk, No such file or directory
255|[email protected]:/system/app # rm MpTestGps.odex
rm failed for MpTestGps.odex, No such file or directory
255|[email protected]:/system/app # exit
255|[email protected]:/ $ exit
[B][COLOR="Red"]C:\Users\akiyoshi\Desktop\MT\etab4\ADB_Fastboot>adb push 20-dns.conf system/etc/dhcpcd/dhcpcd-hooks
failed to copy '20-dns.conf' to 'system/etc/dhcpcd/dhcpcd-hooks/20-dns.conf': Read-only file system[/COLOR][/B]
C:\Users\akiyoshi\Desktop\MT\etab4\ADB_Fastboot>adb shell 0<scripts/readonly.sh
su
mount -o remount,ro /system
exit
exit
[email protected]:/ $ su
[email protected]:/ # mount -o remount,ro /system
[email protected]:/ # exit
[email protected]:/ $ exit
C:\Users\akiyoshi\Desktop\MT\etab4\ADB_Fastboot>adb install apps/com.rhmsoft.fm-1.apk
3920 KB/s (4357102 bytes in 1.085s)
pkg: /data/local/tmp/com.rhmsoft.fm-1.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Users\akiyoshi\Desktop\MT\etab4\ADB_Fastboot>adb install apps/com.buak.Link2SD.apk
3572 KB/s (4218237 bytes in 1.152s)
pkg: /data/local/tmp/com.buak.Link2SD.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Users\akiyoshi\Desktop\MT\etab4\ADB_Fastboot>adb install apps/uk.co.mytechie.setDNS.apk
2696 KB/s (877302 bytes in 0.317s)
pkg: /data/local/tmp/uk.co.mytechie.setDNS.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Users\akiyoshi\Desktop\MT\etab4\ADB_Fastboot>adb install apps/eu.chainfire.supersu-minAPI7.apk
3812 KB/s (5905465 bytes in 1.512s)
pkg: /data/local/tmp/eu.chainfire.supersu-minAPI7.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Users\akiyoshi\Desktop\MT\etab4\ADB_Fastboot>adb reboot
C:\Users\akiyoshi\Desktop\MT\etab4\ADB_Fastboot>PAUSE
Press any key to continue . . .
maybe required mount /etc as writable. etc not linked system??
need help replace system file in etc folder .