Related
I ask before in "guide to root motorla g stylus":
really is no way to work OTA while Magisk installed? i mean some Magisk Hide Props Config, or not install TWRP or anything? i actualy have Nokia 7 Plus (unlocked via unoficial method) and last year while not installed TWRP is possible check system update, install over air (while Magisk is installed), before reboot run MagiskManager, install Magisk to other slot, reboot, started from updated slot with Magisk installed, without need flash stock boot img before ota and flash manualy patched boot img after OTA... sure have Moto G Pro additional check or limitation and this not work? thanks...
Click to expand...
Click to collapse
without reaction, then try make separated thread, i actualy have one week "Motorola Moto G Pro" (XT2043-7), rooted, and wait for OTA, UpdateCheck in Settings not show me, try LMSA Rescue/Download and show me same version as have installed QPRS30.80-109-2-7...
Questions:
- Have any user of same phone, without root, already showed Octorber OTA?
- Is on rooted posible UpdateCheck with show if OTA avaiable?
- Have any working solution for OTA update on rooted phone without need connected with PC? Similar or same as i write about Nokia7Plus?
(i mean without flash back stock img, make ota, patch new boot.img file in MagiskManager, flash it via TWRP booted...
i think without PC be sure posible flash back stock boot.img to boot partition, before OTA, maybe download zip of full "rom" and extract boot.img, patch via MagiskManager, but not flash patched
EDIT: Sollution here
The answers to your first two questions are yes. When on stock I successfully updated. And while rooted there was a notification for ota update, it would download, but fall to install. I came across a way to do it without having to connect to pc. Some said it was successful but I was not able to try. It has something to do with placing your original boot.img into a a folder on one of the root directories but I had no idea how in the hell they came up with the system path to the file (encrypted??) Because I didn't have any of the folders on my phone and was to lazy at the time to ask for help. It was also an older thread so I didn't feel like bringing up a thread that old.
without root you updated system to higher (with Ocrober security patches) version than QPRS30.80-109-2-7 (this version have September security patches) ?
second part of you answer i think not understand, with rooted phone, put boot.img in "a" directory in one (which?where?) root folder and OTA services flash it before upgrade/reboot???
please, anyone with "Motorola Moto G Pro" (XT2043-7), channel "reteu", have already displayed update notification for "QPRS30.80-109-2-8" ?
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Very nice writeup. With respect to step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image? With respect to step 5, how do I get to that point? Is it a prompt after rebooting?
flroots said:
[...] step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image?
Click to expand...
Click to collapse
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
flroots said:
[...] step 5, how do I get to that point? Is it a prompt after rebooting?
Click to expand...
Click to collapse
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
k3dar7 said:
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
Click to expand...
Click to collapse
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
k3dar7 said:
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
Click to expand...
Click to collapse
Thanks
flroots said:
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
Click to expand...
Click to collapse
Understand, but as i write, you must have installed Magisk via TWRP, with this method, Magisk make backup of boot image to "/data/magisk_backup_SomeRandomStrings/boot.img.gz", this file is used when you doing step 3, but if you only patch stock boot file, then ofcourse this backup is not created... i sugest you:
- revert boot to stock via same way as you flash patched before, but using stock boot.img
- boot TWRP (NOT flash, use command is section "Boot") and install Magisk.zip oficial release
- if on your phone/touchscreen variant not work touchscreen in TWRP, then (while still is booted TWRP) install it using adb
Thanks.
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
flroots said:
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
Click to expand...
Click to collapse
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
2. not sure, i not use LMSA
k3dar7 said:
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
Click to expand...
Click to collapse
Thanks, that sounds great. Would you mind elaborating the steps involved? I have TWRP and Magisk installed now.
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Do these steps cause loss of data? Thanks
flroots said:
Do these steps cause loss of data? Thanks
Click to expand...
Click to collapse
i ofcourse not garant ;-) but for me nothing lost, also installed magisk modules is preserved...
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
flroots said:
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
Click to expand...
Click to collapse
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
k3dar7 said:
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
Click to expand...
Click to collapse
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
flroots said:
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
Click to expand...
Click to collapse
maybe magisk backup boot.img have already twrp inside if you install twrp before magisk?
anyway, if you flash stock boot.img, then step 6&7 is not applicable, because this need booted rooted system
btw: method above work for me also while i upgrade from Android10 to Android11 ;-)
First off I'm not responsible for anything that happens to your device
Attached below is the patched image for OnePlus 9 global 11.2.6.6
Flash via fastboot
For support and faster answer look here
Thank you for this! Since Magisk removed the option for OTA install, I was forced to do it the harder way... But you my friend made it much easier on me ! Thank you!!
Sorry for newbie's question, what's the difference between the two files? one is stock and one is patched?
Yes. Stock has to be flashed to take next ota. And patched is for root on current rom. Since op9 now uses google ota if any partitions are modified including the boot image ,it will fail.
Jg1234 said:
Thank you for this! Since Magisk removed the option for OTA install, I was forced to do it the harder way... But you my friend made it much easier on me ! Thank you!!
Click to expand...
Click to collapse
When did they remove OTA install? Mine still has it....
illusiveairforce said:
When did they remove OTA install? Mine still has it....
Click to expand...
Click to collapse
Mine still there as well. But I like to flash stock boot image back. Take ota. Then fastboot boot patched.img. Dump current boot image to sd through shell. Then direct install in magisk. I've seen many users have issues taking ota's using the other method. As in not even being able to boot or booting back into old build . So I prefer this way. Wanna avoid the msm tool and not loose data on device/have to factory reset.
mattie_49 said:
Mine still there as well. But I like to flash stock boot image back. Take ota. Then fastboot boot patched.img. Dump current boot image to sd through shell. Then direct install in magisk. I've seen many users have issues taking ota's using the other method. As in not even being able to boot or booting back into old build . So I prefer this way. Wanna avoid the msm tool and not loose data on device/have to factory reset.
Click to expand...
Click to collapse
What are the shell commands to extract the stock boot?
Amd4life said:
What are the shell commands to extract the stock boot?
Click to expand...
Click to collapse
we are making a group for global only and help can be found there
Amd4life said:
What are the shell commands to extract the stock boot?
Click to expand...
Click to collapse
'dd' command in Linux - GeeksforGeeks
Edit- I got it, I had to flash original images and then updates showed up. Thanks for posting these images.
Hi, thanks for posting the images. I assume global as in the US AA model since that is the only model with OTA from googles server right? The reason I was asking is I am on 11.0.4.4 and never received the notification for the update yet, but using oxygen updater, when I go in settings and check advanced mode, it shows a incremental update. My system under local file of course can't see it or will not show the update. I figured I could fastboot boot the stock image and then maybe it system could see the update, but when I try, the device just hangs on the fastboot screen(right before normally booting). I tried with my image and it booted. Do you have any suggestions? Thanks
Steps as follows if on rooted 11.2.5.5
1. flash stock 11.2.6.6.img
2. install OTA
3. flash patched 11.2.6.6.img
4. profit
TheBurgh said:
Steps as follows if on rooted 11.2.5.5
1. flash stock 11.2.6.6.img
2. install OTA
3. flash patched 11.2.6.6.img
4. profit
Click to expand...
Click to collapse
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
You are correct my friend. One needs stock untouched boot image to be able to take next update. If your on 11.2.5.5 you need that boot image to get ota to install correctly. This 11.2.6.6 img if for next round of updates. Here is 11.2.5.5 for anyone that might still be on older build.
Stock 11.2.5.5.img
drive.google.com
netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
mattie_49 said:
You are correct my friend. One needs stock untouched boot image to be able to take next update. If your on 11.2.5.5 you need that boot image to get ota to install correctly. This 11.2.6.6 img if for next round of updates. Here is 11.2.5.5 for anyone that might still be on older build.
Stock 11.2.5.5.img
drive.google.com
Click to expand...
Click to collapse
Appreciate the input. I have been out of the game since the 6t so I am still trying to catch up
UPDATED POST
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.*
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img**
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*this step presupposes that Magisk has a STOCK boot.img to restore for the unroot procedure. If it does not have that, you're obligated to use the process described in post #11.
**you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
reaper000 said:
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img*
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
Click to expand...
Click to collapse
So doing it this method backs up stock untouched current boot image and reflashes during uninstall of magisk to allow ota to go through.? Since the op9 uses google ota all partitions have to be stock including boot image. Or it fails
reaper000 said:
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img*
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
Click to expand...
Click to collapse
this will fail
FizzyAps said:
this will fail
Click to expand...
Click to collapse
What's the command to flash the stock 11.2.5.5 boot.img? I tried renaming the boot_a.img the mattie_49 posted to boot.img but it would not flash.
TheBurgh said:
What's the command to flash the stock 11.2.5.5 boot.img? I tried renaming the boot_a.img the mattie_49 posted to boot.img but it would not flash.
Click to expand...
Click to collapse
Fastboot flash boot boot.img
mattie_49 said:
Fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks. Got the command to work this time. Tried a few times yesterday but had no luck
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
So, I installed the One ui 5 beta successfully although I am not on Indian region, but I can't live without root. There are too many magisk modules I rely on for daily use. However, since there is no AP file for one ui 5, i can't simply patch it and flash it.
So, what I am asking is if any of you can tell me any methods that might work, even if you haven't tried it.
Here are some of the things I tried so far and failed:
1. Tried patching the one ui 5 update.zip file but error.
2. Tried installing TWRP which worked but after I flash Magisk, it leads to bootloop.
3. Tried installing Pixel Experience recovery to flash magisk but same bootloop.
4. Tried flashing services disabler in TWRP, thinking it would prevent bootloop, but it gets stuck during installation.
So, here are some things I want to try and I want your opinion on whether it would work before trying:
1. Installing one ui 4.1, rooting it with TWRP and then installing the update.zip directly from TWRP.
2. Installing Magisk patched AP for one ui 4.1 and then installing update.zip via stock recovery. (oh wait nvm I tried this and the update.zip didn't install)
Please let me know if there might be a way to install Magisk safely without bootloop in One UI 5.
Hello, extract Boot.img from firmware file, transfert to Phone, With magisk on unrooted Phone, patch the boots.img,transfert to computer and try to make an .tar file with it, and try to patch with Odin in User line
buzzsaw891 said:
Hello, extract Boot.img from firmware file, transfert to Phone, With magisk on unrooted Phone, patch the boots.img,transfert to computer and try to make an .tar file with it, and try to patch with Odin in User line
Click to expand...
Click to collapse
I tried that but how do i extract boot.img from firmware?
Hi I am root my phone is root
MAO kam said:
Hi I am root my phone is root
Click to expand...
Click to collapse
didn't understand that. Are you root or is your phone root?
I'm on "A525FXXU4CVJB" version and have tried to root using files from HalabTech but did not work.
Stuck in boot loop after flashing some zip files.
Still looking for root for Android 13.
Also there is November update for my country.
this is why you are better off just getting google pixel devices
barryallen3038 said:
I tried that but how do i extract boot.img from firmware?
Click to expand...
Click to collapse
Use 7-Zip to extract AP and get "boot.img.lz4" file, then extract boot.img.lz4 with 7-zip and you'll get your boot.img file.
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.