[ROOT]MAGISK-The Universal Systemless Interface

[nigol]

Vorrei rootare il mio Honor 9 STF-L09 8.0.0.362 (C432) originale senza SuperSU.
Se ho capito bene, prima di usare Magisk, dovrei sbloccare il bootloader, (codice di sblocco ottenuto il 10.11.2017, mai usato!), installare il
TWRP (quale? grazie!) e installare la versione di Magisk Manager: v5.6.4 da TWRP.
È corretto?
Grazie per l'aiuto

nigol

[paolocorpo]

Vorrei rootare il mio Honor 9 STF-L09 8.0.0.362 (C432) originale senza SuperSU.
Se ho capito bene, prima di usare Magisk, dovrei sbloccare il bootloader, (codice di sblocco ottenuto il 10.11.2017, mai usato!), installare il
TWRP (quale? grazie!) e installare la versione di Magisk Manager: v5.6.4 da TWRP.
È corretto?
Grazie per l'aiuto

nigol

Ciao
Prima ancora di MAgisk per lo sblocco e la recovery TWRP dai una lettura
QUI

[morfances]

Magisk 16.4 is out!
Changelog here
https://forum.xda-developers.com/sho...php?p=76371726

Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk

[paolocorpo]

Grazie 1000
Questa app è davvero fantastica
La uso su uno XIAOMi Mi6 e su un Nexus 5X senza alcun problema
Fantastici anche i suoi moduli
C'è una lista dei moduli disponibili ?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk

[complicazio]

Grazie 1000
Questa app è davvero fantastica
La uso su uno XIAOMi Mi6 e su un Nexus 5X senza alcun problema
Fantastici anche i suoi moduli
C'è una lista dei moduli disponibili ?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk

https://github.com/Magisk-Modules-Repo?page=1

[paolocorpo]

Grazie 1000 !!

https://github.com/Magisk-Modules-Repo?page=1

Inviato dal mio Galaxy Nexus utilizzando Tapatalk

[morfances]

Magisk 16.6 is out!
Changelogs
Changelog
Magisk
* v16.6
- [General] Add wrapper script to overcome weird LD_XXX flags set in apps
- [General] Prevent bootloop when flashing Magisk after full wipe on FBE devices
- [Scripts] Support patching DTB placed in extra sections in boot images (Samsung S9/S9+)
- [Scripts] Add support for addon.d-v2 (untested)
- [Scripts] Fix custom recovery console output in addon.d
- [Scripts] Fallback to parsing sysfs for detecting block devices
- [Daemon] Check whether a valid Magisk Manager is installed on boot, if not, install stub APK embedded in magiskinit
- [Daemon] Check whether Magisk Manager is repackaged (hidden), and prevent malware from hijacking com.topjohnwu.magisk
- [Daemon] Introduce new daemon: magisklogd, a dedicated daemon to handle all logcat related monitoring
- [Daemon] Replace old invincible mode with handshake between magiskd and magisklogd, one will respwan the other if disconnected
- [Daemon] Support GSI adbd bind mounting
- [MagiskInit] Support detecting block names in upper case (Samsung)
- [MagiskBoot] Check DTB headers to prevent false detections within kernel binary
- [MagiskHide] Compare mount namespace with PPID to make sure the namespace is actually separated, fix root loss
- [MagiskSU] Simplify su_info caching system, should use less resources and computing power
- [MagiskSU] Reduce the amount of broadcasting to Magisk Manager
- [ImgTool] Separate all ext4 image related operations to a new applet called "imgtool"
- [ImgTool] Use precise free space calculation methods
- [ImgTool] Use our own set of loop devices hidden along side with sbin tmpfs overlay. This not only eliminates another possible detection method, but also fixes apps that mount OBB files as loop devices (huge thanks to dev of Pzizz for reporting this issue)



Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk

[morfances]

Magisk 17.0 is out!!
Changelog

*Release Cycles*
Starting from v17.0, the stable channel and the beta channel are considered as "public releases", meaning both will be well tested before release and should be good for most normal users as daily driver. In general (meaning no catastrophic bugs), each major version bump (e.g. v17 -> v18) will be on the stable channel, and each minor version bump (e.g. v17.0 -> v17.1) will be on the beta channel. For version codes, the first 3 digits represent the version of a public release (e.g. 17500 will be v17.5), the last 2 digits are for internal iterations (e.g. 17521 will be v17.6 WIP, iteration 21). There will be a separate "Experimental Channel" in the cutting edge, but this is out of scope for this post.

*New Module Template: 17000*
Due to some oddities to FBE, the path Magisk used to store persist files (/data/adb) cannot be created/accessed in custom recoveries if the folder/data decryption does not exist. Magisk has to install files to an alternative path, and the new template is updated for this change, which at the same time prevents corrupting data on FBE when installing in custom recoveries.

*Install to Inactive Slot is Back!*
Due to some changes in the Pixel OTA engines, the feature to install Magisk to inactive slots after OTA was broken for quite a while. This update added the ability for Magisk to force a slot swap using bootctl, so this super fascinating feature (that I personally do use a lot) is now back!

*SafetyNet Check is Back!*
People are panicking about the "Invalid Response" of SN checks in Magisk Manager. It is actually just a cosmetic issue as Google banned the old API (which Magisk Manager and tons of SN apps in Play Store was still using).
I'm well aware of several games in the wild was recently updated to detect Magisk yet again, I'll focus on that after this stable release, no worries!

*Highlights*
For those that were on the stable channel, here is a highlight of what has changed from v16.0 to v17.0
* Android Pie (9.0) support
* Support targeting sub services when selecting an app to hide with MagiskHide, meaning background services of hidden apps would not be able to detect root
* Fix root loss issue when MagiskHide is enabled
* Support Samsung S9/S9+/Note 9
* And of course, tons of bug fixes and improvements you're not aware of ��

[paolocorpo]

Ciao,
Xiaomi Mi A1 stock 8.1.0 patch di agosto
Magisk aggiornato secondo il filone ultra beta del Developer ianmacd
Sto avendo dei rari soft reboot
Solo io ?

Inviato dal mio Mi A1 utilizzando Tapatalk

[paolocorpo]

Nessuno ha come me questi soft reboot ?
Ho aggiornato alla versione del 02 settembre ma proprio ora ho avuto (unico in giornata) un soft reboot

Inviato dal mio Mi A1 utilizzando Tapatalk