Database Info

Flashing boot.img.tar in Odin...

Hi all,
My first foray into Samsung modification has me wanting to install a patched Magisk boot.img through Odin. However I've never used the tool before and documentation for people new to Samsung with this device is thin on the ground as are any step by step YouTube videos for the latest ODIN for this purpose, so I have looked.
Which option do I use in ODIN to flash the patched_boot.img.tar through? Do I simply tap AP in the latest ODIN build and select the aforementioned image and then enter Download mode and hit Start? Or is there anything further I need to do to the patched_boot.img.tar?
Thanks in advance for your assistance.

You have to flash patched_boot.img.tar as AP in ODIN.

jjocer said:
You have to flash patched_boot.img.tar as AP in ODIN.
Click to expand...
Click to collapse
Thankyou Unfortunately it didn't work and bootloops/hangs at boot. Have you managed to install Magisk with the new method?

I have the same problem today, see: https://forum.xda-developers.com/galaxy-s7/help/replace-stock-boot-img-sm-g935f-t3670348

SB13X said:
Thankyou Unfortunately it didn't work and bootloops/hangs at boot. Have you managed to install Magisk with the new method?
Click to expand...
Click to collapse
Hi. I need a bit of help. How did you manage to extract the boot image from your devise to install Magisk? I don’t have a nano backup and my phone is bricked, but i have the firmware ready to flash via ODIN, and I wold like to procced to install this new root method. Thanks.

First you must install magisk manager then open option>>patched boot output format change to .img.tar only for odin>>then install patch boot img (you can find boot img in firmware.mobi) wait until done>> move patched boot.img.tar to pc then install it with odin
Done!!! Now you hawe magisk installed on your device
Sorry for my bad english

[TESTING] Flash Patched boot.img to achieve Systemless Root

WARNING:
Please do every preparation that could fix your phone to original state before doing this trick.
DOING THIS MAY VOID YOUR WARRANTY, DO IT AT YOUR OWN RISK
I managed to unpack the official firmware of Nokia 7 and 8, and patched their boot.img with SuperSU Systemless Root.
But I don't know if it works on them.
Patched boot.img can be downloaded at:
https://mega.nz/#F!igsBmarT!3rIjD4ZaZN8ueOTVmciGwg
Here's the method you need to do:
1. Install OST LA and patch it, and OPEN IT FROM INSTALLATION DIRECTORY DIRECTLY.
2. Flash required firmware before proceed. If you don't do that, you won't be able to access Wi-Fi after the boot.img flashed.
For Nokia 7, you need to use the firmware "C1N-0430-0-00CN-B05" which I haven't released to public for some reason.
For Nokia 8, you need to use the firmware "NB1-435J-0-00WW-B01" which released in this topic: https://forum.xda-developers.com/showthread.php?t=3678487
If you've already flashed required firmware before proceed, you can skip this part.
Click to expand...
Click to collapse
3. Use the Service Purposed Bootloader trick I've mentioned in the Nokia 6 Root Guide: https://forum.xda-developers.com/showthread.php?t=3702354
4. Type these commands:
Code:
fastboot-android flash boot_a E:\NB1-435J-Boot-Patched.img
fastboot-android flash boot_b E:\NB1-435J-Boot-Patched.img
fastboot-android reboot
For Nokia 7, use C1N-0430-Boot-Patched.img instead. I've attached the Firehose, rawprogram0 and patch0 for Nokia 7 in case you want to use EDL Mode on Nokia 7.
Click to expand...
Click to collapse
5. If it's accepted by the system, the phone will reboot twice, and you'll see SuperSU appeared.
However, if "Verification Failed" appeared on your phone, then the trick failed. You have to flash original firmware to restore your phone to factory state.
If anyone know how to fix that in boot.img, that's a breakthrough of Nokia Android Devices.
You may want to use Flashfire to flash Xposed Framework or something else, but DO NOT RECEIVE ANY OTA UPDATES after your phone rooted.
I'm looking forward to a boot.img manual patcher on PC or Phone available, which could patch boot.img to achieve Systemless Root either SuperSU or Magisk and bypass Verification Boot.

This looks exciting. I have to look deeper into recovery options before I dare this kind of experiment...

Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Update: Can't install 4390 even when I download the update multiple times. Flashed 435J using OST and tried flashing the kernel again but still no root.

ansonscleung said:
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Click to expand...
Click to collapse
Thanks for feedback.
I'll check if anything wrong.
Can you check if you can install SuperSU manually from Google Play?
After you installed it, is root available?

hikari_calyx said:
Thanks for feedback.
I'll check if anything wrong.
Can you check if you can install SuperSU manually from Google Play?
After you installed it, is root available?
Click to expand...
Click to collapse
Nope. SuperSU said "Root not available"

Many thanks for your efforts on this patch, I would love to be able to root my Nokia 8.
Having an unlocked bootloader I am not really worried about, but having root access is a big feature for me.
Any chance this patch will become available to firmware version 00WW_4_390 which is the current latest? (And what my phone is currently running)
Not sure if I can downgrade it to NB1-435J-0-00WW-B01 or not, but I can try that if it is not able to be patched to the latest firmware image.

Thnx hikari_calyx for your hard work!
ansonscleung said:
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Update: Can't install 4390 even when I download the update multiple times. Flashed 435J using OST and tried flashing the kernel again but still no root.
Click to expand...
Click to collapse
Did anyone else but ansoncleung tried this meanwhile?

@hikari_calyx I have a self prepatched boot. IMG for TA1012, flashed via fastboot now I have root with Magisk, but WLAN won't work.
Powered by Nokia 8

2WildFirE said:
@hikari_calyx I have a prepatched boot. IMG for TA1012, flashed via fastboot now I have root with Magisk, but WLAN won't work.
Powered by Nokia 8
Click to expand...
Click to collapse
Log

Op please pm me i am developer too we can do this together.

TheKsM said:
Op please pm me i am developer too we can do this together.
Click to expand...
Click to collapse
Hey we need developers here on Nokia!
And what we need to is a dev who build twrp for Nokia8. The recovery is inside the boot. IMG.
If you want build a one for the community. Thanks
Powered by Nokia 8

[Request] How to Create Patched Boot Image

I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?

https://forum.xda-developers.com/showpost.php?p=79548858&postcount=6

I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.

ozfive said:
I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?
Click to expand...
Click to collapse
1)Download payload dumper.
2)Extract payload file from rom zip.
3)Put payload file in payload_input folder.
4)Run exe file.
5)After process complete check payload_output folder. All extracted there.
Download payload dumper from here :- https://forum.xda-developers.com/attachment.php?attachmentid=4760222&d=1558078935

Patched boot images are irrelevant and only necessary for devices without a working TWRP recovery. If you want to root, either boot TWRP once or boot and install TWRP (recommended) and then install the magisk zip from there.

larsdennert said:
I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.
Click to expand...
Click to collapse
How do you extract the boot.img from the phone? I have the tmo version and would like to say on the stock room with root.
Sent from my GM1915 using Tapatalk

You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.

larsdennert said:
You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.
Click to expand...
Click to collapse
Not rooted yet, but everything I have read so far is that you need a patched boot.img to root, or you can create one from the boot.img in an oos package with magisk manager. The problem is, there isn't a tmo oos package out there yet, so it looks like rooting the tmo software isn't possible at the moment. Is this correct?
Sent from my SM-T550 using Tapatalk

Is your bootloader unlocked? That would be step one. Read up on the thread for that.

Not yet, but will be....trying to get my research done before I go for it... don't want to mess it up, been a few years since I rooted a phone.
Sent from my GM1915 using Tapatalk

[SOLVED] OTA with ROOT...

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 ;-)

Extracted Stock Files

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.