Magisk and Samsung with OREO - Magisk

Can be patched boot from samsung oreo firmware? It has lz4 extension and sais failed during patching process. Also is it possible to fix RMM state lock without flashing zip fix in twrp?

Related

I need help to Root my SM-M105F

Hello i have the Samsung Galaxy M10 SM-M105F.
I need to root the Phone for make Custom Rom or Edit the Scripts.
I have OEM Unlock the Bootloader and install the Unofficial TWRP with Odin From here
https://forum.xda-developers.com/ga...p-3-3-0-twrp-recovery-samsung-m10-sm-t3925243
TWRP work, but the System is in Bootloop.
Pls i need help to root My Device with working TWRP, System boot and Root
BlacklightMG said:
Maybe try flashing 'no-verity-opt-encrypt' and 'RMM Bypass' zip files?
EDIT: Flash Magisk zip too (it removes dm-verity), and format the data partition
Click to expand...
Click to collapse
It'll be rooted when you flash Magisk. And install the Magisk Manager APK too, to allow root control.
I actually rooted without TWRP by flashing the patched boot image generated from Magisk, and then performed a factory reset because file integrity couldn't be verified. But the Magisk binaries worked.
Amazing, can you pls Upload your Modified Bootloader for me and all People here ?
For make the Galaxy M10 open for users and Dev's.
Sorry for the late reply, but it's always better to do it yourself depending on what OTA update you are currently on. Download the firmware, extract the boot image and patch it with Magisk Manager. Then flash it with ODIN or Heimdall while in download mode. Then I had to factory reset because file integrity could not be verified. But the root was preserved.
BlacklightMG said:
Sorry for the late reply, but it's always better to do it yourself depending on what OTA update you are currently on. Download the firmware, extract the boot image and patch it with Magisk Manager. Then flash it with ODIN or Heimdall while in download mode. Then I had to factory reset because file integrity could not be verified. But the root was preserved.
Click to expand...
Click to collapse
Can you show us how to extract the boot image and patch it with magisk manager ?
I have on my SM-M105FD the Firmware 8.1.0 and Working Root.
Download the Firmware 8.1.0 on the PC and the AP File put on the Phone.
Download and install magisk apk on your Device and patch the AP in Magisk file.
flash the Firmware full with Odin but put on the AP Option the Patched AP file flash and work.
I have with Magisk install the Xposed Framework and install nice plugins.
My phone became stuck in a boot loop so i tried to go back but whenever i try to flash the stock rom through odin it says sw REV. Check fail (Bootloader) Device: 2, Binary 1
Iam Facing A Problem Kindly Guide Me Samsung Galaxy M10 Smm105f U2 Installed Twrp Rec
Iam Facing A Problem Kindly Guide Me
Samsung Galaxy M10 Smm105f U2
Installed Twrp Recovery With Odin
Wiped Data
Flashed Successfuy
No Verify Opt
Rmm State Bypass
And Magisk
Now I Want To Boot In System But After Booting In System Process Device Asking Me For A Password
"Ur device Is encrypted For Security Plz Type ur Pswrd "
Even I Haven't Locked Phone With Any Kind Of Privacy
And I Have Also Flashed A New Firmware But Problem is same it's Not Booting in System
It won't work on android 10, you have to switch to android 8.1,then try ?
DJSAJJAD said:
Iam Facing A Problem Kindly Guide Me
Samsung Galaxy M10 Smm105f U2
Installed Twrp Recovery With Odin
Wiped Data
Flashed Successfuy
No Verify Opt
Rmm State Bypass
And Magisk
Now I Want To Boot In System But After Booting In System Process Device Asking Me For A Password
"Ur device Is encrypted For Security Plz Type ur Pswrd "
Even I Haven't Locked Phone With Any Kind Of Privacy
And I Have Also Flashed A New Firmware But Problem is same it's Not Booting in System
Click to expand...
Click to collapse
It won't work on android 10, you have to switch to android 8.1,then try ?

secure download

I was previously able to flash stock image, then, magisk patched AP file, but now, magisk patched AP file, fails.
I have secure download ENABLED and a message:
Only, official released binaries are allowed to be flashed (BOOT).
What can I do to fix it?
I can flash modified boot image: https://forum.xda-developers.com/showpost.php?p=81770511&postcount=561
but can't flash TWRP or magiskpatched AP file using ODIN?
Can anyone help?
Secure download does not matter. {SOLVED}

Magisk patch on SM-A520F (Galaxy A5 2017) FAILED

Hello,
I've been using magisk for some time now and no problem until now. I recently updated my firmware to the last version and intended to update it and keeping magisk, but it didn't worked.
Every time I would flash magisk to the boot image by any mean, the system would boot and tell me "system was modified : press the nuke button to restore it (you will lose all your data lol)" or womething like that.
I was able to flash the stock update and get my phone working with the last firmware but magisk is not installed. I also installed TWRP without problems (helped me a lot to flash the stock boot.img and restore the phone).
I tried to install magisk using :
- Odin : Modified boot.img using magisk app and repacked as boot.img.lz4 in the AP file (with correct lz4 parameters)
- TWRP : Flashed modified boot.img from earlier
- TWRP : Flashed magisk ZIP directly
- Odin : Flash full AP modified by Magisk app
Every time, I have that black screen that tells me my system will be wiped if I continue. Magisk, Odin or TWRP do not return any error
Feel free to ask for any file or further info and thank you for your help !
Firwmare version is A520FXXUGCTKA_CL19831441_QB36271825_REV00
Magisk app returns :
- Ramdisk YES
- A/B NO
- SAR NO
Did you try after you install the new rom through Odin, then instal Twrp and then in Twrp you Format data(not wipe) then immediately install magisk. If dosen't work try with another firmware.
I never update firmwares if there isn any visible difference. Mostly is always some security fixes which i dont care about.
hey, Im having a different issue where after installing lineage 18.1 on my a5 i flashed the latest magisk but once i got in the phone it cycled into a bootloop and now it's eternally turned off cant even turn it into twrp. any suggestion?

So I can't root my M31s due to KG State Prenormal after first reboot with "Only Official Binaries are allowed..." on screen

M31s on latest January Patch. Tried using magisk from twrp, flashing magisk patched image through ODIN and also, removing KnoxGuard.apk
I'm at the end of my wit. Has somebody been facing the same issue?
Fixed it by flashing PrishKernel for M31s at the end of flashing Magisk

Question Orange state Oneplus 10 pro NE2211

I had received incremental Update which I went through with. Then after incremental update was done, Downloaded the full ROM from oxygen updater and flashed patched boot, vendor boot and disabled dm-verity with vbmeta. Now the phone still shows orange state after flashing the patches and vbmeta. Is it because I rooted the phone on an incremental update? Will flashing the full zip (same version) and then rooting work? Or will it brick the phone. Will the orange state message go away if I do a full zip flashing via local update and then disable dm-verity with vbmeta. Please help me
Currently on NE2211_11_C.22
sinduchari said:
I had received incremental Update which I went through with. Then after incremental update was done, Downloaded the full ROM from oxygen updater and flashed patched boot, vendor boot and disabled dm-verity with vbmeta. Now the phone still shows orange state after flashing the patches and vbmeta. Is it because I rooted the phone on an incremental update? Will flashing the full zip (same version) and then rooting work? Or will it brick the phone. Will the orange state message go away if I do a full zip flashing via local update and then disable dm-verity with vbmeta. Please help me
Currently on NE2211_11_C.22
Click to expand...
Click to collapse
same with me, after check with fastboot oem device-info the device is unlocked
Wrong thread. Sorry.

Categories

Resources