Related
I have been looking for some sort of root for the ulefone armor 9, and I can't seem to find anything apart from sketchy websites. Can anyone help?
I found the scatterfile, but i still need to find the authentication file, and a download agent? I don't recall ever having to do any of this to root a phone before. Where do I get these files for a ulefone armor 9?
Look inside here:
Systemless Rooting with MagiskSU - Download APK
MagiskSU is an all-in-one Android rooting solution that is developed by topjohnwu. With Magisk Manager, users can easily root Android smartphones in a fastest and effective way. You can download MagiskSU, Magisk Root, Magisk Manager latest versions here.
magisksu.com
jwoegerbauer said:
Look inside here:
Systemless Rooting with MagiskSU - Download APK
MagiskSU is an all-in-one Android rooting solution that is developed by topjohnwu. With Magisk Manager, users can easily root Android smartphones in a fastest and effective way. You can download MagiskSU, Magisk Root, Magisk Manager latest versions here.
magisksu.com
Click to expand...
Click to collapse
there isn't a twrp for this phone.
M8E1 said:
there isn't a twrp for this phone.
Click to expand...
Click to collapse
TWRP isn't needed at all. Look inside here:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
jwoegerbauer said:
TWRP isn't needed at all. Look inside here:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
Click to expand...
Click to collapse
I did this, and I got a "red state" boot loop
M8E1 said:
I did this, and I got a "red state" boot loop
Click to expand...
Click to collapse
Am I missing something? The phone is apparently locked in fastboot mode, and will not accept downloads.
M8E1 said:
I did this, and I got a "red state" boot loop
Click to expand...
Click to collapse
Then report this issue in the related XDA-thread.
jwoegerbauer said:
Then report this issue in the related XDA-thread.
Click to expand...
Click to collapse
What thread would that be? This is for support and questions, isn't it?
M8E1 said:
What thread would that be? This is for support and questions, isn't it?
Click to expand...
Click to collapse
Of course this one:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
Is there anyone who can help? Fastboot does not respond to commands, and patching the boot.img and vbmeta.img via sp flash tool only puts my phone in a "red state". I have tried so many methods for rooting this phone, i'm starting to become convinced that it doesn't exist.
M8E1 said:
Is there anyone who can help? Fastboot does not respond to commands, and patching the boot.img and vbmeta.img via sp flash tool only puts my phone in a "red state". I have tried so many methods for rooting this phone, i'm starting to become convinced that it doesn't exist.
Click to expand...
Click to collapse
i rooted this phone on the first day i got,, i now trying to get proper working twrp so,, search on the google this,, ulefone armor 9 root hovatek and follow the guide there, thats how i did it.
kanadali said:
i rooted this phone on the first day i got,, i now trying to get proper working twrp so,, search on the google this,, ulefone armor 9 root hovatek and follow the guide there, thats how i did it.
Click to expand...
Click to collapse
Hello,
I tried to root my Armor 9E using Magisk but I ended with a bootloop. after a moment of stress (I'm a noob) I was able to put the original boot.img thanks to Fastboot,
I found your thread on Hovatek, how do you patch vbmeta.img ? in my case it's a Armor 9E
About TWRP, do you have any update ? will it be compatible with 9E also ?
Thanks
EDIT : I had to flash the vbmeta.img , I took it from hovatek here https://forum.hovatek.com/thread-36629.html
Totem95d said:
Hello,
I tried to root my Armor 9E using Magisk but I ended with a bootloop. after a moment of stress (I'm a noob) I was able to put the original boot.img thanks to Fastboot,
I found your thread on Hovatek, how do you patch vbmeta.img ? in my case it's a Armor 9E
About TWRP, do you have any update ? will it be compatible with 9E also ?
Thanks
EDIT : I had to flash the vbmeta.img , I took it from hovatek here https://forum.hovatek.com/thread-36629.html
Click to expand...
Click to collapse
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.
MurdochPizgatti said:
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.
Click to expand...
Click to collapse
Trying this method works fine for me until I try to relock the bootloader. Once I do that, I end up with a red state again.
Any advice? I am relocking the bootloader via fastboot flashing lock - is that correct?
MurdochPizgatti said:
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.
Click to expand...
Click to collapse
Hi!
I'm having the same issue as MulBe039.
Device: UleFone Armor 9E (Android 10)
My steps so far:
0.0 Get boot.img, scatter file, checksum generator (from ulefone), magisk.apk (from github), vbmeta.img, drivers, SP Tool (from Hovatek)
0.1 Install magisk on my phone and patch boot.img.
0.2 Enable developer options on my phone
0.3 Enable OEM unlocking and USB debugging on my phone.
0.4 Install drivers on my PC
0.5 Copy scatterfile, boot.img, vbmeta.img into checksum generator's folder and get checksum.ini.
1.0 Connect phone
> adb devices
> adb reboot bootloader
> fastboot devices
> fastboot oem unlock
> fastboot reboot
Phone boots in orange state.
2.0 Re-enable dev opts, (phone shows as already unlocked), USB debugging and turn off the phone.
2.1 Start SP Flashtool
2.2 Select scatter file
2.3 Check only vbmeta.img
2.4 Start download
2.5 Connect phone
2.6 Download completes successfully.
2.7
> fastboot devices
> fastboot reboot
Orange state.
2.8 Factory reset from phone
3. Repeat 2., except at 2.3 check only the patched boot.img
Still orange state.
Magisk app is installed.
4.0 Turn the phone on, enable dev opts and USB debugging, connect to PC
> adb devices
> adb reboot bootloader
> fastboot devices
> fastboot oem lock
> fastboot reboot
Red state - boot loop.
5.0 Hold power button until it turns off abruptly
5.1 Hold volume up until load some sort of boot selector menu.
5.2 Select fastboot mode with vol up button.
5.3 Vol down to boot selected mode
5.4
> fastboot devices
> fastboot oem unlock
> fastboot reboot
Orange state - everything else is working.
What am I missing / doing wrong? How do I re-lock the bootloader?
Thanks in advance!
I have been able to root my Ulefone armor 9 using the method described here https://github.com/bkerler/mtkclient
1 - download boot partition from your device using mtkclient
2 - patch it with magisk manager
3 - flash it again with mtkclient
4 - flash an empty vbmeta (not really sure if this is necessary)
5 - boot your device
I'm not really sure if it is needed to have the bootloader unlocked, but I had it
0xf331dead said:
I have been able to root my Ulefone armor 9 using the method described here https://github.com/bkerler/mtkclient
1 - download boot partition from your device using mtkclient
2 - patch it with magisk manager
3 - flash it again with mtkclient
4 - flash an empty vbmeta (not really sure if this is necessary)
5 - boot your device
I'm not really sure if it is needed to have the bootloader unlocked, but I had it
Click to expand...
Click to collapse
And remember that you cannot lock your bootloader after modifying stuff because signatures will not match and so on
I had to press volume up + volume down while connecting the usb to get mtkclient working
Hi guys. Is there any root method for the Gigaset Gs4? Thanks.
Anyone?
As long as you have the stock images there is.
Im currently trying to get the stock ROM in any way. If anyone has some tips please reply
Currently I'm trying to get the stock ROM using the image here: https://www.google.com/amp/s/unofficialtwrp.com/download-twrp-3-2-3-mediatek-mt6771-8-1/?amp
I hope that I can extract boot.img with it, to patch it with magisk.
Also take a look here:
Amazing Temp Root for MediaTek ARMv8 [2020-08-24]
Software root method for MediaTek MT67xx, MT816x, and MT817x! So it's no big secret that not too long ago, I found a way to achieve temporary root on MediaTek chipsets. No preinstalled root solution or device unlock was needed. The tool I...
forum.xda-developers.com
Edit: I found another image for the mt6771 that might work as well but keep in mind that it is not made for the Gigaset GS 4: https://www.techswizz.com/twrp-recovery-for-cubot-note-20-pro/ DOES NOT WORK!!
As soon as I got the patched image I think you can use this bypass to flash it: https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/amp/ DOES NOT WORK!!
StarMiner99 said:
As long as you have the stock images there is.
Im currently trying to get the stock ROM in any way. If anyone has some tips please reply
Currently I'm trying to get the stock ROM using the image here: https://www.google.com/amp/s/unofficialtwrp.com/download-twrp-3-2-3-mediatek-mt6771-8-1/?amp
I hope that I can extract boot.img with it, to patch it with magisk.
Also take a look here:
Amazing Temp Root for MediaTek ARMv8 [2020-08-24]
Software root method for MediaTek MT67xx, MT816x, and MT817x! So it's no big secret that not too long ago, I found a way to achieve temporary root on MediaTek chipsets. No preinstalled root solution or device unlock was needed. The tool I...
forum.xda-developers.com
Edit: I found another image for the mt6771 that might work as well but keep in mind that it is not made for the Gigaset GS 4: https://www.techswizz.com/twrp-recovery-for-cubot-note-20-pro/
As soon as I got the patched image I think you can use this bypass to flash it: https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/amp/
Click to expand...
Click to collapse
i managed to extract the stock boot.img and recovery.img using this guide with some modifications:
How to use Wwr MTK + SP Flash tool to backup Mediatek rom
This is a step-by-step guide on how to use Wwr MTK tool & SP flash tool to backup Mediatek (MTK) firmware. We had previously created guides on how to backup or dump firmware from a Mediatek (MTK) devi
forum.hovatek.com
things i did different:
i could not preform the ram test to determine the size of emmc_user so i just used a random length(0x3a3e00000) later on WwR told me that emmc_user should be: 0xe8f800000 i used this value to again read the emmc_user region and loaded it into WwR and continued on the rutorial.
now with this information we should be able to patch boot.img using magisk and flash it to our devices to root it.
to flash your device do the following: reboot into fastboot mode (power + volume up and select fastboot) then in a terminal type:
to unlock the bootloader:
fastboot flashing unlock
to flash an image to your device:
fastboot flash <partition> <image>
the stock images and the scatter file will follow
I managed to succesfully root my smartphone using magisk there was a single problem which is the following:
Android verified boot
you need to flash a new vbmeta image
i made my own empty vbmeta image and flashed it now its working and my smartphone is rooted
[HOW TO ROOT AND HOW TO INSTALL TWRP]
DISCLAIMER:
I will not be responsible for any damage to you device !!!!
step 1 :
make a backup of your smartphone data
step 2 :
unlock your bootloader
1. go to settings -> about phone -> click a few times on the build number
2. go to settings -> system -> developer options -> allow OEM unlocking
step 3 :
install adb and fastboot on your computer
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/ <- you can download a minimal version here
step 4 :
enable usb debugging
go to settings -> system -> developer options -> enable usb-debugging
step 5 :
open a console on your computer and do the adb and fastboot stuff
type the following commands into your cmd:
adb reboot bootloader <- this will reboot your smartphone into fastboot mode
wait until your phone enters fastboot mode
as soon as your phone entered fastboot mode type the following:
fastboot flashing unlock <- this will unlock your bootloader you have to press volume up to confirm it
then flash vbmeta and magisk patched:
fastboot flash vbmeta vbmeta_disabled.img <- this will flash the new vbmeta file
[ROOT]
fastboot flash boot magisk_patched-23000_tvNQq.img <- this will flash the new boot image
[TWRP]
fastboot flash recovery twrp.img <- this will flash the new recovery image
step 6 :
reboot your phone and reconfigure it
Youre Done!
EDIT: please download the twrp image from the official TWRP site: https://twrp.me/gigaset/gigasetgs4.html
@StarMiner99 as I'm thinking about buying it I'm glad to know it can be rooted.
bmwdroid said:
@StarMiner99 as I'm thinking about buying it I'm glad to know it can be root
Click to expand...
Click to collapse
well it was not easy to get the stock images xD
im currently also trying to port lineage os and twrp to the gigaset gs4
StarMiner99 said:
im currently also trying to port lineage os and twrp to the gigaset gs4
Click to expand...
Click to collapse
That's good to hear.
Although if it can be rooted it might be sufficient for me to kill all not needed apps via adb and use Magisk for AFWall+.
Actually I've read about the possibility of a GS version with a better camera so I might wait a while before getting one.
well there arent any unneeded apps
[STOCK ROM + SCATTER FILES + PRELOADER]
here are the stock rom files, the scatter file and the preloader in a zip archive
1.5 GB file on MEGA
mega.nz
StarMiner99 said:
[STOCK ROM + SCATTER FILES + PRELOADER]
here are the stock rom files, the scatter file and the preloader in a zip archive
1.5 GB file on MEGA
mega.nz
Click to expand...
Click to collapse
Hey StarMiner99, is the ADUPS software updating malware in the image you uploaed still working? Could hyou please explain briefly how to flash this stock rom? I have adb and fastboot already running and a rooted device too.
Thanks a lot!
StarMiner99 said:
im currently also trying to port lineage os and twrp to the gigaset gs4
Click to expand...
Click to collapse
any progress on this?
could i do something to help?
First of all: Thank you very much! Everything has worked so far and the device is rooted.
But I still have one question. How does the device behave when the official updates from Gigaset are installed via OTA? The GS4 reports it would have security updates. Can I install them without losing root privileges? Does anyone already have experience? Thanks in advance!
UserSven said:
First of all: Thank you very much! Everything has worked so far and the device is rooted.
But I still have one question. How does the device behave when the official updates from Gigaset are installed via OTA? The GS4 reports it would have security updates. Can I install them without losing root privileges? Does anyone already have experience? Thanks in advance!
Click to expand...
Click to collapse
I have now simply installed the June 2021 update. The good news: It worked. The slightly less good news is that you have to flash the images again. But flashing also works with the latest version and the update check tells that there are no new updates. So it seems to work.
UserSven said:
I have now simply installed the June 2021 update. The good news: It worked. The slightly less good news is that you have to flash the images again. But flashing also works with the latest version and the update check tells that there are no new updates. So it seems to work.
Click to expand...
Click to collapse
Which recovery do you use?
I've read in their forum that updating doesn't work when on TWRP.
StarMiner99 said:
im currently also trying to port lineage os and twrp to the gigaset gs4
Click to expand...
Click to collapse
Why are you not just using the LineageOS GSI?
I have LineageOS17.1 running on my GS4 since Feb. without any issues so far.
ChrisMucDev said:
Why are you not just using the LineageOS GSI?
I have LineageOS17.1 running on my GS4 since Feb. without any issues so far.
Click to expand...
Click to collapse
Is there a tutorial on how to do that?
Wolfgang-Z said:
Is there a tutorial on how to do that?
Click to expand...
Click to collapse
Here is, what I did: (on your own risk)
As far as i can remember, i did not have any issues.
Step 1: Unlock your device
1. Enable Developer Options: Tap 10x on Build-Number (Setttings -> About the phone -> Build-Number)
2. Enable Bootloader Unlocking -> activate OEM-Unlock option (Settings -> System -> (More) -> Developer-Options)
3. Enable ADB Access -> Enable USB-Debugging / ADB (Settings -> System -> (More) -> Developer-Options)
4. (Set USB-Settings (Message-Center) from "No tx" to "PTP")
5. Connect phone to usb port, grant permissions on phone and check connection with `adb devices`
6. Boot to bootloader: `adb reboot bootloader`
7. Unlock Bootloader: `fastboot flashing unlock`
Step 2: Download GSI
1. Reboot your phone and install Treble Info App
(https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en&gl=US)
GS4 should support AB-Partitions
2. Download GSI: https://sourceforge.net/projects/andyyan-gsi/files/
For GS4: treble_arm64_bv*
Step 3: Install GSI
1. Boot to recovery: `adb reboot recovery` or Volume Down + Power
2. Wipe data
3. Wipe cache
4. Enter fastboot
5. Flash GSI: `fastboot flash system <extracted-gsi-image>`
6. Reboot and enjoy
*. (just in case it does not boot, reboot to recovery -> enter fastboot and flash vbmeta: `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img`)
This vbmeta-image should work (see post #6): https://forum.xda-developers.com/attachments/vbmeta_disabled-img.5325563/
Hi everyone urgently need help root instructions for the xcover 5. there is a possibility it runs with android 11. thank you in advance
akin03 said:
Hi everyone urgently need help root instructions for the xcover 5. there is a possibility it runs with android 11. thank you in advance
Click to expand...
Click to collapse
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Tab E said:
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Click to expand...
Click to collapse
thanks for the instruction. what do I have to type in adb mode. Is there a program where I can use the adb mode.
akin03 said:
thanks for the instruction. what do I have to type in adb mode. Is there a program where I can use the adb mode.
Click to expand...
Click to collapse
There is no program. You have to download adb and fastboot tools
Once your phone is in fastboot mode and you have opened command prompt in adb fastboot folder in you pc type
fastboot oem unlock (this unlocks the bootloader)
fastboot flash boot boot.img (this flashed the magisk patched or rooted boot.img to your devices boot partition
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Patch Stock Boot Image via Magisk and Flash it using Fastboot
This tutorial contains explanation on how to Patch Stock Boot Image file of your device and subsequently flash it via Magisk.
www.droidwin.com
Tab E said:
There is no program. You have to download adb and fastboot tools
Once your phone is in fastboot mode and you have opened command prompt in adb fastboot folder in you pc type
fastboot oem unlock (this unlocks the bootloader)
fastboot flash boot boot.img (this flashed the magisk patched or rooted boot.img to your devices boot partition
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Patch Stock Boot Image via Magisk and Flash it using Fastboot
This tutorial contains explanation on how to Patch Stock Boot Image file of your device and subsequently flash it via Magisk.
www.droidwin.com
Click to expand...
Click to collapse
Thanks for the instructions. Did it as described. However, I'm stuck in fastboot mode when sending. Is there a guide or a way to flash the patched file via odin?
akin03 said:
Thanks for the instructions. Did it as described. However, I'm stuck in fastboot mode when sending. Is there a guide or a way to flash the patched file via odin?
Click to expand...
Click to collapse
Yes. Compress the file to '.tar' and flash it
Tab E said:
Yes. Compress the file to '.tar' and flash it
Click to expand...
Click to collapse
Ok just the patched file? And do I have to pay attention to something?? Flashing via AP or BL?
akin03 said:
Ok just the patched file? And do I have to pay attention to something?? Flashing via AP or BL?
Click to expand...
Click to collapse
Ap
Tab E said:
Ap
Click to expand...
Click to collapse
Hi does not get errors on odin. Do I just need to flash the patched file or other files.
Request for help.. Have flashed the whole ap file about magisk after a guide now I have bootloop and the device restarts after 3 min. I don't get the device rooted
Hi. Is n'one who can help me...! It's important...?!
akin03 said:
Hi. Is n'one who can help me...! It's important.
Click to expand...
Click to collapse
Hi, if you send me the exact ROM of your device I can create a Root-AP file (boot.tar) for you which you flash through Odin (AP). Note that after flashing the Root file your phone will be factory reseted.
akin03 said:
Hi. Is n'one who can help me...! It's important...?!
Click to expand...
Click to collapse
Or you can follow this guide, it is the exact same process of rooting newer samsung devices.
How to root Samsung Galaxy X Cover 4s Enterprise Edition (SM-G398F)
Hey there, is there a way to root a Samsung Galaxy X Cover 4s (SM-G398F)? The phone is from June 2019 and runs Android 9.0. I haven't found anything on the forum. Here's a link to the Samsung website...
forum.xda-developers.com
I tried to patch the updated AP (boot loop)
I tried to flash the stock AP and then only the updated boot.img (boot loop)
I also tried flashing a patched recovery.img (HASH_MISMATCH error)
Maybe Magisk has some issues with that phone.
Did anyone have success in rooting the G525F?
hatl said:
I tried to patch the updated AP (boot loop)
I tried to flash the stock AP and then only the updated boot.img (boot loop)
I also tried flashing a patched recovery.img (HASH_MISMATCH error)
Maybe Magisk has some issues with that phone.
Did anyone have success in rooting the G525F?
Click to expand...
Click to collapse
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.
I did this with the latest ATO firmware: https://samfw.com/firmware/SM-G525F/ATO
and ended up in a boot loop.
Maybe it's an issue with the latest Android 11 version - or the Xcover 5
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 p
forum.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
ive tried like evverything but get stuck on a message sayying my phone isnt running on offical firmwire or something like that. But now i have another problem. When in fastboot adb cant find my device. If my phone is just on and im not in fastboot adb finds it. Why is that happening?
Tab E said:
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Click to expand...
Click to collapse
When my phone is in fastboot mode it cant find it.. WHen its on adb devices finds it but not when in fastboot mode.
A search for "root xcover 5" brings up plenty of ways to achieve this, but most of those sites are click bait, with identical instructions for any device you can think of. Other people are more helpful, like those who replied above, but I would like to know if anyone has ACTUALLY ROOTED A XCOVER 5 SUCCESSFULLY. And yes, if so, I'd like to know how it was done.
I rooted my phone using TWRP and Magisk. All's well up till now when I received a notification of a latest update on my phone but the catch is I never made a back up of the stock firmware image while rooting and now as per the instructions on the internet,
see here this article - https://www.droidwin.com/install-ota-rooted-android
I can't restore the stock firmware image after tapping on the uninstall button in Magisk and move on to the next step. I can't flash the stock firmware image, Magisk says STOCK BACK UP DOESN'T EXIST. Please help. I have the stock ROM with me, kept with utmost care. Hahaha ! Please help me and I will thank you you in 5 different languages.
cometicard said:
I rooted my phone using TWRP and Magisk. All's well up till now when I received a notification of a latest update on my phone but the catch is I never made a back up of the stock firmware image while rooting and now as per the instructions on the internet,
see here this article - https://www.droidwin.com/install-ota-rooted-android
I can't restore the stock firmware image after tapping on the uninstall button in Magisk and move on to the next step. I can't flash the stock firmware image, Magisk says STOCK BACK UP DOESN'T EXIST. Please help. I have the stock ROM with me, kept with utmost care. Hahaha ! Please help me and I will thank you you in 5 different languages.
Click to expand...
Click to collapse
If you have a Windows PC use the update option in LMSA
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Then open the LMSA firmware folder, find the new boot.img, and patch it with Magisk
sd_shadow said:
If you have a Windows PC use the update option in LMSA
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Then open the LMSA firmware folder, find the new boot.img, and patch it with Magisk
Click to expand...
Click to collapse
Let me try it.
cometicard said:
Let me try it.
Click to expand...
Click to collapse
sd_shadow said:
If you have a Windows PC use the update option in LMSA
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Then open the LMSA firmware folder, find the new boot.img, and patch it with Magisk
Click to expand...
Click to collapse
I did what you suggested, I downloaded the stock ROM and then copied the boot.img file to the phone's internal storage, patched it by Magisk but all in vain as whenever I tap on the uninstall button in Magisk and select RESTORE IMAGES, Magisk tells STOCK BACK UP DOESN'T EXIST. I'm still getting the same error message. The next step would be to install the OTA but alas can't proceed. to it.
cometicard said:
I did what you suggested, I downloaded the stock ROM and then copied the boot.img file to the phone's internal storage, patched it by Magisk but all in vain as whenever I tap on the uninstall button in Magisk and select RESTORE IMAGES, Magisk tells STOCK BACK UP DOESN'T EXIST. I'm still getting the same error message. The next step would be to install the OTA but alas can't proceed. to it.
Click to expand...
Click to collapse
That's not what i suggested.
I suggested updating with lmsa.
You don't have to unroot, just patch new boot.img after update
sd_shadow said:
That's not what i suggested.
I suggested updating with lmsa.
You don't have to unroot, just patch new boot.img after update
Click to expand...
Click to collapse
I see, let me try it. This seems to be an easier option. Thanks again.
cometicard said:
I see, let me try it. This seems to be an easier option. Thanks again.
Click to expand...
Click to collapse
I'm not sure but it looks like the update firmware has been removed from LMSA.
If this is the case, you have to flash manually or use the rescue option which will factory reset the device.
Using the rescue option is the easier method
if you don't mind losing your data, and re-rooting.
Flashing may be a little tricky the first few times, but is good to know how to do if you are modifying your device (rooting)/
See how to get the correct flash commands from the flash_file.xml
Just remove the "erase userdata" line from the commands, it's usually the last line.
Online FlashFile Converter
sd_shadow said:
I'm not sure but it looks like the update firmware has been removed from LMSA.
If this is the case, you have to flash manually or use the rescue option which will factory reset the device.
Using the rescue option is the easier method
if you don't mind losing your data, and re-rooting.
Flashing may be a little tricky the first few times, but is got to know how to do if you are modifying your device (rooting)/
See how to get the correct flash commands from the flash_file.xml
Just remove the "erase userdata" line from the commands, it's usually the last line.
Online FlashFile Converter
Click to expand...
Click to collapse
Yes brother. They have removed it. Anyway, I googled it and I came across a video on youtube which addresses this issue of STOCK BACK UP DOESN'T EXIST. But LMSA factory resetted my device and I lost root. I have to re-root again. Quite tedious it is to say the least.
sd_shadow said:
I'm not sure but it looks like the update firmware has been removed from LMSA.
If this is the case, you have to flash manually or use the rescue option which will factory reset the device.
Using the rescue option is the easier method
if you don't mind losing your data, and re-rooting.
Flashing may be a little tricky the first few times, but is good to know how to do if you are modifying your device (rooting)/
See how to get the correct flash commands from the flash_file.xml
Just remove the "erase userdata" line from the commands, it's usually the last line.
Online FlashFile Converter
Click to expand...
Click to collapse
Done brother, everything's ok now, I have been able to install the OTA update, and also have root status. Well, it didn't go the way I wanted, I mistakenly flashed the stock ROM instead of disabling root and flashing the stock boot.img but my work is done. I installed the OTA update after that and re-rooted my phone again. Lost all the data but now I'm enjoying an up-to-dated phone and with root of course.
And also, I have got the solution in case if anybody want to know about the STOCK BACK UP DOESN'T EXIST problem while installing OTAs by Magisk. So you're welcome anytime to ask me. Hahahaha.
Hello everyone hope you are all keeping well.
Here is a little guide on how to Unlock/Lock the Bootloader and Root/Unroot our Nord2T.
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
Unlock The Bootloader;
If you haven't done it already...beware that this will erase all of your user data. To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
Rooting Guide;
Unlocking the Bootloader is necessary before continuing
1 - Download Nord2T stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Spoiler: Global Build boot.img's
Stock boot CPH2399_11_A.07 (did not extract it and can't find the firmware file to be able to download and extract, if someone could please upload a link to it on this thread I would sincerely appreciate it)
Stock Boot CPH2399_11_A.09
Stock Boot CPH2399_11_A.11
Stock Boot CPH2399_11_A.14
Stock Boot CPH2399_11_A.15
Stock Boot CPH2399_11_A.16
Stock Boot CPH2399_11_A.17
Stock Boot CPH2399_11_A.19
Stock Boot CPH2399_11_C.24
Stock Boot CPH2399_11_C.26
Stock Boot CPH2399_11_C.27
Spoiler: IND Build boot.img's
Stock Boot CPH2401_11_A.11
Stock Boot CPH2401_11_A.13
Stock Boot CPH2401_11_A.14
Stock Boot CPH2401_11_A.15
Stock Boot CPH2401_11_A.16
Stock Boot CPH2401_11_A.17
Stock Boot CPH2401_11_A.18
Stock Boot CPH2401_11_A.19 (I didn't capture the download for this, if anyone has it please send me a link to the official OTA)
Stock Boot CPH2401_11_C.23
Stock Boot CPH2401_11_C.24
Stock Boot CPH2401_11_C.26
Stock Boot CPH2401_11_C.27
2 - Download latest Magisk Manager from HERE and install it on your phone
3 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
4 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
5 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
6 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
7 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
System Updates;
For system updates. Just apply the OTA update as normal.
Once updated you will have no root and you must follow steps above again with the new boot.img that corresponds to the firmware version you are on.
Unroot;
To unroot simply flash the stock boot.img.
Relock Bootloader;
If you have TWRP installed flash the stock boot.img (same as your firmware version from earlier in this post)
This is so as you can access fastboot properly.
1 - To relock Bootloader first download Oxygen Updater app from the Playstore.
2 - Download the firmware which corresponds to the firmware which you have currently installed.
3 - Move/copy this firmware.zip to your PC and extract it. (inside you will see a folder and a couple files. The only file we need is payload.bin)
4 - Download/install Fastboot Enhance on your PC
5 - Reboot phone to bootloader mode so it gets detected by Fastboot Enhance, from there boot to fatsbootd.
6 - Flash payload.bin in Fastboot Enhance
7 - Wipe data in fastbootd from your Nord 2T, reboot and finish phone setup.
8 - Enable developer options, enable USB debugging from developer options.
9 - Reboot to bootloader and run the command;
Code:
fastboot flashing lock
The device will be now successfully locked.
Hope this helps out
Thank you so much
Thanks so much. Going to try this weekend with my daughter phone.
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
jolaviska said:
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
Click to expand...
Click to collapse
No I still haven't received the ota. Did you get updated to this version already?
I received the update but refusing to apply it
jolaviska said:
I received the update but refusing to apply it
Click to expand...
Click to collapse
It will show up again.
Don't worry.
Rooted my Nord 2T successfully. Thanks once again
Download Nord2T stock boot.img
Click to expand...
Click to collapse
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
luke! said:
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
Click to expand...
Click to collapse
By using THIS software. I will always update this thread with the latest boot.img files in the future but this is the software I used
Thank you.
And what is the procedure to OTA update, once we have magisk_patched_boot.img installed.
OTA won't install, so need to revert somehow install new update and root again?
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Stock Global boot CPH2399_11_A.11 added to OP. Sorry for the delay, only received the update today
nielsync said:
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Click to expand...
Click to collapse
Ya I didnt do it this way at all because my device updated while i was asleep and i was unrooted, so I had to patch the new boot using the method in the OP.
I would definitely advise restoring the stock boot.img before proceeding with an update, then install the update normally and just patch the new image with magisk and then flash.
For a while the 'install to inactive slot' option only works on certain devices, the Nord 2T obviously is'nt one of those devices.
I'm sure the magisk documentation recommends restoring stock images before an update.
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
cioce said:
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
Click to expand...
Click to collapse
I didn't want to share any of the magisk images because there is a new version of magisk every other week and people may like to be on the beta branch or canary branch of magisk or whatever.
It's very easy to patch the image though. Just download magisk.apk and use it to patch the boot.img's I've provided above. Then move the patched.img to your pc and flash.
But anyways here is the magisk patched.img for CPH2399_11_A.11 using magisk 25.2 stable
Stock Boot for Indian variant CPH2401_11_A.13 added to OP
can u post the latest update boot.img for indian unit CPH2401_11_A.14
Stock boot for Indian CPH2401_11_A.14 added to OP
Stock boot for Global CPH2399_11_A.14 added to OP