Database Develop

Can't install SuperSU updated binary

Hey,
I've just rooted my phone for the first time recently. I have a Lenovo S960 so the task wasn't easy.. almost nobody has support for this kind of phone. Ended up using Kingroot. Root Checker tells me all is OK and if I use a terminal, I can switch to and browse as root, so it seems like my phone is indeed rooted.
However, I cannot get write privileges on my /system directory (the main reason why I rooted was so that I could remove all the bloatware which comes with Lenovo phones). If I try to mount it via a terminal it just says "mount: read-only file system" and if I use Root Explorer, when I press "Mount as R/W" in /system, nothing happens.
I read on the internet that I should get SuperSU and grant superuser privileges or something among the lines. So I went to google play and installed SuperSU and when I opened it it told me I needed to update SuperSU binary files and it lets me choose between installing it via recovery or normal. If I choose normal it just tells me that the installation has failed. So I installed CWM recovery (tried first with TWRP but that wouldn't recognize my SD card for some reason). If I go into the SuperSU app and choose "TWRP/CWM" as an installation method it tells me "SuperSu will attempt to reboot your device into recovery. This might not work for all devices" and, indeed, nothing happens. So I manually boot into recovery mode looking for a SuperSU binaries file anywhere, but I couldn't find one. I then downloaded SuperSUv2.6.zip from the internet and flashed it manually (which took a while to figure out since the menu is in Chinese). When I boot up my device, the SuperSU app is now gone (and of course I still can't grant write privileges on /system). I try to install SuperSU from google play again and I run into the exact same situation as before.
Any help would be appreciated.
Thanks in advance.
P.S: I got my zip from a thread here named [STABLE][2015.02.13] SuperSU v2.46; not sure if I can post links here but a search should reveal this thread if anyone is interested. I've also tried downloading it from different sources but it was the exact same file (same md5).

I'm having the same problem with my HTC One M8. Got the v2.46 update but it won't install. I cleared the cache within recovery and it just wipes the phone again. Not a big deal, but there's gotta be something within the structure of the file directories that let it install the old SuperSU that isn't the same with the v2.46 update. I'm still looking into it. E-mail if you figured it out, [email protected]

I have seeder fail ask root with super su 2,64 - Android revolution hd room. I tried to flash latest supersu but still issue HTC-oNe m8 too

jk

Hi I'm having same problem on. lg k7 (lgms330)

Distant1 said:
Hi I'm having same problem on. lg k7 (lgms330)
Click to expand...
Click to collapse
I obtained root today on the MetroPCS K7. Root with kingroot. Apk v4.50 and use older version of SuperSUme (not the current one on Play) to change to SuperSU and delete all the kingroot crap. Reboot after rooting with kingroot then use SuperSUme... No errors here... Updated binary and installed busybox.

Shaun_vip said:
I obtained root today on the MetroPCS K7. Root with kingroot. Apk v4.50 and use older version of SuperSUme (not the current one on Play) to change to SuperSU and delete all the kingroot crap. Reboot after rooting with kingroot then use SuperSUme... No errors here... Updated binary and installed busybox.
Click to expand...
Click to collapse
Ty

"Wolfdroid script" will help with that GOOGLE IT..... ITS VERY SIMPLE..u just bssically use the kingroot to grant ur terminal and SUPERSU root permissions to remove it...kinda setting itself up to fail and be replaced..Harsh in a sense but affective..an evil plot...hahaha

Shaun_vip said:
I obtained root today on the MetroPCS K7. Root with kingroot. Apk v4.50 and use older version of SuperSUme (not the current one on Play) to change to SuperSU and delete all the kingroot crap. Reboot after rooting with kingroot then use SuperSUme... No errors here... Updated binary and installed busybox.
Click to expand...
Click to collapse
By any chance do you know if there's a custom recovery for lg k7 floating around online?

At the time I obtained root, no. Not sure if one had been made or not.

actually I have the same problem.but I use stock rom (official rom from Sammobie)
android 4.4.2 and I don't have recovery cwm or twrp (it's long story).
the point is: how to root my device with this problem?
not/ I use galaxy s3 verizon

supersu not able to provide root permissons : Android 6.0.1
Hi,
I am currently working on an automation task, where i need to provide root access to other supporting apps. But as I am not able to provide the root access the app crashes with an error message as "Unfortunately xyz app has stopped". This was found working with Android L with older supersu app but not working with Android 6.0 with the latest marshmellow version of the supersu app.
Device : It is a test device hence cannot share any data about the product (Sorry for the inconvenience)
OS : Android 6.0.1
SuperSu app version : have tried with v2.37, v2.56 and v2.67
Kindly help us and ASAP @Chainfire : hope chainfire is reading this

KingRoot rooted my LG K7 and installed Superuser. The Binaries needed updating for SuperSU, so I found the stable SuperSU v2.46, which was already saved from Chainfire on Twitter earlier on my PC(Link not found but here is Chainfire's)https://download.chainfire.eu/696/SuperSU/, and placed it on my ext SD Card, got flashify from Google Play and flashed it into Internal. Since there is contravercy about which Recovery's are compatible with this device. Then deleted ALL files except KingRoot and SuperSU. (King User, KingaRoot, Superuser, and all else I could find and have forgot) All seems well at this point.
Reading and studying for a recovery and possibly my first custom ROM.
NOTE: only v2.46 worked on some of my devices, newer versions/updates did nothing without the SuperSU v2.46 being previously flashed.

charliew410 said:
KingRoot rooted my LG K7 and installed Superuser. The Binaries needed updating for SuperSU, so I found the stable SuperSU v2.46, which was already saved from Chainfire on Twitter earlier on my PC(Link not found but here is Chainfire's)https://download.chainfire.eu/696/SuperSU/, and placed it on my ext SD Card, got flashify from Google Play and flashed it into Internal. Since there is contravercy about which Recovery's are compatible with this device. Then deleted ALL files except KingRoot and SuperSU. (King User, KingaRoot, Superuser, and all else I could find and have forgot) All seems well at this point.
Reading and studying for a recovery and possibly my first custom ROM.
NOTE: only v2.46 worked on some of my devices, newer versions/updates did nothing without the SuperSU v2.46 being previously flashed.
Click to expand...
Click to collapse
Which K7 do you have Metro or T-MO? a friend gave me this phone to do something nice with it. Phone only for Music Freedom on the 30$ 5GB plan. Having Viper FX would be nice.

patt2k said:
Which K7 do you have Metro or T-MO? a friend gave me this phone to do something nice with it. Phone only for Music Freedom on the 30$ 5GB plan. Having Viper FX would be nice.
Click to expand...
Click to collapse
It is the Metro PCS Device. And now that I have my 16 gig S4 operational again, maybe I will be playing with the 2 K7's that I have to see what I can come up with.
---------- Post added at 04:58 AM ---------- Previous post was at 04:56 AM ----------
mirfan4 said:
Hi,
I am currently working on an automation task, where i need to provide root access to other supporting apps. But as I am not able to provide the root access the app crashes with an error message as "Unfortunately xyz app has stopped". This was found working with Android L with older supersu app but not working with Android 6.0 with the latest marshmellow version of the supersu app.
Device : It is a test device hence cannot share any data about the product (Sorry for the inconvenience)
OS : Android 6.0.1
SuperSu app version : have tried with v2.37, v2.56 and v2.67
Kindly help us and ASAP @Chainfire : hope chainfire is reading this
Click to expand...
Click to collapse
As I said before only Super SU 2.4.6 have I had luck with updating the binaries.
---------- Post added at 05:03 AM ---------- Previous post was at 04:58 AM ----------
Death_Gun said:
actually I have the same problem.but I use stock rom (official rom from Sammobie)
android 4.4.2 and I don't have recovery cwm or twrp (it's long story).
the point is: how to root my device with this problem?
not/ I use galaxy s3 verizon
Click to expand...
Click to collapse
I just rooted an S4 with Kingroot, had the problem of binaries not installed with Super SU , installed Super sume, ran it,(which uninstalls Kingroot) and Super SU popped up again asking for the binaries, clicked yes, and normal installation and done.

Hi guys, problem as following.
I've a LG G3 running cyanogenmod 13 for a couple of months also updated it.
I haven't needed root access for a while, but now I need it for an app, but it was gone. So I opened SuperSU and I wanted to reactivate root.
But I have problems with the binarys. I can't install them via the app not the twrp.
In the help section it says me to download an apk called supersume but I cannot find this.
Could u help me?
Sebastian
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gesendet von meinem LG-D855 mit Tapatalk

[Magisk ON S7 EDGE]Magisk Safatynet Pass on Samsung Galaxy S7 edge

Hi guys! now i show to work magisk safatynet pass
Thanks @xJovs for your tutorial!
Link for your post Click Here!
Let's go
All rights reserved @xJovs for this tutorial
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
__________________________________​
*UPDATED*
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
- Samsung Galaxy S7
- SamSung Galaxy S7 EDGE
__________________________________​
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0+/7.0+
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Magisk V11.1 & Magisk Manager 4.1
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(If you cannot bypass with Xposed, use Root Switch!)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Step 1:
Clean Install
The first step install your custo rom, i installed SuperRom 1.2 MM and custom Karnel SuperStock 1.6 on installation.
Step 2: (For no MagiskSU users!)
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 4.2.6, SafetyNet Helper Sample, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV11.1
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V11.1, or reinstalling your rom.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "policy", change the permissions of the file from "444" to "440". If MagiskSU pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V11.1. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
If you're still not passing, try disabling USB Debugging in Developer Options!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________​
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.[/QUOTE]

Thanks man!
This actually worked on my S6 Edge SM-G925I.
I was just hoping if you could also figure out a way to use Samsung Pay despite having the Knox triggered.
TIA.

Shrey14 said:
Thanks man!
This actually worked on my S6 Edge SM-G925I.
I was just hoping if you could also figure out a way to use Samsung Pay despite having the Knox triggered.
TIA.
Click to expand...
Click to collapse
You are welcome!
On Android N you have update your Karnel for SuperStock 2.3 for work safetynet.

ClaudioJuniorBR said:
You are welcome!
On Android N you have update your Karnel for SuperStock 2.3 for work safetynet.
Click to expand...
Click to collapse
Currently I'm on Android M and safetynet is working. Please see the attachment.

Close this topic please!

I am stuck on stage 5 because I cannot see the check boxes on magisk manager 4.2.7. How to proceed?

Wow can't belive this actually worked!I spended so many times trying to make it work thanks OP.
However i can't make it work with xposed, the Safetynet check fails, it was strange because the first time it worked but as soon as i rebooted it was not working anymore.
There is a way to make Xposed work?I used Root Switch but it says is not fully supported for Magisk because it says that Magisk have it's own switch, i don't think it's referring to Magisk Hide because i have already enabled it so maybe i'm missing something here?

Help needed with Step 4
Hi guys,
I have been trying to flash Magisk v12 on my S7 edge (SM-G935FD) without super su, in hopes of using Magisk Su but I keep receiving ERROR: 1 in TWRP when it is trying to mount SU.
I am using a stock Rom and have performed a clean wipe in TWRP, but still cannot get Magisk v12 zip to install without the error 1 message. Appreciate if someone can enlighten me on how to over come this issue.

Sandiramogan said:
Hi guys,
I have been trying to flash Magisk v12 on my S7 edge (SM-G935FD) without super su, in hopes of using Magisk Su but I keep receiving ERROR: 1 in TWRP when it is trying to mount SU.
I am using a stock Rom and have performed a clean wipe in TWRP, but still cannot get Magisk v12 zip to install without the error 1 message. Appreciate if someone can enlighten me on how to over come this issue.
Click to expand...
Click to collapse
Error 1 can mean several things, post a recovery log from the installation.
And this guide is a bit outdated... Magisk performs step 6 and 7 automatically since v11.5.
Edit: answer my post in the support thread instead.

With magisk v12.. Any idea?

Didgeridoohan said:
Error 1 can mean several things, post a recovery log from the installation.
And this guide is a bit outdated... Magisk performs step 6 and 7 automatically since v11.5.
Edit: answer my post in the support thread instead.
Click to expand...
Click to collapse
Thank you for your reply. I managed to install Magisk v12 after performing a completely clean wipe and flashing the stock ROM from ODIN. I immediately attempted to install Magisk after flashing the latest version of TWRP and everything works like a charm, even passing Safety Net. However on the other hand, I'm now trying to figure out how to fake Knox 0x0 as mentioned in the changelog. If you do have any idea, please do share and let me know.
Cheers and have a great weekend.

Sandiramogan said:
Thank you for your reply. I managed to install Magisk v12 after performing a completely clean wipe and flashing the stock ROM from ODIN. I immediately attempted to install Magisk after flashing the latest version of TWRP and everything works like a charm, even passing Safety Net. However on the other hand, I'm now trying to figure out how to fake Knox 0x0 as mentioned in the changelog. If you do have any idea, please do share and let me know.
Cheers and have a great weekend.
Click to expand...
Click to collapse
Since you're passing SafetyNet it's a pretty sure bet that you have Magisk Hide enabled. That's all you need to do since the KNOX counter is masked by Magisk Hide. It doesn't work?

Do you know if Google changed something? Today I noticed that I can't see Fire Emblem and Mario Run in the Playstore. Days ago it was working fine but now it seems they are not compatible again.

I don't know why but I can't add new scripts in Kernel Adiutor.
Everything else worked. Any idea?

things i do to play super mario run

Works well when disable xposed in module section in magisk manager then reboot.
Any fix for work safetynet pass with enable xposed ?

koko115 said:
Any fix for work safetynet pass with enable xposed ?
Click to expand...
Click to collapse
Nope...

935V user here: I get "Custom Binary Blocked by Secure Boot". I flashed using Flashfire instead of TWRP. I used the root method described here: https://forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978
Should I have rooted a different way as to utilize TWRP?

some one can help me?
imgur.com/a/4cufj

Does anyone know if this works on any of the US models?

[GUIDE] How to Uninstall a Magisk Module (bootloop fix)

For those who encounter a bootloop because of a Magisk Module or got a bootloop during an update because of a module
This will allow you to go and delete that bad module and allowing you to boot back into the OS
What you need:
Recommended TWRP from TWRP 3.3.1-xx Unified Unofficial by mauronofrio
**Official TWRP may not allow you to boot twrp.img**
OOSNativeCallRecording Module seems to be one culprit. Make sure to Uninstall before updating.
If you already have twrp then go to Instructions
If you do not have TWRP and do not want to Install, use this method
Boot to TWRP (for those of us who do not install TWRP)
Does not work with OxygenOS 9.5.3 and below
Make sure to have adb and fastboot files here
1. Download the TWRP image (not Installer) from post above
2. Boot to fastboot
3. Rename TWRP image to twrp.img and move to folder with adb and fastboot files (after you had extracted)
4. Type
Code:
fastboot boot twrp.img
Instructions
1. Boot to TWRP
2. Go to Advanced > File Manager > data > adb > modules
3. click on the folder of the module you want to delete
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. while inside that folder click on the little folder on the bottom right with the check mark on it
5. click Delete
Done... Reboot back to OS without a bootloop

you should add what to do if you can't boot twrp. Happened to me after I removed Google dialer framework. Only thing I could get it to is bootloader. would not let me fastboot TWRp. I got an error every time. I had the flash boot image

mac796 said:
you should add what to do if you can't boot twrp. Happened to me after I removed Google dialer framework. Only thing I could get it to is bootloader. would not let me fastboot TWRp. I got an error every time. I had the flash boot image
Click to expand...
Click to collapse
This happened to me the other day. Took me an hour to figure out that all I had to do was fastboot boot.img.

diaztradeinc said:
This happened to me the other day. Took me an hour to figure out that all I had to do was fastboot boot.img.
Click to expand...
Click to collapse
I will update it shortly, thank you for the feedback.

Bradl79 said:
For those who encounter a bootloop because of a Magisk Module or got a bootloop during an update because of a module
This will allow you to go and delete that bad module and allowing you to boot back into the OS
What you need:
TWRP from here
If you already have twrp then go to Instructions
If you do not have TWRP and do not want to Install, use this method
Boot to TWRP (for those of us who do not install TWRP)
Does not work with OxygenOS 9.5.3 and below
Make sure to have adb and fastboot files here
1. Download the TWRP image (not Installer) from post above
2. Boot to fastboot
3. Rename TWRP image to twrp.img and move to folder with adb and fastboot files (after you had extracted)
4. Type
Code:
fastboot boot twrp.img
Instructions
1. Boot to TWRP
2. Go to Advanced > File Manager > data > adb > modules
3. click on the folder of the module you want to delete
4. while inside that folder click on the little folder on the bottom right with the check mark on it
5. click Delete
Done... Reboot back to OS without a bootloop
Click to expand...
Click to collapse
Just install the magisk module "Magisk Manger for Recovery".... Done. No need for such long instructions...

matze19999 said:
Just install the magisk module "Magisk Manger for Recovery".... Done. No need for such long instructions...
Click to expand...
Click to collapse
It's actually pretty simple, u just have to provide more instructions for people who haven't used twrp. There is no need to flash anything, ik that the uninmod does not work and I thought I tired mm and could not get it working either.

I use MM for TWRP since years and it always worked perfectly.

matze19999 said:
I use MM for TWRP since years and it always worked perfectly.
Click to expand...
Click to collapse
Have u used it with ur 7Pro yet? I tried it yesterday and would not flash along with uninmod would not mount magisk, I think it's issues with dual partition bc it did the same with my OP6

Bradl79 said:
Have u used it with ur 7Pro yet?
Click to expand...
Click to collapse
yeah. Whats not working for you?

matze19999 said:
yeah. Whats not working for you?
Click to expand...
Click to collapse
Got error when flashing, would u mind sharing the file?

Bradl79 said:
Got error when flashing, would u mind sharing the file?
Click to expand...
Click to collapse
I got the one to install from the download section but I've never used it I'm not sure how it works

He's right uninmod and stuff like that doesn't work at all now. It's unable to mount magisk.img it seems to be an issue with our twrp.
As for the statement about the issue being dual partitions that's wrong it's has nothing to do with that. I know he mentioned that uninmod and others did not work on op6 as well.. But it did cause I used uninmod on my 6 and 6T. This is an issue with this device only and possibly the twrp we have currently.

You saved my ass today! I updated to 9.5.9 and had bootloops. I forgot to disable my magisk modules :silly:

equlizer said:
You saved my ass today! I updated to 9.5.9 and had bootloops. I forgot to disable my magisk modules :silly:
Click to expand...
Click to collapse
Are u using OOSNativeCallRecorder module?

Yes i was using it. Just re-installed it.

Saved my ass!
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
So do we need to disable modules before updating? The re enable after?

spart0n said:
Saved my ass!
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
So do we need to disable modules before updating? The re enable after?
Click to expand...
Click to collapse
Duh what you think? Lol naw for real tho...I've learned that after updating never reinstall mods that aren't up to date with the current os....I can't speak for all mods but magisk roms like renovate ice needs to be updated to the current os or problems will occur....I'm a noobish noob but I learned my lesson

mlock420 said:
Duh what you think? Lol naw for real tho...I've learned that after updating never reinstall mods that aren't up to date with the current os....I can't speak for all mods but magisk roms like renovate ice needs to be updated to the current os or problems will occur....I'm a noobish noob but I learned my lesson
Click to expand...
Click to collapse
Well what I'm getting at is that I deleted all 4 of my magisk mods and fixed the bootloop and then reinstalled all 4 of them and rebooted and everything is fine now. I was asking about should we disable all mods, reboot, update, install magisk, reboot, check root with magisk then reinstall all mods and reboot again?

equlizer said:
Yes i was using it. Just re-installed it.
Click to expand...
Click to collapse
You prob only need to Uninstall that next time b/c that is one that is causing issues. I do not use and I have multiple Modules that survive update not needing to uninstall all modules.

Thanks. I had problem with pernament bootloop after magisk instalation.

Help-me Please

I used a magisk option to rename / hide it, and ended up losing root, tried to root, but to no avail, magisk manager no longer has the modules, magisk hide, or supersu option. Can someone help me ?

Simply uninstall the Manager and then reinstall it manually (apk in the Magisk zip or from @topjohnwu's Github.

Didgeridoohan said:
Simply uninstall the Manager and then reinstall it manually (apk in the Magisk zip or from @topjohnwu's Github.
Click to expand...
Click to collapse
already tried, and already tried to root again, the process happens without fail, but when you check this without
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

danyfenton said:
already tried, and already tried to root again, the process happens without fail, but when you check this without
Click to expand...
Click to collapse
Do you happen to have a second Magisk Manager in your app drawer, just named "Manager"? If so, that's likely the currently, by Magisk, recognised Manager. Uninstall both managers and try again.
If that doesn't help, you're going to have to start being more detailed:
https://didgeridoohan.com/magisk/MagiskHelp

Didgeridoohan said:
Do you happen to have a second Magisk Manager in your app drawer, just named "Manager"? If so, that's likely the currently, by Magisk, recognised Manager. Uninstall both managers and try again.
If that doesn't help, you're going to have to start being more detailed:
https://didgeridoohan.com/magisk/MagiskHelp
Click to expand...
Click to collapse
Yes, I had the manager, I also uninstalled and redo the installation, and without success.
Things I've already done:
- I uninstalled Manager.apk, and reinstalled Magisk
- Redo Root using TWRP.
- I uninstalled Magisk from TWRP via MagiskUnistall.rar file
- Installed Previous Versions of Magisk, like 17.1; 18.1; 19.4 (Beta).
and still unsuccessful, magisk looks like the image I posted above. Worst of all was that I lost root, and even trying to redo the root procedures, does not come back.
I am using google translator, I apologize if the understanding is not so good.

It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.

when I try to install from magisk itself, this error appears.

Didgeridoohan said:
It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.
Click to expand...
Click to collapse
OK, when I get home from work I'll try, thanks.

Didgeridoohan said:
It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.
Click to expand...
Click to collapse
unsuccessful when using unSU.
succeeded in using it on twrp, restarted the phone, and went back to TWRP, and redid the process, and to no avail.

Didgeridoohan said:
It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.
Click to expand...
Click to collapse
- Device platform: armeabi-v7a
- Copying image to cache
1022+1 records in
1022+1 records out
1047368 bytes transferred in 0.016 secs (65460500 bytes/sec)
- Unpacking boot image
Parsing boot image: [/mnt/expand/20683188-08c0-4603-a521-de6372bd2a29/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed

danyfenton said:
unsuccessful when using unSU.
succeeded in using it on twrp, restarted the phone, and went back to TWRP, and redid the process, and to no avail.
Click to expand...
Click to collapse
Didgeridoohan said:
Do you happen to have a second Magisk Manager in your app drawer, just named "Manager"? If so, that's likely the currently, by Magisk, recognised Manager. Uninstall both managers and try again.
If that doesn't help, you're going to have to start being more detailed:
https://didgeridoohan.com/magisk/MagiskHelp
Click to expand...
Click to collapse
I got it, I formatted the phone and redid the whole process. Thanks for the force friend.

danyfenton said:
I got it, I formatted the phone and redid the whole process. Thanks for the force friend.
Click to expand...
Click to collapse
I was just about to come in here and reply to your other message, and I find you got it sorted. Nice.
All I did was point the way, you're the one who fixed it in the end. :good:

Didgeridoohan said:
I was just about to come in here and reply to your other message, and I find you got it sorted. Nice.
All I did was point the way, you're the one who fixed it in the end. :good:
Click to expand...
Click to collapse
thank you for being willing to help, really.

[Release][2022.6.26] Magisk Manager for Recovery Mode (mm)

Magisk Manager for Recovery Mode v7 202206260
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v19.0 - v25.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
- Source code
- Documentation
- Releases
- Original thread
Note: The GUI "Magisk Manager Recovery Tool" project is a different, stand-alone project.
Which is not affiliated with this CLI "Magisk Manager for Recovery Mode" project.
Edit1: Reported as working on Magisk v23.X! Updated the documentation and released a new version
Edit2: Tested and confirmed working on Magisk v25.X! Updated the module's readme, print lines, inner docs...

I might be doing something wrong but it's not working...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Poslano z mojega MI 9 z uporabo Tapatalk

mxxt01 said:
I might be doing something wrong but it's not working... View attachment 4997015
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.

Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
Sorry, all clear now [emoji16]
I was just about to try in TWRP...
Thanks!
Poslano z mojega MI 9 z uporabo Tapatalk

Rikj000 said:
Magisk Manager for Recovery v5 202004170
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v20.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
Flash this in TWRP each time you want to use it, not in Magisk itself.
You can download the new release from my GitHub: https://github.com/Rikj000/mm/releases/tag/2020.4.17
Original thread: https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
Click to expand...
Click to collapse
Thanks this will be handy when experimenting some modules
Sent from my Mi A2 using Tapatalk

Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support

JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork

JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Same here.
Updater process ended with error: 123

Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Sent from my #FlagshipKiller6T using Tapatalk

DarkSJ1998 said:
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Click to expand...
Click to collapse
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.

Rikj000 said:
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork
Click to expand...
Click to collapse
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?

JamesKinds said:
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?
Click to expand...
Click to collapse
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP

Rikj000 said:
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP
Click to expand...
Click to collapse
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?

JamesKinds said:
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?
Click to expand...
Click to collapse
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.

Magisk v20.4 ERROR 123 ((( for Recovery

Latest Magisk Canary, working like a charm, thanks

Rikj000 said:
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.
Click to expand...
Click to collapse
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Sent from my #FlagshipKiller6T using Tapatalk

DarkSJ1998 said:
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Click to expand...
Click to collapse
Upon further inspection might be due to spaces in the zip file name. But magisk script wasnt up to date anyways. So this version will be supported in Magisk for a longer time then the original due to that.

Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
Bro, uninstall all versions this mod, reboot system, boot to twrp flash zip, go in twrp to terminal write mm, write q and click enter, boot to system, reboot to twrp go to terminal and type sdcard/mm important sdcard/mm, now should work

Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
I found the solution to the installation error eventually. The zip itself MUST be somewhere in internal storage when flashing and cannot be in sd card or otg. And even the old mmfr zip installs for me if I place it in internal storage. So maybe include this in your post. For context, I use Android Q rom with Magisk 20.4.