Hello, I have Android 6 Pure IMUI ROM 2.2 and my SuperSU binaries aren't updating.
Whwn I open SuperSU, it displays the update window, I select TWRP and it reboots to recovery.
After a while of installing on recovery, it skips MD5 verification and boots normally, and when I open SuperSU it ask's again that I need to update the binary.
If this helps, Im having this issue on the first update prompt that SuperSU gave me, after installing Magisk app.
Does anyone have any idea?
Thank you!
joaomPT said:
Hello, I have Android 6 Pure IMUI ROM 2.2 and my SuperSU binaries aren't updating.
Whwn I open SuperSU, it displays the update window, I select TWRP and it reboots to recovery.
After a while of installing on recovery, it skips MD5 verification and boots normally, and when I open SuperSU it ask's again that I need to update the binary.
If this helps, Im having this issue on the first update prompt that SuperSU gave me, after installing Magisk app.
Does anyone have any idea?
Thank you!
Click to expand...
Click to collapse
clear super su app data and check it.
also try by uninstalling magisk module.
miststudent2011 said:
clear super su app data and check it.
also try by uninstalling magisk module.
Click to expand...
Click to collapse
Hey, thanks for your help.
I tried uninstalling magisk a week ago, which resulted on me losing root, I simoly restored a backup and its all fine now (totally forgot to reply about this here)
Thanks once again and have a nice day
joaomPT said:
Hey, thanks for your help.
I tried uninstalling magisk a week ago, which resulted on me losing root, I simoly restored a backup and its all fine now (totally forgot to reply about this here)
Thanks once again and have a nice day
Click to expand...
Click to collapse
Glad to hear that you solved your problem
Related
So, a couple days ago SuperSU gave me the update message. did it through PhilZ's recovery. then, SuperSU said there was no binary file.
Next I downloaded both superuser and superuser zips from root thread and have tried flashing both.
Now, I have SuperSU and it is working(with update messages).
Question, How do I go about updating the binary without losing it?
Appreciate any help...
masterjakeway said:
So, a couple days ago SuperSU gave me the update message. did it through PhilZ's recovery. then, SuperSU said there was no binary file.
Next I downloaded both superuser and superuser zips from root thread and have tried flashing both.
Now, I have SuperSU and it is working(with update messages).
Question, How do I go about updating the binary without losing it?
Appreciate any help...
Click to expand...
Click to collapse
turn off auto update and wait
Well, when i start superSU it comes right up to the upgrade or cancel. if i cancel, it closes.
Also, Titanium backup says something about it being an outdated binary and it "may" not work correct?
I have no clue where to find the correct binary to flash through recovery...
masterjakeway said:
Well, when i start superSU it comes right up to the upgrade or cancel. if i cancel, it closes.
Also, Titanium backup says something about it being an outdated binary and it "may" not work correct?
I have no clue where to find the correct binary to flash through recovery...
Click to expand...
Click to collapse
it's fixed now ... just choose update and then choose twrp/cwm option
I updated yesterday no problem
Hey guys,
I have an i9300, rooted with slimbeam installed. A few days ago I dropped my phone and the screen cracked and the display disappeared; so I got it replaced. When I turned my phone on again, it was stuck on the boot screen. So I fully wiped my phone and flashed slimbean again (as I already had the file on my external SD card). This got me passed the boot screen and my phone is working fine except it seems like I don't have proper root access. I downloaded a root checker and thats the message I got "Does not have proper root access" and when I run superSU it said "the su binary needs to be updated" so I click on update and I get a message saying " install failed. Reboot and try again" I reboot and tried again and same error
Anyone know what my best course of action would be?
EDIT: It also randomly keep rebooting.
Thanks a lot guys!
Cheers
bd101 said:
Hey guys,
I have an i9300, rooted with slimbeam installed. A few days ago I dropped my phone and the screen cracked and the display disappeared; so I got it replaced. When I turned my phone on again, it was stuck on the boot screen. So I fully wiped my phone and flashed slimbean again (as I already had the file on my external SD card). This got me passed the boot screen and my phone is working fine except it seems like I don't have proper root access. I downloaded a root checker and thats the message I got "Does not have proper root access" and when I run superSU it said "the su binary needs to be updated" so I click on update and I get a message saying " install failed. Reboot and try again" I reboot and tried again and same error
Anyone know what my best course of action would be?
EDIT: It also randomly keep rebooting.
Thanks a lot guys!
Cheers
Click to expand...
Click to collapse
If you have Phil's touch recovery then go in the settings and reroot your device and install supersu app from play store and update your binaries...
Sent from my GT-I9300
kunal1540 said:
If you have Phil's touch recovery then go in the settings and reroot your device and install supersu app from play store and update your binaries...
Sent from my GT-I9300
Click to expand...
Click to collapse
Would that be in recovery mode? Cause I couldn't find anything regarding root there. or should I follow this http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953
Thanks! I realy appreciate your help
bd101 said:
Would that be in recovery mode? Cause I couldn't find anything regarding root there. or should I follow this http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953
Thanks! I realy appreciate your help
Click to expand...
Click to collapse
yes in philz recoverey in philz settings i think...re root option and install supersu from play store..or
alternative is to flash supersu zip file from the respective thread..
Flash the latest supersu's .zip from a custom recovery.... Here's the thread
http://forum.xda-developers.com/showthread.php?t=1538053
kunal1540 said:
yes in philz recoverey in philz settings i think...re root option and install supersu from play store..or
alternative is to flash supersu zip file from the respective thread..
Click to expand...
Click to collapse
i did flash superuser from the respective thread. When I run the root checker app I still get the "Sorry! This device does not have proper root access". When I run SuperSU it says "There is no SU binary installed and SuperS cannot install it. This is a problem! "
What do I do now? I was hoping flashing SuperSU would solve the problem.. but i guess that didnt work
I have an HTC One M8 with ROM 4.16.1540.8 (5.0.1)
I'm trying to remove my SuperSU app so that i can downgrade it to a lower version(2.20) due to incompatibility with some of my apps (puzzle and dragons).
Bootloader is unlocked and it is s-on.
I have tried removing SuperSU through the app itself by using the reinstall, switch superuser app, and full unroot functions, but everytime I restarted the phone superSU would be back and in version 2.46. I also tried manually deleting the apk and su files in the bin and xbin folders in system using es file explorer but a restart just brought those back too.
Any help would be greatly appreciated. Thanks!
Find the flashable zip for the "older" version and flash in recovery. I would think that should do it.
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
ah46657 said:
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
Click to expand...
Click to collapse
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
how to unflash supersu zip
redpoint73 said:
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
Click to expand...
Click to collapse
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
rajkumar1221 said:
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
Click to expand...
Click to collapse
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
redpoint73 said:
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
Click to expand...
Click to collapse
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
rajkumar1221 said:
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
Click to expand...
Click to collapse
I don't personally use Lineage. I believe you will need to flash both of those, yes.
@redpoint73 , found this script made by osm0sis to "unSU". not sure if is relevant to earlier posts but thought maybe if you havent seen it yet would be worth looking at. maybe could help someone.?
http://forum.xda-developers.com/showthread.php?p=63615067
Hi guys,
I need to run Pokemon Go on two Samsung S3 i9300. Anyone who actually is running it on his/her S3 can suggest me the easiest way to do that on a custom rom? I saw about Magisk but while I am running it without any problems on RRemix on my Redmi Note 3 Pro, I cannot run it on my nephews' s3 phones
Anyone can help?
I did it using SuperSU and SUHide on RRemix on I9300.
https://www.reddit.com/r/pokemongod...mple_and_easy_magisk_on_cm13_tutorial/d88ip96
I used this tutorial just without Xposed cause I don't need it
KaSkA3eR said:
I did it using SuperSU and SUHide on RRemix on I9300.
https://www.reddit.com/r/pokemongod...mple_and_easy_magisk_on_cm13_tutorial/d88ip96
I used this tutorial just without Xposed cause I don't need it
Click to expand...
Click to collapse
Thanks, I'll give it a try! BTW, did you install SuperSU the 'normal' way or via recovery, when it asks you at first launch?
fparri said:
Thanks, I'll give it a try! BTW, did you install SuperSU the 'normal' way or via recovery, when it asks you at first launch?
Click to expand...
Click to collapse
First after installing rr with gapps i installed supersu from play store and did full unroot. Then i made a file in sdcard1 named .supersu with "systemless=true" if i remember good. After that i rebooted to recovery and moved file .supersu to /data/ using aroma file manager and flashed supersu. Now it doesnt work so im trying new method because safetynet has got fail payload when you try to run it on i9300.
SuperSU + suhide + removing /system/bin/su and /system/xbin/su will make pokemon go work on RR and any rom with built in SU. You can avoid the last additions if you're running AOSP.
Hey everyone. So, today, I was messing around with my F1 today, and I tried to install MultiROM and was, for the most part, successful. But, when I restarted my phone and tried to boot the secondary ROM, it failed and then I couldn't even get into my intenal ROM.
So, I headed back into TWRP, uninstalled MultiROM and flashed back the non-MultiROM TWRP recovery. All was fine, I installed my primary ROM again and it booted fine, although I'd forgotten to flash GApps and Magisk. I set-up the ROM and then rebooted to TWRP and flashed GApps and Magisk. GApps were working fine, all well set-up, but Magisk wasn't appearing anywhere. CPU-Z also detected the phone as being rooted, but when launching Kernel Adiutor and SD Maid, I wasn't able to get a prompt for root access (Kernel Adiutor even told me I had no root access on the phone).
I also tried to install the Magisk Manager APK to no avail.
Does MultiROM mess with the partition scheme?
So, can anybody tell me what's going on here, what I messed up, so that I can correct it and go back to using Magisk?
BTW: The storage is encrypted, I never got around to use DFE, maybe I'll do so today.
Thanks in advance!
bskov said:
Hey everyone. So, today, I was messing around with my F1 today, and I tried to install MultiROM and was, for the most part, successful. But, when I restarted my phone and tried to boot the secondary ROM, it failed and then I couldn't even get into my intenal ROM.
So, I headed back into TWRP, uninstalled MultiROM and flashed back the non-MultiROM TWRP recovery. All was fine, I installed my primary ROM again and it booted fine, although I'd forgotten to flash GApps and Magisk. I set-up the ROM and then rebooted to TWRP and flashed GApps and Magisk. GApps were working fine, all well set-up, but Magisk wasn't appearing anywhere. CPU-Z also detected the phone as being rooted, but when launching Kernel Adiutor and SD Maid, I wasn't able to get a prompt for root access (Kernel Adiutor even told me I had no root access on the phone).
I also tried to install the Magisk Manager APK to no avail.
Does MultiROM mess with the partition scheme?
So, can anybody tell me what's going on here, what I messed up, so that I can correct it and go back to using Magisk?
BTW: The storage is encrypted, I never got around to use DFE, maybe I'll do so today.
Thanks in advance!
Click to expand...
Click to collapse
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
SamyakJ said:
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
Click to expand...
Click to collapse
Yeah, im going to back it all up once I get home and wipe it clean to flash DFE and flash the ROM on top.
Also, I flash Magisk Uninstaller, it told me it couldn't find a stock boot image (and then proceeded to generate one), and then once I restarted the phone I went to CPU-Z to check root access and it changed to "No", so something was taking effect.
SamyakJ said:
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
Click to expand...
Click to collapse
So, I tried decrypting, but I can't, because of something with Android Pie. Doesn't matter now, I wiped every storage partition clean and flashed the firmware twice, then flashed Magisk on top, now it's working. Thanks anyway!
That prompt not showing up and magisk manager not showing in app drawer is a common issue for me even though I've never installed MultiROM on my device. You can ignore both.
Here's what I do to resolve the issue:
1) Install Magisk Manager apk.
2) Go to settings, scroll down to "automatic response", click that, click either grant or deny, then click it again and this time set it as prompt.
That should show the superuser prompt.