[CLOSED][BETA][2018.7.19] Magisk v16.7 (1671)

Status
Not open for further replies.
Search This thread
By:
Advanced…
AlkaDragos

AlkaDragos

Senior Member
Sep 20, 2011
590
591
[RO]
Hey guys, just passing by and wanted to post my feedback related to latest beta. Everything works as it should, SafetyNet passes, Netflix / SuperMario shows in Playstore again and can be installed :) root works just fine. So everything it's back on rails :p.
I flashed latest beta in recovery on top of latest stable version , v12.

So, thanks @topjohnwu for this awesome work you do everyday for us and keep it up. :highfive:

Cheers,
 

Attachments

  • Screenshot_20170616-215256.png
    Screenshot_20170616-215256.png
    190.9 KB · Views: 936
  • Screenshot_20170616-215245.png
    Screenshot_20170616-215245.png
    214.1 KB · Views: 927
L

lepicane1

Senior Member
Dec 9, 2016
204
58
Kapiljhajhria said:
I can confirm that none of the magisk works on mido. Developer rom.
But i still keep trying with every new developer ROM and also with every new magisk update.
If u people also like to keep trying and join in we could make a small group on telegram and continue testing different things.
My telegram id @kapilj
Click to expand...
Click to collapse

Maybe MIUI 9 changes it all, at least I can use the stable ROM and know I'm still on the 'latest' android version :D

Happy to help test things....well, I'm good at following instructions since I don't have a great understanding how android stuff works. PM me what logs to produce with every new version of Magisk 13 beta.

My biggest issue with 13 is that I can't hide the root with a third party app.... version 12 was fine.
 
A

azamet90

Senior Member
May 16, 2017
89
1
SacredDeviL666 said:
did you flash the uninstaller before flashing v13 beta? if not can you do so ?

reboot to recovery

a) flash magisk uninstaller http://tiny.cc/latestuninstaller

b) flash magisk v13.0(96f8efc) https://xdaforums.com/att...5&d=1497598287

reboot device

------
@DodoGTA 101 page with 1001 post :p
Click to expand...
Click to collapse

It worked with this method but now all the modules is gone should I re install the modules or r the modules only hidden?

Sent from my Samsung Galaxy S8+ using XDA Labs
 
jenslody

jenslody

Senior Member
Jun 13, 2017
1,426
3,218
Flashing latest beta (96f8efc) does not work on my J5.
Same error as some other already have posted (log attached).
I replaced update-binary and boot_patch.sh with my modified version from b3da28e (modified to use 32-bit paths, even if 64-bit is incorrectly detected) and flashing works flawlessly.
SafetyNet passes with osm0sis busybox and f-droid privileged extension as module if xposed is not active. Unfortunately this is not an option, because I need it for xprivacy.

After activating or deactivating modules, sometimes also after a clean flash of magisk, I have to reboot two or three times before root is working or the modules are shown (no log for this issue).
 

Attachments

  • 96f8efc.recovery.log
    27.1 KB · Views: 22
P

p34rp34r

Senior Member
Jan 4, 2013
122
75
I hate to be "that guy" that posts with no logs, but my phone is currently setting everything up again... My install problem is that same as several others before me - during installation, right after the install script looks for /data/magisk.img, it fails with the error:
Code: 
! Magisk image mount failed...
Updater process ended with ERROR: 1

It doesn't matter if the script finds or creates the img, it fails either way. This occurs even after completely flashing back to stock (system, boot, data, everything except recovery) and attempting to install either v12 or the latest v13. Seems like the mount_image command is not recognized, which is strange since I previously installed v12 just fine. Any suggestions?

Nexus 6
6.0.1 MOB31T
Kernel version: 3.10.40

EDIT: of course, after posting here and feeling guilty for no logs, I tried installing v13 a90e8b6 and it worked. There doesn't appear to be anything different in the script, so I have no idea why this worked.

EDIT 2: spoke too soon. a90e8b6 indeed appears to install, but after rebooting, nothing appears to have actually installed. No Magisk Manager or anything. Manually extracting the apk and installing it doesn't do anything, since the app FC's on launch. 96f8efc still won't install; always gives the failed mount error.

EDIT 3: log. same as several posters. loop device can't mount, says it's busy.

EDIT 4: Took the opportunity to jump to Android N, and 96f8efc now installs but it won't boot now. Stuck on boot animation...
 

Attachments

  • recovery.log
    24 KB · Views: 53
Last edited:
  • Like
Reactions: ath0m
A

atarek

Senior Member
Dec 15, 2014
252
179
Cairo
Samsung Galaxy Note 3
Google Pixel 6a
Issue with samsung note 3

Thanks for any support in advance .

I have samsung note 3 n9005
Rom: S7E Port 6.0.1 by NXTeam (darklord reborn).
Kernel: Phantom v.1.2k (6h0st).
Recovery: TWRP materialized V:2.8.7.0.

I was using magisk su v.12 and magisk manager v:3.4.4 before google update and every thing was working flawlessly.
I decided to try beta test so i followed these steps:

* Uninstalled magisk manager v:3.4
* Boot to recovery and run "Magisk-uninstaller-20170608.zip"
* Flash Magisk-v13.0(a90e8b6).zip
* Reboot but manager wasn't installed after boot up
* I installed manager manually from zip file but it didn't detect magisk installed
* Return manager 3.4 and v.12 then try to run "Magisk-v13.0(a90e8b6).zip" as a module installation and update manager but also no root detected.
* I booted to recovery flashed "Magisk-uninstaller-20170608.zip" then my Kernel then
* Run Magisk-v13.0(96f8efc).zip but i got attatched error and recovery log.
*********************************************************
* I returned to my stable state with version 12 and manager 3.4 and started testing again
* I flashed "Magisk-uninstaller-20170608" then flashed "a90e8b6" and rebooted
* I found old magisk manager so i uninstalled it and extracted manager in "96f8efc" and installed it. attatched screenshots and adb log.

Any advice. regarding these issues.

Also as my knowledge magisk v13 flashable should install magisk manager why this not happen with me.

i could support any kind of info or logcat required and i'm ready to test any scenario.
Screenshot_20170616-131522.jpg
View attachment a90e8b6_recovery.txt
View attachment ADB_magisksu_log.txt
View attachment 96f8efc_recovery.txt
 
godpowerrr

godpowerrr

Senior Member
Jun 9, 2016
371
280
Thanks for the support though i wish it was abroad. Im not going to go through every single post... that being said, even with boot.img successfully flashed and conquer root, it crumbles after flashfire installation. :( I hate Samsung sometimes. GL Bro with expanding features & compatibility... you don't know how bad our models wish we could have your creations.

Sprint [SM-G935P] QE1 - NEEDS RECOVERY
Sprint [SM-G935U] QD2 - NEEDS RECOVERY
:(

Great work again I was certain there was hope...the boot.img flashed in ODIN so I'd say you're on the right track for us locked bootloader holders.
 
NotATreoFan

NotATreoFan

Moderator Emeritus
Jul 12, 2006
18,431
9,084
The Interwebs
twitch.tv
Samsung Galaxy S21 Ultra
Device: LG V20
OS: 7.0
Patch Level: May 2017

I'm suddenly unable to flash Magisk during a clean install of my ROM. I use Aroma, and after placing boot.img in the correct location, I then call for the Magisk installer to run. This was not an issue when I clean flashed last week. I went from 11.6 in the prior ROM, to then using 13-170606 and the matching Magisk Manager. The boot injection was fine and all was well.

Now I'm working on a new update, which of course I'm testing, and 13.0(96f8efc) is failing with the error: Sony ELF32 format detected

I don't have a Sony device, and I'm using the same kernel that I was before. Restored my TWRP backup, and I can dirty flash 13.0(96f8efc) on top of the older 13 beta.

Any idea what may be going on? To be clear, I can flash Magisk now only if it's on top of an existing. If I flash my kernel back to stock, then Magisk fails to load again.
 
Last edited:
Captain_Throwback

Captain_Throwback

Recognized Developer
Aug 22, 2008
20,445
23,058
The Nothing
Asus Eee Pad Transformer Prime
HTC One (M8)
NotATreoFan said:
Device: LG V20
OS: 7.0
Patch Level: May 2017

I'm suddenly unable to flash Magisk during a clean install of my ROM. I use Aroma, and after placing boot.img in the correct location, I then call for the Magisk installer to run. This was not an issue when I clean flashed last week. I went from 11.6 in the prior ROM, to then using 13-170606 and the matching Magisk Manager. The boot injection was fine and all was well.

Now I'm working on a new update, which of course I'm testing, and 13.0(96f8efc) is failing with the error: Sony ELF32 format detected

I don't have a Sony device, and I'm using the same kernel that I was before. Restored my TWRP backup, and I can dirty flash 13.0(96f8efc) on top of the older 13 beta.

Any idea what may be going on? To be clear, I can flash Magisk now only if it's on top of an existing. If I flash my kernel back to stock, then Magisk fails to load again.
Click to expand...
Click to collapse
Sup, NATF.

Can you post your full recovery log and your boot.img so @topjohnwu can take a look at how magiskboot is handling it? Thanks!
 
Cypher_01

Cypher_01

Senior Member
Nov 18, 2012
280
186
Magisk Manager v5.* crashes

Magisk Manager v5.* crashes on some of my devices. :confused:
  • Crashing on Nexus 4 (Official CyanogenMod 13, Google Security Patch Level: December 2016)
  • Crashing on Nexus 9 (Official CyanogenMod 13, Google Security Patch Level: August 2016)
  • Working on OnePlus 3 (Unofficial CyanogenMod 13 by Sultanxda, Google Security Patch Level: April 2017)
Maybe it's because of different Google Security Patch Levels?

Here's a log from my Nexus 9:
Code: 
06-16 22:40:08.140   722      1645        ActivityManager  I  START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.topjohnwu.magisk/.SplashActivity bnds=[459,1789][665,1928] (has extras)} from uid 10090 on display 0
06-16 22:40:08.255   722      991         ActivityManager  I  Start proc 5845:com.topjohnwu.magisk/u0a171 for activity com.topjohnwu.magisk/.SplashActivity
06-16 22:40:08.307   1818     5244     PBSessionCacheImpl  I  Deleted sessionId[7997146201721475] from persistence.
06-16 22:40:08.334   722      731                     art  W  Suspending all threads took: 9.006ms
06-16 22:40:08.472   722      731                     art  I  Background sticky concurrent mark sweep GC freed 276088(14MB) AllocSpace objects, 10(208KB) LOS objects, 30% free, 30MB/44MB, paused 13.053ms total 290.457ms
06-16 22:40:08.559   5845     5845   FirebaseInitProvider  I  FirebaseApp initialization unsuccessful
06-16 22:40:08.947   179      5863                 Magisk  D  su: request from client: 8
06-16 22:40:08.947   179      5863                 Magisk  D  su: request from uid=[10171] (#1)
06-16 22:40:08.950   179      5863                 Magisk  D  su: wait_result waiting for 5864
06-16 22:40:08.950   5864     5864                 Magisk  D  su: child process started
06-16 22:40:08.951   5864     5864                 Magisk  D  su: use namespace of pid=[5862]
06-16 22:40:08.951   5864     5864                 Magisk  D  su: argc=[2]
06-16 22:40:08.951   5864     5864                 Magisk  D  su: argv[0]=[su]
06-16 22:40:08.952   5864     5864                 Magisk  D  su: argv[1]=[-v]
06-16 22:40:08.952   5864     5864                 Magisk  D  su: cwd=[/]
06-16 22:40:08.952   5864     5864                 Magisk  D  su: pts_slave=[]
06-16 22:40:08.969   179      5863                 Magisk  D  su: return code to client: 0
06-16 22:40:09.023   179      5867                 Magisk  D  su: request from client: 13
06-16 22:40:09.023   179      5867                 Magisk  D  su: request from uid=[10171] (#1)
06-16 22:40:09.024   179      5867                 Magisk  D  su: wait_result waiting for 5868
06-16 22:40:09.024   5868     5868                 Magisk  D  su: child process started
06-16 22:40:09.024   5868     5868                 Magisk  D  su: use namespace of pid=[5865]
06-16 22:40:09.024   5868     5868                 Magisk  D  su: argc=[1]
06-16 22:40:09.024   5868     5868                 Magisk  D  su: argv[0]=[su]
06-16 22:40:09.024   5868     5868                 Magisk  D  su: cwd=[/]
06-16 22:40:09.024   5868     5868                 Magisk  D  su: pts_slave=[]
06-16 22:40:09.682   722      1458        ActivityManager  I  START u0 {cmp=com.topjohnwu.magisk/.MainActivity} from uid 10171 on display 0
06-16 22:40:09.690   5845     5888                 Parcel  E  Reading a NULL string not supported here.
06-16 22:40:09.698   5845     5888                 Parcel  E  Reading a NULL string not supported here.
06-16 22:40:10.303   722      5711   NetlinkSocketObser..  D  NeighborEvent{elapsedMs=1131623, fd18:e04c:1a02::1, [0024A5BD62B6], RTM_NEWNEIGH, NUD_PROBE}
06-16 22:40:10.304   722      792         ActivityManager  I  Killing 3931:tw.fatminmin.xposed.minminguard/u0a153 (adj 15): empty #17
06-16 22:40:10.368   5845     5887                    art  W  Long monitor contention event with owner method=void java.lang.Object.wait!(long, int) from Object.java:4294967294 waiters=0 for 657ms
06-16 22:40:10.442   5845     5948         OpenGLRenderer  D  Use EGL_SWAP_BEHAVIOR_PRESERVED: true
06-16 22:40:10.483   5845     5887                 System  W  ClassLoader referenced unknown path: /system/framework/tcmclient.jar
06-16 22:40:10.576   5845     5948         OpenGLRenderer  I  Initialized EGL, version 1.4
06-16 22:40:10.828   5845     5855                    art  I  Background sticky concurrent mark sweep GC freed 117939(9MB) AllocSpace objects, 12(240KB) LOS objects, 48% free, 11MB/21MB, paused 4.875ms total 171.270ms
06-16 22:40:11.127   722      808         ActivityManager  I  Displayed com.topjohnwu.magisk/.MainActivity: +1s322ms (total +2s909ms)
06-16 22:40:11.166   5845     5845          Choreographer  I  Skipped 31 frames!  The application may be doing too much work on its main thread.
06-16 22:40:13.385   5845     5888                   libc  F  invalid address or address of corrupt block 0x1b passed to dlfree
06-16 22:40:13.386   5845     5888                   libc  F  Fatal signal 11 (SIGSEGV), code 1, fault addr 0xfffffffd in tid 5888 (AsyncTask #3)
06-16 22:40:13.387   247      247                   DEBUG  I  property debug.db.uid not set; NOT waiting for gdb.
06-16 22:40:13.387   247      247                   DEBUG  I  HINT: adb shell setprop debug.db.uid 100000
06-16 22:40:13.387   247      247                   DEBUG  I  HINT: adb forward tcp:5039 tcp:5039
06-16 22:40:13.492   247      247                   DEBUG  F  *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-16 22:40:13.494   247      247                   DEBUG  F  CM Version: '13.0-20160820-SNAPSHOT-ZNH5YAO0J1-flounder_lte'
06-16 22:40:13.494   247      247                   DEBUG  F  Build fingerprint: 'google/volantisg/flounder_lte:6.0.1/MOB30W/3031100:user/release-keys'
06-16 22:40:13.494   247      247                   DEBUG  F  Revision: '0'
06-16 22:40:13.497   247      247                   DEBUG  F  ABI: 'arm'
06-16 22:40:13.499   247      247                   DEBUG  F  pid: 5845, tid: 5888, name: AsyncTask #3  >>> com.topjohnwu.magisk <<<
06-16 22:40:13.500   247      247                   DEBUG  F  signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffd
06-16 22:40:13.531   247      247                   DEBUG  F  Abort message: 'invalid address or address of corrupt block 0x1b passed to dlfree'
06-16 22:40:13.532   247      247                   DEBUG  F  r0 00000000  r1 00000000  r2 00000000  r3 00000000
06-16 22:40:13.532   247      247                   DEBUG  F  r4 fffffff9  r5 c0000000  r6 f70d1eb8  r7 ab099000
06-16 22:40:13.533   247      247                   DEBUG  F  r8 00000001  r9 dcfbdfcc  sl f7032853  fp f703285c
06-16 22:40:13.533   247      247                   DEBUG  F  ip 00000000  sp dcfbdeb8  lr 00000000  pc f709d30c  cpsr 200f0030
06-16 22:40:13.543   247      247                   DEBUG  F  backtrace:
06-16 22:40:13.543   247      247                   DEBUG  F  #00 pc 0003030c  /system/lib/libc.so (dlfree+59)
06-16 22:40:13.543   247      247                   DEBUG  F  #01 pc 00015769  /system/lib/libandroidfw.so (_ZN7android13ResStringPool6uninitEv+38)
06-16 22:40:13.543   247      247                   DEBUG  F  #02 pc 000164b9  /system/lib/libandroidfw.so (_ZN7android10ResXMLTree6uninitEv+14)
06-16 22:40:13.544   247      247                   DEBUG  F  #03 pc 000164d7  /system/lib/libandroidfw.so (_ZN7android10ResXMLTreeD1Ev+4)
06-16 22:40:13.544   247      247                   DEBUG  F  #04 pc 00013223  /system/lib/libandroidfw.so (_ZN7android12AssetManager10getPkgNameEPKc+258)
06-16 22:40:13.544   247      247                   DEBUG  F  #05 pc 0001327f  /system/lib/libandroidfw.so (_ZN7android12AssetManager18getBasePackageNameEj+62)
06-16 22:40:13.544   247      247                   DEBUG  F  #06 pc 000872d7  /system/lib/libandroid_runtime.so
06-16 22:40:13.544   247      247                   DEBUG  F  #07 pc 72a686e1  /data/dalvik-cache/arm/system@framework@boot.oat (offset 0x1f84000)
06-16 22:40:13.751   247      247                   DEBUG  F  Tombstone written to: /data/tombstones/tombstone_02
06-16 22:40:13.751   247      247                   DEBUG  E  AM write failed: Broken pipe
06-16 22:40:13.752   722      806            BootReceiver  I  Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE)
06-16 22:40:13.760   722      5967        ActivityManager  W  Force finishing activity com.topjohnwu.magisk/.MainActivity
06-16 22:40:13.765   722      806    DropBoxManagerServ..  W  Dropping: SYSTEM_TOMBSTONE (10 > 0 bytes)
06-16 22:40:13.777   722      5968   DropBoxManagerServ..  W  Dropping: data_app_native_crash (1586 > 0 bytes)
06-16 22:40:13.780   722      1460          GraphicsStats  D  Buffer count: 6
06-16 22:40:13.781   722      889         InputDispatcher  W  channel '6d6e6f0 com.topjohnwu.magisk/com.topjohnwu.magisk.MainActivity (server)' ~ Consumer closed input channel or an error occurred.  events=0x9
06-16 22:40:13.781   722      889         InputDispatcher  E  channel '6d6e6f0 com.topjohnwu.magisk/com.topjohnwu.magisk.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
06-16 22:40:13.796   179      5867                 Magisk  D  su: return code to client: 0
06-16 22:40:13.801   255      255                  Zygote  I  Process 5845 exited due to signal (11)
06-16 22:40:13.824   722      1460            WindowState  I  WIN DEATH: Window{6d6e6f0 u0 com.topjohnwu.magisk/com.topjohnwu.magisk.MainActivity}
06-16 22:40:13.827   722      1460        InputDispatcher  W  Attempted to unregister already unregistered input channel '6d6e6f0 com.topjohnwu.magisk/com.topjohnwu.magisk.MainActivity (server)'
06-16 22:40:13.836   722      5967        ActivityManager  W  Exception thrown during pause
06-16 22:40:13.836   722      5967        ActivityManager  W  android.os.DeadObjectException
06-16 22:40:13.836   722      5967        ActivityManager  W  at android.os.BinderProxy.transactNative(Native Method)
06-16 22:40:13.836   722      5967        ActivityManager  W  at android.os.BinderProxy.transact(Binder.java:503)
06-16 22:40:13.836   722      5967        ActivityManager  W  at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
06-16 22:40:13.836   722      5967        ActivityManager  W  at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:334)
06-16 22:40:13.836   722      5967        ActivityManager  W  at android.os.BinderProxy.transact(<Xposed>)
06-16 22:40:13.836   722      5967        ActivityManager  W  at android.app.ApplicationThreadProxy.schedulePauseActivity(ApplicationThreadNative.java:727)
06-16 22:40:13.836   722      5967        ActivityManager  W  at com.android.server.am.ActivityStack.startPausingLocked(ActivityStack.java:879)
06-16 22:40:13.836   722      5967        ActivityManager  W  at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:2992)
06-16 22:40:13.836   722      5967        ActivityManager  W  at com.android.server.am.ActivityStack.finishTopRunningActivityLocked(ActivityStack.java:2848)
06-16 22:40:13.836   722      5967        ActivityManager  W  at com.android.server.am.ActivityStackSupervisor.finishTopRunningActivityLocked(ActivityStackSupervisor.java:2828)
06-16 22:40:13.836   722      5967        ActivityManager  W  at com.android.server.am.ActivityManagerService.handleAppCrashLocked(ActivityManagerService.java:12429)
06-16 22:40:13.836   722      5967        ActivityManager  W  at com.android.server.am.ActivityManagerService.makeAppCrashingLocked(ActivityManagerService.java:12300)
06-16 22:40:13.836   722      5967        ActivityManager  W  at com.android.server.am.ActivityManagerService.crashApplication(ActivityManagerService.java:13016)
06-16 22:40:13.836   722      5967        ActivityManager  W  at com.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:12521)
06-16 22:40:13.836   722      5967        ActivityManager  W  at com.android.server.am.NativeCrashListener$NativeCrashReporter.run(NativeCrashListener.java:86)
06-16 22:40:13.838   240      240         lowmemorykiller  E  Error opening /proc/5845/oom_score_adj; errno=2
06-16 22:40:13.849   722      1321        ActivityManager  I  Process com.topjohnwu.magisk (pid 5845) has died
06-16 22:40:13.898   722      1475         OpenGLRenderer  I  Initialized EGL, version 1.4
06-16 22:40:14.040   1666     3204   UdcContextManagerH..  W  Empty context buffer. Thus might mean that the context is not synced down.
06-16 22:40:14.040   1666     3204   GetDeviceDataUploa..  W  Empty context model while retrieving upload opt-in status!
06-16 22:40:14.067   722      731                     art  I  Background partial concurrent mark sweep GC freed 104178(7MB) AllocSpace objects, 21(2MB) LOS objects, 33% free, 29MB/44MB, paused 2.874ms total 247.519ms
06-16 22:40:14.139   1666     3204   UdcContextManagerH..  W  Empty context buffer. Thus might mean that the context is not synced down.
06-16 22:40:14.139   1666     3204   GetDeviceDataUploa..  W  Empty context model while retrieving upload opt-in status!
Sorry, the log is not filtered, I didn't get that working (shame on me).

Magisk v13 Beta however works. MagiskSU works and the module Xposed systemless also loads and works. But I can't manage anything. :(

Any ideas?
 
Status
Not open for further replies.

Similar threads

T
  • Sticky
Magisk General Support / Discussion
Replies
58K
Views
6M
W
wei34
T
  • Locked
  • Sticky
Magisk - The Magic Mask for Android
Replies
56
Views
6M
T
topjohnwu
Deic
[Magisk v14.0] Universal SafetyNet Fix | Universal Hide [v2 Beta 5]
Replies
2K
Views
886K
N
Noweir
T
  • Locked
[CLOSED][DEV] Magisk Canary Channel - Bleeding Edge Builds
Replies
3K
Views
737K
FerryAr
FerryAr
yochananmarqos
Collection of Magisk Modules v2
Replies
1K
Views
1M
あなたの
あなたの

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 1777
    T
    topjohnwu
    Hello, 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
    Donation
    I spent endless hours to create Magisk. If you like my work, feel free to donate.
    https://www.paypal.me/topjohnwu​
    View
    428
    T
    topjohnwu
    New 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.
    View
    294
    T
    topjohnwu
    reserved
    View
    229
    T
    topjohnwu
    2017.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.
    View
    227
    T
    topjohnwu
    Beta releases are no longer "development oriented", this thread will be closed and replaced with a more "experimental channel" thread.
    Thank you to all reported useful logs and info, and I highly appreciate all moderators involved in moderating this thread extensively.
    View

New posts