Related
I have never had an issue, but a few people have commented recently (odd that it's mostly recent) that when they delete a file it seems to re-appear.
IF (and only if), you are having this issue, could you please post the version of Root Explorer you are using and the build you are running (and perhaps how you got your build, ie kies, ota, odin, flash).
I'm hoping this will lead to a common issue (not likely, worth a shot).
The most recent build is 2.12.4. I don't understand why there is a small number of people having issues. I've been trying to contact the developer as well and hope this thread will help him too.
Thanks.
Have you tried root manager?
I'm using Root Explorer - 2.10.2 with JI6. I updated through Odin. I do have root.
^^ nomad, not trying to sound rude:
"I have never had an issue"
"IF (and only if), you are having this issue, could you please post"
Click to expand...
Click to collapse
I had this issue with 2.12.2 and Bionix Fusion & Obsidian.
Sean what did u do to resolve it?
This is sort of ot, but Astro has decided to let me delete system apps which it never did before. I'm running fusion 1.2 stock kernel.
Don't blame me, blame my keyboard's autocorrection algorithm.
flashyp said:
Sean what did u do to resolve it?
Click to expand...
Click to collapse
didn't resolve it really, I wanted to delete some bloatware but I ended up just freezing the apps in Titanium Backup.
I contacted the developer *and got a super fast response*. Please make sure you are on the latest build. Please see his email pasted below.
Hi,
Thanks very much for your support, it’s much appreciated. I actually have a Galaxy S myself with Android 2.1 and have been running Root Explorer on it successfully for some months now. There was an issue a while back in that remounting the system partition didn’t work, but that was fixed in a recent update. Also, I’ve just updated to Froyo and rooted using Z4Root and Root Explorer is still working well. So on a rooted stock Galaxy S I know there are no problems.
So the question is, what is the difference on the phones where there’s a problem? Are there any major differences in the carrier specific versions? And are the problems only happening on custom ROMs? One person recently reported that Root Explorer didn’t recognise root on his Galaxy and I found that he was running a custom ROM and the su file was placed in a non-standard location.
Ok, something has just come to mind. When I first received my phone I was surprised to find that the system partition was mounted as R/W even before rooting. But of course you still don’t have permission to change system files. I’ve just replicated this situation by remounting system as R/W and renaming su to sux. I then closed Root Explorer and restarted it. It started in non-root mode and when I went to system it correctly reported the file system state as r/w but there was no “Mount R/O” button. I tried a delete and then a rename and the app reported these as having worked. But going out and back in showed that the changes didn’t actually work. I’m pretty sure this must be what’s happening for some people. So the question you need to ask them is whether they can see the mount button. If not then their phone isn’t rooted. Do you agree that this is the most likely scenario?
In the meantime I need to make a change to Root Explorer to properly check whether these operations worked and not mislead the user that the change happened.
Thanks for pointing this out. Galaxy S phones are probably the most popular out there at the moment. I think by fixing this issue there will be a lot more happy Root Explorer users!
Best Regards,
Colin
Click to expand...
Click to collapse
Once I pointed out that users were indeed rooted and saw the button, this is the response I received:
Well that blows my theory out of the water
The actual delete is just a simple rm command so there isn’t much that can go wrong. One possibility is a dodgy BusyBox binary. I’ve seen this cause problems for a few people but it’s very rare. If BusyBox is ok then I can only guess that the remount hasn’t worked. One question to ask is whether the remount operation appears to work. If it does nothing and the mount status stays as either r/w or r/o then this may be the problem. If this is the issue then it would be useful to see the output from a mount command. I can then push this through Root Explorer in debug mode and find out what command it’s running to perform the remount.
Click to expand...
Click to collapse
thanks for your help.
I'm running Root Explorer 2.12.2 on Obsidian v2.2 Froyo. I do see the Mount as R/W button, and I'm running BusyBox v1.17.1
I'm going to try re-installing BB, I'll post back if it fixes the issue.
Edit: WTH, it's working now. I had a dodgy BusyBox install.
Edit x2: And it's broken again. Weird.
The developer said there was an issue with old builds, why not update?
s15274n said:
The developer said there was an issue with old builds, why not update?
Click to expand...
Click to collapse
Working on that now. I don't think it's an issue with Root Explorer though because if, upon the permission failure, I simply re-install BB, RE is then able to edit files again. I need to mess around with it more to be sure, but I'll update RE in the meantime.
Download rar file with apk:
dump.ru/file/5037798
or
depositfiles.com/files/7sh8g638s
rar password: cea69e0419
sha1sum of apk: 80ff2925e12b8d3f2e9c0cabd5b294e6556b2e3f
Archangel one-click-root from the Archaism Team
This will give you temporary or permanent root on your Archos 101 - firmware 2.0.71
Archos are kind enough to provide a SDE firmware which can allow root access,
but involves some significant changes to the system and they say that they will
invalidate your warranty if you install it. This is a bit frightening for new owners.
Archangel solves this with a painless one-click-root which you can uninstall at any time.
It does not use the SDE developer firmware.
This was specifically designed for the Archos 101 with firmware 2.0.71 - it may work on
other Archos devices or firmwares, but has not been tested and is not recommended for them.
If you find this application useful, please donate to those great forums who have given
the android root community so much. Encourage them to keep up their great work. We are
fans of C-Skills Blog, XDA Developers and Modaco Forum.
When installed, this app will use approx 10mb of storage space. Don't run it if you don't
have that much spare.
Usage Instructions:
1) Make sure you have 10mb of space available on the internal storage
2) Make sure you are connected on Wifi
3) Run the Archangel app
4) Click to install SuperUser application
5) Click to get root!
6) Check everything is working correctly, try an app which needs root
7) Once you have root you can tick the "Permanent" root option to always have root.
8) Party Hard!
To turn off root, either just reboot, or turn off permanent root and reboot if you had
enabled it.
To uninstall, just uninstall like any other app. You may also want to use the menu item
to clean up before you uninstall.
You can create a script in /sdcard/sdcard/extraroot.sh and this will be executed as root
whenver you reboot, so you can use this to do any additional root functions you want.
Enjoy!
does this work?
anyone try yet?
I have A70 so i'm not sure if this will work for me
ohh a video demo would be nice
I think this is a scam "Permanent" root is not possible because the filesystem is a read-only filesystem. But I can be wrong.
I'll download this and try to inspect it.
I hope this works, I really want to get Titanium Backup working.
Well I haven't tried yet, but did a quick analysis on the APK:
Permissions on the APK does not seem to be too fishy:
Storage: modify/delete SD card contents
System tools: view and change WIFI state
and automatically start at boot
APK contains superuser, su and ls binaries.
It Works
jsperri: I saw the same as you when I looked at it.
I did install it and it seems to be working. I was able to go su from the terminal and backup an app with Titanium Backup.
I can also confirm that if permanent root is checked this will still work after reboot. When I was looking at the app it looked like it plugged into the launcher process. So perhaps it is just starting just after android is loaded.
Although I have not verified, I suspect that /system is still read only because of squashfs.
What bothers me is first the dates within the apk are 29/2/2008 for all files.
Then the binaries su is a gzipped binary superuser is a gzipped superuser.apk BUT ls is not compressed.
Why do they need ls the ls of the ROM should work fine. I suspect a trojan but i'm not sure. I could be paranoid but a rar with passwords come on......
xdaAlan said:
jsperri: I saw the same as you when I looked at it.
I did install it and it seems to be working. I was able to go su from the terminal and backup an app with Titanium Backup.
I can also confirm that if permanent root is checked this will still work after reboot. When I was looking at the app it looked like it plugged into the launcher process. So perhaps it is just starting just after android is loaded.
Although I have not verified, I suspect that /system is still read only because of squashfs.
Click to expand...
Click to collapse
So xdaAlan your first post and you claim it works and what proof you can give us? screenshots maybe.....
I agree with extreme caution on files coming from the "wild" (my apologies to archaism1).
Permissions on the APK seems to be reasonably OK.
Like wdl1908 I was also puzzled about the files dates and the presence of ls binary.
Well, I'll run this Archangel beast on a resetted tablet and report here the results with proofs
The ls binary is definitely fishy I reexamined the rar file and the file dates for the readme.txt and the apk are 18/8/2009 whats up with that.......
jsperri said:
I agree with extreme caution on files coming from the "wild" (my apologies to archaism1).
Permissions on the APK seems to be reasonably OK.
Like wdl1908 I was also puzzled about the files dates and the presence of ls binary.
Well, I'll run this Archangel beast on a resetted tablet and report here the results with proofs
Click to expand...
Click to collapse
Thxs jsperri I don't have a spare unit and don't really want to reset my unit.
Does not seem to be doing much on my A32 test machine.
Just tested on my 70H, no root either ;(
What the application does is:
- install superuser apk
- does something while it says "please wait"
(ps on adb shell shows a
Code:
/tmp/ls 0x62c7a315 0x260de680
so ls may well be part of the exploit)
There is a checkbox "Permanent root" that probably just starts Archangel program on boot
(this is just my guess, based on the APK permission, and the fact there is little chance that the squashfs gets written)
Well, I'm pausing my investigation here, waiting for others feedback, hopefully positive.
There is a screenshot of the application here along with a comment from a user saying it worked on an Archos 70 IT.
hi,
i haven't been very careful about trojan risks, but i installed it on my 70it and it works!
how can i know if a trojan is instaled?
toutiwai said:
hi,
i haven't been very careful about trojan risks, but i installed it on my 70it and it works!
how can i know if a trojan is instaled?
Click to expand...
Click to collapse
Was WIFI enabled ?
How long does it take after the button says "Please wait" ?
What's next step on screen ?
Regarding the trojan risk, it's hard to say, you'd eventually want to run tcpdump to log for internet traffic on the tablet when the program is running. Also check if there are programs left (appart from Superuser) after uninstalling Archangel.
note: after install, i didn't asked to be "permanent root", but it launches "archangel" at startup anyway (but no root if i don't ask for)
wifi enabled: yes, enabled AND connected, if not it can't get "root"
how long? if wifi connected, say... 15-25 sec...
next step: nothing, the button "install root" changes in "i'm root" or something like this...
note: i had "superuser" already installed (but not rooted) before installing archangel, so it didn't asked me to install superuser
i'll try to be more precise next time if important...
archaism1,
Can you please give us some details on Archangel program, how the exploit works, why is Wifi necessary ? It would be great to trust this new tool, but it's difficult without having more details on a program coming from a dump archive and not a very well know author...
archaism1 said:
....
Archangel one-click-root from the Archaism Team
This will give you temporary or permanent root on your Archos 101 - firmware 2.0.71
Archos are kind enough to provide a SDE firmware which can allow root access,
but involves some significant changes to the system and they say that they will
invalidate your warranty if you install it. This is a bit frightening for new owners.
Archangel solves this with a painless one-click-root which you can uninstall at any time. It does not use the SDE developer firmware.
...
Click to expand...
Click to collapse
Will this work on my archos 43 Internet tablet ? Anyone brave to test and report.
http://www.appbrain.com/app/root-checker/com.joeykrim.rootcheck
anyone tried root-checker after trying this "1-click-root"? to check that it does what it claims?
I'd love to believe this, but i'm naturally sceptical.
i just tried (archos 70IT), and "rootchek" says it's ok
well at least that is promising , thanks
So I successfully followed this guide for rooting my V20:
http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
I now have SuperSU and TWRP on my phone. However, nothing actually works whenever I do anything root related. I can't uninstall any system apps with "System app remover", deleting anything in /system/app with "Root Browser" doesn't work, and even changing some buildprop settings with "BuildProp Editor" gives me an error that I don't have root. The SuperSU pop-up to grant access showed up for each of them, and I granted access for each of them, yet they still work as if I have no root. Although, checking my root with "Root Checker" or "Root Check" both say that I have root.
If it helps any, my software version is exactly "H91810d".
I'm not really a root wiz, so I'm not sure what to do now. Any help from here is greatly appreciated!
Fixed it
I have finally fixed it! Apparently I need to install BusyBox first to actually be able to do anything. I thought I already have it installed from the App Store; however, I apparently also need to install it by going to the BusyBox app, going to Installer, then installing it there to /su/xbin. For anyone with a similar problem, hopefully this will solve it. Cheers, and Merry Christmas!
Thanks to @kryz who managed to generalize the Dirty Cow exploit, XT1528 now has a way to get temporary root : link Notice that the /system will still be read-only, but at least full access to /data is available. Given the state of XT1528, this looks like a pretty good progress!
Steps to get temp root (in Lollipop):
0) uninstall SuperSu apk if you have it installed, see thisfor the reason to uninstall
1) install Croowt.apk, use the 2nd option in the menu : "Get root"
2) install SuperSu apk from the playstore (don't update the binary)
3) install RootChecker apk from the playstore
4) enjoy temporary root (until hard reboot)
I've tested this on 5.0.2, but should probably work on 5.1.1 as well (as long as it was not patched since the end of Oct). Here is the output of Root Checker (where everything looks nice and green !) :
Device: XT1528 (MOTO E Verizon prepaid)
Android Version: 5.0.2
Additional - SELinux
Status: NOT enforcing
Status stored in /sys/fs/selinux/enforce
SuperSu works (untill hard reboot) !!!
@9acca9, @dreyeth, @Whoareyou, @bendrexl, @docna, @caspar347, @Dishe, @hp79
This is great!
Thank you @kryz
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
jcpowell said:
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
Click to expand...
Click to collapse
This looks like the old Kingroot behavior - temp root which is highly unstable. Once after a Kingroot attempt I had to factory reset the device due to the "junk" left behind, at least here it's all nice and clean ! I wonder if forcing a soft reboot right after root may help to make it more stable ... Or perhaps something else is going on ?
No idea if anyone is looking into unlocking this phone's bootloader still but hopefully this leads to it. Happened with my Droid Turbo. The initial process was use Kingroot for temp root and sunshine to unlock.
Tried sunshine and after second test it gives an error. Won't even try
jcpowell said:
Tried sunshine and after second test it gives an error. Won't even try
Click to expand...
Click to collapse
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
bibikalka said:
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
Click to expand...
Click to collapse
There is a bug if you have SuperSU is installed before get the root, the restore init function will not work properly.
So the instructions in this post should be changed, and clarify that is required uninstall it.
Also ive fixed another bug related to clean the state of the system, the apk is updated in the main post.
Really after the restore clean the phone should be in a clean state, but if supersu is installed i don't know why is denying the access to the app.
Can you check this issue please?
@kryz I'm actually finding it more unstable with the updated app.
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Idk, as soon as I attempt to use my phone after root it freezes and reboots. If I let it sit it'll last an hour at least, lol
jcpowell said:
@kryz I'm actually finding it more unstable with the updated app.
Click to expand...
Click to collapse
Let's see what's going on
-Are you using the apk or adb script?
-If you use the apk and don't restore init what happens?
-If you restore init is laggy or reboot?
-Can you try the adb script and tell me if you also get a reboot?
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Regards,
---------- Post added at 01:33 AM ---------- Previous post was at 01:16 AM ----------
fenlon said:
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Click to expand...
Click to collapse
First about the sdcard, i will look after that bug that i know what's happening,please don't remove/mount/umount for now.
Do you have a computer to do some checks?
You say that with the new version there is not reboot but laggy, can you check if there is some process eating the cpu with top:
Code:
/data/local/tmp/busybox top
I suspect there is the last process restauring init that is eating the cpu, check for this or ;
Code:
ps | grep dirtycow
If that is the case kill it and we will know if is the responsible of that lag.
In other hand can you attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Guessing that you are using the apk, what happen if you don't restore init?
Is laggy or just unstable, don't start wifi/bluetooth you can't change settings are like locked.
Have you tried the script adb version, can you try and tell me if you have the same issue?
Best regards,
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
jcpowell said:
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
Click to expand...
Click to collapse
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
kryz said:
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
Click to expand...
Click to collapse
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
jcpowell said:
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
Click to expand...
Click to collapse
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
kryz said:
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
Click to expand...
Click to collapse
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
jcpowell said:
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
Click to expand...
Click to collapse
If it reboots just checking permissions the problem is the fsck_msdos process not the shellcode in init, i saw in the files that you attach all is ok.
I've updated the apk in the main post, now it will release the sdcard, please check that version in the same way, first before get root, click "check perm" wait to see the results and work with the phone to see if reboots again for a while.
If all is working with "check perm" and you don't get reboot, try get root, is very probably that now doesn't reboot.
I think with the adb script will work because it overwrites run-as, anyways ive updated the apk for release the sdcard check process and it'll return ok status.
The instructions for the rar and adb.
First you need adb installation in your computer, i mean connectivity with the device via adb.exe.
When you have adb working you need to put all the content of the rar in the path /data/local/tmp/.
So extract the rar in your computer in a folder and with adb push copy all the files to that folder:
(in the folder of the rar contents)
Code:
adb push * /data/local/tmp/
Then get a shell with adb:
Code:
adb shell
Execute the script to exploit it:
Code:
cd /data/local/tmp
./exploit.sh
Wait the logs and if all is ok execute:
Code:
run-as -s2
Wait 5 seconds and:
Code:
su
If all is ok you will have a root shell, this method is more stable even doesn't clean the init you can do it in the app, but test all before.
That last apk causes me immediate reboot. Maybe it was not the fsck_msdos cause I was able to do a check and not get a reboot with the debug apk you gave me. I am trying the adb method but I think I am messing up some steps. Will let you know when I get through it.
@kryz I should have some time tomorrow to test the shell commands. Thank you again for taking your time to do this.
This is an Android TV box, equipped with a deeply modified android 4.4 system, while the device is shielded from usb interface adb debugging, the only way to adb is to use root privileges to actively start adb wifi from the device.
I tried kingo root yesterday, and it's the only root tool I've found so far that still works with one click.
Seemed to have good luck as it worked once, but after I rebooted it today, kingo superuser tells me the device is not rooted yet.
I noticed that the location /system/bin/su still has a valid binary file (about 70KB in size).
I even installed a terminal emulator to actively execute the su command, but the result should also be as you guessed, no errors reported and no log output, and again, my permissions did not change from $ to #.
I've tried Google, but haven't found anything useful.
Is there anything I can try to solve this problem? I've tried sending a tweet to kingo root and sending feedback to the official website, but the last tweet on its Twitter feed was sent in 2018 and I think it's unlikely that anyone from the official team will be able to see my feedback.
So I'm trying to ask for help on the XDA forums, this is my first post here and I hope I'm not sending it to the wrong partition.
Thank you all.
===
Finally, I'd like to add a bit of information.
Since kingo root thinks the device is rooted, there is no way for me to get it to perform the root steps all over again.
Also, although kingo superuser provides the ability to remove root, there is no way for me to use it to remove this su file and kingo superuser since it suggests the device is not rooted, which seems to be stuck in a dead end loop
Even because it's a box, I don't even seem to have a way to get into fastboot
===
这是一台安卓的电视盒子，搭载的是经过深度修改的android 4.4系统，同时设备从usb接口上屏蔽了adb调试，想要进行adb的唯一办法就是使用root权限从设备上主动启动adb wifi。
我昨天尝试了kingo root，这是我目前找到唯一的一个还能够运行一键的root工具了。
看起来运气不错，因为一次就成功了，但是我今天重启了它之后，kingo superuser告诉我设备尚未root。
我注意到/system/bin/su这个位置依然存在着有效的二进制文件（大约70KB大小）。
甚至我还安装了一个终端模拟器，主动去执行su命令，但是结果也应该正如你所猜测的那样，没有报错，也没有输出log，同样的，我的权限也没有从$变成#。
我尝试过谷歌，但是没有查到过什么有用的东西。
请问我有什么可以尝试的办法去解决这个问题吗？我已经尝试向kingo root发送推特和向官网上发送反馈，但是它的推特上最后一条推文是在2018年发送的，我认为官方团队不大可能能够有人看到我的反馈。
所以我尝试在XDA论坛上寻求大家的帮助，这是我第一次在这里发帖，希望我没有将帖子发送到错误的分区。
谢谢大家
===
最后，我想补充一点信息。
因为kingo root认为设备已经root了，所以我也没有办法让它重新执行一遍root的步骤。
另外，虽然kingo superuser提供了移除root的功能，但是由于它提示设备无root权限，我也没有办法用它把这个su文件和kingo superuser移除掉，这看起来似乎陷入了一个死循环
甚至因为它是一个盒子，我似乎连进入fastboot的办法都没有