I'm try to root that new firmware. No method working now. Not work patching boot.img with magisk and flash in AP Not work flash empty Vbmeta with boot img patched with Magisk. Not work to flash twrp-3.7.0_12 by Afaneh92, multidisabler, FORMAT with YES on data partition. Nothing work. After all that...restart, restart, restart. the phone not boot.
What version of Magisk are you using and where did you download it from? Flashing Magisk 25.2 in TWRP should work fine.
Kernel Sources aren't released yet. So there is no way to root it yet. Stick to the Jan Patch for now.
V0latyle said:
What version of Magisk are you using and where did you download it from? Flashing Magisk 25.2 in TWRP should work fine.
Click to expand...
Click to collapse
In this 3 days I flashed Magisk 25.2, Magisk Canary to try, not of this is working correct at all. There is no meaning what I flash and which order. Just restart.
JazonX said:
Kernel Sources aren't released yet. So there is no way to root it yet. Stick to the Jan Patch for now.
Click to expand...
Click to collapse
Ok, but how to downgrade the bootloader, because ODIN not flash the older firmware, issue some error. Patched one ODIN too.
Vishnarov said:
Ok, but how to downgrade the bootloader, because ODIN not flash the older firmware, issue some error. Patched one ODIN too.
Click to expand...
Click to collapse
bootloader downgrade is not possible
Run stock firmware clean for now; until a solution is made. I'm sure @afaneh92 will come up with something after the kernel sources are out.
JazonX said:
Run stock firmware clean for now; until a solution is made. I'm sure @afaneh92 will come up with something after the kernel sources are out.
Click to expand...
Click to collapse
I will. I have no choice
Vishnarov said:
I will. I have no choice
Click to expand...
Click to collapse
Patch ap file with magisk and Flash via odin like normal whole firmware
Just Installed 5.1 on my S22U (S908E) and prepared a ROM as usual. Magisk 25.2,TWRP,Decryption everything works as it is on 5.0 ROM
I have no reason to believe anything will be different on S908B
Even Magisk 25.2 works on S23Ultra too. (I have my pre-rooted ROM already with magisk 25.2 for S23U) just needs manual patch but that's only for S23U, not needed for S22U, even TWRP works pretty fine and yet we don't have kernel source. OneUI 5.1 is no much different than 5.0
dr.ketan said:
Just Installed 5.1 on my S22U (S908E) and prepared a ROM as usual. Magisk 25.2,TWRP,Decryption everything works as it is on 5.0 ROM
I have no reason to believe anything will be different on S908B
Even Magisk 25.2 works on S23Ultra too. (I have my pre-rooted ROM already with magisk 25.2 for S23U) just needs manual patch but that's only for S23U, not needed for S22U, even TWRP works pretty fine and yet we don't have kernel source. OneUI 5.1 is no much different than 5.0
Click to expand...
Click to collapse
Thanks for this confirmation, So I assume only a permissive kernel is missing and that's only required for System R/W ?
Regardless of that, the existing TWRP, Magisk works to get a rooted 5.1 ?
JazonX said:
Thanks for this confirmation, So I assume only a permissive kernel is missing and that's only required for System R/W ?
Regardless of that, the existing TWRP, Magisk works to get a rooted 5.1 ?
Click to expand...
Click to collapse
Yes if you planning to run multidisabler or system-rw script, you must needed to flash permissive kernel and that's what probably OP is missing.
Alternatively, flash system-rw custom ROMs
dr.ketan said:
Just Installed 5.1 on my S22U (S908E) and prepared a ROM as usual. Magisk 25.2,TWRP,Decryption everything works as it is on 5.0 ROM
I have no reason to believe anything will be different on S908B
Even Magisk 25.2 works on S23Ultra too. (I have my pre-rooted ROM already with magisk 25.2 for S23U) just needs manual patch but that's only for S23U, not needed for S22U, even TWRP works pretty fine and yet we don't have kernel source. OneUI 5.1 is no much different than 5.0
Click to expand...
Click to collapse
I wonder how is happen this, but obvious is truth as soon as you say that , because Im not new in flash processes and Im doing what is do in previous firmware when rooted the stock ROM, the same flash and everything , but the things is going to wrong way , just infinite reboot. Flashed new firmware 5 times with Odin and tried everything. Last I must to try to flash AP Magisk patched and whole firmware with it just like Be_Cruel said above .
Vishnarov said:
I wonder how is happen this, but obvious is truth as soon as you say that , because Im not new in flash processes and Im doing what is do in previous firmware when rooted the stock ROM, the same flash and everything , but the things is going to wrong way , just infinite reboot. Flashed new firmware 5 times with Odin and tried everything. Last I must to try to flash AP Magisk patched and whole firmware with it just like Be_Cruel said above .
Click to expand...
Click to collapse
If you are flashing TWRP and run multidisabler OR run system-rw script, you will have bootloop because this requires custom kernel which is not available yet for OneUI 5.1
Magisk Patching AP will 100% work (without TWRP), do this
Patch AP file with magisk
Flash patched AP file with other BL CP and CSC file (use CSC* instead of HOME_CSC as this will auto format device) and all should be good
dr.ketan said:
If you are flashing TWRP and run multidisabler OR run system-rw script, you will have bootloop because this requires custom kernel which is not available yet for OneUI 5.1
Magisk Patching AP will 100% work (without TWRP), do this
Patch AP file with magisk
Flash patched AP file with other BL CP and CSC file (use CSC* instead of HOME_CSC as this will auto format device) and all should be good
Click to expand...
Click to collapse
One of the things what I does was to flash clean firmware, ,TWRP with Vbmeta, multidisabler, format Data with YES, and flashed Magisk after that. Again bootloop.
Can I flash clean firmware, Vbmera with TWRP and Magisk without multidisabler and format data ?
Lastly I should do what you said to flash magisk patched AP with all firmware.
Vishnarov said:
One of the things what I does was to flash clean firmware, ,TWRP with Vbmeta, multidisabler, format Data with YES, and flashed Magisk after that. Again bootloop.
Can I flash clean firmware, Vbmera with TWRP and Magisk without multidisabler and format data ?
Lastly I should do what you said to flash magisk patched AP with all firmware.
Click to expand...
Click to collapse
TWRP without multidisabler have limitation, you won't able to make data backup nor can store other backup to Int storage
You have following optios before permissive kernel available for 5.1
- Flash TWRP without multidisabler or system-rw script (Limites TWRP use, No system-rw)
- Patch Magisk with AP and flash as said above (No TWRP)
- Go with custom ROM which support full TWRP+system-RW
Ok, I will try, but to mention for the last you said...No old ROM (not yours nor enything else) want to begin to install with the newest bootloader. TWRP issue a warning that want the older bootloader to install your ROM, for instance...Something as "You must be to S908BXXS2BWA2 formware to install this.
Vishnarov said:
Ok, I will try, but to mention for the last you said...No old ROM (not yours nor enything else) want to begin to install with the newest bootloader. TWRP issue a warning that want the older bootloader to install your ROM, for instance...Something as "You must be to S908BXXS2BWA2 formware to install this.
Click to expand...
Click to collapse
My OneUI 5.1 Full rom for S908E is available, for S908B it is under internal testing, will be public soon
dr.ketan said:
My OneUI 5.1 Full rom for S908E is available, for S908B it is under internal testing, will be public soon
Click to expand...
Click to collapse
When you ROM be done, will try. I tried to flash magisk patched AP with all the rest firmware , nothing, again reboot. Tried
GSI ROM ,again reboot, reboot. I can not figure out what is happening. Work just stock firmware
@
dr.ketan said:
My OneUI 5.1 Full rom for S908E is available, for S908B it is under internal testing, will be public soon
Click to expand...
Click to collapse
hello Dr.ketan
i have been using your roms Note 3, Now I had been to US An d purchased Galaxy S22 Ultra and returned to India Last week tried inserting Jio sim, to my shock 5G don't work on it, tried searching solution but in vain, couldn't find anywhere ! any help from you side will appreciated .
Thank-you
Regards
Related
Can anyone upload a Magisk patched boot image for 10.0.1GM57AA? The model that I have is GM1900. When I try to patch it myself on Magisk, I get an error saying "process error"
Anyone able to help?
Heelixx said:
Anyone able to help?
Click to expand...
Click to collapse
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
meltbanana said:
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
Click to expand...
Click to collapse
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Heelixx said:
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Click to expand...
Click to collapse
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
meltbanana said:
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
Click to expand...
Click to collapse
I flashed the 4.14.117-perf+.img that you uploaded and then I booted in TWRP and flashed my original stock boot image. While still in TWRP, I flashed the zip of Magisk and then I rebooted. That got it working. So I'm rooted now. Thanks for sending me the image. I appreciate it!
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
lvints said:
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
Click to expand...
Click to collapse
I was rooted on 10.0 and then I upgraded to 10.0.1
There is a procedure for upgrading to 10.0.1 and still keeping root. I wasn't aware of this and after I got the update, I restarted my device and ended up without root access.
A Magisk patched boot image is important for getting your device rooted.
If you're asking for the procedure to root your device, then you can follow this link which explains it, https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
How can i install an OTA update and maintain root ?
I have rooted using TWRP 3.5 and Magisk 22
I've found several instructions using the “TWRP A/B Retention Script”
but since the Samsung A8 (2018) has an A-Only (or non A/B) partition scheme
i am left in the dark ...
ReMiOS said:
How can i install an OTA update and maintain root ?
I have rooted using TWRP 3.5 and Magisk 22
I've found several instructions using the “TWRP A/B Retention Script”
but since the Samsung A8 (2018) has an A-Only (or non A/B) partition scheme
i am left in the dark ...
Click to expand...
Click to collapse
Why not download and flash firmware updates manually?
For me, official OTA updates are often too late. I want to install an update as soon as I can get my hands on it.
It_ler said:
Why not download and flash firmware updates manually?
For me, official OTA updates are often too late. I want to install an update as soon as I can get my hands on it.
Click to expand...
Click to collapse
Seems like a good idea, but how can i install a OTA manually ?
ReMiOS said:
Seems like a good idea, but how can i install a OTA manually ?
Click to expand...
Click to collapse
I use Frija (https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/) to check for and download latest stock Samsung firmware files. Then I use Odin to flash it to my phone.
It_ler said:
I use Frija (https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/) to check for and download latest stock Samsung firmware files. Then I use Odin to flash it to my phone.
Click to expand...
Click to collapse
Thanks for your reply
When using Frija and Odin wil this wipe my data ?
Or will the phone-data be untouched and also the TWRP Root (Magisk) ?
ReMiOS said:
Thanks for your reply
When using Frija and Odin wil this wipe my data ?
Or will the phone-data be untouched and also the TWRP Root (Magisk) ?
Click to expand...
Click to collapse
Downloading with Frija does nothing on your device.
Flashing firmware files with Odin will overwrite the corresponding system partitions ... and when flashing another CSC file, you may have to wipe data partition to get the device rebooting into system again.
But as long as you do not flash another CSC file (I always use Home_CSC file to stay on my current CSC), data partition will not be overwritten or wiped.
Concerning root / Magisk IDK. If you have changed something in system partitions for rooting the device, this may be overwritten by flashing the stock Samsung firmware. In this case, you will have to do the needed changed again for rooting the device.
As I am not rooted with Magisk ATM, I am not familiar with the exact steps. I heard about "patching" a system file, but better to ask someone more familiar with rooting with Magisk.
BTW... after flashing stock firmware, will have stock recovery. No more TWRP. If you want/need it back, you will have to flash TWRP recovery again afterwards.
It_ler said:
Downloading with Frija does nothing on your device.
Flashing firmware files with Odin will overwrite the corresponding system partitions ... and when flashing another CSC file, you may have to wipe data partition to get the device rebooting into system again.
But as long as you do not flash another CSC file (I always use Home_CSC file to stay on my current CSC), data partition will not be overwritten or wiped.
Concerning root / Magisk IDK. If you have changed something in system partitions for rooting the device, this may be overwritten by flashing the stock Samsung firmware. In this case, you will have to do the needed changed again for rooting the device.
As I am not rooted with Magisk ATM, I am not familiar with the exact steps. I heard about "patching" a system file, but better to ask someone more familiar with rooting with Magisk.
BTW... after flashing stock firmware, will have stock recovery. No more TWRP. If you want/need it back, you will have to flash TWRP recovery again afterwards.
Click to expand...
Click to collapse
GitHub - Magisk-Modules-Repo/twrp-keep: twrp-keep
twrp-keep. Contribute to Magisk-Modules-Repo/twrp-keep development by creating an account on GitHub.
github.com
It's called a TWRP retention script.
Hello,
I have problem with patch my boot.img with Magisk manager. After patching I got error : "The phone is not running Samsung's official software". After flash again stock boot.img everything works.
I use Odin to flash.
I tried to install unofficial TWRP from other thread but I got SVD Fail and vbmeta errors during boot.
Somebody have any idea how solve this problem?
Model : SM-A127F/DSN
Baseband version : A127FXXU2AUG7
Android 11 (UI 3.1)
Info from download mode :
KG STATE : Checking
FRP LOCK : OFF
OEM LOCK : OFF(U)
Secure Download : Enabled
RP SWREV : B:2 K:2 S:2
I found similar situation on movie :
But for me recovery mode and factory reset not solve problem. Phone stuck on "Samsung's official software" and reboot after a few minutes.
Best Regards
Patch the boot image of the fimware your phone is currently running.
I used the same boot.img and instructions from This thread
In attachment magisk patching log
I solved this problem by This thread
SM-A127F have a different hardware than for example SM-A125F and working on Exynos 850 the same as Samsung A21s.
Magisk 23 still not working.
Regards
cryptoranger said:
I solved this problem by This thread
SM-A127F have a different hardware than for example SM-A125F and working on Exynos 850 the same as Samsung A21s.
Magisk 23 still not working.
Regards
Click to expand...
Click to collapse
I have same phone A127
Do you rooted your device now ?
If yes how do you root device ?
And thank you
khaledoghlo said:
I have same phone A127
Do you rooted your device now ?
If yes how do you root device ?
And thank you
Click to expand...
Click to collapse
Hi, Yes I have root on this device !
It's very simple, but official Magisk have a bug which prevents the device from booting properly and your phone will be stuck with in bootloop.
1. You must get custom patched Magisk (jn attachment) - from This thread and install it on phone.
2. Get your original firmware from : https://samfw.com/firmware/SM-A127F
3. Unpack your firmware and upload AP_XXXXX file on phone and patch it with magisk.
4. Flash with ODIN and done
You have full instruction : Here but I recommend patch full AP_XXX file not only boot.img. Full AP patch It will allow you to turn off DM-Verity immediately and trouble with vbmeta.
SAMSUNG A127F/DS ROOTED FIRMWARE
Samsung A127F rooted firmware Bit2 hang on logo fixed file is free Enjoyhttps://drive.google.com/file/d/1hX8Jv2FlHHiWWhclqhNEbWncMyO8yiFb/view?usp=sharing
ultratechgeek.com
Here is the pre Rooted firmware buy Ultratech geek Team
you can download free via google drive link
no password
tested by me Working 100%
cryptoranger said:
Hi, Yes I have root on this device !
It's very simple, but official Magisk have a bug which prevents the device from booting properly and your phone will be stuck with in bootloop.
1. You must get custom patched Magisk (jn attachment) - from This thread and install it on phone.
2. Get your original firmware from : https://samfw.com/firmware/SM-A127F
3. Unpack your firmware and upload AP_XXXXX file on phone and patch it with magisk.
4. Flash with ODIN and done
You have full instruction : Here but I recommend patch full AP_XXX file not only boot.img. Full AP patch It will allow you to turn off DM-Verity immediately and trouble with vbmeta.
Click to expand...
Click to collapse
Thanks for this.
I just bought this phone and looking forward to building a custom kernel for it.
marrygsm said:
SAMSUNG A127F/DS ROOTED FIRMWARE
Samsung A127F rooted firmware Bit2 hang on logo fixed file is free Enjoyhttps://drive.google.com/file/d/1hX8Jv2FlHHiWWhclqhNEbWncMyO8yiFb/view?usp=sharing
ultratechgeek.com
Here is the pre Rooted firmware buy Ultratech geek Team
you can download free via google drive link
no password
tested by me Working 100%
Click to expand...
Click to collapse
Nice work
Thanks for the root method.
I've discovered that this phone has the same set of CPU frequencies for big and little
Twrp and custom kernels now being developed.
I'll post as soon as they have been tested.
ROOTed ROM for Galaxy A12 A127F A127FXXU2AUH4 (magisk) (OS11)
AP > https://drive.google.com/file/d/1o4qJCAkqZJ7AmakJ4jcGLsCchTeN9VF7/view?usp=sharing
BL > https://drive.google.com/file/d/1W8BBaNND401qeGFV5chqX6jaE1e9P__Q/view?usp=sharing
CP > https://drive.google.com/file/d/1negTtWBj7pcR0NrW8T_k0Onthc_O-Ac_/view?usp=sharing
CSC > https://drive.google.com/file/d/1_cvoKKUunfjHxBQ1T2Tvtb_ASBPWxaZe/view?usp=sharing
HOME CSC > https://drive.google.com/file/d/1oCYzRTONa2JezHsWxkrPppnwvRNWBYWF/view?usp=sharing
PS . flash patched versions odin3 ... uncheck autoreboot ... manual reboot device when flash finished.
DONE !
Bonus > back original state > boot.img vbmeta.img
boot_vbmeta_orig_auh4_tar.tar
drive.google.com
Twrp and custom kernel now available
physwizz said:
Twrp and custom kernel now available
Click to expand...
Click to collapse
really ? working ?
hesen_89 said:
really ? working ?
Click to expand...
Click to collapse
Yep
See my kernel thread
[ROOT] [TWRP] [KERNEL] [GSI] for SM-A127f (a12s)
Root Method https://forum.xda-developers.com/t/root-for-all-exynos-850-devices.4367799/ Twrp and Kernel https://forum.xda-developers.com/t/custom-kernel-and-recoveries-for-m127f.4361841/ Latest twrp...
forum.xda-developers.com
physwizz said:
Yep
See my kernel thread
Click to expand...
Click to collapse
install twrp but not kernel
kernel need install or not ??
Thanks . great work
hesen_89 said:
install twrp but not kernel
kernel need install or not ??
Thanks . great work
Click to expand...
Click to collapse
kernel dont working ( how i install old kernel ?? i cant find it
hesen_89 said:
kernel dont working ( how i install old kernel ?? i cant find it
Click to expand...
Click to collapse
What do you mean?
hesen_89 said:
kernel dont working ( how i install old kernel ?? i cant find it
Click to expand...
Click to collapse
Not exactly sure, maybe physwizz confirm, I presume, you tried install kernel file by Install button in TWRP. I tried it too, failed it too and
a) you have done backup in TWRP, thats usual reason to setup TWRP - you just in case backup those special partition and if you done it, restore boot from backup will help
b) really not sure about that, but Odin, button BL and flash BL file from original stock ROM.
Can anybody advanced confirm? Maybe it can be helpful to know exactly, what for sure are kernel (AFAIK part of boot partition), "bootloader" and "boot" partion, BL button in Odin
honzazkrumlova said:
Not exactly sure, maybe physwizz confirm, I presume, you tried install kernel file by Install button in TWRP. I tried it too, failed it too and
a) you have done backup in TWRP, thats usual reason to setup TWRP - you just in case backup those special partition and if you done it, restore boot from backup will help
b) really not sure about that, but Odin, button BL and flash BL file from original stock ROM.
Can anybody advanced confirm? Maybe it can be helpful to know exactly, what for sure are kernel (AFAIK part of boot partition), "bootloader" and "boot" partion, BL button in Odin
Click to expand...
Click to collapse
can't do another type. yes i did that type. but twrp does not work and does not mount any unit. install fails. I returned everything. deleted
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Than
Click to expand...
Click to collapse
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
Click to expand...
Click to collapse
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
hammered58 said:
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
Click to expand...
Click to collapse
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
¿GotJazz? said:
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
Click to expand...
Click to collapse
1. Yes that is the app Iam talking about.
2. Will you lose data? I always do a format (after the down grade) so I lost data but I never tried it with out formating, it might work, you could try it and see what happens .If it acts strange then it will need a format.
3. Yes you install 11.04 via twrp
4. Yes you will get root but if you want twrp you will have to reinstall
Once you down grade install the oxygen updater, let it download the update , don't let it install it, you can then grab the update from your root directory as it doesn't hide it, then your good to go, you can extract the boot.img by using payload dumper, then take the boot.img and patch that with the magisk app . ( Just install the magisk app on your downgraded 11.04 you don't need root to run the app ) ,,Then after your thru upgrading to 11.05 and after setup just reboot to bootloader and run the magisk patched boot.img, ( fastboot flash boot boot.img) reboot and wait a minute for the magisk app to appear ,it will want to install and do a reboot . Then you can install twrp if you want.
This is how I did it and it worked, you may find a simpler way once you start doing it ,, hth
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
¿GotJazz? said:
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
Click to expand...
Click to collapse
Right now I have 11.05 installed and Iam rooted, tomorrow I will unroot and downgrade to 11.04 without wiping and let you know what happens iam curious myself
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
¿GotJazz? said:
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
Click to expand...
Click to collapse
I guess that's possible , I never thought of that, the only way to know is to do a fresh install only this time setup encryption then try to install magisk . But for now your rooted,, until the bug hits you or me to try another rom then we can start the whole thing over again,,
So I see a lot of people using magisk patched boot images that are really old. It'd be better to patch the image yourself from magisk and use that. The problem might be that it's not that easy to extract it.
You can find most of the stuff from stock rom extracted by me here. The files were extracted from the Indian varient. Make sure to use the appropriate files for your stock rom. The index site does have other files like some old and unstable kernels so don't go flashing everything you see from the root directory. This just started as a personal archive. The domain is free, so idk how long it'll stay active either.
As always, use everything at your own risk.
Do Magisk versions newer than v24.3 work this way?
newt23 said:
Do Magisk versions newer than v24.3 work this way?
Click to expand...
Click to collapse
Yes, patching the boot image is the recommended way to install Magisk.
The official guide does ask to patch AP wholly for samsung devices, but patching the boot image itself is faster.
Official Guide
I don't understand why I get bootloops if I update to v25.x from v24.3 from the Magisk app (using direct method). As I understand it, it also (re-)patches the boot image.
newt23 said:
I don't understand why I get bootloops if I update to v25.x from v24.3 from the Magisk app (using direct method). As I understand it, it also (re-)patches the boot image.
Click to expand...
Click to collapse
That's how I updated too. Try flashing the magisk zip directly.
Or, only update the magisk app, patch the boot image, rename it as boot.img, put it in a tar file, and then flash it to "AP" using Odin.
Hmm... this is funny. I patched the stock boot image and flashed it using Odin and still got bootloops. I took a full nandroid backup beforehand so I was able to get everything working by flashing TWRP again and restoring the previous boot image.
I get bootloops if I install v25.x from TWRP after installing a rom or update to v25.x from v24.3 directly or by patching the stock boot image. The only one that's left now is flashing v25.x zip from TWRP (while having a functioning system with v24.3) but something tells me it's going to end in bootloops too.