[CLOSED][BETA][2018.7.19] Magisk v16.7 (1671)
- Thread starter topjohnwu
- Start date
- Status
I tried to flash the different versions of beta through recovery and every time it said it was an invalid zip. So I extracted the magisk manger 5.1 from the zip installed the APK and installed the zip through the magisk manger and it worked. Passing safety net and didn't have to reinstall my mods!!!
In Magisk Manager settings enable Magisk hide
Sent from my Sony Xperia XZ using XDA Labs
At the same place it was before. If it's not there, I don't know, try another installation.
JonathanRAZ
Senior Member
Version 5.x does not have magisk hide option it brings magisk hide implemented if you are using version 4.3.3 you will have the option
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs
I tried to install in full wipe, i mean with uninstall Magisk v12 before with uninstaller but i have this error
************************
* Magisk v13.0(0b4baad) Installer
************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- Creating /data/magisk.img
CANNOT LINK EXECUTABLE "/dev/tmp/magisk/arm64/magisk": cannot locate symbol "__fread_chk" referenced by "/system/lib64/libicuuc.so"...
Aborted
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
! Magisk image mount failed...
run_program: child exited with status 1
script result was [/data]
Installer Sucessfull (Status 0)
End at : Thu Jun 8 21:21:39 2017
If i install on top without uninstall Magisk v12 before, it flash but Magisk is not Installed at all
See here
https://xdaforums.com/showthread.php?p=72598121
Try installing the manger APK like you would any other APK and install the zip as a module it worked for me. When I tried through recovery it said invalid zip for every version every time.
Sent from my LG-K550
Last edited:
Working flawlessly over magisk 12,just flashed over it without uninstalling the manager v4. xx
Running oos open beta 8 with franco kernel on the oneplus 3t, to pass the safety net, had the setup in the screenshot
Running oos open beta 8 with franco kernel on the oneplus 3t, to pass the safety net, had the setup in the screenshot
Attachments
Last edited:
Confirm working on MM MIUI 8.3 GlobeROM, but sometimes Magisk Manager is FC
Redmi Note 4 MTK
https://drive.google.com/file/d/0B6ehuMWVh07LRUZabEFDU1ZJcG8/view?usp=drivesdk
Redmi Note 4 MTK
https://drive.google.com/file/d/0B6ehuMWVh07LRUZabEFDU1ZJcG8/view?usp=drivesdk
Last edited:
Yeah, thanks. I've been facing this since the first snapshots came with the apk builtin too, and still happening with the betas.
Ja_som
Senior Member
- Apr 1, 2013
- 3,720
- 2,045
Not now, but maybe tomorrow I will try it...
Sent from my Nexus 7 (2013) using XDA Labs
Hi Eddy,
Just in case, did you try dirty flash rom + magisk?
I was on magisk v12, I dirty flash rom +magisk v13+kernel blu_spark and voila :
Sent from my OnePlus3 using XDA Labs
Attachments
hi, i want to pass the safety net but there are options in your screenshot, not on mine.. ?
I'm disoriented, I can't install any Magisk module, I get "Installation error" in a toast, and nothing more. Nothing about the error is recorded on the logs.
Tried flashing the modules trough TWRP and Flashfire. No errors there, but after booting up installed modules list is empty.
I'm using a Moto G5 with stock ROM. Android 7.0. Any suggestion?
Tried flashing the modules trough TWRP and Flashfire. No errors there, but after booting up installed modules list is empty.
I'm using a Moto G5 with stock ROM. Android 7.0. Any suggestion?
Wait for topjohnwu update the templates and docs in some days. Maybe that's the cause. I've had some modules here (specially related to music mods like viper or am3d) and it says they were installed on twrp but they do not show on drawer (using v13 obviously).
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1777Hello, welcome to the beta Magisk thread! First check the main thread before starting.
I expect users reporting to at least have basic debug skills, this thread is heavily moderated so refrain from spamming with "useless" reports!
Latest Magisk Beta: v16.7 (code: 1671)
Bundled Magisk Manager: v5.8.3
Release Note | Changelogs | Download
If you need a clean start, use the uninstaller in the main thread to uninstall any verison of Magisk installation
Symptoms and Diagnose Procedure:
- Installing Magisk fails:
If you're flashing in TWRP: Upload the recovery logs (pull the file /tmp/recovery.log, or select "Advanced > Copy Log" and upload)
If you're installing in MagiskManager: Choose to save logs after installation and upload - I want to report a Magisk bug:
Magisk logs are placed in /cache/magisk.log
If you face any issue, please upload /cache/magisk.log
Starting from v16.6, /data/adb/magisk_debug.log is NOT USED anymore! - Magisk Manager is crashing:
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:
If it worked in previous versions, please at least upload /cache/magisk.log
Please do NOT SPAM the forum with these kind of issues! It is NOT a priority to fix
I spent endless hours to create Magisk. If you like my work, feel free to donate.
https://www.paypal.me/topjohnwu428New Stable Release Coming In a Few Hours!
Thanks for everyone involved in testing the brand new Magisk and provide useful information for me to fix the bugs
And here I give the moderators a sincere respect, please accept my highest appreciation!
Everyone on the Internet has a real life, not only me but also the moderators. It's very heartwarming to see them willing to sacrifice their time just to give me a better time on the forums.
I cannot be more grateful, so thanks to all of you again :good:
Thread will be temporarily closed until a next beta is available, all future releases (except quick hotfixes) should go through a beta stage before directly going to the masses.2292017.8.13 Magisk v13.5 (1350)(beta)
Here comes another public beta!
As most of you should know, Magisk is a fairly young project, and only recently does it undergo a complete rewrite on v13, so I place stability and compatibility first before I kept adding more features into it. This release comes with several major under-the-hood changes, both in native Magisk and Magisk Manager sides.
Busybox Fights Back Strong
Previously I had completely removed busybox from Magisk for causing too many troubles, and also the difficulty to build it myself. But after dealing with so many compatibility issues, and the need of reliable and feature packed command-line tools pushed me to add this gem back. I spent quite a lot of time integrating busybox sources into Magisk's building system, and believe me this isn't an easy task: busybox's config is based on Linux kernel, which itself is a complex topic. I created a tool (ndk-busybox-kitchen) to automatically handle the generation of config-based headers, and parse those files into Android.mk to support building with ndk-build command. To be honest this is super dope IMO, and I'm really proud of it lol.
The next effort is to maximize compatibility for the Magisk installation process. I decided instead of adding busybox directly into the flashable zip, I would directly embed busybox into update-binary, which is now a specially crafted shell script to dump the correct binary for the CPU architecture, and then execute the installation process completely on the busybox's shell and command-line tools. The extracted busybox will also be utilized in many other places such as boot scripts (yes, the boot scripts will now run in a complete busybox environment) and Magisk Manager. The busybox binary will be installed only for internal use, if you want to install busybox to your device, @osm0sis already uploaded a Magisk Module on the repo, please install that instead.
Finalizing Magisk Procedures
Magisk hijacks specific points in the boot process, and will go through its own procedures to fulfill all the features. The order of these procedures are now be finalized, which means it is very less likely to change in the future. For post-fs-data mode, general scripts (scripts under post-fs-data.d) and modules scripts (post-fs-data.sh in each module) are executed before magic mount happens. This means experienced developers can now customize magic mount's behavior to a certain degree. However, I still suggest that most scripts should be run in service mode unless necessary such as time critical commands. Service mode will guarantee SELinux patches are finished, and setting props with proper init triggers will not block the device's boot or lead to a crash.
Samsung Stock Kernel Workarounds
Well, apparently Samsung is always here to break everything. On stock kernels, it places a restriction on how binaries can behave if they are executed from /data. An additional magisk binary mirror is created to overcome this issue, and will be used extensively in Magisk Manager (it will not effect recovery). Unfortunately, even though I had offloaded most of the functionality into a shell script function collection that can be upgraded through Magisk updates, the template itself still has to be slightly updated to reflect the changes. Magisk Module Template v5 is already live on another branch. However, before you go and upgrade all your modules to v5, please think twice and consider it as a Developer Preview. It depends on the updated util_functions.sh in this beta, so if you upgrade them into the Online Repo, your module won't install on users running the latest stable Magisk version (v13.3). It will be the default template version once the next stable release is live.
A Small Mistake
There was a small mistake in v13.3, which the SHA1 of the stock image cannot be acquired, and also the SHA1 backed up within ramdisk is also not extracted. This leads to stock boot image restoration (happens when uninstalling) fails, and will only revert your device by ramdisk backups. This mean you will be able remove Magisk, but the boot image will not be 100% reverted. If you are concern about the backups, restore your boot image back to stock, and reflash this current build to re-create the Magisk's stock boot image backup. - Installing Magisk fails:
New posts
-
-
How To Guide [GUIDE][HOWTO] Use banking apps on your rooted device- Latest: cliffhanger54
-
Question Android Chrome: Cannot Click Saved Password Button- Latest: AntarticShaurant
