Database Develop

Flashing Patched Boot.img in ODIN Not Working

I installed Magisk Manager 5.3.0 and opened it and clicked on Install to download Magisk 14 and to patch the boot.img file that I got from the Samsung Firmware file.
I patched the file and that completed fine with no errors.
I then copied the patched boot.img file to my computer so I could run ODIN on to flash it. Its in the proper format, "magisk.img.tar" is that I called it.
I opened ODIN 3.12 and selected the file under BL and plugged my phone in while in Download Mode.
ODIN detected my phone with the Added! msg in the log window.
ODIN is still running as I type this and all that is in the log is the following:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
Theres no change on the phone screen either.
OEM Unlock is enabled as on the phone screen it says FRP Lock: Off
Phone is a Samsung Galaxy J3 Emerge (J327P) with Boost Mobile
Samsung firmware file from SAMMOBILE is J327PVPU1AQF4_J327PSPT1AQF4_BST

John877 said:
I installed Magisk Manager 5.3.0 and opened it and clicked on Install to download Magisk 14 and to patch the boot.img file that I got from the Samsung Firmware file.
I patched the file and that completed fine with no errors.
I then copied the patched boot.img file to my computer so I could run ODIN on to flash it. Its in the proper format, "magisk.img.tar" is that I called it.
I opened ODIN 3.12 and selected the file under BL and plugged my phone in while in Download Mode.
ODIN detected my phone with the Added! msg in the log window.
ODIN is still running as I type this and all that is in the log is the following:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
Theres no change on the phone screen either.
OEM Unlock is enabled as on the phone screen it says FRP Lock: Off
Phone is a Samsung Galaxy J3 Emerge (J327P) with Boost Mobile
Samsung firmware file from SAMMOBILE is J327PVPU1AQF4_J327PSPT1AQF4_BST
Click to expand...
Click to collapse
It has to be added in AP not BL.

I did the same and I tried to flash it in odin in AP but odin crushes!!
My phone is Galaxy S7 edge

Hani88 said:
I did the same and I tried to flash it in odin in AP but odin crushes!!
My phone is Galaxy S7 edge
Click to expand...
Click to collapse
Can you by any chance send me the boot-image, stock, patched, tared ?
Or do you have the possibility to untar the image (or create just the boot.img) and use a "real" gnu-tar (preferred on linux).
Or give me the exact firmware, so I can try to create the image and tar it with the tar on my Fedora system ?
When doing the (internal) beta-tests I had the same issue, because of incorrect tar-headers (gnu-tar does not care about it). That should be fixed in MagiskManager, but Odin seems to be extremely nitpicking about the tar-header.
It might also be a problem with signed (or better not signed) bot-image, but I guess this would lead to another error.

jenslody said:
Can you by any chance send me the boot-image, stock, patched, tared ?
Or do you have the possibility to untar the image (or create just the boot.img) and use a "real" gnu-tar (preferred on linux).
Or give me the exact firmware, so I can try to create the image and tar it with the tar on my Fedora system ?
When doing the (internal) beta-tests I had the same issue, because of incorrect tar-headers (gnu-tar does not care about it). That should be fixed in MagiskManager, but Odin seems to be extremely nitpicking about the tar-header.
It might also be a problem with signed (or better not signed) bot-image, but I guess this would lead to another error.
Click to expand...
Click to collapse
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux

Hani88 said:
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux
Click to expand...
Click to collapse
Can you give me the exact version of your rom, so I can download it and send you a patched image for testing ? Or send me the boot.img either patched, stock or patched and tared ?

Hani88 said:
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux
Click to expand...
Click to collapse
Well, if that's what you did, no wonder why it's failing and Odin is stuck on analyzing the image—it's not in the proper format, you shouldn't rename it, you need to tar the boot.img file.

jenslody said:
Can you give me the exact version of your rom, so I can download it and send you a patched image for testing ? Or send me the boot.img either patched, stock or patched and tared ?
Click to expand...
Click to collapse
It is
GF935FXXS1DQHM
I downloaded it from samfirm
I can send you the boot.img tomorrow because my laptop is not with me
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
白い熊 said:
Well, if that's what you did, no wonder why it's failing and Odin is stuck on analyzing the image—it's not in the proper format, you shouldn't rename it, you need to tar the boot.img file.
Click to expand...
Click to collapse
Now I understand because inside it also there is not "meta inf " folder. How to tar it ?

Hani88 said:
It is
GF935FXXS1DQHM
I downloaded it from samfirm
I can send you the boot.img tomorrow because my laptop is not with me
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
Now I understand because inside it also there is not "meta inf " folder. How to tar it ?
Click to expand...
Click to collapse
In MagiskManager's settings chose the .img.tar output format. The patched image should be named "patched_boot.img.tar", if it's just "patched_boot.img" you can not directly flash it!

jenslody said:
In MagiskManager's settings chose the .img.tar output format. The patched image should be named "patched_boot.img.tar", if it's just "patched_boot.img" you can not directly flash it!
Click to expand...
Click to collapse
But in odin in AP I am not able to import img file

Hani88 said:
But in odin in AP I am not able to import img file
Click to expand...
Click to collapse
That's why you have to chose the correct patch-format in MagiskManager's settings before patching the stock boot.img .
In the settings click/touch "Patch Boot Output Format" and chose ".img.tar", then in the main menu click/touch "Install", then again "Install", then "Patch Boot Image File", chose the stock-image and wait until it is patched.
This should create a file named "patched_boot.img.tar" in the MagiskManager-folder of your internal storage.
This should be flashable.
Changing just the ending of any file does not change the format and can not work therefore.

jenslody said:
That's why you have to chose the correct patch-format in MagiskManager's settings before patching the stock boot.img .
In the settings click/touch "Patch Boot Output Format" and chose ".img.tar", then in the main menu click/touch "Install", then again "Install", then "Patch Boot Image File", chose the stock-image and wait until it is patched.
This should create a file named "patched_boot.img.tar" in the MagiskManager-folder of your internal storage.
This should be flashable.
Changing just the ending of any file does not change the format and can not work therefore.
Click to expand...
Click to collapse
Thanks for the explanation.. I will do it tomorrow
Flashing a patched boot image will trip the knox counter right ? Of course mine is tripped but I want to know that

@jenslody I have just tried flashing the patched boot.img file in ODIN under the AP/PDA field and depending on ODIN version it either crashes or is stuck at file analysis. I have named the file "magisk" to keep the filename short. Therefore the full filename is magisk.img.tar. It was created using the patcher in magisk manager with the output setting of img.tar. I prefer to flash it in ODIN as I would like to keep the stock recovery for the sake of future updates.
How I obtained the boot.img file is from opening the stock firmware image from SAMMOBILE and extracting the AP file and grabbing the boot.img. I also grabbed the recovery.img this way just to have it. I dont have access to any other way of extracting the files as I dont have or use linux personally so its my windows 10 computer only.
As you offered the other guy above I am including my stock extracted boot.img file as well as my exact firmware version on SAMMOBILE.
The exact firmware filename is: J327PVPU1AQF4_J327PSPT1AQF4_BST
Its the Samsung Galaxy J3 Emerge (2017) from Boost Mobile (J327P) with Baseband version ending in QF4. Its on Android 6.0.1.
I was unable to attach the boot.img file here cause its too big (11.7mb) and the upload failed when I tried to ZIP it instead cause the limit there is 20mb. So here it is on DropBox instead.
https://dl.dropboxusercontent.com/s/azyeqrx7rtvjvik/boot.img
Once again the is extracted directly from the firmware file with winrar with no magisk patching.

John877 said:
@jenslody I have just tried flashing the patched boot.img file in ODIN under the AP/PDA field and depending on ODIN version it either crashes or is stuck at file analysis. I have named the file "magisk" to keep the filename short. Therefore the full filename is magisk.img.tar. It was created using the patcher in magisk manager with the output setting of img.tar. I prefer to flash it in ODIN as I would like to keep the stock recovery for the sake of future updates.
How I obtained the boot.img file is from opening the stock firmware image from SAMMOBILE and extracting the AP file and grabbing the boot.img. I also grabbed the recovery.img this way just to have it. I dont have access to any other way of extracting the files as I dont have or use linux personally so its my windows 10 computer only.
As you offered the other guy above I am including my stock extracted boot.img file as well as my exact firmware version on SAMMOBILE.
The exact firmware filename is: J327PVPU1AQF4_J327PSPT1AQF4_BST
Its the Samsung Galaxy J3 Emerge (2017) from Boost Mobile (J327P) with Baseband version ending in QF4. Its on Android 6.0.1.
I was unable to attach the boot.img file here cause its too big (11.7mb) and the upload failed when I tried to ZIP it instead cause the limit there is 20mb. So here it is on DropBox instead.
https://dl.dropboxusercontent.com/s/azyeqrx7rtvjvik/boot.img
Once again the is extracted directly from the firmware file with winrar with no magisk patching.
Click to expand...
Click to collapse
This should work, unless your ODIN-version stumbles about other things than mine.
Nevertheless, I uploaded a patched version of your boot.img to my server: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar .
It's tared with the tar from my Fedora-system, but the (tar-header related) fixes @topjohnwu made to the java-tar he uses in MagiskManager made the created image flashable on my J5 (latest stock).
I also added a tared image with md5-checksum for you to test: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar.md5

jenslody said:
This should work, unless your ODIN-version stumbles about other things than mine.
Nevertheless, I uploaded a patched version of your boot.img to my server: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar .
It's tared with the tar from my Fedora-system, but the (tar-header related) fixes @topjohnwu made to the java-tar he uses in MagiskManager made the created image flashable on my J5 (latest stock).
I also added a tared image with md5-checksum for you to test: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar.md5
Click to expand...
Click to collapse
@jenslody, just for me to understand—you get the patched version via Magisk Manager, then untar it, then tar it again with a custom built tar?
Where are the patches you mention?

I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now.
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Also would this be how to flash the recovery.img file too if I flash TWRP and want to go back to the stock recovery?

白い熊 said:
@jenslody, just for me to understand—you get the patched version via Magisk Manager, then untar it, then tar it again with a custom built tar?
Where are the patches you mention?
Click to expand...
Click to collapse
I used the stock boot for J3, patched it through MagiskManager (one as *.img, one as *.img.tar), renamed the patched_boot.img to boot.img (taht's what Odin expects inside the tar, used Fedora's tar (I'm on Fedora 26) to create a tar archive from it and just for testing added a md5-checksum to one version of it.
MagiskManager is the 5.30 released with/for Magisk 14.4, bot patched. The fixes I mention were made by @topjohnwu in the (internal) beta-testing for 14.4.
To be clear:
the released Magisk with MagiskManager create img.tar-files that work for my J5 with the Odin-version I use (Odin3 v3.10.7) without any tweaking.
My self-tared versions are for testing purposes, to see if other Odin versions are more nitpicking than mine (about tar-headers). The included boot.img is exactly (binary) the same.

John877 said:
I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now.
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Also would this be how to flash the recovery.img file too if I flash TWRP and want to go back to the stock recovery?
Click to expand...
Click to collapse
Same question here.. and you are not the only one who's feeling like an idiot now
---------- Post added at 09:23 AM ---------- Previous post was at 09:02 AM ----------
jenslody said:
Can you by any chance send me the boot-image, stock, patched, tared ?
Click to expand...
Click to collapse
here is it thanks for helping
https://drive.google.com/file/d/0B9_cANW46As_Y2Jwa0xsR1p2UkE

John877 said:
I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now. [emoji14]
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Click to expand...
Click to collapse
It's unnecessary, you should just select .img.tar as the output format in Magisk Manager's settings. Then you can use the .img file you've extracted from the stock firmware. Magisk Manager will patch the .img file and create a patched .img.tar
This you should be able to flash with Odin.

白い熊 said:
It's unnecessary, you should just select .img.tar as the output format in Magisk Manager's settings. Then you can use the .img file you've extracted from the stock firmware. Magisk Manager will patch the .img file and create a patched .img.tar
This you should be able to flash with Odin.
Click to expand...
Click to collapse
When I extracted the boot.img file from the firmware it was boot.img. When I patched it from magisk manager, it was boot.img still even though I chose output format img.tar.

twrp s10

Hi, I rooted my s10 with magisk but cannot flash twrp parched with odin because the file is .img and odin accepts file tar.
What do I Havel to do?

Guide to Extract Boot image file and flash via Odin Tool
First, download the preferred Samsung Stock ROM for your device model.
Extract the firmware zip file on your computer within a folder.
Now, the boot image file named as AP_xxx (similar kind of) file.
Recently, Samsung firmware files use a new compression type called .lz4 extension. You may see something like boot.img.lz4 file name.
Extract the boot.img.lz4 file via 7Zip to .tar extension and now you will see the boot.img.tar file. Download 7Zip - github (dot) com (slash) mcmilk (slash) 7-Zip-zstd (slash) releases
Now, open the Odin tool and connect your device to the PC via a USB cable.
Click on the ‘AP’ button and select the boot.img.tar file from your computer.
Click on the ‘Start’ button.
That’s it. Wait for flashing to complete and reboot your handset.
Hope this guide will be helpful to you. If you’re facing any issue, you can ask your queries in the comments below.

Update after root pixel 4a 5g

Hi, I have unlock the boot loader and root my pixel 4a 5g in february update.
I don't understand how update it when new update comes ?
I can update it with Ota when comes in settings/System/Update ?
Or I do flash system image with fastboot and then flash the boot.img with Magisk to flash it in Fastboot mode ?
But I see : Flashing a new system image deletes all user data !!?
Before on Oneplus and later Xiaomi is more easy with Twrp. But now it's very complicated to update my freshly updated Pixel 4a 5g and Root
Please that it is the easiest procedure to update every month with Magisk installed. Previously I stopped all the Mods installed so as not to have a similar bootloop for Substartum .. Thank you
Thanks

Here's what I do:
- Download full factory image
- Unzip the archive
- There will be flash-all.bat (for Windows) and flash-all.sh (Linux) files created. You will need to edit the appropriate file to remove the -w flag on the "fastboot -w update image-bramble-rq1c.210205.006.zip" command near the bottom of the script.
- Within the archive you just unzipped, a directory will be created i.e. bramble-rq1c.210205.006 and within that there will be another zip file i.e. image-bramble-rq1c.210205.006. This zip file also needs to be uncompressed to extract the individual .img files including boot.img.
- Copy boot.img to your phone (Download directory is a good place)
- Flash the update using the edited flash-all script
- Once flashing is complete and the phone has rebooted, go into Magisk Manager and Install Magisk using the "select and patch a file" method. Navigate to the Downloads directory and select boot.img. Once complete, there will be a patched boot image named something like magisk_patched_bEKaK.img created in the Download directory. Copy that file back to your PC and then use fastboot to flash it to your phone i.e. "fastboot flash boot magisk_patched_bEKaK.img".
- Reboot phone and profit!

weissbierdood said:
Here's what I do:
- Download full factory image
- Unzip the archive
- There will be flash-all.bat (for Windows) and flash-all.sh (Linux) files created. You will need to edit the appropriate file to remove the -w flag on the "fastboot -w update image-bramble-rq1c.210205.006.zip" command near the bottom of the script.
- Within the archive you just unzipped, a directory will be created i.e. bramble-rq1c.210205.006 and within that there will be another zip file i.e. image-bramble-rq1c.210205.006. This zip file also needs to be uncompressed to extract the individual .img files including boot.img.
- Copy boot.img to your phone (Download directory is a good place)
- Flash the update using the edited flash-all script
- Once flashing is complete and the phone has rebooted, go into Magisk Manager and Install Magisk using the "select and patch a file" method. Navigate to the Downloads directory and select boot.img. Once complete, there will be a patched boot image named something like magisk_patched_bEKaK.img created in the Download directory. Copy that file back to your PC and then use fastboot to flash it to your phone i.e. "fastboot flash boot magisk_patched_bEKaK.img".
- Reboot phone and profit!
Click to expand...
Click to collapse
Thank you very much.
Have a good day..
I have now the good procedure to update it. Thanks

how to update my rooted phone to android 11?

that's the question, it says I can't update because I have a modified system
it's stock rom manually flashed with unlocked bootloader

If you rooted your phone using magisk download the latest firmware from samfw or any other site transfer the AP file to your phone patch it using magisk and then use ADB to pull it because if you just drag and drop the file from your phone to your pc it will probably lose some things on the way so download ADB and use the command adb pull "location of the patched file" don't use " after that when you flash the new firmware with odin in the AP slot select the patched file it would be named magisk_patched and some random letters, in the rest of the slots use the normal files from the firmware you downloaded and thats it. If this helped you make sure to like my response ! Thank you

Samsung Galaxy stuck in download mode loop when TWRP is flashed on Odin

Hi, I recently flashed the latest TWRP for S10 (twrp-3.5.2_9-3-beyond1lte.img) using Odin.
In the Odin app, everything appears to be successful, however, the phone now shows the warning for the bootloader being unlocked and immediately switches to a Download Mode screen. At the top left of the screen it shows this:
ODIN MODE (AVB Fail)
recovery: Error validating footer. (0)
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
VBMETA 6973FXXSBFUF3, 41014081R
No matter how many times I turn the phone off and on, it constantly keeps going back to this screen. The only way I can fix this is by flashing the stock firmware onto the phone with Odin. IfI try to flash TWRP again after this, it just repeats the previous problem. TWRP was working yesterday when I was using it, sol am really confused
as to why this issue is occurring.
This issue seems to have started after I flashed Lineage 18.1 onto my phone through TWRP. Lineage was constantly launching so I turned the phone off and went back onto TWRP and deleted my data, OS and internal storage. I don't know how this would affect anything though, but I can't access TWRP since.
If anyone would have any idea how to resolve this problem and allow me to access TWRP on my phone again, it would be greatly
appreciated. Thank you
(My phone model number is SM-G973F/DS).

Did you ever manage to get this solved?
I'm having the same issue with my S10e.
After flashing TWRP it goes into download mode and whatever I try it always boots into download mode until I flash the stock rom and start over again.

My phone is Samsung Galaxy S10 (SM-G973F).
I have never used Lineage, but I read that Lineage has problems with TWRP.
I root Stock ROM with Magisk. With Magisk I patched AP file, and install BL, CP, CSC and patched AP with ODIN.
After that I install TWRP and vbmeta.
TWRP.img I patched with Magisk. Version of Magisk is 25.1. After I patched .img with Magisk, I copy it on PC with ADB. After copy on PC, I convert patched .img to .tar and it install with ODIN.
First of all, transfer the patched TWRP image (magisk_patched.img) file from your phone’s storage to the PC.
Open the folder where the file was transferred.
Hold the SHIFT key on the keyboard and right-click on any empty space inside the folder.
Then select the ‘Open PowerShell window here’ option.
Now, enter the following command to rename the ‘magisk_patched.img’ to ‘recovery.img’:
mv magisk_patched.img recovery.img
Instead of magisk_patched.img, type the name you got when you patched the .img with Magisk and then Enter.
For me it looks like this:
Next command for Galaxy S10 is: tar cf twrp-beyond1lte.img.tar recovery.img
Now you can install TWRP with ODIN.
I installed TWRP.tar and vbmet.tar with ODIN.

Thanks!
I will give it a try.
Where did you get the vbmeta file?
Or did you have create it yourself? - That's one part I'm unsure of.

Cilvaring said:
Thanks!
I will give it a try.
Where did you get the vbmeta file?
Or did you have create it yourself? - That's one part I'm unsure of.
Click to expand...
Click to collapse
Before root Android.
From here:
[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy S10/e/+/5G Exynos
Official TWRP 3.6.1-* For Galaxy S10/e/+/5G Only for exynos variants - G970F / G973F / G975F / G977B (Europe - Global, Single/Dual-SIM), G970N / G973N / G975N / G977N (South Korea) Disclaimer I am not responsible for bricked devices, dead SD...
forum.xda-developers.com
Here you can download TWRP, vbmeta and multidisabler samsung.
For vbmeta and multidisabler samsung you need click on Instructions: Odin (Windows) CLICK TO SHOW CONTENT. Here are links for download.
Boot into TWRP, Flash Multi-Disabler zip, and Format the Data
Press Power and Volume Down buttons together to exit Download Mode.
As soon as the screen turns off, quickly press and hold the Power, Volume Up, and Bixby buttons together until the Bootloader Warning message appears.
Once the Bootloader Warning screen appears, release the Bixby and Power buttons, and keep holding the Volume Up button to enter TWRP recovery mode.
Tap on the ‘Install’ button in TWRP.
Navigate to the MicroSD card and select the Multi-Disabler ZIP file.
Swipe the button on the screen to flash the Multi-Disabler zip file on your Galaxy S10.
Once the file has been flashed successfully, go to ‘Wipe’ > ‘Format Data’ in TWRP.
Enter ‘Yes’ in the field to format the data partition/factory reset the device.
Finally, go to the ‘Reboot’ menu in TWRP and select ‘Recovery’ to boot your Samsung Galaxy S10 device into rooted OS with.

this method of patching is good, thanks for sharing!
ZmisiS said:
My phone is Samsung Galaxy S10 (SM-G973F).
I have never used Lineage, but I read that Lineage has problems with TWRP.
I root Stock ROM with Magisk. With Magisk I patched AP file, and install BL, CP, CSC and patched AP with ODIN.
After that I install TWRP and vbmeta.
TWRP.img I patched with Magisk. Version of Magisk is 25.1. After I patched .img with Magisk, I copy it on PC with ADB. After copy on PC, I convert patched .img to .tar and it install with ODIN.
First of all, transfer the patched TWRP image (magisk_patched.img) file from your phone’s storage to the PC.
Open the folder where the file was transferred.
Hold the SHIFT key on the keyboard and right-click on any empty space inside the folder.
Then select the ‘Open PowerShell window here’ option.
Now, enter the following command to rename the ‘magisk_patched.img’ to ‘recovery.img’:
mv magisk_patched.img recovery.img
Instead of magisk_patched.img, type the name you got when you patched the .img with Magisk and then Enter.
For me it looks like this:
Next command for Galaxy S10 is: tar cf twrp-beyond1lte.img.tar recovery.img
Now you can install TWRP with ODIN.
I installed TWRP.tar and vbmet.tar with ODIN.
Click to expand...
Click to collapse

Foxlegendary said:
this method of patching is good, thanks for sharing!
Click to expand...
Click to collapse
You are welcome.