Better click his 'like' button!Wow thanks for going the extra mile.

Better click his 'like' button!Wow thanks for going the extra mile.
No fun if you give away the secret.Better click his 'like' button!PW
Keep giving away the important ones...No fun if you give away the secret.![]()
Wow thanks for going the extra mile.
If you have a working TWRP you should be able to backup the boot-partition and patch the image-file from backup with Magisk.Keep giving away the important ones...
That one's sure to help me (and others) in future. (My last LOS had boot.img in root of zip IIRC.)
Edit: Found this tutorial for PC also (Uses Payload Dumper Tool and Python to extract firmware files including boot.img):
And here's one to extract using phone!:![]()
How to Extract payload.bin and get stock boot image file - DroidWin
To extract the payload.bin file from stock firmware and get the stock boot image file, you should refer to the instructions given in this guide.www.droidwin.com
![]()
[Tutorial] Android OTA payload dumper on Android
Introduction This tutorial will teach you how to specifically extract the boot.img from your OTA/ROM's payload.bin on your Android device, rather than a computer. In addition to this, you will also have the ability to access all other img files...forum.xda-developers.com
Don't know why LOS doesn't host the image files for root users; perhaps they make it difficult intentionally as Magisk makes prop spoofing etc easy and the have strict anti-spoofing policies etc... or perhaps some other reason, I don't know. PW
Keep giving away the important ones...
That one's sure to help me (and others) in future. (My last LOS had boot.img in root of zip IIRC.)
Edit: Found this tutorial for PC also (Uses Payload Dumper Tool and Python to extract firmware files including boot.img):
And here's one to extract using phone!:![]()
How to Extract payload.bin and get stock boot image file - DroidWin
To extract the payload.bin file from stock firmware and get the stock boot image file, you should refer to the instructions given in this guide.www.droidwin.com
![]()
[Tutorial] Android OTA payload dumper on Android
Introduction This tutorial will teach you how to specifically extract the boot.img from your OTA/ROM's payload.bin on your Android device, rather than a computer. In addition to this, you will also have the ability to access all other img files...forum.xda-developers.com
Don't know why LOS doesn't host the image files for root users; perhaps they make it difficult intentionally as Magisk makes prop spoofing etc easy and the have strict anti-spoofing policies etc... or perhaps some other reason, I don't know. PW
read the changelog which can be found here https://topjohnwu.github.io/Magisk/releases/22000.htmlBut boot.img for magisk update must be original from stock image or a arleady boot IMG patched by Magisk ?
Can some One explain how to update from 21.4 to 22 cause disaster i made Yesterday ?
Thank you
I had same corrupted boot.img thru update (froze during direct update, looped to fastboot after I restarted phone) fixed by fastboot flashing working boot image previously patched w/ earlier Magisk.But boot.img for magisk update must be original from stock image or a arleady boot IMG patched by Magisk ?
Can some One explain how to update from 21.4 to 22 cause disaster i made Yesterday ?
Thank you
hey, i just updated to 22.0 now when i open magisk i get a warning that says - abnormal state running this app as system app is not supported, please revert the app to a user app.
The thing is magisk came built-in in my rom. Should i revert older version?
Is there a flashable zip for the new version? - ok rename new version apk file to zip. gonna try flashing, maybe it would fix my problem.
No luck, same error but it seems to be working though.
Edit-
my rom has been abandoned for some time now.
So i booted in recovery and deleted the magisk folder from system/app. i reflash magisk 22.0 and booted. the error is gone now and magisk "seems" to be working as normal. Could it be that simple or do you think ill encounter problems later on?
It's now Magisk-v22.0.apk, not zip unless renamed.where can i find the latest magisk.zip for the samsung a530f?
Yep, i was using that one, and it made apps recognise root(btw i'm using mcdonald's app for testing hiding root from apps which detects it, as i was suprised that trivial app for some reason is that complexed and made to search for anything like bank apps, even for busybox as i now found out), so i hope magisk module busybox will hide it better, now will wipe phone and put everything again, and test it with module xDbusybox is "must have" application if you are rooted .. like for instance
Titanium Backup would not work without it
also the most infamous game hacking apps for android Lucky Patcher would not work correctly aswell without it ...
i recommend this https://play.google.com/store/apps/details?id=stericson.busybox it's free and does the job
also if i remember correctly there's a busybox magisk modules never tried it thou
Если у вас установлен magisk, вам больше не нужен SuperSu + pro. вы можете управлять рутированным приложением внутри magiskSuperSu+pro версия,не запустится Magisk.Пишет ошибка при загрузки файла,любого.SuperSu затребовал обновления что и сделал,потом сам перезагрузил.сторонний канал невкючать написано.загружать файлы по другим каналам.
SuperSu+pro версия,не запустится Magisk.Пишет ошибка при загрузки файла,любого.SuperSu затребовал обновления что и сделал,потом сам перезагрузил.сторонний канал невкючать написано.загружать файлы по другим каналам.
Если у вас установлен magisk, вам больше не нужен SuperSu + pro. вы можете управлять рутированным приложением внутри magisk
Thats a useful option I haven't considered for some time!If you have a working TWRP you should be able to backup the boot-partition and patch the image-file from backup with Magisk.
Yes"dual Magisk": Did you try to put Magisk in *both* boot and recovery?
See this log for patching recovery image (Recovery mode checked):I do not understand "ANY attempt to flash Magisk to recovery finds recovery's 'stock boot image' and patching succeeds": What is "find", and what is "succeeds"?
- Device platform: arm64-v8a
- Installing: e136fb3a (22102)
- Copying image to cache
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
****************************
Output file is written to
/storage/emulated/0/Download/magisk_patched-22102_xumwp.img
****************************
- All done!
You said Xiaomi. I have a Samsung.
But recovery ramdisk and boot ramdisk are implemented differently.I agree the bootloader supports ramdisk. As I quibbled with you earlier, I believe that it is the kernel that may or may not look for / use a ramdisk: it's the same bootloader, whether you boot boot or boot recovery, so if recovery always has a ramdisk, the bootloader always supports ramdisk.
As I understand it, to use any ramdisk type requires ramdisk specific bootloader support. Kernel and ramdisk can be patched, but bootloader (again, generally) cannot be, due to proprietary nature.Or the bootloader doesn't even know about ramdisk, and the kernel finds the ramdisk at the end of what the bootloader thought was kernel. Of course, there could be a flag in the kernel's meta-data that tells the bootloader not to bother doing ramdisk stuff, but that would still be a matter of the *kernel* choosing to not allow ramdisk.
Yep, understand that.I agree that it seems to be possible to install Magisk in boot on my device.
I do not believe that I have Magisk in boot -- I told you I had to boot repeatedly before hitting the sweet spot that caused Magisk to activate.
Covered by @zgfg.I do not know if my version of Magisk Manager has a reboot option, but I would be afraid to try to use it to get back to Magisk active from Magisk inactive. I would expect the Manager to need root privilege to trigger a reboot, let alone to trigger a reboot to recovery. Are those really things that Android will allow an unprivileged app to do?
Magisk shows Error when checking SafetyNet, not Fail.Re Google SafetyNet changes:
Not sure what's going on yet, but basicIntegrity fail imay be good sign fix may not be too difficult; this has usually been achieved fairly easily.
Of course, it may well be Bootloader / Hardware key Attestation related too. In this case, the fun may well be over... PW
At the end of 2019, when I got my Xiaomi Mi 9T, I think it was MIUI 10/Pie and Magisk v19 or v20, I searched how to root.Well, tried to test dual Magisk on my RN8T (Ramdisk = no), but more surprises: ANY attempt to flash Magisk to recovery finds recovery's 'stock boot image' and patching succeeds, but booting fails with 'System Has Been Destroyed'; Fastboot only available.(flash stock recovery fixes). Not sure what the problem is with recovery-ramdisk, but understand other Xiaomi users have also failed to gain root by official Ramdisk= no method also. Fortunately, it generally works with boot-ramdisk.
I've tried builds from latest back to 20.3 with same results... Must try patching custom recovery.img soon!
I'm not sure of anything either (now more so), but still strongly suspect your device has boot-ramdisk bootloader support (despite no factory boot-ramdisk) like mine, and that after Magisk patching adds basic missing boot-ramdisk with Magisk-init (working since this commit: https://github.com/topjohnwu/Magisk/commit/e72c6685edf81706617a3444575c4500b9b8fe6c ), Magisk in boot works. If reports of .zip installer from twrp working are true I think this MUST be the case.
Not sure if this does account for booting to Magisk without recovery key combo for you, but I think it could.
I noticed using reboot from Magisk App boots to recovery after checking Recovery mode too. I'm guessing that when system is able to boot from recovery w/ Magisk, this should get one back to back to system with Magisk in recovery.
I just can't see how this could work after normal power off. From this state, the kernel directly mounts the system partition as rootdir and exec /init to boot (ie. SAR). Kernel doesn’t need initramfs (ie. ramdisk) to boot Android (because rootdir is in system), and there is NO ramdisk in boot partition to access... unless it is added manually...
But I certainly could be missing something... PW
I believe it was 20.4Does anyone know which version of Magisk still has the "Install in to inactive Slot (AfterOTA)? I know it was removed temporarily, having a difficult time finding the version before it it was removed.
I have 22.1 installed and it's thereI believe it was 20.4
Looks like you have /dev/bootimg as your real partition location and it is still higher in the list in util_functions.sh like how I fixed it in the linked commit, so this is definitely a regression from some other recent change to Magisk.. sigh, I'll look into it.@osm0sis
Thank you for having an eye on that.
Did the "ls" twice, first from a TWRP-terminal in recovery, second from a terminal while phone is "up and running".
No, the phone is an Estar Takee1.
ROM is from here: Mikel Android 7 for Takee1
and is itself a port from this ROM: RidonOS for Micromaxx A311
You're right, sorry for that. Now here the installation log for canary-version:
- Target image: /dev/BOOT
- Device platform: armeabi-v7a
- Installing: f152b4c2 (22005)
nanddump: MEMGETINFO: Not a typewriter
Parsing boot image: [boot.img]
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
That was quick... Didn't even have to whisper your name three times in the mirror.
Boot image is here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84688655
And this is supposedly the install log:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84686805
And for good measure there's a Magisk log as well:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84695083
And some device info:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84689305