Hi Did you succeed at rooting xCover 5 ??
Same problem with Xcover 5 (Italy) - stock ROM downloaded from sammobile (G525FXXS4AUI6 - took like 2 days lol).I have the same issue . Stuck on boot screen after flashing. Works fine after I re-flash original boot or do a complete re-flash with original firmware. I can successfully root my s9 so am not a complete noob. My region is NEE
One more weird thing is that i cant seem to get it in recovery after the rooted boot flash. Any ideas for checking relevant logs?
There is a extra file in the boot.img called vmbeta compared to the s9 boot.img. Is it possible that this is the issue or am i completely wrong?
![]()
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your pforum.hovatek.com
![]()
[CLOSED] What is "vbmeta.img" ?
What is "vbmeta.img" and why it is needed? How it works? Does anybody knows?forum.xda-developers.com
Don't do this Xcover 5 users, this is for xcover 4, and from a screenshot here it seems not to have ramdisk - this method will not work Odin will only fail in flashing.How to Root via Magisk Patch:
1) Download and open the stock ROM
2) Extract the boot.img.lz4 and convert it to boot.img with a program like lz4_win64
3) Convert the boot.img to boot.tar with 7zip or winRAR
4) Copy boot.tar to your mobile phone and patch it with Magisk, so you will get magisk-patched.tar
5) Rename the patched magisk-patched.tar to boot.tar
6) Flash it with Odin in AP mode and you are rooted!
Only this method worked for me, if you try it differently it may not work! (Xcover4s)
Should work on all Samsung phones with Android 9 or higher.
So I can understand that it's impossible to root xCover 5?Same problem with Xcover 5 (Italy) - stock ROM downloaded from sammobile (G525FXXS4AUI6 - took like 2 days lol).
It is stuck in bootloop after following the Magisk installation guide for SAR devices. You can enter recovery by pressing volume down and power button, and as soon as the screen switches off you keep the power button pressed but switch to pressing the volume up. It does a weird thing the first time you do it after trying to root (android symbol and "Erasing.." written below), but the second time it works. Remember the phone must be attached to the pc otherwise you can't get into recovery mode (it makes no sense but it's like this, apparently). You can go in download mode by detaching the shut down phone, pressing volume up and down, and plugging it in the PC (the only way to recover from the bootloop is to flash through odin all the stock rom files (bl ap csc and cp).
I will try the method mentioned above and will let you know if I manage to root...but it seems impossible.
This OEM is not Open in Xcover 5 SirDon't do this Xcover 5 users, this is for xcover 4, and from a screenshot here it seems not to have ramdisk - this method will not work Odin will only fail in flashing.
I can confirm Adrianfocke instruction, it works - thank you!I was able to root my device (g535f/ds) by following the droidwin guide (linked below) closely, but with making adjustments. What I did was to:
- warning: this will delete all your data!
- warning: you need to unlock your bootloader for this to work!
- decompress the stock firmware
- decompres the AP part of it
- decompress the lz4 boot img in AP
- patched the boot img from AP part via Magisk
- replaced the original lz4 boot img in the AP folder with the patched img
- compressed the modified AP part again (file type: .tar archive, not signed!)
- flashed stock BL, CP, CSC and modified AP_archive.tar including the the patched img in ODIN
- rebooted device
To sum it up: Except step 4.3 (Delete all the files inside that folder except for recovery.img and vbmeta.img.)
and the hacky recovery boot stuff from the end (to fix some weird bootloop) of the post, I did all the steps from there. I can also create a new thread in case a more detailed guide is wanted.
Furthermore: I dont know if xda has specific rules on which file hosts are allowed. Please tell me so if it is the case, thx. I could not find anything in this regard.
My used files (Android 13, CSC Open Austria ATO) for ODIN can be downloaded here: http://u.pc.cd/fOV7 (shortened link). These files are already customized, you do not have to go through the guide with these. You may use them, though I do not give any warranty. Original firmware I used is linked below.
External resources:
Droidwin guide: https://www.droidwin.com/extract-boot-img-lz4-root-samsung/
Original firmware: https://samfw.com/firmware/SM-G525F/ATO/G525FXXS5CWA8
Hi! Is it posible to send me this modified boot.img for odin flash? My phone is in odin mode, tried flashing full stock system thru odin but it just wont exit from odin mode. Phone is oem locked and debugging is not turned on. Im running out of ideasI confirm too, it works very well! Thank you! I didn't understand the step by step guide Adrianfocke gave, so I followed the summary which was quite clear.
Before compressing it in tar format, the modified AP folder must contain:
- the contents of the AP folder patched by magisk
- AND the boot.img patched by magisk (from the boot.img file which comes from the compressed boot.img.lz4 file wich comes from the offical AP-part folder wich comes from the compressed AP-part.tar.md5 file downloaded on samfw.com)
I hope it's clearer this way, otherwise all you have to do is follow Adrianfocke's summary.
Don't patch only boot.img, do the whole AP in magisk 24 or above to make it work, or else it will fail.Hi! Is it posible to send me this modified boot.img for odin flash? My phone is in odin mode, tried flashing full stock system thru odin but it just wont exit from odin mode. Phone is oem locked and debugging is not turned on. Im running out of ideas
I cant patch anything, waiting for phone to discharge completely and I super rusti with samsung phones, havent flashed any since galaxy s2Don't patch only boot.img, do the whole AP in magisk 24 or above to make it work, or else it will fail.
Hi, I tried the procedure for my device (g535f/ds) has OEM lock, but in Odin it reports Fail and the message appears on the screen: only official releases are allowed.... (KNOX Block)I was able to root my device (g535f/ds) by following the droidwin guide (linked below) closely, but with making adjustments. What I did was to:
- warning: this will delete all your data!
- warning: you need to unlock your bootloader for this to work!
- decompress the stock firmware
- decompres the AP part of it
- decompress the lz4 boot img in AP
- patched the boot img from AP part via Magisk
- replaced the original lz4 boot img in the AP folder with the patched img
- compressed the modified AP part again (file type: .tar archive, not signed!)
- flashed stock BL, CP, CSC and modified AP_archive.tar including the the patched img in ODIN
- rebooted device
To sum it up: Except step 4.3 (Delete all the files inside that folder except for recovery.img and vbmeta.img.)
and the hacky recovery boot stuff from the end (to fix some weird bootloop) of the post, I did all the steps from there. I can also create a new thread in case a more detailed guide is wanted.
Furthermore: I dont know if xda has specific rules on which file hosts are allowed. Please tell me so if it is the case, thx. I could not find anything in this regard.
My used files (Android 13, CSC Open Austria ATO) for ODIN can be downloaded here: http://u.pc.cd/fOV7 (shortened link). These files are already customized, you do not have to go through the guide with these. You may use them, though I do not give any warranty. Original firmware I used is linked below.
External resources:
Droidwin guide: https://www.droidwin.com/extract-boot-img-lz4-root-samsung/
Original firmware: https://samfw.com/firmware/SM-G525F/ATO/G525FXXS5CWA8
Don't patch only boot.img, do the whole AP in magisk 24 or above to make it work, or else it will fail.Hi! Is it posible to send me this modified boot.img for odin flash? My phone is in odin mode, tried flashing full stock system thru odin but it just wont exit from odin mode. Phone is oem locked and debugging is not turned on. Im running out of ideas