Related
Hi guys, I've been having problems getting magisk v11.1 to install correctly.
I have a Samsung galaxy s5 which I use to play about with. I flashed magisk v11.1 which installed properly. After starting up my phone and getting the Magisk manager app it's telling me magisk is not installed. Yet the manager also tells me its properly rooted 6:MAGISKSU (topjohnwu)
The manager gives me the option to download and install v11.1 when I install it through the manager app it says installation succeeded, yet when I reboot I get the same results again. Magisk is not installed, properly rooted.
Does anyone have any ideas what I might be doing wrong?
Ok. This has been reported a few times, but I've not seen it properly troubleshooted yet.
1 - Root is working on your device? You can grant root to root apps?
2 - Do you have a file called magisk.img in /data?
I can't see the file in that directory. I also did a search and nothing came up
I can use root explorer in ES file explorer
Just to make sure: it's supposed to be in the /data folder found in root (where you'll also find /etc, /system, and so on), not in your main storage. If it's not there, that's your problem. That the Magisk image isn't installing correctly.
Could you also upload a recovery log from flashing Magisk in recovery?
Sorry I made a mistake, I was looking in Data>Magisk folder, in / Data there is a file called magisk.img
Awesome. Then that's not the issue then...
Recovery log and Magisk log, please...
Sorry for the noob question, but where do I find the logs?
Exactly the same problem with my NOTE 4 on Android 6.0.1. After Reboot Magisk is gone. Without Reboot works perfect (SU and Safetynet).
Looks like temporary "magisk".
The Boot Image Path is automatic (mmcblk0p17). Maybe change. But which one? There are about 20 paths.
I did a quick search and found another couple of posts in the support thread about this issue. Guess what you all have in common? Samsung... The statistical material is way to small to make any definite assumptions, but it points to a trend. And we know that Samsung doesn't always play nice with Magisk.
Have you guys tried a custom kernel? No guarantees, of course...
Possibly useful logs for troubleshooting:
- Recovery log from installation (saved in recovery right after flashing Magisk, can also possibly be found in /cache/recovery after booting up the device).
- Magisk log. Found and exported from the Manager (make sure verbose logging is enabled), or if that doesn't work it can be found in the /cache folder (accessible though TWRP if nothing else works).
- Logcat from boot. Use a computer, connect the device and use ADB to catch a logcat from boot up until you can confirm that Magisk reports "not installed" (How to logcat).
If nothing works, open an issue on GitHub with a detailed description, logs and boot image attached (just make sure no-one else has opened one before, if so post your information to that issue).
Same problem
Same problem here in a G900F (galaxy s5) with [ROM][G900F][ALEXNDR] CQBW, i can grant access to apps and the magisk.img is in /data, but magisk manager says that magisk is not installed.
Attached magisk and recovery logs
recovery and magisk logs
I tried a custom kernel like you said and it seems to work now. The status is all passes. I used this [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
K3vG said:
I tried a custom kernel like you said and it seems to work now. The status is all passes. I used this [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
Click to expand...
Click to collapse
Did somebody knows something like this above for the NOTE 4 SM-N910F? I have no experience with custom kernels.
Since @K3vG managed to fix the problem with a custom kernel it's very probable that this is a compatibility issue with the stock boot image.
Would any of you fine gentlemen like to contribute to the community and development of Magisk? It'd be helpful if one of you could open an issue on GitHub about this, with details and a copy of the problem boot image. It'd probably also be helpful if the rest of you then could add your boot images...
Of course, there are no guarantees, but if there's an open issue on GitHub with the above mentioned information there's at least a chance that @topjohnwu can take a look at it and possibly even fix the compatibility issue.
Didgeridoohan said:
Since @K3vG managed to fix the problem with a custom kernel it's very probable that this is a compatibility issue with the stock boot image.
Would any of you fine gentlemen like to contribute to the community and development of Magisk? It'd be helpful if one of you could open an issue on GitHub about this, with details and a copy of the problem boot image. It'd probably also be helpful if the rest of you then could add your boot images...
Of course, there are no guarantees, but if there's an open issue on GitHub with the above mentioned information there's at least a chance that @topjohnwu can take a look at it and possibly even fix the compatibility issue.
Click to expand...
Click to collapse
There is already an open issue https://github.com/topjohnwu/Magisk/issues/94
ccerrillo said:
There is already an open issue https://github.com/topjohnwu/Magisk/issues/94
Click to expand...
Click to collapse
Awesome! I checked but missed that one. Then someone should upload a boot image to that issue.
Didgeridoohan said:
Awesome! I checked but missed that one. Then someone should upload a boot image to that issue.
Click to expand...
Click to collapse
What is that image? /data/magisk.img??
ccerrillo said:
What is that image? /data/magisk.img??
Click to expand...
Click to collapse
You'll find boot.img in your ROM zip or factory image. Alternatively you can make a backup of Boot in TWRP and upload that.
K3vG said:
I tried a custom kernel like you said and it seems to work now. The status is all passes. I used this [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
Click to expand...
Click to collapse
I flashed that kernel too, and then i can install magisk, but magisk manager tell's "SafetyNet failed CTS profile missmatch"
What i do:
1.- Flash Alexndr rom (G900FXXS1CQBW_DevBase_v3.8.zip << Android 6.0.1 - stable)
2. Reboot
3.- Flash [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
4.- Reboot
5.- Flash Magisk V11.1
6.- Reboot
7.- Enable Magisk Hide
8.- Reboot
9.- "SafetyNet failed CTS profile missmatch" :crying:
What i'm missing?? What steps did you follow to bypass SafetyNet??
---------- Post added at 09:11 PM ---------- Previous post was at 09:06 PM ----------
Didgeridoohan said:
You'll find boot.img in your ROM zip or factory image. Alternatively you can make a backup of Boot in TWRP and upload that.
Click to expand...
Click to collapse
I got it!! Thanks!
ccerrillo said:
I flashed that kernel too, and then i can install magisk, but magisk manager tell's "SafetyNet failed CTS profile missmatch"
What i do:
1.- Flash Alexndr rom (G900FXXS1CQBW_DevBase_v3.8.zip << Android 6.0.1 - stable)
2. Reboot
3.- Flash [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
4.- Reboot
5.- Flash Magisk V11.1
6.- Reboot
7.- Enable Magisk Hide
8.- Reboot
9.- "SafetyNet failed CTS profile missmatch" :crying:
What i'm missing?? What steps did you follow to bypass SafetyNet??
---------- Post added at 09:11 PM ---------- Previous post was at 09:06 PM ----------
I got it!! Thanks!
Click to expand...
Click to collapse
did u manage to get this fixed?
I mean, did you found a way to get safetynet to pass with a custom kernel?
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is oppo neo 7 android 5.1
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Didgeridoohan said:
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Click to expand...
Click to collapse
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
rajoholic said:
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
Click to expand...
Click to collapse
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Didgeridoohan said:
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Click to expand...
Click to collapse
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
I m also facing same problem
rajoholic said:
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is Micromax canvas nitro a310 current android version is cyanogen mode 13
Click to expand...
Click to collapse
rajoholic said:
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
Click to expand...
Click to collapse
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
sorry bout that. i just search the google free and temporary storage online. haha! thank you for the help. I'll try what u just said
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
rajoholic said:
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
Click to expand...
Click to collapse
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Didgeridoohan said:
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
rajoholic said:
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
Click to expand...
Click to collapse
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Didgeridoohan said:
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Click to expand...
Click to collapse
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
rajoholic said:
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
Click to expand...
Click to collapse
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Didgeridoohan said:
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Click to expand...
Click to collapse
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
rajoholic said:
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
Click to expand...
Click to collapse
Sir, did you manage to install? when i tried to install log is failed.
Canary Magisk Manager: Link
Canary Magisk Manager (Debug): Link
Latest Release Notes: Link
All Canary Files: Link
The Canary Builds are similar to Google Chrome's: bleeding edge of the source.
Be warned: Canary can be unstable.
The binaries from debug channel are built with debug flag ON
Install Canary Magisk Manager and go to Settings > Update Channel and switch to either Canary or Canary (Debug)
If you need a clean start, download the Canary Uninstaller to uninstall any version of Magisk
How to Report:
Only report bugs/logs using the debug channel!!
Magisk installation failure:
In TWRP: Upload the recovery logs (pull the file /tmp/recovery.log, or select "Advanced > Copy Log" and upload)
In MagiskManager: Choose to save logs after installation and upload
Magisk bugs:
Magisk logs are placed in /cache/magisk.log (For A/B devices, they are actually in /data/cache/magisk.log)
If you cannot boot or stuck in bootloops, grab logcats (and kernel dmesg if possible) on boot
Magisk Manager bugs:
Grab logcat (NOT magisk logs) when the crash occurs, upload the logs and report how to reproduce
SafetyNet / CTS / XXX app won't work after enabling MagiskHide:
Ignored
I just installed this on one of my Nextbook Ares 8A's, x86, Android 6.0.1. It was previously on @ianmacd 's unofficial build. So far, it appears to be working great. I un-installed my previous MM, before I install the new one, downloaded the Magisk.zip in MM and flashed it through TWRP.
How much overhead does the extra logging create? I don't notice any difference. Do you think it will affect battery life?
When I check the magisk.log it does appear that it is continuously logging, because each time I check it the time stamp is updated.
If I am not mistaken, on non debug builds the magisk.log is only created at boot and not updated again until next boot?
Thanks, @topjohnwu for creating this new channel for testers.
Wew, downloading and testing on my 7.1.2, so far so good. Thanks.
Aye official snapshots! Awesome. Been using @kantjers up until now. Thanks for this
Sent from my LG Nexus 5X using XDA Labs
Testing now. Thanks ?
No issues with any of my used modules ?
When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.
jcmm11 said:
When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.
Click to expand...
Click to collapse
Yes, I think Magisk Manager should ask for the storage permission on first launch and not later when the actual storage permission is need. I have been bit by the storage permission a few time in other instances of using MM.
Good find @jcmm11 , I have not used that option to patch the boot.img.
Any way to fix the phone off charging issue? To recap. When phone is powered of and plugged in. The charging battery icon.stays on and freezes the screen. Only hard reboot gets phone started.
New Canary Build up for Testing!
Support bypassing FGO, CrackProof protections, and Fortnite!
jcmm11 said:
When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.
Click to expand...
Click to collapse
This issue is resolved, thank you for your report!
def-g said:
Any way to fix the phone off charging issue? To recap. When phone is powered of and plugged in. The charging battery icon.stays on and freezes the screen. Only hard reboot gets phone started.
Click to expand...
Click to collapse
I'm aware of this issue, will try to figure out the cause of the issue
topjohnwu said:
New Canary Build up for Testing!
Support bypassing FGO, CrackProof protections, and Fortnite!
This issue is resolved, thank you for your report!
I'm aware of this issue, will try to figure out the cause of the issue
Click to expand...
Click to collapse
Cool. To be honest, only a minor inconvenience. Your work is greatly appreciated.
I just installed this build and it appears to be fine on my device. The logcat was taken in Logcatx using the per app logcat for Magisk Manager. If you would like a full system logcat, let me know, or if you would like any other info such as last_kmsg or dmsg, let me know.
I have been installing through TWRP, since recently I have twice experienced data corruption issues with the direct install method in unofficial builds, noted in the unofficial thread.
As always, Thanks
Hi, after fullwipe the MM is not installed on first Phone start? Is this a Bug?
I use a S7 Edge with SM 2.8.
Please Help.
BustedFly said:
Hi, after fullwipe the MM is not installed on first Phone start? Is this a Bug?
I use a S7 Edge with SM 2.8.
Please Help.
Click to expand...
Click to collapse
I suggest you download MM from here and try to install it. I have been flashing Unofficial builds of Magisk for some time and this appears to be a common issue. It should not happen if you did a full wipe of the ROM though.
The latest Canary Magisk Manager.apk download:
https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/app-full-debug.apk
Direct download for all of the latest Canary builds:
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Thx.
I try a few build... Offi and unoffi.... The only one without this Bug ist the builds from kantjer. All other cant install the MM after a fullwipe. I try this many times
BustedFly said:
Thx.
I try a few build... Offi and unoffi.... The only one without this Bug ist the builds from kantjer. All other cant install the MM after a fullwipe. I try this many times
Click to expand...
Click to collapse
By fullwipe, I presume you mean full wipe of the ROM? If not, you must remove the Magisk Manager of the unofficial build before installing this one, as it is signed with a different key.
Yes.. I mean fullwipe by twrp and clean Installation of the Rom
BustedFly said:
Yes.. I mean fullwipe by twrp and clean Installation of the Rom
Click to expand...
Click to collapse
After flashing Magisk and rebooting, the app-full-debug.apk will not install? That is a strange issue. Maybe someone else can help.
On one device with @kantjer 's latest build, I first un-installed his Magisk Manager, installed the app-full-debug.apk, opened it, set up the custom update channel to the link in the op: https://bit.ly/2MPKGY5 and hit install, download Zip only, then rebooted to TWRP and installed that downloaded Magisk.zip and rebooted to a working Magisk install.
Hey @topjohnwu,
I've noticed a line just after rebooting using the Canary:
Code:
09-09 14:34:38.542 3913 3913 D Magisk : resetprop: decode with protobuf from [/data/property/persistent_properties]
09-09 14:34:38.542 3913 3913 D Magisk : resetprop: prop [persist.magisk.hide] does not exist
I'm not sure if it's important or not for magisk functionality, however I wanted to report it just in case something is off.
I'm using OnePlus 6 with Open Beta 2 (Pie, 9.0).
I'm going to make it my duty to delete any and all posts that are not relevent to what the developer wants or is asking for.
I'll be checking this thread daily from here on out. If I find myself deleting a ton of any reoccurring member's posts, I'll be escalating to consequences.
Please, thoroughly give your posts some thought prior to submitting them, and ask yourself if whether or not it fits into how or what the OP is asking.
Thank you
So, tried last canary, nothing critical to report apart that FGO doesn't work (it crashes like before with error 61), here there are both magisk log and catlog.
Catlog (too big for xda, dunno why): https://mega.nz/#!LUoBQY6L!X--KKkCCzQn4SLwaIX1hYsmrKzzNfx1TTSGCh1b-0E4
Magisk log attached.
OnePlus 6 OOS 5.1.11, 8.1 July Patch
If anything else is needed I'll provide it right away
Is there a version of Magisk that works on the realme Pro 5g RMX2075?
I tried the version 20.4 after unlocking the bootloader and installing recovery-TWRP-3.4.1B-04-17-realme-x50-pro-wzsx150, but it fails the signature. If I disable checking the signature on TWRP, it loads but bricks the phone until I re-install the stock boot.img, and then Magisk is not installed.
Providing the install log is usually a good first step when troubleshooting.
And, if you can't get the stable release installed it's usually a good idea to try the Canary release since it might have been updated with more compatibility.
Didgeridoohan said:
Providing the install log is usually a good first step when troubleshooting.
And, if you can't get the stable release installed it's usually a good idea to try the Canary release since it might have been updated with more compatibility.
Click to expand...
Click to collapse
I'm not sure how to find the log, but I'll try the Canary release first, thank you very much for the quick answer.
Being a bit paranoiac (a LOT in fact), I have 2 RMX2075, so bricking is not catastrophic. I can take my time to find how to unbrick it.
Since some manips like unlocking the bootloader wipes everything, it make easier to restore using the clone phone app.
I know, I know, I should get a life...
Edit: just saw the log was a link, I will provide with the canary if it fails too.
Ok, some info I failed to provide:
realme X50 Pro 5G RMX2075
Android 10
realme UI version 1.0
TRWP installed with recovery-TWRP-3.4.1B-04-17-realme-x50-pro-wzsx150, and with the file EN_Recovery-twrp-oneclick-EN.bat.
I need to run this .bat file every time I want to use TRWP, Up (or Down) + Power does not work and gives me the standard bootloader, which I unlocked with the deep testing app.
With Magisk-v20.4.zip the signature test failed. I had the brilliant idea to disable checking it, and it installed and bricked my phone until I used again EN_Recovery-twrp-oneclick-EN.bat to re-install boot.img in the bot partition.
The signature failed also with magisk-debug.zip. I did not try to install without checking it first, once bitten...
The oppo_log directory is empty. Please let me know if there is another place to look. I don't have an ADVANCED directory in TRWP. I checked before rebooting, so instead, I send a screen cap.
I don't see how to attach a file, so here is a link:
https://postimg.cc/py17ct1q
You have to disable zip signature validation in TWRP or you won't be able to flash a Magisk zip at all.
The actually recovery log is completely necessary to be able to troubleshoot. The ADVANCED part in TWRP isn't a directory, but one of the buttons on the main page. You'll then be able to save a log and you'll find it in /sdcard. The log has to be saved directly after flashing the zip, or it won't show the info we need.
Didgeridoohan said:
You have to disable zip signature validation in TWRP or you won't be able to flash a Magisk zip at all.
The actually recovery log is completely necessary to be able to troubleshoot. The ADVANCED part in TWRP isn't a directory, but one of the buttons on the main page. You'll then be able to save a log and you'll find it in /sdcard. The log has to be saved directly after flashing the zip, or it won't show the info we need.
Click to expand...
Click to collapse
OK, I'll try later. Thanks for the info.
Didgeridoohan said:
You have to disable zip signature validation in TWRP or you won't be able to flash a Magisk zip at all.
The actually recovery log is completely necessary to be able to troubleshoot. The ADVANCED part in TWRP isn't a directory, but one of the buttons on the main page. You'll then be able to save a log and you'll find it in /sdcard. The log has to be saved directly after flashing the zip, or it won't show the info we need.
Click to expand...
Click to collapse
Same problem with the debug version, unable to reboot.
I used TWRP to create a log.
I'm not sure where it went exactly, here are all the logs I could find in various places, I don't have a /sdcard directory:
https://wetransfer.com/downloads/3f...4d3d4ca52a615682f34f182520200725060951/875fb2
If I missed the correct log, please let me have some info where to find it exactly and I'll try again. Now that I could unbrick twice my phone, I feel safer!
Thanks.
I rooted my Motorola One Macro yesterday, I unlocked bootloader and installed Magisk. I don't have custom recovery beacuse i had problem with installing it. Root Checker says root is properly installed on my device, but I have somme issues with getting things to work. I downloaded Magic Mask Repo, and tried installing Energized module. It downloaded suscessfully, but installation doesn't seem to do anything even after reboot. I also tried installing it manually with Magisk, but I got this in console:
- Copying zip to temp directory
! Unzip error
Pasting uzipped energized folder to /data/adb/modules makes it appear in module section in Magisk, but still it don't work. Material Terminal says acces denied after typing in energized - m command. Reinstallation of Magisk didnt helped. I dont really want to factory reset my phone, is there anything that i can do?
_lama195 said:
I rooted my Motorola One Macro yesterday, I unlocked bootloader and installed Magisk. I don't have custom recovery beacuse i had problem with installing it. Root Checker says root is properly installed on my device, but I have somme issues with getting things to work. I downloaded Magic Mask Repo, and tried installing Energized module. It downloaded suscessfully, but installation doesn't seem to do anything even after reboot. I also tried installing it manually with Magisk, but I got this in console:
- Copying zip to temp directory
! Unzip error
Pasting uzipped energized folder to /data/adb/modules makes it appear in module section in Magisk, but still it don't work. Material Terminal says acces denied after typing in energized - m command. Reinstallation of Magisk didnt helped. I dont really want to factory reset my phone, is there anything that i can do?
Click to expand...
Click to collapse
this is an easy one....
that error *usually* implies youve downloaded a master zip of a github repo, and not a zip file from the releases section
if you went to
GitHub - Magisk-Modules-Repo/energizedprotection: Energized Protection Magisk Module.
Energized Protection Magisk Module. Contribute to Magisk-Modules-Repo/energizedprotection development by creating an account on GitHub.
github.com
and then downloaded the zip it will NOT work, and they dont have a release
so heres the easy fix, and why it fails
1) unzip the file, you'll get a folder (energizedprotection-master)
Note this is why magisk wont install it, it expects to find files (especially crucial files to tell it how to install the module) and folders in the root directory, not a single folder with nested files and folders under it...
2) go into energizedprotection-master folder
3) select all files/folders
4) zip the selected contents into a new zip file (ideally with 7zip - WinRAR can create dud zips)
5) move that zip to device and flash
Ideally you'll install Fox's Magisk Module Manager and use that for most modules - energized may not be on it - download the .apk
Release Release v2.0.2 · Fox2Code/FoxMagiskModuleManager
Please read the full changelog. It contains very important information on the future of this app and caveats when updating. Release notes: https://www.androidacy.com/magisk-module-download-simplifi...
github.com
the old magisk repo was decommisioned....
It works now, I greatly appreciate it, thanks!
73sydney said:
this is an easy one....
that error *usually* implies youve downloaded a master zip of a github repo, and not a zip file from the releases section
if you went to
GitHub - Magisk-Modules-Repo/energizedprotection: Energized Protection Magisk Module.
Energized Protection Magisk Module. Contribute to Magisk-Modules-Repo/energizedprotection development by creating an account on GitHub.
github.com
and then downloaded the zip it will NOT work, and they dont have a release
so heres the easy fix, and why it fails
1) unzip the file, you'll get a folder (energizedprotection-master)
Note this is why magisk wont install it, it expects to find files (especially crucial files to tell it how to install the module) and folders in the root directory, not a single folder with nested files and folders under it...
2) go into energizedprotection-master folder
3) select all files/folders
4) zip the selected contents into a new zip file (ideally with 7zip - WinRAR can create dud zips)
5) move that zip to device and flash
Ideally you'll install Fox's Magisk Module Manager and use that for most modules - energized may not be on it - download the .apk
Release Release v2.0.2 · Fox2Code/FoxMagiskModuleManager
Please read the full changelog. It contains very important information on the future of this app and caveats when updating. Release notes: https://www.androidacy.com/magisk-module-download-simplifi...
github.com
the old magisk repo was decommisioned....
Click to expand...
Click to collapse
Hey I am trying to install BCR - Module module from github " https://github.com/chenxiaolong/BCR " but I am unable to install it in magisk. It is throwing the same error . Can you help me with that ? Thanks in advance
Arnavsingh7075 said:
Hey I am trying to install BCR - Module module from github " https://github.com/chenxiaolong/BCR " but I am unable to install it in magisk. It is throwing the same error . Can you help me with that ? Thanks in advance
Click to expand...
Click to collapse
go to the Releases section on the right of the page with Version 1.29 and green latest to the right of it, scroll down to assets and click on BCR-1.29-release.zip to download the module...this WILL flash, or your money back...
....like my earlier post says, youre probably downloading the master or source code which wont work unless you unpack and repack it (and then sometimes not, if they havent actually compiled the apk if theres an apk component), if there is a Release section with active Releases, use that....
73sydney said:
go to the Releases section on the right of the page with Version 1.29 and green latest to the right of it, scroll down to assets and click on BCR-1.29-release.zip to download the module...this WILL flash, or your money back...
....like my earlier post says, youre probably downloading the master or source code which wont work unless you unpack and repack it (and then sometimes not, if they havent actually compiled the apk if theres an apk component), if there is a Release section with active Releases, use that....
Click to expand...
Click to collapse
You are an absolute hero, thank you so so much for this
73sydney said:
go to the Releases section on the right of the page with Version 1.29 and green latest to the right of it, scroll down to assets and click on BCR-1.29-release.zip to download the module...this WILL flash, or your money back...
....like my earlier post says, youre probably downloading the master or source code which wont work unless you unpack and repack it (and then sometimes not, if they havent actually compiled the apk if theres an apk component), if there is a Release section with active Releases, use that....
Click to expand...
Click to collapse
Bro what abt this it's having same issue is there any other way rather unzip and zip it again https://github.com/rithvikvibhu/nh-magisk-wifi-firmware