Related
I installed SuperSu v2.67 on a Nexus 5 running stock Marshmallow 6.0.1, and SuperSu works great for me so far!
The only (minor) issue I've encountered thus far is that the SuperSu icon seems to be missing from the Google Now launcher home screen and app drawer.
I can still launch SuperSu by searching for it in the Google Play store and clicking "Open", and it still pops up when an unauthorized app is requesting root access.
I've tried to do a complete unroot + reinstall, change the SuperSu icon from the app's settings etc. - without success.
Has anyone else encountered this? Is there any way to get SuperSu icon to show up?
Thanks in advance.
Try this with your computer:
adb uninstall eu.chainfire.supersu
Reboot back into Android, then reboot into recovery and reflash, or extract the APK from the zip and "adb install" it.
Edit:
Correction! Found the icon. It was buried in the app drawer all along. What threw me off was that for some reason, when I write "SuperSu" or any prefix of the name in the search box at the top, it doesn't find SuperSu, like it does pretty much any other app. Weird.
Anyway, thanks for the help and sorry about the false alarm.
Chainfire said:
Try this with your computer:
adb uninstall eu.chainfire.supersu
Reboot back into Android, then reboot into recovery and reflash, or extract the APK from the zip and "adb install" it.
Click to expand...
Click to collapse
I'm having a similar problem as the OP except that 2.6.7 binaries don't install on a T-Mobile Note 4 (SM-910T3) in either Lollipop or Marshmallow using either the Normal or TWRP methods. 2.6.5 and 2.6.6 binaries install properly, however.
I tried the command in recovery and got the following error:
In other words, you have a completely different problem that isn't even vaguely related. Not enough info, wrong thread.
Also, adb uninstall doesn't work from recovery, only full Android.
Chainfire said:
In other words, you have a completely different problem that isn't even vaguely related. Not enough info, wrong thread.
Also, adb uninstall doesn't work from recovery, only full Android.
Click to expand...
Click to collapse
You're right I didn't explain things right. My ROM comes preinstalled with SuperSU 2.6.6 and I have the same issue as the OP as the app doesn't appear in either app drawer and I can't launch it from the Play Store either. I'll try adb uninstall properly.
The 2.6.7 failed install is a separate issue. Do I start another thread here in the same forum? What info do you need?
Mate if adb shell not working then use this as i got same issues before anyway go to setting/application manger then roll down to find this
eu.chainfire.supersu
Then uninstall it & reboot then re install supersu app extracted from supersu zip it should work for u ok
thereassaad said:
Mate if adb shell not working then use this as i got same issues before anyway go to setting/application manger then roll down to find this
eu.chainfire.supersu
Then uninstall it & reboot then re install supersu app extracted from supersu zip it should work for u ok
Click to expand...
Click to collapse
Thanks. I got it to uninstall and was able to reinstall, but it still wouldn't show up in app drawer or open from the Play Store.
Worked Well on All Lollipop Versions of ALE-L21
After many unsuccessful attempts, finally i found a solution, and it works like a charm...
First of All Download KINGROOT.apk
install it and run Kingroot... It will take some time to root your ALE-L21.
if unsuccessful, try again, it will surely work after retries... in my case it rooted my phone in third attempt.
After rooted successfully with Kingroot. then another step is to replace kingroot with SUPER SU, because Super SU works with all rooted apps, KINGROOT lack this feature.
I have made a small script to remove Chinese kinguser, all related files and folders, and install SuperSU.
This script will do all the work for you without using PC, just by terminal, first of all, thanks to chainfire for his SuperSU files.
Before starting :
Download and install Terminal emulator app.
Download and unzip "Replace_Kingroot_With_SuperSU.zip" file.
Steps :
Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files
Open Terminal emulator and type :
Code:
su
Allow root permission
Type :
Code:
sh /sdcard/mrw/root.sh
It might display some error, at the end it will launch supersu or open supersu manually.
Update su binary normal, then reboot.
Done !
Now you can enjoy the power of root and Super Su...
Terminal Emulator for android
https://play.google.com/store/apps/...ore/apps/details?id=jackpal.androidterm&hl=en
Replace_Kingroot_With_SuperSU.zip
http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip
KingRoot.apk
http://androidmtk.com/download-kingroot-application
Thanks,
It works with me.
ALE-L21C185B130
--------
Hopefully soon we get simple way to unlock boot loader.
Huawei cloud application accounts for the unlock code is not on this phone log more than 14 days!
Happy to Hear this from you.
But can't works on the beta build marshmallow's.
dkonect said:
But can't works on the beta build marshmallow's.
Click to expand...
Click to collapse
Not Tested on Marshmallow.. that's why mentioned that it works on Lollipop..
Some errors on script start
Kingroot icon is still there and can't remove
com.kingroot.kinguser still active, if freezed supersu doesn't work anymore
ItalianWolf said:
Some errors on script start
Kingroot icon is still there and can't remove
com.kingroot.kinguser still active, if freezed supersu doesn't work anymore
Click to expand...
Click to collapse
You got error because you did not send mrw folder in main directory of sd card, you should send that folder to internal and external memory also to avoid any errors... update me when done...
saifkhan9187 said:
You got error because you did not send mrw folder in main directory of sd card, you should send that folder to internal and external memory also to avoid any errors... update me when done...
Click to expand...
Click to collapse
I'm following your instruction exactly, why not?
how can i blame you if i don't follow exactly what you wrote?
mrw was in root of sdcard, supersu and su binaries are working (if i don't freeze com.kinroot.kinguser) but what i wrote it's valid.
I launched again the script and after a lot of errors this time supersu asked me to reboot, first time didn't; now seems all kingroot trace are gone!
EDIT:
After testing i see that a lot of times supersu needs to be started manually to have the auth promp for an app, my english isn't so good, i'll write an example:
start (first time) an app that requires root
wait for auth prompt by supersu
wait a lot, so open supersu, then it shows the request for authorize
a second app started just after show immediatly the auth promp
When com.kingroot.kinguser was active the promp from supersu was everytime immediate.
Latest: kngroot unlocks bootloader
Is some chance this work in future on marshmallow ? thanks
Dear saifkhan9187,
How to update superSU?
I got failure message when SuperSU try updating.
Making this I still can get the OTA updates?
Is that ota still available?
Recently, about a month, I got the b188 update... Android 5.0.1
aab44 said:
Dear saifkhan9187,
How to update superSU?
I got failure message when SuperSU try updating.
Click to expand...
Click to collapse
Got the same error first time, reboot, launch again the script (you will see lot of errors this time file are already deleted no matter) then start supersu if not starts; this time doesn't fail.
@ItalianWolf how did you check for unlocked boot loader? Fastboot? Thanks!
@rHycH yes, reboot in fastboot mode and you can see in red that bootloader is unlocked
ItalianWolf said:
Got the same error first time, reboot, launch again the script (you will see lot of errors this time file are already deleted no matter) then start supersu if not starts; this time doesn't fail.
Click to expand...
Click to collapse
Thanks, its updated now.
--------
Waiting for simple way to unlock boot loader of ALE-L21
@aab44 bootloader is unlocked now, you can see in fastboot!
Please, is there any way to undo this and use kingroot again ??
or at least have an option to use an different busybox ??
since this have made Link2sd and foldermount unuseable for me
Many Thanks in advance
nibb-1 said:
Please, is there any way to undo this and use kingroot again ??
or at least have an option to use an different busybox ??
since this have made Link2sd and foldermount unuseable for me
Many Thanks in advance
Click to expand...
Click to collapse
Junst do full unroot from supersu and use again kingroot (install and root)
Hi, im new here and this is my first post, so i appreciate all the help and feedback you can give me.
im interested in using xposed in android TV Box's and Dongles, i've been reading and learning all about it for more than a month now. i've got it to work on most TV Box's and dongles that i have "RK based devices with android V 4.4 or less",but i still have a problem with one device which is an RK3288 based with android 5.1 that is already rooted.
i used twrp to flash xposed-v86-sdk22-arm.zip which was successful, than i wiped Dalvik/cache and rebooted, but the boot stuck on bootanimation, i disabled xposed by installing the uninstaller.zip and everything went back to normal. i tried it many times but with no use. i noticed that twrp doesnt mount internal SD, i installed an older version of bootloader which gave me the ability to mount the internal Sdcard, and i tried to install xposed again and this time it pass the animation and goes to a black screen where i can use the mouse but nothing else. with some research i found that UT3+ is based on firefly board and their original ROM is available for download and it has the same bootloader version that came installed with the device, after flashing the new ROM i was able to mount the internal Sdcard and i tried to install xposed again, and this time it gives me optimizing apps but after it finish the device reboot and get stuck again on bootanimation.
my question is, if there is a log for errors to know why the system/boot get stuck , where can i find them??
and if there is no logs how can i monitor the booting process to find the info i need??
also i know or read what bootloader is but i dont understand how it is effecting xposed installation.
Sorry for the long post, and thank you for your help in advanced
EDIT: i finally got adb connection with the device and used logcat to get the logs, but im not sure how to attach the files. if anyone can help i will gladly send the logs. thanks
Update 1
i was looking at the logs "didnt know what to search for im not a developer" and i noticed that everything is crashing and "Not granting permission" ,"Unknown permission " are everywhere .
sample of logs:
Code:
"com.google.android.partnersetup.permission.WRITE_APP_PROVIDER in
package com.android.vendingW/PackageManager( 4712): Not granting
permission android.permission.BIND_WALLPAPER to package
com.android.camera2 (protectionLevel=18
flags=0x58bc45)W/PackageManager( 4712): Not granting permission
android.permission.BIND_APPWIDGET to package com.android.launcher3
(protectionLevel=18 flags=0x583e45)W/PackageManager( 4712): Unknown
permission android.permission.READ_SETTINGS in package
com.android.launcher3W/PackageManager( 4712): Unknown permission
com.android.launcher.permission.READ_SETTINGS in package
com.android.launcher3W/PackageManager( 4712): Unknown permission "
so i decided to root again with KingRoot, and i tried installing xposed again, and it kinda worked. the system boot and the launcher opens but crashing messages keeps showing "Stresstest for 5.0 has stopped running" , "The process com.android.phone has stopped running", and others.
now im not sure about what im doing but i'll test two methods:
1- i will unpake ROM.img put xposed in the root and update the updater script to install xposed when i flash the ROM.
2- the device can run Linux version from SD card so i might run it and manually install xposed files.
if anyone have any tips or info please let me know. thanks
SOLUTION
For those who are having problems with their RK based android TV Box with android 5.1, if you get stuck on Boot animation or the system boots with black screen and you can use your mouse only, or if you getting errors when you boot the main problem would be your firmware is modified and up to Xposed V.86 is not supported because of the error "No implementation found for void dalvik.system.VMRuntime.clam" you can read more about it in this post https://github.com/rovo89/Xposed/issues/167.
and luckily dsa8310 made a modefied version of xposed, i tested it and it works you can find the download link here http://forum.xda-developers.com/showpost.php?p=67787484&postcount=325
viVaPale said:
luckily dsa8310 made a modefied version of xposed, i tested it and it works you can find the download link here http://forum.xda-developers.com/showpost.php?p=67787484&postcount=325
Click to expand...
Click to collapse
I can't get to the page with the link. (I get a noob alert) We want to try this xposed on a ugoos ut3s (android 5.1 with a rk3288)
Would someone please be so kind to post it here or tell me where I can download it.
Anyone that can compile Xposed v87 to fix this problem for RK3288 Lollipop devices?
https://github.com/rovo89/Xposed/issues/167
https://android.googlesource.com/platform/art/+/379d09fe3c3feb7c2a2fb5a3623689b5ace7e79b
Are there instructions somewhere so we can compile it ourselves?
The code above looks like it needs to be applied to Android source code, what must be changed in Xposed Github code to fix it and compile our own new Xposed only for our devices?
Thanks
humptydumpty said:
I can't get to the page with the link. (I get a noob alert) We want to try this xposed on a ugoos ut3s (android 5.1 with a rk3288)
Would someone please be so kind to post it here or tell me where I can download it.
Click to expand...
Click to collapse
Please try this link https://mega.nz/#!300ggYoJ!1vdLP0OyU2D1ky6pWv-Y3VJFH5paHSAqV3Y8A64bvkk
i recommend you download the xposed uninstaller in case something wrong happend
viVaPale said:
Please try this link https://mega.nz/#!300ggYoJ!1vdLP0OyU2D1ky6pWv-Y3VJFH5paHSAqV3Y8A64bvkk
i recommend you download the xposed uninstaller in case something wrong happend
Click to expand...
Click to collapse
Wow ! Work nice on my haier pad971 (ifive air clone) rk3288 5.1.1 !!
Thanks so much
does anyone know if there's an RK3288 enabled xposed v89 built to avoid the issues described by viVaPale? Tried the one from 3.1.5 installer, but after boot it doesn't load the launcher, only mouse can be moved around like viVaPale describes.
I have my Samsung A30 (SM-A305F) rooted with magisk canery (87de0e7a) by flashing patched boot img via odin. Now, If i try to hide magisk with random package , it demands internet connection and install the latest version (9348c5ba). BUT i don't want to upgrade as the updated version has weird bug of rejecting SU automatically (with a very brief pop-up). I then need to ---> uninstall the repackaged app ---> Reboot ---> install 87de0e7a version ---> then it become functional again. I don't have TWRP installed. Re-flashing new patched boot requires wiping data. i don't want to do factory reset
Now I want to hide magisk as PUBG MOBILE might be crashing due to root detection. Please help me achieve solution:
(1) hide magisk manager without updating
(2) update magisk manager without that BUG of rejecting SU automatically
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions and owner).
Edit: replace the package name above with the one your Manager uses.
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Note: i previously managed to hide it successfully when there was no newer version. It would just download the same version from the internet and repackage itself with random package name. But some days ago, i restored original manager and now i can't get it to hide.
Didgeridoohan said:
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions).
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Click to expand...
Click to collapse
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Shihabus Sakib Rad said:
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Click to expand...
Click to collapse
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Didgeridoohan said:
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Click to expand...
Click to collapse
yes with MiXplorer.
When Manager updated itself , i tried to update the magisk ( not the manager). But it bricked my phone as it won't start. i had to flash stock firmware via odin. It happened what i feared about. Now, i will try to patch boot img with new version.
UPDATE: I patched and flashed boot img using canary 290. after rebooting , this time there was not that Bug of rejecting SU automatically. Root was functional. But when it asked to do additional setups, it was stuck on setup operation forever and when i tried to hide manager, it showed "hiding magisk manager failed". so i uninstalled canary 290 and installed 7.5.1 (267) . This time additional setup was completed and rebooted automatically. But there was some problem with su access. so i uninstalled 7.5.1 (267) and installed canary 290. Root is now functional and it does not ask for additional setup anymore. (meaning setup was complete?). But still shows "hiding magisk manager failed" when try to hide manager. I don't know what is the problem . I was using canary 284 without any problem. PUBG mobile was runnig without problem. Now I am tired......
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Didgeridoohan said:
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Click to expand...
Click to collapse
Disabling Play Protect Worked !!!! Thank you Sir :angel:
Hi
I have magisk installed but my phone is reporting not rooted.
My setup:
Xiaomi Redmi Note 7
Ressurection remix
Magisk 23.0
Things I've tried:
Disabled battery optimisation for magisk app
Reinstalled magisk a couple of times from twrp
Other root requiring apps (no change)
I've attached the logs from Root Checker, magisk and snip of my magisk. Please let me know if there is more info I can provide.
Thanks in advance for any suggestions!
re-flashing latest stable magisk.zip with the custom recovery then reboot to system and open the magisk wait to downloading requested resources and see..
Hi
Thanks for your reply.
I just downloaded this and flashed it with twrp: https://magisk.me/
Rebooted and found the same issue. Any other ideas?
Cheers
Oliver
arahknxs said:
Hi
Thanks for your reply.
I just downloaded this and flashed it with twrp: https://magisk.me/
Rebooted and found the same issue. Any other ideas?
Cheers
Oliver
Click to expand...
Click to collapse
1 - Don't use that website. The only place for verified and safe Magisk downloads is on John's Github:
https://github.com/topjohnwu/Magisk
2 - Exactly what is it that's reporting that your device isn't rooted? Because Magisk quite clearly says it is, according to your screenshot...
Didgeridoohan said:
1 - Don't use that website. The only place for verified and safe Magisk downloads is on John's Github:
https://github.com/topjohnwu/Magisk
2 - Exactly what is it that's reporting that your device isn't rooted? Because Magisk quite clearly says it is, according to your screenshot...
Click to expand...
Click to collapse
Hi
Thanks for the reply.
Okay so I went to Git and downloaded this file https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk I then renamed it to .zip and flashed it via TWRP. Is this correct?
When I reboot I find the same situation. Magisk appears installed correctly however no app can access root. No popup appears to accept/reject the su request and apps behave as if no root access. I've tried Root Checker, Titanium Backup and am happy to try any others.
Do you have any suggestions please on what else I can try?
Cheers
ara
Ah... So the problem is not that you do not have root access The problem is that there's no superuser prompt when an app requests root.
IIRC there's a Xiaomi settings to allow apps to display popup messages (should be under app permissions). The Magisk app also need to be allowed to auto start. Of course, this is for MIUI and you're using RR so I have no idea if there is such a setting on your device currently...
Could of course be something completely different though.
Didgeridoohan said:
Ah... So the problem is not that you do not have root access The problem is that there's no superuser prompt when an app requests root.
IIRC there's a Xiaomi settings to allow apps to display popup messages (should be under app permissions). The Magisk app also need to be allowed to auto start. Of course, this is for MIUI and you're using RR so I have no idea if there is such a setting on your device currently...
Could of course be something completely different though.
Click to expand...
Click to collapse
Yes I suspect this is the issue - the notification is being blocked somehow.
Under app settings -> Magisk, I believe the settings are right:
Battery optimisation = off
Notifications = all allowed
There are plenty of guides out there of using RR with Magisk and no mention of any special settings to make it work.
I am also using nova launcher, I wonder if this could affect the notification somehow?
All suggestions welcome!
Cheers
ara
I noticed in Magisk under the Superuser tab, it just says "no app has asked for superuser permission yet." So perhaps not a notification issue after all?
I downloaded another app, "root checker basic". It also generated no popup, said I do not have root, and nothing appeared in the Magisk logs.
I feel like I am doing something wrong here but missing what it is.
Cheers
ara
arahknxs said:
I noticed in Magisk under the Superuser tab, it just says "no app has asked for superuser permission yet." So perhaps not a notification issue after all?
I downloaded another app, "root checker basic". It also generated no popup, said I do not have root, and nothing appeared in the Magisk logs.
I feel like I am doing something wrong here but missing what it is.
Cheers
ara
Click to expand...
Click to collapse
One thought: make sure that nothing is restricting the Magisk app from autostarting and running in the background.
Also, have you checked with other users of your ROM? Might be a good place to get help for stuff like this...
This happened to me before. I had to rename the same zip to "uninstall.zip" and flash it, reboot, and then rename the zip to something else like Magisk.zip and flash again.
dsiva said:
This happened to me before. I had to rename the same zip to "uninstall.zip" and flash it, reboot, and then rename the zip to something else like Magisk.zip and flash again.
Click to expand...
Click to collapse
Thanks for the suggestion, I tried this but no change afterwards unfortunately.
Also good idea @Didgeridoohan, I will cross post this on the forum for RR.
extract the boot.img and copy to phone. in Magisk, install and pick boot.img. copy the result file to pc, and flash using fastboot flash boot magi....img
if unlocked bootloader, flash direct and reboot.
arahknxs said:
Hi
I have magisk installed but my phone is reporting not rooted.
My setup:
Xiaomi Redmi Note 7
Ressurection remix
Magisk 23.0
Things I've tried:
Disabled battery optimisation for magisk app
Reinstalled magisk a couple of times from twrp
Other root requiring apps (no change)
I've attached the logs from Root Checker, magisk and snip of my magisk. Please let me know if there is more info I can provide.
Thanks in advance for any suggestions!
Click to expand...
Click to collapse
Rename the file to uninstall.zip then flash the firmware then flash the magisk it will work for sure i was also facing the same problem