Database Develop

How to flash magisk_patched.tar to Samsung Galaxy S10+ using Heimdall?

I know the guide to flash that tar file assumes that people use Windows and Odin, but for those of use that use Heimdall in Linux, is there a guide on how to flash magisk_patched.tar to the phone?
I know I can use VMware or VirtualBox, but I really don't like to use Windows anymore so I would be happy if someone could give me a failsafe way to flash in Linux.

I'd like to know that too since the official installation guide unfortunately only refers to Odin.

I ended up flashing the *img within TWRP as boot image. It worked.

geronimoge said:
I ended up flashing the *img within TWRP as boot image. It worked.
Click to expand...
Click to collapse
Can you explain what you mean? I don't have TWRP should I install that first and how?
I'm also stuck on this step, using Heimdall to flash the patched Magisk firmware without instructions

I have the same problem - not sure how to flash a magisk_patched.tar file (to Samsung Galaxy Tab A7 lite) using Heimdall on Linux. However, I cannot use the TWRP method because there isn't one yet for this device.
Heimdall is set up and recognises the device. I downloaded and saved the PIT file. Then in the flash tab on Heimdall I add the PIT file, then I'm not sure which partition to choose to flash the magisk.tar to. I also don't quite understand the magisk install instructions where it says "flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware". Do I have to extract the contents of AP....tar.md5, insert the magisk_patched.tar file and compress it again? Or do I simply select all of the folders from the original firmware package (AP, BL, CO, CSC) and magisk_patched.tar individually and flash them all (in the same way you can queue up zip files to flash via a custom recovery?
Thanks for any help.

tixos said:
Can you explain what you mean? I don't have TWRP should I install that first and how?
I'm also stuck on this step, using Heimdall to flash the patched Magisk firmware without instructions
Click to expand...
Click to collapse
This is how I managed to have a iode OS (lineage based) rom with magistk root using heimdall on a linux machine.
activate usb developer mode.
Download Magisk-v25.2.zip and put it on the phone (internal storage).
unlock the bootloader.
Download twrp recovery image. twrp for s10e, this is for s10e, but you have to use the twrp for s10+
issue: adb reboot bootloader
issue: heimdal flash --RECOVERY {twrp.img} --no-reboot
press power + volume down to reboot and then QUICKLY press power + bigsbi + volume up to boot into recovery. If you are booting in the normal system then you were not quick enough, you have to repeat steps 5, 6, 7.
in twrp install the Magisk-v25.2.zip from the internal storage and select wipe.
reboot in normal system.
rename Magisk-v25.2.zip to Magisk-v25.2.apk and install it.
enjoy the root!!
The pitfalls that I found and do not work.
Take the stock ap.tag image and patch it with the Magisk aplication on the phone and take the *.img and flash them with heimdall.
Install the Magisk-v25.2.zip via adb sideload.
Step 7 is maybe not intuitive enough: on s10e if you flash the twrp recovery and then it boots in the normal system image, the system image will revert the recovery image back to the original so you loose the twrp.
Hope this help some one else.

ETTT said:
This is how I managed to have a iode OS (lineage based) rom with magistk root using heimdall on a linux machine.
activate usb developer mode.
Download Magisk-v25.2.zip and put it on the phone (internal storage).
unlock the bootloader.
Download twrp recovery image. twrp for s10e, this is for s10e, but you have to use the twrp for s10+
issue: adb reboot bootloader
issue: heimdal flash --RECOVERY {twrp.img} --no-reboot
press power + volume down to reboot and then QUICKLY press power + bigsbi + volume up to boot into recovery. If you are booting in the normal system then you were not quick enough, you have to repeat steps 5, 6, 7.
in twrp install the Magisk-v25.2.zip from the internal storage and select wipe.
reboot in normal system.
rename Magisk-v25.2.zip to Magisk-v25.2.apk and install it.
enjoy the root!!
The pitfalls that I found and do not work.
Take the stock ap.tag image and patch it with the Magisk aplication on the phone and take the *.img and flash them with heimdall.
Install the Magisk-v25.2.zip via adb sideload.
Step 7 is maybe not intuitive enough: on s10e if you flash the twrp recovery and then it boots in the normal system image, the system image will revert the recovery image back to the original so you loose the twrp.
Hope this help some one else.
Click to expand...
Click to collapse
Sorry for necro-ing here, but, after following these steps, which I was already familiar with, I noticed that there is, quite literally, no way to follow through with this if, say, a button is not working.
I am trying these steps with a Galaxy S6, you see, and the home button is broken. Were not for that, it'd have taken me less than an hour to flash a custom ROM and Gapps on my relative's phone. However, because the Home button is broken, there is no way to go from download/bootloader mode directly into recovery mode, making it so that the stock firmware always overwrites the recovery partition.
Would you be so kind as to offer any insights into alternative solutions, if they exist?

099349613a5fbd51bd6237f13 said:
Sorry for necro-ing here, but, after following these steps, which I was already familiar with, I noticed that there is, quite literally, no way to follow through with this if, say, a button is not working.
I am trying these steps with a Galaxy S6, you see, and the home button is broken. Were not for that, it'd have taken me less than an hour to flash a custom ROM and Gapps on my relative's phone. However, because the Home button is broken, there is no way to go from download/bootloader mode directly into recovery mode, making it so that the stock firmware always overwrites the recovery partition.
Would you be so kind as to offer any insights into alternative solutions, if they exist?
Click to expand...
Click to collapse
+1
Similar problem here, with a defected "Volume Up" button on SM-T530 tablet.
I followed this tutorial and successfully flashed boot partition with magisk_patched-25200_4042u.img. Hope this helps.
https://www.reddit.com/r/Android/comments/79fzxy

Heimdall just cant read files above 5gb and for the super.img of my galaxy tab a8 is 6.3 gb. any solutions?

How to update rooted S20 FE 5G without lost data ?

Hello,
I have XEO software from security patch 07.21
And rooted phone.
I try upgrade FW Odin. Choose CSC Home and update...
And telephone not started
Only try three times started and write fault system.
Only wipe data working and starting
How i can in future rooted my telephone, only uses magisk, and safe upgrade to next update without lost data ???
Please help... Thanks

I've never tried it...
[S20_FE SM-G781U/U1_Snapdragon]-[Upgrade Easily Firmware Using Odin]-[Automatically Root Remove Forceencrypt Patch Bluetooth And Fix Safetynet]
Must Have An Unlocked Bootloader To Do This! This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install...
forum.xda-developers.com

Thanks for info.
But i think i not good for my model.
I have SM-G781B
Other advaice please...
I try moore times and always i must wipe data
Always if add home CSC ( without delete data ) must later wipe data in menu ( always corrupted data, system )

onken said:
Thanks for info.
But i think i not good for my model.
I have SM-G781B
Other advaice please...
I try moore times and always i must wipe data
Always if add home CSC ( without delete data ) must later wipe data in menu ( always corrupted data, system )
Click to expand...
Click to collapse
If you were rooted while patching the boot.img with magisk you will have to redo it on each odin update with patched AP and Home CSC to keep the root & data.
This is the way I do it but it implies not to use twrp therefore caution is in order regarding modules which could lead to bootloop.

Full House said:
If you were rooted while patching the boot.img with magisk you will have to redo it on each odin update with patched AP and Home CSC to keep the root data.
Click to expand...
Click to collapse
Hello, thanks.
I can use old patched AP for new software ?

onken said:
Hello, thanks.
I can use old patched AP for new software ?
Click to expand...
Click to collapse
No you can't, you have to patch AP each time with magisk before flashing

Full House said:
No you can't, you have to patch AP each time with magisk before flashing
Click to expand...
Click to collapse
Ok.
Thanks for info
Maybe know why not can rooted new mode Samsung A52s ?
I always run this same method and telephone not starting

onken said:
Ok.
Thanks for info
Maybe know why not can rooted new mode Samsung A52s ?
I always run this same method and telephone not starting
Click to expand...
Click to collapse
Have you unlocked the BL?
Didn't you have the camera problem?
If you followed the procedure and it doesn't work maybe the patched AP file was corrupted during the transfer have you eliminated this probability?

I try many times patched. Always not working.
Not only in me.
But about camera not checked but if yes to big problem.
If not can uses later camera for rooted, why possible unlock bootlader permission from Samsung....

unlocking the bootloader doesn't cause an issue with the camera on this phone.
different story on the Galaxy Fold 3 but we are OK to unlock.
once you have patched the AP file DON'T use windows file manager to move it, use ADB pull command.
ADB Push and Pull - Push and Pull Files on Android Using Commands
You can push and pull files on Android using ADB commands. ADB Push and Pull make Android development easy &save time by reducing data retrieving tasks.
www.droidviews.com

[Galazy Z Fold2 F916U/U1_Snapdragon]-[Upgrade Easily Firmware Using Odin]-[Automatically Root Remove Forceencrypt Patch Bluetooth And Fix Safetynet]

Must Have An Unlocked Bootloader To Do This!
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install magislk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2
I Do Not Recommend Mixing Bit 1 With Higher Firmware!!!!
Unless Using Bit Safe Firmware That Is Patched​
Downloads
SM-F916U/U1/W- Model
USERDATA_AIO_F916U_5G_FORCE_WIPE_10_10_21.tar.md5
This will force a wipe of data no mater what.
Full Odin 3.1.1 Bit1 Safe Firmware
F916USQS2EUH9_BIT1_SAFE.7z Thanks @markfm
This are odin files and will safely update all image files too bit 4 and keep bit 1 bootloaders. Unfortunately this will wipe data this is beyond my control as it seems to be a side affect of mixing firmware it causes data not to mount and therefore my AIO will format it. This is full firmware with USERDATA_AIO. This will put you on U firmware. Before flashing I recommend removing your google account and make sure in download mode you are not frp locked
If above USERDATA_AIO_G78*_FORCE_WIPE_NO_BL is newer than the one in this zip use the newer one from above
Odin3_v3.14.1_3B_PatcheD.zip
TWRP Recovery Provide by afaneh92
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions For Newly Unlocked Devices
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load file USERDATA_SLOT_F916U_**.tar.md5 you must choose one of the FORCE_WIPE files and load in the USERSDATA slot of odin and flash file
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Install Instructions For Updating Firmware On Phone Already Unlocked
1. Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above
2. Use patched 3.14 odin and load stock firmware in appropriate slots use regular CSC file in the CSC slot and load file one of the USERDATA_SLOT_F916U_**.tar.md5 in the USERSDATA slot of odin and flash firmware. Do not use the User Data file that comes with firmware.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not
Install Instructions If Updating Images With TWRP
1. When done flashing images in TWRP Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above.
2. Use patched 3.14 odin and load file USERDATA_AIO_F916U_NO_WIPE_NO_BL.tar.md5 in the USERSDATA slot of odin and flash file.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not.
4. Alternatively to using USERDATA_AIO_F916U_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_22_S20_Series.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
elliwigy
klabit87
Krog18
me2151
stang5litre
Raymonf for modified odin
rayan-refoua for boot animation
TheMadScientist
afaneh92
kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
JDBarlow for test S20 stuff
Xylvion for testing s21
dark11b for testing s21

Hi, can i have the procedure for rooted Fold2 F916B for firmware update.

I'm super excited about this. Hope to see the info for bootloader unlock soon so I can try it. Thanks you're awesome!

Does this mean it can be updated on the latest firmware with root?

PLZ PLZ PLZ do this for the z Fold 3 u1 snapdragon please sir your work has been a God send since the s8+ for me. Thank you

The full odin bitsafe firmware link isn't working

Hey can you fix the link to the odin firmware please?

Nothing? Please fix the link to the odin firmware it doesn't work.

same here. Please reupload to the drive.

halx said:
same here. Please reupload to the drive.
Click to expand...
Click to collapse
What's going on here ? Why hasn't the OP responded to us?

Ok it's official....samsung murked the OP.

Help with rooting galaxy s10 with no ramdisk

I bought a second phone Sam Galaxy s10 SM-G973F Exynos with display dead(Can be seen but green).
Iam doing inner os things with scrcpy
What things have i done till now??
I downloaded firmware from Frija.
I unlocked bootloader
I patched AP file with magisk app and ramdisk says no
I Used BL,CP and Home CSC with magisk pached image as AP with Odin
I got a bootloop
I flashed back to stock by reflashing with AP file without patching.
But the previous baseband version of stock binary 9(G973FXXUEHVB9) changed to G***********VC6.
Should I download VB9 for to work???

My wrong.

Hello Léon FH, these version VB9 me I have the version there G973FXXUFHVE1 - XEF (France) Android 12 S (May 2, 2022)
You have successfully transferred with ADB the AP magisk_patched mobile via pc.

meric57 said:
Hello Léon FH, these version VB9 me I have the version there G973FXXUFHVE1 - XEF (France) Android 12 S (May 2, 2022)
You have successfully transferred with ADB the AP magisk_patched mobile via pc.
Click to expand...
Click to collapse
I said, When I transfer Magisk_patched image, It bootloops.
After clearing dalvik, wiping, Iam ablw to get to it.
I flashed magisk.zip too(Which is useless in device with no ramdisk)
But still, no root in magisk manager.

Iam not able to root with magisk patched image.....
I patched magisk.zip also
No hope

Leon FH said:
Iam not able to root with magisk patched image.....
I patched magisk.zip also
No hope
Click to expand...
Click to collapse
You can install CSC instead CSC HOME. You will lose everything you installed.
If you install HOME CSC try this: #2,668

Look here https://forum.xda-developers.com/t/magisk-root-for-the-galaxy-s10-series.3918699/
I think you misunderstood redone all from A to Z take the official firmware S10 SM-G973F exynos android 12 UI 4.1 look at the one I have in my signature.
You backup your data with smart switch then you flash the official Android 12 XEF firmware. G973FXXUEHVC6 install magisk 25.1 the firmware AP r transfer to the S 10 and modify it with magisk once done you will have a file in internal memory magisk_patched xxx.tar you transfer it either directly to the pc or as john Wu says with adb for no lose bytes of the file it must 6.02 GB.
Then you open odin you put 4 files there BL-AP patched- BL HOME CSC you flash at startup install magisk and you activate zygisk in parameter once which is rooted you turn off and you start in download mode are you flash up_param.tar with odin take the one at https://forum.xda-developers.com/attachments/up_param-tar.5645391/ for rooted device
I hope you will understand complicated to explain

meric57 said:
Look here https://forum.xda-developers.com/t/magisk-root-for-the-galaxy-s10-series.3918699/
I think you misunderstood redone all from A to Z take the official firmware S10 SM-G973F exynos android 12 UI 4.1 look at the one I have in my signature.
You backup your data with smart switch then you flash the official Android 12 XEF firmware. G973FXXUEHVC6 install magisk 25.1 the firmware AP r transfer to the S 10 and modify it with magisk once done you will have a file in internal memory magisk_patched xxx.tar you transfer it either directly to the pc or as john Wu says with adb for no lose bytes of the file it must 6.02 GB.
Then you open odin you put 4 files there BL-AP patched- BL HOME CSC you flash at startup install magisk and you activate zygisk in parameter once which is rooted you turn off and you start in download mode are you flash up_param.tar with odin take the one at https://forum.xda-developers.com/attachments/up_param-tar.5645391/ for rooted device
I hope you will understand complicated to explain
Click to expand...
Click to collapse
Just like you said. I patched the rom. put it into odin. flashed it. Installed magisk 25.1 apk . No sign of root.

Leon FH said:
Just like you said. I patched the rom. put it into odin. flashed it. Installed magisk 25.1 apk . No sign of root.
Click to expand...
Click to collapse
You need patch onley AP. Copy AP on PC with ADB.
Try connect phone with PC with USB vcable. Open ADB and in ADB type 'adb reboot recovery' and Enter. After restart phone you you should have rooted phone.

ZmisiS said:
You need patch onley AP. Copy AP on PC with ADB.
Try connect phone with PC with USB vcable. Open ADB and in ADB type 'adb reboot recovery' and Enter. After restart phone you you should have rooted phone.
Click to expand...
Click to collapse
Thanks man. It worked!!✌

Leon FH said:
Thanks man. It worked!!✌
Click to expand...
Click to collapse
I should go adb reboot recovery to see root always??

Leon FH said:
I should go adb reboot recovery to see root always??
Click to expand...
Click to collapse
No. Install Root Essentials. For restart phone, open Root Essentials select Rebooter, click on Reboot Recovery and it is it. If you accidentally lose root, just repeat the type 'adb reboot recovery' and Enter.

Question [Updated] This is ENG binary Please Use USER binary after stock flash with Odin

New update to topic:
I decided to repair the software of my Galaxy S21 (Exynos) by flashing official firmware from Samfirmware, same version as I was running. It was in a bootloop before, so there was nothing esle to do. Phone was rooted with magisk, stock recovery.
I found what my firmware is from the recovery, found the exact same file, with the correct CSC.
Downloaded that firmware from Samfirmware, downloaded patched Odin from XDA.
Added, flashed, used HOME_CSC in order to preserve my data.
Reboot and immediately before I even get the boot logo or the charging animation, I get this error:
This is ENG binary Please Use USER binary
Allegedly this is what happens when you flash an engineering build, not an official one. But how? I downloaded and flashed official stuff? It's the exact same version my phone is already running. Where did I go wrong and how can I fix that?
I've attached the Download screen of my phone.
Thanks!
Old news:
Hello,
Hope this is the right place to ask for this kind of help.
I have a Galaxy S21 5G (SM-G991B), rooted with Magisk back in March 2021. Phone is bootloader unlocked, not encrypted, but the recovery is stock. Version currently running is Android 11. USB Debugging is enabled, but my computer is listed as unauthorised.
Yesterday my phone died due to low battery, so I plugged it and after it charged a bit I switched it on, only to be greeted with a constant bootloop. The bootloop is "soft", meaning only the system crashes, it doesn't go all the way to the initial boot screen (as if the battery was unplugged). The phone crashes about 1-2 seconds after the initial lockscreen is displayed.
Is there any way to help me recover this and save my phone? My entire life is there, from photos that can't be recovered, to authenticators I need for work and bank logins I need to be able to pay rent.
I thought about flashing TWRP and just doing a backup from there, but would it be as simple as that? All the tutorials talk about requiring to flash some extra zips and wiping the data, but those tutorials are combo root+twrp tutorials, and I've already done those steps. so no wiping should be needed to put TWRP on?
I'd be very grateful if anyone is profficient enough to help me recover the data, I already gave the phone to a data recovery company but they say it's unlikely anything will come out of it. If you manage to help me get my phone working as it was (or at least get my data back somehow), I'd gladly pay you the money for your efforts.
Help me XDA, you're my only hope.
Click to expand...
Click to collapse

Flashing TWRP = having to delete data (to be able to access the internal storage)
I am pretty sure (wait for confirmation before doing it) that if you flash the HOME_CSC file instead of the CSC on Odin it keeps your data.
This is why we need to vote with our wallets and buy phones with sd cards. I dont really care, because I never keep anything important on my phone, but I feel for you buddy.
EDIT: from here: https://www.droidviews.com/difference-between-csc-and-home_csc-samsung-firmware/
CSC – If you flash the CSC file, it’ll perform a factory reset of your Galaxy device and wipe all data while installing a new firmware to bring your device to the same state as it was when you purchased it. Go with CSC if you want a clean installation.
HOME_CSC – On the other hand, if you want to keep your Samsung phone’s data and settings even flashing the stock firmware, you can select the HOME_CSC file.
At your own risk, pls dont blame me if it doesnt work!

Flash a patched vbmeta again

GeeAyeZee said:
Flash a patched vbmeta again
Click to expand...
Click to collapse
Hi, what do you mean? Flash both TWRP and vbmeta, as if I'm doing it for the first time?
I think the phone was already decrypted while following the Magisk root tutorial, so these two steps should be the only thing necessary for the phone to boot to TWRP, right? I know how to rescue everything once I'm in there.

Try entering safe mode and disable all magisk modules:
Power on your Galaxy phone or tablet in Safe mode
We’ll walk you through how to start your Samsung Galaxy phone or tablet in Safe mode. This mode prevents third-party apps from running on your device.
www.samsung.com
You can access adb when on recovery mode or download mode so you can also enter safe mode via one of these commands:
setprop persist.sys.safemode 1
or
echo "1" > /data/property/persist.sys.safemode

dikime said:
Hi, what do you mean? Flash both TWRP and vbmeta, as if I'm doing it for the first time?
I think the phone was already decrypted while following the Magisk root tutorial, so these two steps should be the only thing necessary for the phone to boot to TWRP, right? I know how to rescue everything once I'm in there.
Click to expand...
Click to collapse
Flash the vbmeta file in odin

shaharofir said:
Try entering safe mode and disable all magisk modules:
Power on your Galaxy phone or tablet in Safe mode
We’ll walk you through how to start your Samsung Galaxy phone or tablet in Safe mode. This mode prevents third-party apps from running on your device.
www.samsung.com
You can access adb when on recovery mode or download mode so you can also enter safe mode via one of these commands:
setprop persist.sys.safemode 1
or
echo "1" > /data/property/persist.sys.safemode
Click to expand...
Click to collapse
The phone auto-enters safe mode after a few bootloops, so I guess that's beat. When the phone is in stock recovery, doing any adb commands tells me the device is recognized, but "unauthorized".

dikime said:
The phone auto-enters safe mode after a few bootloops, so I guess that's beat. When the phone is in stock recovery, doing any adb commands tells me the device is recognized, but "unauthorized
Click to expand...
Click to collapse
So you can enter download mode and flash stock (just super)

You gonna have to get authorized again. Check youtube for help. I had that issue a couple months ago. Think it had to delete the android folder and reinstall adb

Alright, decided to flash stock firmware with Odin. Found my files from Samfirmware, and since I want to keep my data, flashed HOME_CSC. Now the phone won't boot at all, giving the error:
This is ENG binary, please use USER
Now why did this happen and can I do anything to change that? I would really like to not flash CSC and wipe my phone, but it's looking more and more likely.
I used the patched 3.14.1 Odin, could that be the issue? Shouldn't matter.
The Download mode screen says: