I have a car Android device in which I am able to install magisk extracting boot.img and then patching it. I was having some problems and have reset, and now I am having some issues:
I flashed latest magisk and got bootloop, so I managed to install 20.2 version and it gives superuser access, but I can't install no modules (it seems to install them but they are not there after a reboot).
I think before the reset I had 20.4 installed, but I don't know how to update my version to 20.4, it always offers me latest version, which ends in bootloop. I don't have access to any custom recovery, so I think the only way to make it work is to update through a custom channel pointed to 20.4, but can't figure out how to set it.
Any help would be appreciated.
Ok, I realized a simpler way to do it: I downloaded 20.4 zip and flashed it through magisk. Now it works perfectly, but when I use Viper4android together with sygic, sygic crashes.
Related
For the past two days I've tried unsuccessfully to install Magisk for the hide SafetyNet option.
My phone is a D5803 with the firmware 23.5.A.1.291 R12D Nordic Combined
Let me give the background to my dilemma.
I bought the phone already unlocked
I had TWRP installed and rooted with SuperSU
After a few months, I've decided to change the root for magiskSU so I uninstalled SuperSU 2.92 and attempted to flash Magisk 14 with the result of Error 1. After some fiddling I've bricked the phone and did a full reinstallation of my phone with the untouched firmware.
After reinstalling TWRP 3.1.1 I've tried my luck again to no avail, this time backing up my system.
I scoured the forum and on the net for pointers on how I could do this but I can't seem to find anything to make this work.
I tried going back to the kernel 575, flash Magisk, flash 291 just like the superSU thread,
tried reinstalling stock firmware, unSU, uninstall Magisk, flash magisk,
tried using bootbridge and even Magisk Manager app to patch the boot.img but comes up as failed ELF32 format detected and to use bootbridge needs to be used.
Using bootbridge with Magisk in TWRP "appears" to work but really doesn't do anything
I've tried flash tool from and xperifirm to get a boot.img different of the one I have but when I come to create a ftf, the program jams on me.
I don't want to reinstall SuperSU if I can as I tried HideSU with no results. Help would be greatly appreciated
Kesymos said:
For the past two days I've tried unsuccessfully to install Magisk for the hide SafetyNet option.
My phone is a D5803 with the firmware 23.5.A.1.291 R12D Nordic Combined
Let me give the background to my dilemma.
I bought the phone already unlocked
I had TWRP installed and rooted with SuperSU
After a few months, I've decided to change the root for magiskSU so I uninstalled SuperSU 2.92 and attempted to flash Magisk 14 with the result of Error 1. After some fiddling I've bricked the phone and did a full reinstallation of my phone with the untouched firmware.
After reinstalling TWRP 3.1.1 I've tried my luck again to no avail, this time backing up my system.
I scoured the forum and on the net for pointers on how I could do this but I can't seem to find anything to make this work.
I tried going back to the kernel 575, flash Magisk, flash 291 just like the superSU thread,
tried reinstalling stock firmware, unSU, uninstall Magisk, flash magisk,
tried using bootbridge and even Magisk Manager app to patch the boot.img but comes up as failed ELF32 format detected and to use bootbridge needs to be used.
Using bootbridge with Magisk in TWRP "appears" to work but really doesn't do anything
I've tried flash tool from and xperifirm to get a boot.img different of the one I have but when I come to create a ftf, the program jams on me.
I don't want to reinstall SuperSU if I can as I tried HideSU with no results. Help would be greatly appreciated
Click to expand...
Click to collapse
Have you tried with a different stock kernel, (maybe Elite)? Not sure what the problem is. I've never had trouble with Magisk, but now that I think about it, I don't think I ever tried to flash it on straight stock rom, (I prefer phh anyway in general).
Another thought I had is, if Magisk has a problem with elf format, maybe use Rashr to make a kernel backup image, then flash the backup, (I really don't know anything about this stuff, just shooting in the dark...).
hello guys, hope you can help me here.
so as per title say, i got error when installing magisk manager 5.6.4, app not installed.
have try with older version but got same problem.
before this, i tried to upgrade system from nougat to oreo. successful with flashable roms.
at nougat, i got magisk manager, but couple steps to upgrade they recommended to remove magisk, so i use magisk uninstaller. and magisk gone for good.
after booting to oreo, i want to recover root, but cant even install magisk manager apk.
try to flash magisk 16.0, success with no problem.
now im very confuse. need help.
EDIT 1: and for some reason i cant install OTA. is this related?
Unfortunately I ran into the same problem. I tried installing Magisk Manager (5.6.3 and 5.6.4) on a stock, clean Nexus 6P but received that same error when running the app. I originally used ADB to install it and when that didn't produce the expected result I just used ADB to push the file to the device and then installed it manually. Neither method resulted in Magisk Manager running so I ended up having to install TWRP (which is what I was trying to avoid) and then flash the Magisk zip file. After that Magisk Manager ran successfully.
Too bad the documentation makes assumptions about everyone automatically understanding what is meant by 'install Magisk Manager'.
Sent from my Pixel 2 XL using Tapatalk
Hi There,
I met some issues when I tried to flash the Magisk zip to my MIX2S.
Phone MIX 2S
OS:MIUI 10.3 by xiaomi.eu 9.2.15
Recovery:TWRP
Situation:
Part 1, at the beginning, I flashed the xiaomi.eu rom to my MIX 2S, and then flashed magisk zip file, everything works well except sometime the saftynet check will fail. After I check the post of saftypatcher , I changed to ianmacd mod. Everything seems fine until then. I need to re-flash the magisk official zip every time after I update my phone, and than update magisk to ianmacd mod in magisk manager.
Part 2,
Today I updated my rom to MIUI 10.3 by xiaomi.eu 9.2.22, I then re-flash the official magisk zip as usual, and then updated to ianmacd mod in magisk manager. I re-boot the phone, then it reboot to recovery when I tried to input my pin. Reboot again, still went to the recovery. So I use ianmacd uninstaller to uninstall the magisk, and tried to flash the official zip. The phone booted into the system, but when I open the magisk manger, it shows that mangisk is not installed. I reflashed again, still the same issue.
I uninstalled the manger, tried to install the offical manger apk file, told the app was not installed.
I downgrade my system to MIUI 10.3 by xiaomi.eu 9.2.15, reflash the offical 18.1 zip file, reboot, no magisk manger on my phone, tried to install the apk file, still failed.
I boot into the recovery to uninstall and install again, still no manger in the system. Now I'm totally lost.
Part 3, some of my app tells me that my phone is rooted, so I guess the magisk is in somewhere of my system?
Attached is the recovery log.
Thank you in advance. Sorry for my English.
You've been mixing Managers with different signatures (the official with unofficial)...
Try this:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager
Didgeridoohan said:
You've been mixing Managers with different signatures (the official with unofficial)...
Try this:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager
Click to expand...
Click to collapse
Thank you very much for the help. It fixed my issue.
Now I need to investigate the "boot to recovery" issue.
I forgot to add on the title -- my phone is the EU variant with Snapdragon 5G. (G781B)
Hello, did anyone get Edxposed for the phone?
I've succesfully rooted but edxposed seems to be always causing some kind of bootloop.
I haven't need to use edxposed as I was refusing to upgrade from my old oneplus 3, so I'm a complete noob here at this point,
However, it does seem like there seems to be issue on this area anyway.
If anyone succeeded, please share what you did.
Thanks!
everlasting207 said:
I forgot to add on the title -- my phone is the EU variant with Snapdragon 5G. (G781B)
Hello, did anyone get Edxposed for the phone?
I've succesfully rooted but edxposed seems to be always causing some kind of bootloop.
However, it does seem like there seems to be issue on this area anyway.
If anyone succeeded, please share what you did.
Click to expand...
Click to collapse
Morning
I have just purchased the same phone, but I didn't get as far as you, so in the hope we can help each other here is a summary of what I did and how far I got -
I upgraded stock ROM all the way upto Android 11
Then enabled dev. options, and clicked on OEM unlock and then rebooted following the new unlock bootloader option on the download screen.
Then rebooted into download mode and flashed vbmeta_disabled.tar via ODIN (this then factor reset the phone).
Then had to re-flash stock android (via ODIN), as OEM unlock disappeared from dev. options.
Then back into download model to flash twrp 3.5.1 via ODIN.
Then after to trial and error and help from @afaneh92 I figured how to get into twrp recovery (and how to stop the phone from restoring stock recovery).
I then extracted & patched boot.img in Magisk (see instructions)
Then I booted back into download mode and 'tried to flash to new magisk patched boot.img via ODIN, but it failed with Can't open the specified file (line: 2006)
I then installed magisk manager 8.05, then tried flashing Magisk 21.2 via twrp and it failed with (Android Rescue party trigger).
So I then re-flashed multi-disabler.zip via TWRP and without rebooting formated data, then power off and boot back into recovery. I then flashed magisk 21.2 no problem.
Back into Android I loaded up magisk to confirm I was rooted and to get Riru & EdXxposed installed.
I installed EdXposed manager via its APK.
I then went back into Magisk manager and found and installed Riru 23.3 (this as i understand it replaced Riru - core).
I then found the latest stable version of EdXposed YAHFA 0.4.6.4 (4563) and this refused to install via magisk manager, with error ( ' Riru - core ' is not installed, Unsupported v22+ is installed, user 21.3 instead ) . So Clearly the above ver. of EdXposed isnt compatible with the latest version of Riru.
I then installed the alpha version of EdXposed 0.5.1.4 (4655) and this installed, but when I went into EdXposed manager it said it was installed but not active
So I have my shiny new SM-G781B, w/custom recovery & rooted, but no Xposed framework. I need Xposed for Xprivacy_lua so not having this running isnt an option. So I am going to try Riru - core 21.3/EdXposed_ 0.4.6.4 and if that fails then going all the way back to Android 10 and starting from the top.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What versions of Android, Twrp, Magisk, EdXposed, Riru - have you got installed? Also regarding your EdXposed bootloop - if you read the supports docs, its does say that YAHFA can cause soft loop, and to try Sandhook. But on my old S7, Sandhook caused a boot-loops so I went to and am using YAHFA with no issues - so as always your mileage will always vary.
Hello,
I have rooted my GPlay and installed TWRP.
Unfortunately my banking app detects the root and refuses to work.
I heard about Magisk which can be used to bypass this.
Can anyone tell me where to get this for my GPlay and how to install it?
I have TWRP 2.8.7.0 hw4c installed and SuperSU Free v2.68 (SuperSU-v2.68-SYSTEMMODE.zip)
Phone:
Model: CHC-U01
EMUI 4.0 Android 6
I've downloaded the Magisk App and try to install. But get this error:
Installation failed
Boot Image patched by unsupported programs
Please restore back to stock boot image
That error message tells you exactly what you need to do... You need to first remove SuperSU. After that you might be able to install Magisk, but you might need to use the patch boot image method, since that TWRP could be a bit too old.
But, even if you get Magisk installed it's not certain that you'll be able to circumvent your banking app's root detection. There are ways of detecting root that Magisk cannot hide. But, you've certainly got a better chance with Magisk than with SuperSu... You'll find some root hiding tips here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Ok. I forget about Magisk.
Thanks to you Didgeridoohan and jwoegerbauer.