Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Magisk22 problem on android to go #3970

Closed
hw-schrauber opened this issue Mar 2, 2021 · 6 comments
Closed

Magisk22 problem on android to go #3970

hw-schrauber opened this issue Mar 2, 2021 · 6 comments

Comments

@hw-schrauber
Copy link

hw-schrauber commented Mar 2, 2021

Hi, on my Lenovo M7 (Android to GO 9.0) I've installed MAGISK 21.4 with 8.0.7.apk to the recovery. Anything worked fine. After I made a direct update to the recovery the App 22000 and also the app 8.0.7 show, that MAGISK isn't installed. Also after a restart. A suprise is, that anny app that get root before the update have still root rights. New Apps aren't able to get root rights. The new MAGISK.app also don't show the actual MAGISK version and the menu for moduls etc.. The 8.0.7 will do.

Please fix it.

@pndwal
Copy link
Contributor

pndwal commented Mar 2, 2021

Did you have hidden Manager/app w/8.07? Did you restore to unhidden before updating? (Need clearly stated in release Notes.)

@hw-schrauber
Copy link
Author

No, the App wasn't hidden. I have to devices and on both the same issue.

@pndwal
Copy link
Contributor

pndwal commented Mar 3, 2021

Ok seems Magisk is in recovery. (Ramdisk in boot = no).

Did you install new 22.0 App using Update in old manager, then direct install 22.0 Magisk root update? Or did you download and install new APK?

Do you somehow have two apps? Most likely if you uninstall both old Manager app and new Magisk app, then reinstall 22.0 app all will be fine... You should never have more than one manager app installed.

@hw-schrauber
Copy link
Author

hw-schrauber commented Mar 3, 2021

Direct means direct. When MAGISK is installed, after an apk update the manager app provided a MAGISK update. When I then start the update I have two options. Update an image or "direct" update. Maybe direct means that the partition is direct updated. This is, was I have done.
Now to the config. The MAGISK (21.4) is installed to the recovery. The manager app is 8.0.7. Anything fine. After I update the manager apk I get the Info that there is an update for the partition is also available. I make the update and after the Update the manager app shows, that MAGISK isn't installed. But this is not right. Apps they have root before the update have root also after the update. New apps are not able to get root.

After this I have deinstall the manager (22000) apk. I install the manager apk 8.0.7. With this apk I have the same issue with the rootrights. Also there is a difference in the display. The 8.0.7 manager shows the actual MAGISK version. The newer manager(22000) don't give this Info.

Update: I've tried to make a clean installation. Android factory default, MAGISK-manager apk 22 installed, recovery image patched and installed with fastboot. With the patched recovery with MAGISK21.4 works like known but the same way with a recovery patched image with MAGISK22 is not bootable. Starts ever with a clean brand new System. Back to recovery with MAGISK21.4 works fine again.

IMG_20210303_090527
IMG_20210303_090721
IMG_20210303_090642

@pndwal
Copy link
Contributor

pndwal commented Mar 3, 2021

Sure, I understood you used direct install for Magisk in recovery boot image; I was concerned about Manager/App Installation as symptoms suggest there may be two, causing conflicts. However, it does seem you may have other issues.

To be of any real use to troubleshoot however, you do need to follow John's issue Template.

You should reproduce the issue using Canary build,
upload appropriate logs (install logs, magisk.log, a boot logcat, etc). Also, the recovery.img you used when patching failed to boot and dmesg (kernel logs) as well as result of cat /proc/mounts when recovered device WITHOUT root.

See below:

**## READ BEFORE OPENING ISSUES

All bug reports require you to USE CANARY BUILDS. Please include the version name and version code in the bug report.

If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default. In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.

If you experience issues during installation, in recovery, upload the recovery logs, or in Magisk Manager, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.

If you experience a crash of Magisk Manager, dump the full logcat when the crash happens. DO NOT upload magisk.log.

If you experience other issues related to Magisk, upload magisk.log, and preferably also include a boot logcat (start dumping logcat when the device boots up)

DO NOT open issues regarding root detection.

DO NOT ask for instructions.

DO NOT report issues if you have any modules installed.

Without following the rules above, your issue will be closed without explanation.**

@hw-schrauber
Copy link
Author

Thanks. For the moment I have three images. The original recovery. The working recovery with MAGISK 21.4 and the non working recovery with MAGISK22.
Hmm, is not working. zip is too big. For the logs I need some time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants