Running OK here.I lost hide manager and download section on canary build, anyone has same problem?
I lost hide manager and download section on canary build, anyone has same problem?
I'm on the latest canary build and my Banking app "UBS Access" detects root after his latest update. I want to flash the canary debug build and help to optimize it, I think it's a new detection method. Do I need to post magisk.log and logcat? Or which information do you need?
I did all like in the official best practices for magiskhide, safetynet passes und device is certified
Yes, sadly because too much people only report stuff without wanting to help the dev and most of the time it's their fault. I hope that he fixes it at any time. I think I need to reanimate my old phone with stock rom and without root for the e-bankingMy guess is that this will fall in the category by topjohn of:
...
See here:
https://github.com/topjohnwu/Magisk/issues/1152
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
Of course, people use Magisk on Q for quite some time.Hello everybody.....belated Happy Christmas and Early new year to all.
I am searching all, reading all thru magisk developers notes. It looks till now it is still working in twrp/recovery mode on Q.
Anybody using magisk on Android 10? Need it working on my RN8 AOSIP 10
Thanks
Hello everybody.....belated Happy Christmas and Early new year to all.
I am searching all, reading all thru magisk developers notes. It looks till now it is still working in twrp/recovery mode on Q.
Anybody using magisk on Android 10? Need it working on my RN8 AOSIP 10
Thanks
- Copy the boot/recovery image to your device
- Download and install the latest Magisk Manager
- If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
- Press Install → Install → Select and Patch a File, and select your stock boot/recovery image file
- Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
- Copy the patched image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
- adb pull /sdcard/Download/magisk_patched.img
- Flash the patched boot/recovery image to your device and reboot. For most devices, here is the fastboot command:
- fastboot flash boot /path/to/magisk_patched.img or
- fastboot flash recovery /path/to/magisk_patched.img if you are patching a recovery image
Hello. My device is using system-as-root without A/B partitions. I want to install Magisk.
I found this guide but It's not clear to me if I must do that with both recovery.img and boot.img or just one of them? Thanks
I'm other words: use the recovery image.If your device is NOT A/B, but IS using system-as-root, then you will have to install Magisk to the recovery partition of your device. Follow the instructions in Boot Image Patching, but instead of using your boot image, use your recovery image. Read through the Magisk in Recovery section!
edzamber;81366479 [user=4470081 said:@topjohnwu[/user]
Hi bro
First Happy New year 2020 [emoji4]
Seems something goes wrong with last magisk manager : after hide it, it appears out of date...
@topjohnwu
Hi bro
First Happy New year 2020 [emoji4]
Seems something goes wrong with last magisk manager : after hide it, it appears out of date...
It's the stub apk version that's not updating (for whatever reason). It's been brought to @topjohnwu's attention already, so he'll likely have it fixed soon.
Fixed by installing the most recent manager app from the download link in the release there's, then uninstalling the old app and rebooting .
Not elegant, but it will work for now. Sure to be fixed properly in the next release
Please clarify your instructions here as that didn't work for me unless you mean a manager not hidden?
I downloaded the latest app-debug.apk.
https://github.com/topjohnwu/magisk_files/tree/canary
Thanks
Which exact issue with Play Protect?anyone with the same issue with the latest update in canary?
it has an issue with play Protect...
i cant post picture here..Which exact issue with Play protect?
Btw, it was recommended earlier (a month or so ago, at the time of Magisk 20.1 and corresponding Canary builds)), to temporarily disable Play Protect while updating Magisk
Update:
Solution: Restore magisk manager, do not hide or rename magisk manager
Sent from my Redmi K20 Pro Premium Edition using Tapatalk