Related
Hi, do i need install systemless SuperSU always in twrp before install magisk v11 if I want use new MagiskSU instead??
If I try install Magisk v11 with superSU uninstalled and phone unrooted TWRP give me error and installation fails and if I install superSU and after Magisk v11, Magisk manager say system is using SuperSU instead MagiskSU. How do I install Magisk with MagiskSU??
I have Samsung Galaxy S4 with optimized LineageOS 14.1
Read the pinned Magisk thread...
Unroot again using unSu by osm0sis (Google) before flashing magisk
Installation Instructions
If you're already rooted with MagiskSU, Magisk phh's superuser (not original), or Official Systemless SuperSU
Install/upgrade Magisk Manager from Play Store
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
Click to expand...
Click to collapse
I read 200 times but when I install Magisk without SuperSU (because I want MagiskSU) TWRP give me an error and install fail... read my initial post first please....
Error:
Code:
! SU image mount failed...
! Please immediately flash SuperSU now
! Installation will complete after flashing SuperSU
[B]Updater process ended with ERROR: 1
Error installing zip file 'sdcard/Download/Magisk v11.1/Magisk-v11.1.zip[/B]
dhaern said:
I read 200 times but when I install Magisk without SuperSU (because I want MagiskSU) TWRP give me an error and install fail... read my initial post first please....
Error:
Click to expand...
Click to collapse
You need to FULLY unflash superSU using the zip that the other person told you to google.
PartyPlease said:
You need to FULLY unflash superSU using the zip that the other person told you to google.
Click to expand...
Click to collapse
Ok I will try unflash with the zip, I was using unroot inside superSU menu but installation instructions dont say nothing about the unflash with an extrenal script
dhaern said:
Ok I will try unflash with the zip, I was using unroot inside superSU menu.
Click to expand...
Click to collapse
Yeah that button doesn't work for systemless superSU. It doesn't roll back your boot.IMG like it should.
Worst case scenario, flash the stock boot.img and then flash magisk.
Thanks guys, I installed Magisk v11.1 with MagiskSU working, Magisk Hide enabled but I have CTS mismatch error now in Safetynet test. I guess I cant do nothing about this error. Optimized LineageOS 14.1 and Samsung Galaxy S4
EDIT: Finally I passed the Safetynet test (no CTS mismatch error) disabling ADB interface in developer options. Thanks for Magisk, amazing.
PartyPlease said:
Yeah that button doesn't work for systemless superSU. It doesn't roll back your boot.IMG like it should.
Worst case scenario, flash the stock boot.img and then flash magisk.
Click to expand...
Click to collapse
ahh, this would explain why my boot.img was not the same after "unrooting"! thanks for clearing this up for me...
dhaern said:
Thanks guys, I installed Magisk v11.1 with MagiskSU working, Magisk Hide enabled but I have CTS mismatch error now in Safetynet test. I guess I cant do nothing about this error. Optimized LineageOS 14.1 and Samsung Galaxy S4
EDIT: Finally I passed the Safetynet test (no CTS mismatch error) disabling ADB interface in developer options. Thanks for Magisk, amazing.
Click to expand...
Click to collapse
By disabling ADB interface, do you mean the USB debugging part? for some reason I am still getting Safetynet error.
vicky_ag said:
By disabling ADB interface, do you mean the USB debugging part? for some reason I am still getting Safetynet error.
Click to expand...
Click to collapse
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
dhaern said:
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
Click to expand...
Click to collapse
Thanks but doesn't seem to work for me.
dhaern said:
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
Click to expand...
Click to collapse
Thanks for this hint; got my build "passed" now appreciate it
What settings are you guys using in Magisk? I have disabled BusyBox, enabled Magisk Hide and systemless hosts. Superuser options are Access to "Apps and ADB" and Automatic Response set to prompt
I'm still having an issue installing Magisk on my phone with RAMROM V10. It gives me an ERROR 1.
It has been suggested that I should re-flash my boot.img with TWRP following the instruction:
Place your BOOT.img on your sdcard
Reboot into TWRP recovery
Tap "Install"
In the bottom right corner tap "Install Image"
Select your BOOT.img
Select the Boot Partition, then swipe to confirm Flash
However, when I follow the step, my TWRP cannot seem to find BOOT.IMG in my SD Card (I know it is there). What did I do wrong? Can anyone help?
i think the .img thingy is only for twrp.img files. You have to use another method to place your boot image like. -> make a backup of only your boot image via twrp backup function. Then duplicate that backup folder of twrp containing only the newly just regernated files, in the twrp folder. Then replace the su-modified boot file there with your original boot file, you obviously have to rename your boot image to fit the right name. (eg. with the logo image -> logo.bin changes to logo.emmc.win -> etc;.) Then use the twrp restore function to restore your "original" boot logo.
Hierarchy folder view would be like:
TWRP->folder 1 (original folder, in case something goes wrong)-> boot file and others
->folder 2 (our modified folder)-> files
sm00th4f3 said:
i think the .img thingy is only for twrp.img files. You have to use another method to place your boot image like. -> make a backup of only your boot image via twrp backup function. Then duplicate that backup folder of twrp containing only the newly just regernated files, in the twrp folder. Then replace the su-modified boot file there with your original boot file, you obviously have to rename your boot image to fit the right name. (eg. with the logo image -> logo.bin changes to logo.emmc.win -> etc;.) Then use the twrp restore function to restore your "original" boot logo.
Hierarchy folder view would be like:
TWRP->folder 1 (original folder, in case something goes wrong)-> boot file and others
->folder 2 (our modified folder)-> files
Click to expand...
Click to collapse
FIY: Flashing regular boot.img files works just fine with "Install Image" in TWRP (of course, YMMV, depending on your device).
As far as I know there is no TWRP for Android x86_64 for PC. How could I ever get Magisk 14 installed?
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I'm thinking on using it on Bliss which is running Nougat 7.2 x86_64. I really want root but some apps will not work with root.
Magisk manager has an option to install magisk without recovery, of course this means you will need some sort of root solution before hand
Xmaster24 said:
Magisk manager has an option to install magisk without recovery, of course this means you will need some sort of root solution before hand
Click to expand...
Click to collapse
No it doesn't. It means you'll need a copy of your device's boot image and some way to flash it to your device after the Manager has patched it. No root required...
Didgeridoohan said:
No it doesn't. It means you'll need a copy of your device's boot image and some way to flash it to your device after the Manager has patched it. No root required...
Click to expand...
Click to collapse
Well he is talking about a pc which does not use a boot image the same way a normal device does, anyways Bliss rom comes with root.
EDIT: actually now that you mention that I was not aware you could select a boot image to patch in magisk manager, if he does that he can just copy the boot image to wherever Bliss rom stores the emulated boot image
Xmaster24 said:
Well he is talking about a pc which does not use a boot image the same way a normal device does, anyways Bliss rom comes with root
Click to expand...
Click to collapse
I know... So in other words it's probably not gonna happen. Magisk relies entirely on patching the boot image.
My answer to your post was simply to prevent any future misunderstandings for anyone reading it. :good:
Well I think RMXtools or similar is used to mount the .img file and root it with SuperSU for Android x86 for PC. Could this also be done for Magisk?
I would need to know exactly where the files would need to go I guess and also which image to mount for Android x86 for PC
saulin78 said:
Well I think RMXtools or similar is used to mount the .img file and root it with SuperSU for Android x86 for PC. Could this also be done for Magisk?
I would need to know exactly where the files would need to go I guess and also which image to mount for Android x86 for PC
Click to expand...
Click to collapse
And that was made with the system or systemless type of install for SuperSU? Magisk can only be installed systemlessly...
If it's possible, you can probably find the info you need here: https://github.com/topjohnwu/Magisk
Android x86 has no boot partition. It contains kernel binary and initrd image.
Didgeridoohan said:
And that was made with the system or systemless type of install for SuperSU? Magisk can only be installed systemlessly...
If it's possible, you can probably find the info you need here: https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
For PC installations of Android x86 you can edit the system and data images with that tool. I believe root is achieved by editing the system partition.
Bliss already comes pre-rooted or without root, depending on which *.iso is used for the installation. I picked the rooted image and tried to uninstall SuperSU which looks like I did successfully, however this app I have still detects that the device has been modified or is rooted it says.
I will install the non-root version today and see if the message goes away. If it does then I know there must still be traces of root on the other image. Now the ideal thing would be to get Magisk somehow installed because then I could hide the root which seems to work for the apps I have tried it on on my Shield Android TV Box.
**Edit**
Well Magisk on Android x86 sure seems possible judging by the posts and screenshots from youling 257
https://groups.google.com/forum/#!s...elevance/android-x86/omGg6QZlEGc/H4_QXjhQBwAJ
However this all seems way too complicated for me.
https://groups.google.com/forum/#!msg/android-x86/311n2ivCLYw/hfIZnqkXBwAJ
I was able to install Magisk V12.0 on Android x86 7.1.2 rc2, using this tools to create a "fake" boot.img using kernel and ramdisk.img files:
https://forum.xda-developers.com/showthread.php?t=2319018
But I had to make small modifications in the install script and magic_mask.sh to bypass some errors and correctly mount system to the magisk folder. Newer versions don't have magic_mask.sh anymore but a binary, so unless you modify the source and compile it yourself I think it won't work. Probably because v12.0 is somewhat old I can't install modules automatically using Magisk Manager tho...
https://forum.xda-developers.com/phoenix-os/phoenix-os-news-qa--development/magisk-15-3-t3735310
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is oppo neo 7 android 5.1
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Didgeridoohan said:
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Click to expand...
Click to collapse
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
rajoholic said:
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
Click to expand...
Click to collapse
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Didgeridoohan said:
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Click to expand...
Click to collapse
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
I m also facing same problem
rajoholic said:
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is Micromax canvas nitro a310 current android version is cyanogen mode 13
Click to expand...
Click to collapse
rajoholic said:
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
Click to expand...
Click to collapse
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
sorry bout that. i just search the google free and temporary storage online. haha! thank you for the help. I'll try what u just said
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
rajoholic said:
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
Click to expand...
Click to collapse
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Didgeridoohan said:
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
rajoholic said:
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
Click to expand...
Click to collapse
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Didgeridoohan said:
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Click to expand...
Click to collapse
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
rajoholic said:
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
Click to expand...
Click to collapse
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Didgeridoohan said:
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Click to expand...
Click to collapse
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
rajoholic said:
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
Click to expand...
Click to collapse
Sir, did you manage to install? when i tried to install log is failed.
Good evening from Spain.
I tried to flash Magisk onto my SM-J530F (Samsung Galaxy J5 2017) but not successfully.
Here's the log:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled.
Installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
********************
* Magisk v16.0 Installer
********************
- Mounting /system, /vendor
- Found boot/ramdisk image: /dev/block/mmcblk0p10
- Device platform: arm
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs.
! Please restore stock boot image
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Updating partition details...
Failed to mount '/system' (Device or resource busy)
...done
Consider that I did the following:
- Flashed stock rom (J530FXXU2ARB3_J530FPHE2ARB3_PHE.zip content)
- Flashed "CF-Auto-Root-j5y17lte-j5y17ltexx-smj530f.tar" in Download mode via Odin, to root and install SuperSU, since it's needed
for flashing TWRP to avoid any bootloop.
- Flashed TWRP.
- Since I already have TWRP, I tried to uninstall SuperSU from the very app, in Options > Full unroot but gave "Uninstallation error", so then I tried to uninstall SuperSU by flashing "UPDATE-unSU.zip" on TWRP.
- Once that is done, I tried to flash "Magisk-v16.0.zip" and it throwed the log I've above mentioned.
- Since it says: "! Boot image patched by other programs.
! Please restore stock boot image", I rebooted it onto Download Mode, and flashed ONLY the BL (bootloader/boot) slot. Came back to TWRP, I flashed again "Magisk-v16.0.zip" but still have the same problem.
Hope there's any solution to install Magisk onto my SM-J530F. Thank you.
Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).
Didgeridoohan said:
Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).
Click to expand...
Click to collapse
Well, something changed!!!
The problem related with the boot image is solved but I still have the " Failed to mount '/system' "
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled.
Installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
********************
* Magisk v16.0 Installer
********************
- Mounting /system, /vendor
- Found boot/ramdisk image: /dev/block/mmcblk0p10
- Device platform: arm
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Backing up stock boot image
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Updating partition details...
Failed to mount '/system' (Device or resource busy)
...done
Thank you very much.
EDIT: Despite this problem: "Failed to mount '/system' (Device or resource busy)", your solution was correct! Now I have Magisk correctly installed.
Thank you
Nice to hear it worked. Just for the record, the "Failed to mount /system" message is a TWRP thingy. The Magisk installation is done at the "-Done" line.
Hi, I have the same problem of error 1 while trying to install Magisk from TWRP.
I looked everywere and they say that it is related to a boot image that have to be reinstalled. I did that and no luck, I tryed with boot.img, no working, I even restored ALL the ROM Stock from Samsung ( AP, BL, CP and CSC) and it is not working. I dont know what to do anyware...
Regeet the time was easy to root Samsung with CF autoRoot,
I tried that and ask me to restore all thephone, so still no root??
Some can help please??
Thx
saoudien07 said:
Hi, I have the same problem of error 1 while trying to install Magisk from TWRP.
I looked everywere and they say that it is related to a boot image that have to be reinstalled. I did that and no luck, I tryed with boot.img, no working, I even restored ALL the ROM Stock from Samsung ( AP, BL, CP and CSC) and it is not working. I dont know what to do anyware...
Regeet the time was easy to root Samsung with CF autoRoot,
I tried that and ask me to restore all thephone, so still no root??
Some can help please??
Thx
Click to expand...
Click to collapse
Provide a recovery log or it's going to be impossible to say what the issue is...
Didgeridoohan said:
Provide a recovery log or it's going to be impossible to say what the issue is...
Click to expand...
Click to collapse
Thx for the reply, I am trying to open the content and upload the report here, but no luck. how can I open the log??? can not get a program to do so .......
saoudien07 said:
Thx for the reply, I am trying to open the content and upload the report here, but no luck. how can I open the log??? can not get a program to do so .......
Click to expand...
Click to collapse
The log is just a text file. Did you check the link I posted? In TWRP: Advanced - Copy log, and then post the resulting file.
Didgeridoohan said:
The log is just a text file. Did you check the link I posted? In TWRP: Advanced - Copy log, and then post the resulting file.
Click to expand...
Click to collapse
I got a file "recovery.log" thats why I can not open it, maybe change the extention to "txt" ???
saoudien07 said:
I got a file "recovery.log" thats why I can not open it, maybe change the extention to "txt" ???
Click to expand...
Click to collapse
That would work, but you should be able to open it directly with pretty much any text editor as well. If you're going to post the log text directly, please at least use HIDE tags...
So here what I just did:
I wanted to do a last try to get that error 1 msg and get the repport directly to publicate it here...
So I decide to go to a clean basis. So,
1- Install all the stock ROM with odin. I choose the Home_CSC
Was another just CSC without Home, dont know exactly which one I had to choose, I choose Home_CSC.
2- Turn the fone off
3- Turn it back to download mode
4- Install the TWRP recovery, and I did not reboot.
5- Turn off the fone.
6- Turn on to recovery mode.
7- Format the data (yes)
8- Reboot to Recovery mode.
9- Install Magisk!
AT MY BIG SURPRISE I DID NOT GET ANY ERROR MSG!!! The installation finished without error!
So I continued...
10- install No verity
11- install SuperUS 2.82
13- Reboot the phone.
I was thinking that the root was ok, now I have a new pb. When I tryed to verify with Root Checker, it says no root. When I entered the app, it said BINARY OCCUPIED.
So any suggestion?
saoudien07 said:
9- Install Magisk!
...
11- install SuperUS 2.82
Click to expand...
Click to collapse
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.
Didgeridoohan said:
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.
Click to expand...
Click to collapse
You guessed right, I am not using a so old tuto, it says it is for oreo...
So I have to use or Magisk or SuperSU,right?
The thing is that i thought SuperSu is to install the SuperSU app, I did notknow that it root also the phone...
I am kind of newby to Android world, u figured it already...
So what are insterest of using Magisk or no-verity??
---------- Post added at 08:22 PM ---------- Previous post was at 08:17 PM ----------
Didgeridoohan said:
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.
Click to expand...
Click to collapse
Can I put a link to the tuto here??
For you guys to have a lock at it?
saoudien07 said:
You guessed right, I am not using a so old tuto, it says it is for oreo...
So I have to use or Magisk or SuperSU,right?
The thing is that i thought SuperSu is to install the SuperSU app, I did notknow that it root also the phone...
I am kind of newby to Android world, u figured it already...
So what are insterest of using Magisk or no-verity??
---------- Post added at 08:22 PM ---------- Previous post was at 08:17 PM ----------
Can I put a link to the tuto here??
For you guys to have a lock at it?
Click to expand...
Click to collapse
The root management app for Magisk/MagiskSU is the Magisk Manager. SuperSU and it's accompanying app is a whole different root solution (that has been sold by @Chainfire and seemingly abandoned by it's new owners).
Magisk usually takes care of dm-verity itself, so there shouldn't be any need for an extra no-verity zip. Sometimes it is needed, but I would skip it until you've tried using Magisk only. If you don't know, dm-verity is used by Android to determine if your device has been tampered with. If you wan't to root your device (tampering), you usually have to disable dm-verity or the device won't boot at all.
If you want root with Magisk, do your list again, but skip step 10 and 11. If it doesn't boot after that, go back to TWRP and flash the no-verity zip.
Didgeridoohan said:
The root management app for Magisk/MagiskSU is the Magisk Manager. SuperSU and it's accompanying app is a whole different root solution (that has been sold by @Chainfire and seemingly abandoned by it's new owners).
Magisk usually takes care of dm-verity itself, so there shouldn't be any need for an extra no-verity zip. Sometimes it is needed, but I would skip it until you've tried using Magisk only. If you don't know, dm-verity is used by Android to determine if your device has been tampered with. If you wan't to root your device (tampering), you usually have to disable dm-verity or the device won't boot at all.
If you want root with Magisk, do your list again, but skip step 10 and 11. If it doesn't boot after that, go back to TWRP and flash the no-verity zip.
Click to expand...
Click to collapse
I just repeated all the procedure, this time just with Magisk, like you said. its installation finished without any error.
I just tryed ROOT Checker, any I finally have the root on my fone!! Thanx you very much for the support, and the explanation.
Can I use Backup/Restoration with TWRP knowing that I rooted with Magisk??
saoudien07 said:
I just repeated all the procedure, this time just with Magisk, like you said. its installation finished without any error.
I just tryed ROOT Checker, any I finally have the root on my fone!! Thanx you very much for the support, and the explanation.
Can I use Backup/Restoration with TWRP knowing that I rooted with Magisk??
Click to expand...
Click to collapse
Great to hear! :good:
You can use TWRP without any issues. Magisk has no impact on it and TWRP has it's own su.
Didgeridoohan said:
Great to hear! :good:
You can use TWRP without any issues. Magisk has no impact on it and TWRP has it's own su.
Click to expand...
Click to collapse
Thx you one more time. Going to install some of my app and configure my new fone then do a backup, for a clean restoration in some months...
I have a problem for the Backup with TWRP. When I want to do a Backup, I get this msg:
failed to mount /data (Invalid argument)
I ve looked on google to fix it, the solution I found is to change data to ext2, then back to ext4.
The pb is that it is removing everything from my phone?
Anyone is having the same issue??
Didgeridoohan said:
Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).
Click to expand...
Click to collapse
Hi, i am rooting samsung a5 a520w. I am following the steps in the instructions (https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535).
Now I met a problem like this:
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Error installing zip file '/sdcard/MagiskManager/Magisk-v17.1.zip'
I have no idea where is the boot.img located. All documents in the external card is:
RMM-State_Bypass;
no-verity-opt-encrypt-6.0;
Magisk_17.1
@imcn001 Your answer is in the link from the post you quoted.
Disclaimer: Your warranty will be void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Hi.
Based on the feedback from this thread, the following steps can be used to aquire root on the SM-T590. The process is quite similar to rooting other devices by using Magisk. It might also work on other versions of the SM-T59x family, which can be OEM unlocked (sorry Verizon users).
Obtain the boot image
Get the firmware that matches the version installed on your device. This is important, otherwise you can easily end up in a bootloop.
Extract the AP tar.md5 file, e.g. "AP_T590XXU2ARJ1_CL14463952_QB20043720_REV00_user_low_ship_MULTI_CERT_meta.tar.md5".
Upon the extracted files, there is a file called boot.img.lz4. Extract it. Important: Most standard compression tools, e.g. 7-zip, are unable to extract lz4 compression ccorrectly. Use the offical lz4 binary from your Linux distribution or get the Windows version here. Once extracted, you should have a file called boot.img.
Patch the boot image
Copy the boot.img file to your device.
Download and install the Magisk Manager apk from the offical Magisk Thread.
In Magisk Manager settings, set the image format to "img.tar".
Enable the "Keep AVB2.0/dm-verity" in the Magisk main screen.
Hit "Install" and select "Patch boot image".
Select the boot image copied previously to your device.
Once finished, the patched image will be located in the Download directory on the internal storage.
Copy the patched image back to your PC.
Unlock and flash
Go into settings and enable developer settings.
In the developer settings, select OEM unlock, read the help text and enable the unlock, if you consent.
Once the device is factory reset and rebooted, turn the device off.
Boot the tablet into download mode.
Flash the patched boot image with Odin in the AP-slot
Reboot, Install Magisk Manager apk again and check if root is available.
Have fun.
Thanks to @gscollier, @airmaxx23 and @EinsamerSpieler for testing.
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
did you find a solution?
stupid question
I know this is a dumb question but where do you get the firmware....
Also was wondering if that reboot thing is still an issue.
I'll still root, I would like to try the LineageOS, eventually... how well does this work with Android apps/F-droid?
Update: still looking for confirmation on which boot image to use... guess you can't do a backup before flashing like you used to be able to do.
I installed heimdall and adb both seem to work
heimdall instructions
User848 said:
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
Click to expand...
Click to collapse
the same happens to me.
I also tried removing some microsoft apps with Titanium, but after removing the excel, it goes to a kernel panic...
And then there's the "Security notice" from "SecurityLogAgent" notifications (unauthorised actions have been detected, unauthorised access to a secured area)
any solutions, followed steps but no root
I have the same problem Root is present but once i try to rename a file in /system/app, the device reboots.
Using SM-T590 with canadian image:T590XXU2ASC1
Using Magisk version V7.1.2(208) - V19.1 (19100)
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Quick help please, I have the patched boot image on my pc but when I click the AP slot on odin it doesnt detect it only finds tar, md5 files etc. in the settings i cant change the format to .tar there is no option.
IET_DEMO said:
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Click to expand...
Click to collapse
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
mingkee said:
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
Click to expand...
Click to collapse
Well I did it on android 8.1.0, seems like it work on Oreo too
IET_DEMO said:
Well I did it on android 8.1.0, seems like it work on Oreo too
Click to expand...
Click to collapse
How about Titanium Backup?
It works on rooted T510
mingkee said:
How about Titanium Backup?
It works on rooted T510
Click to expand...
Click to collapse
I dont have or use Titanium Backup, I usually clone my devices with twrp backup
There needs to be a better option that works without the current issues when rooting. You either end up with reboots or can not log in to Samsung account at all
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Would it work on 595? Bootloaders should be the same without boot loop?
vq8acsxht said:
Would it work on 595? Bootloaders should be the same without boot loop?
Click to expand...
Click to collapse
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
kidkrooks said:
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
Click to expand...
Click to collapse
Mine is on it's way. I will try it when I get it. I think bootloaders should be same in in both 590/595.
kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Does this still have "Modifying system files leads to reboot" issue or it's solved ?