Problems Rooting my Samsung S10 vendor.img Fail... - Samsung Galaxy S10 Guides, News, & Discussion

Hello Guys,
like the Title tells i got Problems rooting my Samsung S10
I follow this Guide: https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
and already tried to look up the error i get but i didnt find anything usefull yet
so everything works fine till i have to flash the Magisk Patched AP to my phone then it fails at vendor.img and after a Reboot the System is damaged. After that i just flash the unpatched AP and it works again but no matter how often i retry all steps or just the flashing part it always fails at the Vendor.img now i wanted to ask if anyone could help me or atleast tell me whats the mistake
Spoiler: Other maybe Useful Screens
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: Log from Odin
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 7084 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> param.bin
<ID:0/007> up_param.bin
<ID:0/007> cm.bin
<ID:0/007> keystorage.bin
<ID:0/007> uh.bin
<ID:0/007> vbmeta.img
<ID:0/007> dt.img
<ID:0/007> dtbo.img
<ID:0/007> system.img
<ID:0/007> vendor.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

---

Look below.

---

||||| said:
S10 Root Tutorial - optimized (orange)
S10/e/+ Root & Custom Rom Guide
Credits go to our Hero TopJohnWu & Developers & Contributors!
I attached the original File (see at the bottom)
Change log
• 21/06/2019 – Initial Version
• 03/09/2019 – Correct typo with Download Mode key combo
• 11/09/2019 – Added link to Telegram group in ROM section
• 11/09/2019 – Added change log.
• 12/09/2019 – Add note about TWRP version
• 07/12/2019 – added some more Notes & Nice to Knows |||||
Details
This guide will help you take your virgin S10 phone to a fully rooted phone running a custom rom.
It is highly recommended that you use an external SD card for this process as the steps has you formatting the internal data a couple of times, so having this on an external SD will keep this all intact.
Also note that MTP to your phone via a PC can get varied results, hence why again using an SD card is recommended as with an adaptor you can plug this straight into your PC and into phone when needed.
You must understand - that you always have to handle the Booting Process manually with the key combinations of Buttons after flashing - else you will have reboots and fails(no twrp etc)!
--Download Latest/your Official Firmware Version (PC)--
• On PC Download Samfirm from the following link: Updato& Sammobile (S10-Example) or search on google
• Extract the zip and run samfirm.exe
• Enter your model and Region (I.E Model=G975F, Region=BTU)
• Tick ‘Auto’
• Click Check Update
• It should show you the latest firmware version
• Click Download
• Firmware will download and decrypt (if Decrypt automatically was ticked)
• Default download location (My Documents)
>> • Prepare those Files (Unpack them) and get them on your External SD-Card - you will need them later <<<
--Download ODIN 3.13.1 (PC - FLASHSOFTWARE) --
• Go here and download the latest version of ODIN
>>> • Be sure to uncheck "Auto-Restart" later on - because there is a Twist to this (see Tipps&Tricks) <<<
--Unlock Bootloader--
**WARNING THIS WILL WIPE YOUR DATA**
• Enable developer Settings
(Settings > About Phone > Software Information > Tap build number 7 times (Enter your device pin)
• Go into Developer option and enable ‘OEM Unlocking’ (Enter Device Pin)
>>> THIS WILL ONLY SHOW UP - IF you have Internet activated (WLAN or 3G/LTE) & you must set your Date 7+ Days into the Future! <<<
• WARNING MESSAGE: Click turn on
• Power off your phone
• Hold Bixby + Volume Down and plug in your phone to your PC
>>> Bixby + Volume down + USB-Cable (plug it) = Downloadmode <<<
Download mode should now be shown
• Hold Volume Up, you’ll get a warning message, then press volume up to accept.
• This will now wipe your data and automatically reboot
• Boot the phone
• Go through initial set-up but skip everything for now
• Enable developer mode again and OEM unlocking (or should be enabled and greyed out)
• You are now done, and your bootloader will now allow ‘Unofficial Images’
--Download Latest TWRP (Phone)--
• On your phone Download the latest TWRP image for your model to the phone external SD card from here
• **NOTE – If you are installing Beyond Rom version 5.3 and onwards then you need to download a minimum of TWRP version 3.3.1-7
• We will need this later….
--Patch Firmware & TWRP File--
• On your PC extract the firmware files (AP, BL, CP and HOME_CSC)
• Copy the AP file to your SD card and enter SD card in your phone
• On your phone download the latest Magisk Manager APK from here
• Install the app.
• You may need to allow to “Install Unknow Apps” for chrome
1. Load up Magisk Manager on your phone
2. Next to ‘Magisk is not installed.” Click Install
3. Click Install on the pop up
4. Click ‘Select and Patch a File’
5. Select the AP file you copied across to your external SD
6. Magisk will now patch the AP file
7. A file called magisk_pached.tar will be created
• Repeat steps 2-4 but this time for the TWRP image file you downloaded earlier to your external SD.
• At the end of this process you should have two files
magisk_patched.tar and magisk_patched.img
• One is a Magisk patched version of TWRP (.IMG) and the other is a Magisk patched version of stock rom (.TAR)
--Rename and repackage--
• Remove the SD card from your phone and plug into PC
• Copy the above files from the SD to you PC
magisk_patched.tar & magisk_patched.img
• Rename the file magisk_patched.img to recovery.img
• Open the file magisk_patched.tar using a zip tool (I.E 7Zip) inside the archive remove the existing recovery.img and replace with the new patched recovery.img you made above
--Download Multi-disabler (Phone)--
• On your phone download multi disabler from here
• Ensure this is on your External SD card
--Download Custom Rom (Beyond) (Phone)--
• Head over to the ROM telegram group to download the latest version of Beyond ROM and tips/tricks and notices the telegram group is here
• Download the latest ROM to your phone.
• Ensure this is on your External SD Card
--Flash Patched File--
• Turn off your phone and boot into download mode (Hold BIXBY + VOL DOWN + Plug in USB)
• Press volume up to enter download mode
• On PC load up Odin
• Using the patched file and other files you extracted earlier place the following files in the following location
AP = magisk_patched.tar (Created above with custom patched recovery.img inside)
BL = BL_XXXXXXX (Extracted from original firmware file)
CP = CP_XXXXX (Extracted from original firmware file)
CSC = HOME_CSC_XXXXXX (Extracted for original firmware file)
• Under the options tab ensure ‘AUTO REBOOT’ is not ticked
• Click Start – This should take 5 – 10mins to complete.
--Full Data Wipe--
**DO NOT SKIP THIS STEP**
• Your phone should still be in Download Mode
• Review the next few steps to familiarise yourself with the button combinations
• Press Power + Volume Down for a few seconds to exit download mode
• AS SOON AS THE SCREEN GOES BLACK
HOLD Power + Bixby + Volume Up
KEEP HOLDING THESE KEYS UNTIL YOU SEE THE TWRP LOGO
• If TWRP runs a script and then reboots, immediately hold the same buttons again to get back into TWRP
--Multidisabler and Date Wipe--
• Click Install and select the Multidisabler.zip you downloaded earlier – DO NOT REBOOT
• Back to main menu in TWRP select WIPE>FORMAT DATA and TYPE YES, CLICK TICK BUTTON
**WHEN COMPLETE DO NOT REBOOT**
• Back to menu of TWRP select WIPE and swipe to do a Factory Reset (Data, Cache and Dalvik wipe) **WHEN COMPLETE DO NOT REBOOT**
• Back to main menu, Click Reboot, and Choose Recovery (Don’t hold any Buttons)
• The system will start booting (and will automatically reboot the first time)
• When booted, complete the initial set-up (Internet Connection is required), If you are going to custom rom, then you can skip logging into your account.
• Open Magisk (if it’s not in your app draw then manually install)
• Complete the steps required by Magisk
--Install Custom Rom (Beyond Rom)--
• Power off your phone
• Hold Power + Bixby + Volume Up until you see the TWRP logo
• Click Install
• Select the Beyond custom rom zip you downloaded to your phone earlier
• Follow the Aroma install options (do clean install the first time)
• When flash is complete, use reboot option and select reboot to recovery.
>>> DO NOT JUST REBOOT AFTER FLASHING - ALWAYS GO BACK IN MAIN MENU > REBOOT MENU & BOOT INTO RECOVERY - SO YOU WILL HAVE ROOT - OTHERWISE NOT! <<
• Congratulations you now have Custom rom installed on your S10.
Notes/Tips/Tricks
• Every time you reboot you will need to use the key combo or..
>>> Do this right after the flashing Process - when you it restarts - or better restart manually <<
◦ Hold Power + Bixby + Volume Up to TWRP logo to enter recovery
◦ Hold Power + Bixby + Volume Up until you see the Samsung warning screen for the 2nd time to boot into rooted rom.
When you get Stuck or something doesn't go well - don't worry - you can always flash a patched TWRP by itself!
• Go to Download Mode
• Use a patched TWRP and put it as recovery.img inside a recovery.tar (you create the archive (pack the .img as a .tar instead of .zip) using 7zip or similar)
• After you flashed it successfully and the screen turns dark (your restart)
- you instantly hold VOLup + Bixby + Power Button ( over the first 2 Screens)
- and let go, but hold VOLup down with your finger UNTIL TWRP comes up! - you are safe now! (almost) :silly: :victory:
>>> DO NOT JUST REBOOT AFTER FLASHING - ALWAYS GO BACK & BOOT INTO RECOVERY - SO YOU WILL HAVE ROOT - OTHERWISE NOT! <<
• Edxposed works for Pie and supports some functionality for Samsung phones like:
◦ Removing high volume warning
◦ Removing high brightness warning
◦ Advance power menu (Reboot to recovery, download etc..)
◦ Details can be found here
Here is a Video as well, wich is good to follow
But after you did this all in the Video - you need to flash patched TWRP!
I recommend to do it right after the patched AP File - let it stay in downloadload-mode, plug the usb-cable out and back in and flash the recovery.tar!
And you will have TWRP and now you can flash ROMS & BACKUP etc !
TWRP has also has File Manager - you can move/copy folders & files from internal to external etc
ok, well I added everything in orange what else was needed to be said! Wich I had to find out the hard way... and wich saves lots of Time!!
I still not slept for over 42 and wrote all this the last 2 hours, because I was so excited and wanted to give back! (and the Backup goes from internal to external at the same time
I will may add more to this Thread here... I have many tipps & tricks... wich is not so easy to find out first
I wish you all the best with your Rooted Samsung S10 S10+ etc
God bless you & sleep well
Best regards :victory:
|||||
Click to expand...
Click to collapse
Here.

---

Kenora_I said:
Look below.
Click to expand...
Click to collapse
so that is basically what i did and what didn't work.

---

Parelath said:
so that is basically what i did and what didn't work.
Click to expand...
Click to collapse
Did you follow each steps correctly?
Did you install a custom ROM?

---

I am just trying to install Magisk nothing else and yeah i did the steps multiple times with the same outcome it always fails at the Odin Flash part.

---

Parelath said:
I am just trying to install Magisk nothing else and yeah i did the steps multiple times with the same outcome it always fails at the Odin Flash part.
Click to expand...
Click to collapse
So you did flash a custom rom successfully and the issue is when you flash the modified AP?

---

so no i did not flash a custom rom it is not required for Magisk
like i said i just try to flash the Patched Magisk AP and it always fails at the Vendor.img

---

.

---

ianmacd said:
The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a Qualcomm SoC at their core. This includes the S10 and S20 series, the N10 and N20 series, the A10 - A70 series, the Tab A and Tab S series, Z Flip and (Z) Fold devices, and many more.
When flashed onto a compatible device, the multi-disabler will semi-permanently disable a number of device protection features and services that become problematic on a rooted device. Some pose a threat to the rooted state of the device, while others become dysfunctional and generate a flood of log messages. Semi-permanently in this context means that the disablement will persist until re-enabled by the user, for example as a side-effect of flashing new firmware with Odin. You will therefore need to reflash the multi-disabler every time you perform a system-wide firmware update.
The methodology of the multi-disabler is the path of least intervention. This means that for any given device, only those services that must be disabled to ensure the smooth operation of the device will be tackled.
The following is a list of features disabled by the multi-disabler on Samsung devices launched in 2019:
FBE (file-based encryption): Until this is disabled, most versions of TWRP — all for Exynos devices and many for Qualcomm — cannot read files on /data (the userdata partition). You must format /data to actually remove FBE after disabling it. Back up your data first!
Vaultkeeper: Magisk now dynamically disables this during boot, but if you boot outside of Magisk, it will return with a vengeance on some devices.
Process authentication (a.k.a. proca): This service must be disabled on some devices in order to use a custom kernel without problems. Note that all 2019 devices with TWRP utilise a custom kernel for Android, because the same kernel is shared by Magisk to boot the system. This does not apply to devices lauched in 2020 and later.
Stock recovery auto-restoration: In certain circumstances, your device will automatically restore its stock recovery partition, overwriting your custom recovery (TWRP). Magisk now also provides dynamic protection against this, but again, this will not save you if you boot outside of Magisk.
wsm: On Android 10 and 11, this service prevents Samsung smartwatches from connecting to the Galaxy Wearable app.
Extra services are disabled as needed per device.
Furthermore, when the ZIP file is renamed to contain the string _btfix somewhere in the name and the file is then flashed on a supported Android 10 device, the system's libbluetooth.so library will be patched in situ to prevent the loss of Bluetooth pairings across reboots. This is a recurring issue with many rooted Samsung devices manufactured before 2020 and updated to Android 10. Devices launched in 2020 and later do not need this patch.
The multi-disabler's support for this solution is limited to a relatively small number of Samsung devices and is deprecated as of v3.0. It will be removed in a future release.
If you find that patching fails on your device, please refer to Arthur Trouillot's superior libbluetooth patcher, which supports a much wider variety of devices.
The multi-disabler is written in Bourne shell, so you can — and ideally should — audit the code yourself to ensure its safe operation. It's performing open-heart surgery on the software of your device, so you should not simply trust it. Apart from anything else, bugs can creep in from time to time, despite or sometimes even because of my refactoring of the code.
The multi-disabler is idempotent, which means you can safely flash it multiple times without incurring unintended side-effects.
The package is attached to this posting and the code is available on GitHub.
Click to expand...
Click to collapse
Have you also flashed this?

---

ianmacd said:
If rooting with Magisk alone and in accordance with John Wu's instructions, this disabler isn't needed. If you're going to use a rooted TWRP image instead of stock recovery, however, then you're probably going to want to flash it.
Click to expand...
Click to collapse
no i didnt yet.
do i need it cause here he says its not needed if i only flash magisk
and isnt that a Post Flash process?

---

Do you have ramdisk when looking in magisk?

---

it says No

---

Parelath said:
Hello Guys,
like the Title tells i got Problems rooting my Samsung S10
I follow this Guide: https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
and already tried to look up the error i get but i didnt find anything usefull yet
so everything works fine till i have to flash the Magisk Patched AP to my phone then it fails at vendor.img and after a Reboot the System is damaged. After that i just flash the unpatched AP and it works again but no matter how often i retry all steps or just the flashing part it always fails at the Vendor.img now i wanted to ask if anyone could help me or atleast tell me whats the mistake
Spoiler: Other maybe Useful Screens
View attachment 5365435
View attachment 5365437View attachment 5365439
Spoiler: Log from Odin
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 7084 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> param.bin
<ID:0/007> up_param.bin
<ID:0/007> cm.bin
<ID:0/007> keystorage.bin
<ID:0/007> uh.bin
<ID:0/007> vbmeta.img
<ID:0/007> dt.img
<ID:0/007> dtbo.img
<ID:0/007> system.img
<ID:0/007> vendor.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Magisk in Recovery​If your device does not have ramdisk in boot images, Magisk has no choice but to hijack the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk enabled.
Since Magisk now hijacks the recovery, there is a special mechanism for you to actuallyboot into recovery mode. Each device model has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). A quick search online should easily get you this info. As soon as you press the combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. If you decide to boot into the actual recovery mode, long press volume up until you see the recovery screen.
As a summary, after installing Magisk in recovery (starting from power off):
(Power up normally) → (System with NO Magisk)
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Recovery Key Combo) → (Splash screen) → (Long press volume up) → (Recovery Mode)
(Note: You CANNOT use custom recoveries to install or upgrade Magisk in this case!!)
So you read the above?
​

---

ok so u now just repeat the stuff said in the guide i linked?
i told u i do everything step by step but as soon as i have to flash the AP i cant cause it fails at the vendor.img nothing post flash its WHILE flashing it fails

---

Yeah i got that before posting, internet sucks right now.
Parelath said:
ok so u now just repeat the stuff said in the guide i linked?
i told u i do everything step by step but as soon as i have to flash the AP i cant cause it fails at the vendor.img nothing post flash its WHILE flashing it fails
Click to expand...
Click to collapse

---

When patching the AP file did you select recovery mode in magisk?
And im assuming you used adb pull not MTK to transfer the file to the pc

---

yep i checked Recovery Mode
and used the adb method so the file wont get corrupted

---

Parelath said:
yep i checked Recovery Mode
and used the adb method so the file wont get corrupted
Click to expand...
Click to collapse
And your sure the vendor.img is the issue. Dosent Odin give a err code?

---

Oh, and you should be using the latest version and the binary should be the same.