FORUMS
Remove All Ads from XDA

Magisk General Support / Discussion

1,839 posts
Thanks Meter: 57,372
 
By topjohnwu, Recognized Developer / Recognized Contributor on 4th August 2016, 02:20 AM
Post Reply Email Thread
Announcement from topjohnwu: Info regarding the next release
22nd March 2019, 01:41 PM |#32121  
R3van's Avatar
Member
Thanks Meter: 5
 
More
Hello,

i`m on Stock Samsung ROM and rooted with Magisk.
Today i`ve got a message from Magisk Manager that an update is available.
Magisk Manager showed me that there were no root installed.

I started TWRP, flashed latest Magisk (18.1) and rebooted. since then i`m Stuck at the flashing Samsung Logo.

I`v hidden the Magisk Manager app within itself with a random package name.
Now i would like to uninstall the Manager app via TWRP to see if that helps. I`ve found a package with a name that looks like randomly arranged letters, can i assume that this is Magisk Manager?
 
 
22nd March 2019, 03:10 PM |#32122  
Senior Member
Flag Indianapolis, IN
Thanks Meter: 1,393
 
More
Quote:
Originally Posted by R3van

Hello,

i`m on Stock Samsung ROM and rooted with Magisk.
Today i`ve got a message from Magisk Manager that an update is available.
Magisk Manager showed me that there were no root installed.

I started TWRP, flashed latest Magisk (18.1) and rebooted. since then i`m Stuck at the flashing Samsung Logo.

I`v hidden the Magisk Manager app within itself with a random package name.
Now i would like to uninstall the Manager app via TWRP to see if that helps. I`ve found a package with a name that looks like randomly arranged letters, can i assume that this is Magisk Manager?

More than likely, yes, because most apps have a name like the app name or developer name in the package name like com.topjohnwu.magisk.
An easier way would have been to unhide the Magisk Manager in settings, before you tried to update, though.
22nd March 2019, 03:38 PM |#32123  
R3van's Avatar
Member
Thanks Meter: 5
 
More
Removed the app, but it doesn`t helped.

Now i`m running out of ideas
22nd March 2019, 04:14 PM |#32124  
Senior Member
Flag Indianapolis, IN
Thanks Meter: 1,393
 
More
Quote:
Originally Posted by R3van

Removed the app, but it doesn`t helped.

Now i`m running out of ideas

Have you tried running the Magisk uninstaller,followed by reflashing Magisk in TWRP, all before rebooting? When running the uninstaller, you should see a message that the stock boot.img was successfully restored. If the stock boot.img is not successfully restored for some reason, you might have to flash the stock boot.img before reflashing Magisk, all before rebooting.

If you run the uninstaller, you will have to reinstall any modules you are using.

You could also try the latest Canary build.
22nd March 2019, 05:01 PM |#32125  
R3van's Avatar
Member
Thanks Meter: 5
 
More
I tried that already, uninstalling reflashing, without rebooting between, with rebooting between, deleting Dalvik&Cache and so on.

When i flash the uninstaller, the message says always that stock image was successfully restored.

Whe i try to boot to System after uninstalling Magisk i get immediatly bootloops.

Can i securely flash stock BL with Odin without losing anything?
Another idea that i have is maybe to related to swift installer overlays. I tried to find them in twrps file manager and via adb but no luck here.

Edit: Tried Canary Build, no luck
22nd March 2019, 05:14 PM |#32126  
Senior Member
Flag Uranus
Thanks Meter: 141
 
More
So I installed a module, and now I can't boot my device.
I tried restoring the stock boot.img
I can not flash those modules that allows you to manage the modules.

What can I do?

Code:
--------- beginning of main
--------- beginning of system
05-10 22:40:06.872   615   615 I Magisk  : Magisk v18.2-945f8810(18121) daemon started
05-10 22:40:06.872   615   615 I Magisk  : * Device API level: 28
05-10 22:40:06.894   615   616 I Magisk  : ** post-fs-data mode running
05-10 22:40:06.897   615   616 I Magisk  : * Initializing Magisk environment
05-10 22:40:06.900   615   616 I Magisk  : * Mounting mirrors
05-10 22:40:06.900   615   616 I Magisk  : mount: /sbin/.magisk/mirror/system
05-10 22:40:06.900   615   616 I Magisk  : mount: /sbin/.magisk/mirror/vendor
05-10 22:40:06.901   615   616 I Magisk  : mount: /sbin/.magisk/mirror/data
05-10 22:40:06.902   615   616 I Magisk  : * Setting up internal busybox
05-10 22:40:06.909   615   616 I Magisk  : * Running post-fs-data.d scripts
05-10 22:40:06.918   615   623 I Magisk  : * Starting MagiskHide
05-10 22:40:06.918   615   623 I Magisk  : hide_utils: Hiding sensitive props
05-10 22:40:06.919   615   623 I Magisk  : hide_list init: [com.snapchat.android/com.snapchat.android]
05-10 22:40:06.923   615   623 I Magisk  : hide_list init: [com.snapchat.android/com.snapchat.android:LoggingOut]
05-10 22:40:06.925   615   623 I Magisk  : hide_list init: [com.snapchat.android/com.snapchat.android:crash]
05-10 22:40:06.927   615   623 I Magisk  : hide_list init: [com.snapchat.android/com.snapchat.android:phoenix]
05-10 22:40:06.929   615   623 I Magisk  : hide_list init: [com.snapchat.android/com.snapchat.android:stuffing]
05-10 22:40:06.932   615   623 I Magisk  : hide_list init: [com.google.android.apps.walletnfcrel/com.google.android.apps.walletnfcrel]
05-10 22:40:06.934   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
05-10 22:40:06.936   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.gms]
05-10 22:40:06.938   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.gms.feedback]
05-10 22:40:06.941   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.gms.learning]
05-10 22:40:06.943   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.gms.nearby.connection]
05-10 22:40:06.945   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.gms.persistent]
05-10 22:40:06.947   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.gms.room]
05-10 22:40:06.950   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.gms.ui]
05-10 22:40:06.952   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.gms:car]
05-10 22:40:06.954   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.gms:snet]
05-10 22:40:06.957   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.play.games.ui]
05-10 22:40:06.959   615   623 I Magisk  : hide_list init: [com.ziraat.ziraatmobil/com.ziraat.ziraatmobil]
05-10 22:40:06.962   615   623 I Magisk  : hide_list init: [com.cpuid.cpu_z/com.cpuid.cpu_z]
05-10 22:40:06.965   615   623 I Magisk  : hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
05-10 22:40:06.968   615   623 I Magisk  : hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
05-10 22:40:08.046   615   997 I Magisk  : ** late_start service mode running
05-10 22:40:08.046   615   997 I Magisk  : * Running service.d scripts
05-10 22:40:08.048   615   997 I Magisk  : service.d: exec [v4afx.sh]
05-10 22:40:08.048   615   997 I Magisk  : service.d: exec [propsconf_late]
--------- beginning of crash

edit: debug logs: https://pastebin.com/c7iUhZhs
22nd March 2019, 05:31 PM |#32127  
Junior Member
Thanks Meter: 0
 
More
Magisk 18.1 doesnt work on Japanese S8+

SC03JOMU1BSA1
Oreo

After installed Magisk 18.1, boot loop.
Please fix.
22nd March 2019, 07:00 PM |#32128  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by kotuamoalt

Have you tried holding the reset button for a longer. Of time? Say, 15 to 30 seconds?

Hi, yes....over a minute and it comes back to life afterwards (having to press power button for 15 secs) to the flashing red triangle again.

Could I ask if someone can kindly confirm that I have managed to actually kill this tablet?

To sum up:
I have tried to reinstall the stock rom through a Mac's terminal command line on an unlocked bootloader having wiped user data and cache. Unfortunately I ignorantly only flashed the boot image and not the entire stock rom folder which included the recovery. Now, on boot it flashes the Android red triangle man and says 'supported API:3'. I can only switch this off by poking the reset button. It cannot be recognised through ADB shell via USB.
  • Are my attempts to find a recovery mode futile as I have managed to delete the initial recovery?
  • Is there a scenario by which an Android device can be rendered completely useless, and if so, have I found it?
  • I've read of SP Flash tools...can this toolkit communicate (via Windows machine)?
  • How do manufacturers install onto a completely empty disk in the first place, and is there a route to recovery via that?
Again, I am very grateful for this community for the support offered...trying to learn by the empirical route certainly comes at a price!
22nd March 2019, 07:14 PM |#32129  
Junior Member
Thanks Meter: 4
 
More
Hey guys, only magisk version works for me, all that above leads to a reboot in recovery (twrp). Any ideas how to fix?
22nd March 2019, 07:57 PM |#32130  
Recognized Contributor
Thanks Meter: 3,166
 
More
Quote:
Originally Posted by lyoks

Hey guys, only magisk 16.0 version works for me, all that above leads to a reboot in recovery (twrp). Any ideas how to fix?

What device? What ROM/Android version? Install logs? Any other possible relevant details? (No logs means everything is working just fine)
22nd March 2019, 08:07 PM |#32131  
guest4711's Avatar
Senior Member
Flag Београд (Beograd/Belgrade/Griechisch Weißenburg/Alba Graeca; Alba Bulgarica)
Thanks Meter: 2,170
 
More
Quote:
Originally Posted by The War Profiteer

So I installed a module, and now I can't boot my device.
I tried restoring the stock boot.img
I can not flash those modules that allows you to manage the modules.

What can I do

Either force Magisk to run in core-only mode or if you are on an current Magisk use the filemanager in TWRP to delete the module from /data/adb/magisk/modules/

To enable core-only mode you can open a shell/terminal from TWRP and enter
Code:
touch /cache/.disable_magisk
- as far as I remember. Search in this thread to find the correct spelling if it does not work.

Edit: The spelling is correct. Please note the dot before disable; the char behind is an underline...
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes