Related
The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Edit: oem unlock will fix drk - if not you must follow next step
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
If you cannot be bothered doing by yourself you can pay https://www.facebook.com/gsm.xraxxx/ to do this.
(after he used plexihub to fix phone, i believe he is using similar method. It doesn’t seem fair to post this guide as i’ll be damaging his income but it seemed also unfair to keep this as a secret. If you want to donate to me please donate to him and his team instead at https://spacial-file.com/ or paypal [email protected] Thx)
Special Thanks to -
Samsunguser932 - testing this guide you can see his post on https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
Ravi Kumar - for his help in giving me clues how to fix.
Resources: (where i got most my info)
https://forum.xda-developers.com/galaxy-note-8/help/unbrick-methods-t3703767
https://forum.xda-developers.com/galaxy-note-8/help/to-fix-efs-secondary-note-8-t3785600
https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
http://forum.gsmhosting.com/vbb/f453/samsung-s8-g955f-2426383/
Comment below for help.
Give me a thanks if you find this guide very/extremely helpful. :angel:
Share it with those in need.
edit: not all images were able to upload
update: to skip 7 day oem unlock imei must be 0000
The best method for bypassing oem unlock for 7 days.
Requirements - clean phone with stock firmware, samsung account logged in, imei 0000
Go to setting and check for manual update. This will fail/stuck and oem unlock would appear in development settings
Reserved
hello , i have samsung j737t with bad efs ,
Recovery error E:Failed to mount /efs (Invalid argument)
any help please ,i have cert in hand
maxpatri9 said:
hello , i have samsung j737t with bad efs ,
Recovery error E:Failed to mount /efs (Invalid argument)
any help please ,i have cert in hand
Click to expand...
Click to collapse
Try the above guide. This guide isn't just designed for the note 8.
from what file i need to create efs.img for s8+ g955F?
ditternation said:
from what file i need to create efs.img for s8+ g955F?
Click to expand...
Click to collapse
You do not need an efs.img to repair efs failed to mount. It is only required for the functionality of the phone (sim). This guide would work without an efs.img, it is recommended to install a custom rom after the guide. Even though this guide can allow you phone to work, but due to drk/dm-verify errors, it is currently impossible to restore the phone to the original state.
Note - you'll need to find someone that is kind enough to share a copy/backup of their efs.img g955F. Most people think it is illegal to share as the efs.img contain imei, but with cpid devices, the imei would be overridden by your current device. Most importantly you need to change the serial number in the SVC (or else you will have the same serial number as the person sharing.
plz my problem is oem lock on, frp on and drk error. i have combination file and stock can your guide work for me?
soundn said:
plz my problem is oem lock on, frp on and drk error. i have combination file and stock can your guide work for me?
Click to expand...
Click to collapse
This would only work if you're still on binary 3. Follow the steps for DM verity fix with 7.1.1 firmware. Flash stock 7.1.1 with replaced boot.img using Odin and fix frp using adb (guides online to enable adb). Wait for 7 day OEM unlock (no method to skip do not restart). Flash twrp and use twrp to flash custom ROM or DM verify fix.
Note - this method would fix function ability of the phone only if efs is not corrupted. (If you had paid someone to fix efs, this would not work). Finally the phone will become Knox 1 and normal update functions might not work. Practically makes the phone unable to resell as a working phone.
Hello. My efs partition was erased by a z3x box. Or an octopus, I do not know. I followed your instructions. The IME combination is empty. I install a modified firmware, it works but I can not enter the Samsung account (crashing), I can not check the system updates (infinite device registration). Should I wait 7 days before the OEM unlock? Will it work?
@Alarg read post 2 to skip 7 days. Infinite device registration should make OEM unlock show with samsung account logged in. OEM unlock must be first done before installing modified firmware (suggest kernel). You must have backup of efs, a backup from another phone will not work.
bluecub1st said:
@Alarg read post 2 to skip 7 days. Infinite device registration should make OEM unlock show with samsung account logged in.
Click to expand...
Click to collapse
I can't log in Samsung account (processing failure). Imei unknown, s/n 0000000000 This method does not work for me.
@Alarg Which firmware ver are you using?
Have you tried nand flash combination file and then flash firmware (before boot, hold download mode buttons so the phone won't boot to factory mode). I do not see a reason why Samsung account would not work, try another ver maybe the version you downloaded is corrupted.
bluecub1st said:
The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
If you cannot be bothered doing by yourself you can pay https://www.facebook.com/gsm.xraxxx/ to do this.
(after he used plexihub to fix phone, i believe he is using similar method. It doesn’t seem fair to post this guide as i’ll be damaging his income but it seemed also unfair to keep this as a secret. If you want to donate to me please donate to him and his team instead at https://spacial-file.com/ or paypal [email protected] Thx)
Special Thanks to -
Samsunguser932 - testing this guide you can see his post on https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
Ravi Kumar - for his help in giving me clues how to fix.
Resources: (where i got most my info)
https://forum.xda-developers.com/galaxy-note-8/help/unbrick-methods-t3703767
https://forum.xda-developers.com/galaxy-note-8/help/to-fix-efs-secondary-note-8-t3785600
https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
http://forum.gsmhosting.com/vbb/f453/samsung-s8-g955f-2426383/
Comment below for help.
Give me a thanks if you find this guide very/extremely helpful. :angel:
Share it with those in need.
edit: not all images were able to upload
update: to skip 7 day oem unlock imei must be 0000
Click to expand...
Click to collapse
thanx! for your guide but i have this problem after taking an official OTA!
DM-Verity ERRor!
any help will be greatly appreciated!
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
klisza1993 said:
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
Click to expand...
Click to collapse
Just Google "EFS android"
pixel989 said:
thanx! for your guide but i have this problem after taking an official OTA!
DM-Verity ERRor!
any help will be greatly appreciated!
Click to expand...
Click to collapse
Follow
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
Click to expand...
Click to collapse
Note -
dm verify cannot be completely fixed, it can only be bypassed (in the system by flashing no dm verify).
You will need to wait for 7 days for oem unlock (there is no method to skip oem unlock)
Warranty will be voided (KNOX 1) - don't think there is a method to avoid tripping knox.
Suggest installing a custom rom after oem unlock (many reports that no dm verify on latest oreo does not work without root)
klisza1993 said:
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
Click to expand...
Click to collapse
EFS partition is not touched when flashing roms (they actually do but in a safe way), only retards like I would try to mod efs partition.
Hi guys, will it work in my case? https://ibb.co/mJRcHK
Device is SM-N950N FRP ON and OEM ON.
What kind of solution should I follow?
@Anvar2005 - This looks like a drk verify error. Which binary are you on? frp bypass only works with binary 3. You will not find anything for frp unlock on this forum. Same steps for drk verify but use nougat.
Hello,
I've uploaded some image files for Nokia 3.2 and want to share them.
I've packed some images for Nokia 3.2 00WW variant (e.g. Magisk, fastboot ROM) and will upload user images for the 00EEA variant, too.
It just needs some more time to upload completely.
EDIT: I transfered all the files to Mega.nz
https://mega.nz/folder/hVMTiCbT#OhmmxhtKabnNn2hWfiIgHQ
P.S. if someone has the european Variant and wants to provide matching Magisk Patched boot images just send me a link to those and i will add them to my Mega.nz folder
Hello,
i just uploaded the patched boot image december 2019 for the europe 00EEA version in other thread under https://forum.xda-developers.com/attachment.php?attachmentid=4929795&d=1579367908.
Perhaps you can add it to your google drive.
Greetings
Hi, sorry i didnt see it. Could you created a Copy of it with dm-verity disabled? You can do it with superr's kitchen. So that we have a magisk Image for GSIs.
Thanks
P.S. i will Upload the magisk patched image tomorrow.
EDIT: I can Just remove dm verity on my own. :silly:
I've created a Telegram Channel for Nokia 3.2
Updates regarding Source Code, the Google Drive mirror (magisk stuff,Firmwares etc.) And any helpful information will be posted by me on the Channel.
Note information inside ReadMe file on the Google Drive link
TA-1156 Qcn
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
chinovaso said:
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
Click to expand...
Click to collapse
Hi I don't have any qcn file. My Nokia 3.2 is currently being repaired. But I've found a tool what could help you.
https://www.getdroidtips.com/download-imei-qcn-tool/
Just test it and look if it works
chinovaso said:
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
Click to expand...
Click to collapse
Thank you s3tupw1zard, but I try this tool already, it works , *06# when it checks it shows the imei numbers but there still no a gsm signal.
Also the serial number is shown as 012345678E0000 and in *#*#4636#*#* servise menu when i chek says Mobile radio is oFF
How to flash using fastboot
Hey mate
Can u guide me through flashing magisk boot img
Im kinda of confused becoz of A B partitions
Any detailed guide would be appreciated
Im on latest January update 2020
Nokia 3.2 (deadpool)
chinovaso said:
Thank you s3tupw1zard, but I try this tool already, it works , *06# when it checks it shows the imei numbers but there still no a gsm signal.
Also the serial number is shown as 012345678E0000 and in *#*#4636#*#* servise menu when i chek says Mobile radio is oFF
Click to expand...
Click to collapse
Hi,
I can't help you in this case. Best would be if you send it in.
You can get your imei with 'fastboot getvar all' (without quotes) to send it in.
You need the imei for sending it in. Dont worry about warranty the ar not allowed anymore to denying warranty due to new google terms.
Just go to nokia website and order a repair.
No0bGuy said:
Hey mate
Can u guide me through flashing magisk boot img
Im kinda of confused becoz of A B partitions
Any detailed guide would be appreciated
Im on latest January update 2020
Nokia 3.2 (deadpool)
Click to expand...
Click to collapse
I write a short guide into a new thread. I pack some files for gsi flashing together.
You will find this guide in about 30 Minutes on the Nokia 3.2 Guides section
Hello,
i uploaded the january 2020 patched boot.img for the European 00EA with dm-verify=off.
Please include on your googledrive!
https://forum.xda-developers.com/attachment.php?attachmentid=4956671&d=1582404743
Greetings
Using these images
Hi All
i've bought a Nokia 3.2 for installing lineageOS ! So i could unlock it and installed this ASOP-Image (probably the 00WW-Version) thru ADB and fastboot with the result to get a crappy OS without WiFI.
At the end i needed about 10 days to get a connection (probably thru qualcomm-drivers) to the pc again, where i can use your (hopefully working) images.
In order to avoid a malfunctioning NOKIA, i am asking about the right way to install the 00EA-Version:
Again i can use adb and fastboot, so first step is to use flash-user-bin.bat for flashing boot.bin, dtbo.bin, system.bin, vendor.bin and vbmeta.bin !
Now there should be a working OS with WiFI, second step would be patching boot_jan2020_dmOFF_00EA.img and third step patching twrp-3.2-dpl-00eea.img.
At last it should be possible to install LineAgeOS thru Magisk Manager (or CWM) ?
Thanks for your advices
Your device needs the images with the same version. So boot.img from January combined with firmware from December lead into bugs like WiFi not working. Reboot to bootloader, there is a info where either 00WW (international Variant) or 00EEA (European Variant) is written. I've uploaded a GSI base for both variants on the Google drive Link at the beginning of this thread. You can find both base 7z Files Inside GSI folder. But be sure which Variant you have. After executing flash-all.bat execute the other bat file (it will flash magisk patched img with dm-verity removed) and after that finishes you can flash any GSI to system.
And you can't install ROMs through Magisk. It is Superuser. You need to be in Bootloader mode.
And USB debugging needs to be on and your PC needs to be authorized by your device. Just activate USB debugging in developer options and type adb devices. There should appear a prompt.
thx
for fast reply. It should be 00EEA, because i've bought it in Austria. I think, i have seen it in the settings/my phone too.
So i will use the GSI-Version tomorrow. With Magisk-Manager i should could load this TWRP-Image (on a SD-Card) too ?
Stupid Question: what is the meaning of the shortciut GSI ?
Regards
other bat-file
s3tupw1zard said:
Your device needs the images with the same version. So boot.img from January combined with firmware from December lead into bugs like WiFi not working. Reboot to bootloader, there is a info where either 00WW (international Variant) or 00EEA (European Variant) is written. I've uploaded a GSI base for both variants on the Google drive Link at the beginning of this thread. You can find both base 7z Files Inside GSI folder. But be sure which Variant you have. After executing flash-all.bat execute the other bat file (it will flash magisk patched img with dm-verity removed) and after that finishes you can flash any GSI to system.
Click to expand...
Click to collapse
Hi s3tupw1zard !
where is this other bat-File ? This GSI (generic system image)-Folder of 00EEA is empty, but i've used user_images_00EEA.7z and this is working perfectly.
In spite of it i would like to change booting (with magisk-patched.img). but this is existing for 00WW only. I've tried to flash twrp-Image too, but there i've got errors, so i've flashed user_images_00EEA completely again.
Thanks for your work
At last
i could create something, but still there is something missing !
I've downloaded boot_nodm_magisk_patched.img from shared googleDrive and patched it with MagiskManager.
Unfortunelately i tried to flash this file without renaming - so i had to reset to factory settings, because booting was not working.
After that, i was remembering to rename this boot-file to boot.img, flashed to factory new system - following flashing the system with LineAgeOS from Andy - https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/ (renamed it to system.img)
The result: booting procedure for working LineAgeOS needs about 5 minutes and wifi is missing !
Does anyone have a clue ?
Do i need to setup system with user-Image (December 2019) from Manuels Google Drive before ?
ThankYou for advices
Gerhard
Then you flashed the wrong boot.img.
You must look for your Version - 00WW or 00EEA - and you must have the corresponding security level to your firmware, means January or December ........
00ww - 00eea
page1875 said:
Then you flashed the wrong boot.img.
You must look for your Version - 00WW or 00EEA - and you must have the corresponding security level to your firmware, means January or December ........
Click to expand...
Click to collapse
thanks for reply.
If i am lucky, i will use boot_jan2020_dmOFF_00EA.img next time - but for now i have (possibly) corrupted partition table file and so device is ended in a fastboot-mode loop - Android ONE Logo flashes up less than 1 second
So hopefully with fastboot flash partition Firmware\gpt_both0.bin (gpt_both0.bin from Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL) i can restore partition table file in spite of this 00WW-Version.
Does anyone have seen firmware for 00EEA-Version ?
cheers
Idiots Guide
The reason for infinite bootloop and ADB-Flash error messeage 'FAILED (remote: partition table doesn't exist)' may be (as i remember) is to rename boot.bin from user_images_00EEA of our wizard to boot.img.
Resetting to factory defaults is not possible anymore - so beware of it !
is there a custom rom SM-A107f ?
and how to install TWRP recovery on SM-A107f?
-No
-And does not exist yet from what I can tell.
ShaDisNX255 said:
-No
-And does not exist yet from what I can tell.
Click to expand...
Click to collapse
thats a sad news
Consider this
ddiv1de said:
thats a sad news
Click to expand...
Click to collapse
Have you tried gsi roms? for more information head over to geektoandroid.com i hope this helps
Infant9099 said:
Have you tried gsi roms? for more information head over to geektoandroid.com i hope this helps
Click to expand...
Click to collapse
I've tried a couple, none have booted for me.
GSI Treble rom
ShaDisNX255 said:
I've tried a couple, none have booted for me.
Click to expand...
Click to collapse
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Infant9099 said:
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Click to expand...
Click to collapse
You have the A10, which is a bit different than the A10s so it is most likely that any GSI that boots to your phone will not boot for mine. Besides, A10s does not have TWRP yet and A10 does
Infant9099 said:
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Click to expand...
Click to collapse
any luck pal?
Infant9099 said:
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Click to expand...
Click to collapse
any luck pal?
Can A107F (A10s) be rooted?
Rootthegalaxy said:
Can A107F (A10s) be rooted?
Click to expand...
Click to collapse
Yes.
how to root SM-A107f Samsung Galaxy A10s
ShaDisNX255 said:
Yes.
Click to expand...
Click to collapse
so this is what i did to root my A10s.
1. check what binary your phone is running I already updated mine so my phone is on Android 10 binary 6.
how to check your binary - goto setings-about phone-software info, check Baseband version so on my phone its A107FXXU6BTES the U6 indicates your binary some has U3 binary 3 or U5, S5 binary 5
once you determined your binary.
2. activate DEVELOPER OPTIONS then activate OEM UNLOCK
samfw.com/firmware/SM-A107F/XTC/A107FXXU6BTF
go to this website and download the appropriate firmware.
each will contain a BL, AP, CP, and Home_CSC.
3. once finished downloading unlock your bootloader just boot to download mode then there is an option to press and HOLD VOLUME UP to unlock bootloader then press volume up again. if it didn't reboot instantly press and hold volume up and down again just do it again until when you choose to unlockbootloader it will reboot instatly.
4. after unlocking bootloader just go through the entire process of setting up your phone keep the bootloader unlock, INSTALL Magisk manager, so yeah install magisk choose patch image then from your downloaded firmware remove the "MD5" at the end of the files so it will be AP_A107F.tar then choose the AP to patch hrough magisk
5. after patching copy the patched file to your PC extract it by WINRAR get the boot.img if its boot.img.lz4 it means patch was not sucessful
6. after getting the boot.img copy it to your phone again and patch again make sure to rename it boot.img from inside the generated patch file then compress it as TAR using 7zip
7. flash it through odin on AP section and there your magisk rooted.
sorry for the long post
nyxl said:
how to root SM-A107f Samsung Galaxy A10s
so this is what i did to root my A10s.
1. check what binary your phone is running I already updated mine so my phone is on Android 10 binary 6.
how to check your binary - goto setings-about phone-software info, check Baseband version so on my phone its A107FXXU6BTES the U6 indicates your binary some has U3 binary 3 or U5, S5 binary 5
once you determined your binary.
2. activate DEVELOPER OPTIONS then activate OEM UNLOCK
samfw.com/firmware/SM-A107F/XTC/A107FXXU6BTF
go to this website and download the appropriate firmware.
each will contain a BL, AP, CP, and Home_CSC.
3. once finished downloading unlock your bootloader just boot to download mode then there is an option to press and HOLD VOLUME UP to unlock bootloader then press volume up again. if it didn't reboot instantly press and hold volume up and down again just do it again until when you choose to unlockbootloader it will reboot instatly.
4. after unlocking bootloader just go through the entire process of setting up your phone keep the bootloader unlock, INSTALL Magisk manager, so yeah install magisk choose patch image then from your downloaded firmware remove the "MD5" at the end of the files so it will be AP_A107F.tar then choose the AP to patch hrough magisk
5. after patching copy the patched file to your PC extract it by WINRAR get the boot.img if its boot.img.lz4 it means patch was not sucessful
6. after getting the boot.img copy it to your phone again and patch again make sure to rename it boot.img from inside the generated patch file then compress it as TAR using 7zip
7. flash it through odin on AP section and there your magisk rooted.
sorry for the long post
Click to expand...
Click to collapse
HOW THA?
it worked guy
thank yu guy
I hope that you maybe able to help me as my bootloader will not load
1 The OEM UNLOCK is on
2 Have pressed buttons as instructions but the phone just switches of
guyz that they dont know how to write magisk patch with odin
i had same problem that when i started to writing i got a failed error
if your bootloader is unlocked and yu renamed patched.img to boot.img
but yu got error do this :
change your frimware
if your a10s frimware is
A107FU5ATA9 it dosent support any root . change your frimware to a107fxxs5asl3
now start patching magisk !
Mirloo_HK said:
guyz that they dont know how to write magisk patch with odin
i had same problem that when i started to writing i got a failed error
if your bootloader is unlocked and yu renamed patched.img to boot.img
but yu got error do this :
change your frimware
if your a10s frimware is
A107FU5ATA9 it dosent support any root . change your frimware to a107fxxs5asl3
now start patching magisk !
Click to expand...
Click to collapse
Hi '''Mirloo''''About rooting the (Samsung Galaxy 10s SM-A107f) I have tried most of the rooting akps with no luck (cfautoroot I have not tried yet)'''''''As for using Odin & magisk I am getting so many different instructions from different posts
1 unlock the bootloader This I have done successfully
The next steps using Magisk & Odin Start to get misleading
one site says Copy the AP to your phone and patch it where another site says says change the format of the AP file to tar by deleting .mds then copy it to your phone
I seem to get confused now as what to do next ''''Please could you give me full instructions ....Thank you
I have attempted to patch boot.img around 7 times unsuccessfully, I have the SM-A107F, can someone please send me the correctly patched boot image for my device, will be much appreciated.
i have this device, SM-A107F/DS, still no custom rom? is it possible to install lineage os?
fatdog1 said:
i have this device, SM-A107F/DS, still no custom rom? is it possible to install lineage os?
Click to expand...
Click to collapse
I'm also waiting for this. Tried flashing twrp recovery using odin but I failed. The error says "only official binaries are allowed to be flashed" tried flashing the original firmware but same error. Wondering why.
Hello is the Galaxy tab s7+ wifi model bought in the us rootable? i ask this becuase i know that the us model galaxy phones arent rootable so im asking if the same applys to the tablets
Yes, it is rootable, just rooted my SM-T970 today
Can you still watch netflix/amazon in HD after rooting? On which windevine level are you now?
I don't use either of these services, so I don't know, sorry.
BigBucha said:
Yes, it can be rooted, just rooted my SM-T970 today
Click to expand...
Click to collapse
merhaba s7'm var artı t970'im var nasıl rootlayacağız
Translation: hello i have s7 plus i have t970 how do we root
I followed this guide below that I found somewhere in this forum, it is not mine, I just added some notes to it. I recommend searching for the original thread. There could also be a newer firmware version now, please check yours before rooting. It has been almost 2 months since I did it.
Unlock OEM (under developer options)
Boot in download mode (with the tablet powered down, press volume up + volume down and connect USB cable to PC)
Long press volume up to unlock bootloader (you will lose all your data!)
Download the original firmware ( https://www.sammobile.com/samsung/galaxy-tab-s7/firmware/SM-T970/XAR/download/T970XXU1ATJ4/502568/ )
Flash it using ODIN in download mode (Optional, just to make sure you are using the same image you are going to patch)
Extract boot.img.lz4 from AP_xxxx tar file.
Decompress the lz4 to get the uncompressed boot.img (I had to use a separate tool since 7zip was not able to compress/uncompress the lz4 archive, https://github.com/lz4/lz4/releases )
Copy the file to the tablet
Patch it using the latest Magisk Manager. ( https://github.com/topjohnwu/Magisk)
Copy the patched boot image back to the PC.
Recompress it as boot.img.tar (rename magisk_patched.img to boot.img then compress as boot.img.tar)
Flash it using AP slot in Odin and reboot tablet. (I had to do a full factory reset)
Install Magisk again
For AdAway to work you will need to enable systemless module in Magisk
You are done! Magisk manager should say now it is rooted. (you will also have a BIG warning every time the tablet is powered on, telling you how irresponsible and despicable you are by modifying the device)
I rooted my Samsung S20 before by following this guide
it is very similar to what is described above.
BigBucha said:
Mod edit, broken quote removed
Click to expand...
Click to collapse
Mod edit: Google Translate translation added.
I have android 11 installed on my device, can you help me with remote team use?
Original post:
Cihazımda yüklü android 11 var, uzak ekip kullanımında bana yardım edebilir misin?
@simerenya Please use English on XDA Forums. If you want, you can use the translating service of your choice. See the forum rules for more details.
@BigBucha I suggest that you do not link to that particular website for Magisk downloads (or any other website that pretends to be the Magisk website). None of those websites are run by @topjohnwu and in the best case they're just re-hosting the files to get ad-revenues, but in the worst case you'll download a malicious version of Magisk. That wouldn't be good. The only place for sure and safe downloads of Magisk is on @topjohnwu's Github: https://github.com/topjohnwu/Magisk
@Didgeridoohan , understood, thanks! I didn't know about Magisk's official web site, just googled it. I updated my previous post.
@simerenya,
Not sure if I understood your question. I used google translate.
You asked for a screen-sharing session?
I have done rooting of this tablet model only once myself, that was 2 months ago, not sure if I can be of much help to you.
Please try following the guide step by step yourself. If in doubt, I recommend not doing this since you may brick your tablet.
You can post your questions in the forum if you get stuck or brick your device. I will try to answer them.
I was able to root my tablet from the first try.
Good luck.
Is it possible to root Galaxy tab s7+ using Kingroot, kingoroot, towelroot, or any of the other 1 click rooting apps?
BigBucha said:
I followed this guide below that I found somewhere in this forum, it is not mine, I just added some notes to it. I recommend searching for the original thread. There could also be a newer firmware version now, please check yours before rooting. It has been almost 2 months since I did it.
Unlock OEM (under developer options)
Boot in download mode (with the tablet powered down, press volume up + volume down and connect USB cable to PC)
Long press volume up to unlock bootloader (you will lose all your data!)
Download the original firmware ( https://www.sammobile.com/samsung/galaxy-tab-s7/firmware/SM-T970/XAR/download/T970XXU1ATJ4/502568/ )
Flash it using ODIN in download mode (Optional, just to make sure you are using the same image you are going to patch)
Extract boot.img.lz4 from AP_xxxx tar file.
Decompress the lz4 to get the uncompressed boot.img (I had to use a separate tool since 7zip was not able to compress/uncompress the lz4 archive, https://github.com/lz4/lz4/releases )
Copy the file to the tablet
Patch it using the latest Magisk Manager. ( https://github.com/topjohnwu/Magisk)
Copy the patched boot image back to the PC.
Recompress it as boot.img.tar (rename magisk_patched.img to boot.img then compress as boot.img.tar)
Flash it using AP slot in Odin and reboot tablet. (I had to do a full factory reset)
Install Magisk again
For AdAway to work you will need to enable systemless module in Magisk
You are done! Magisk manager should say now it is rooted. (you will also have a BIG warning every time the tablet is powered on, telling you how irresponsible and despicable you are by modifying the device)
I rooted my Samsung S20 before by following this guide
it is very similar to what is described above.
Click to expand...
Click to collapse
Thanks for the instruction. I was finally installed magdisk on S7+ tab. Root check is good. But some app like adaway does not detect root and never ask for root access when installed. Do you know how to solve this?
xiaozi said:
Thanks for the instruction. I was finally installed magdisk on S7+ tab. Root check is good. But some app like adaway does not detect root and never ask for root access when installed. Do you know how to solve this?
Click to expand...
Click to collapse
Not sure about other apps, but for AdAway to work I had to do these steps:
1. Open Magisk
2. Go to Modules (the jigsaw icon)
3. Install "Systemless Hosts" module
4. Reboot and try selecting root mode in AdAway again
Please check this thread https://forum.xda-developers.com/t/systemless-adaway-with-magisk.3733839/
BigBucha said:
I followed this guide below that I found somewhere in this forum, it is not mine, I just added some notes to it. I recommend searching for the original thread. There could also be a newer firmware version now, please check yours before rooting. It has been almost 2 months since I did it.
Unlock OEM (under developer options)
Boot in download mode (with the tablet powered down, press volume up + volume down and connect USB cable to PC)
Long press volume up to unlock bootloader (you will lose all your data!)
Download the original firmware ( https://www.sammobile.com/samsung/galaxy-tab-s7/firmware/SM-T970/XAR/download/T970XXU1ATJ4/502568/ )
Flash it using ODIN in download mode (Optional, just to make sure you are using the same image you are going to patch)
Extract boot.img.lz4 from AP_xxxx tar file.
Decompress the lz4 to get the uncompressed boot.img (I had to use a separate tool since 7zip was not able to compress/uncompress the lz4 archive, https://github.com/lz4/lz4/releases )
Copy the file to the tablet
Patch it using the latest Magisk Manager. ( https://github.com/topjohnwu/Magisk)
Copy the patched boot image back to the PC.
Recompress it as boot.img.tar (rename magisk_patched.img to boot.img then compress as boot.img.tar)
Flash it using AP slot in Odin and reboot tablet. (I had to do a full factory reset)
Install Magisk again
For AdAway to work you will need to enable systemless module in Magisk
You are done! Magisk manager should say now it is rooted. (you will also have a BIG warning every time the tablet is powered on, telling you how irresponsible and despicable you are by modifying the device)
I rooted my Samsung S20 before by following this guide
it is very similar to what is described above.
Click to expand...
Click to collapse
get an error : blocked by OEM...What did I wrong? andoid 11 latest firmware
dolf123 said:
get an error : blocked by OEM...What did I wrong? andoid 11 latest firmware
Click to expand...
Click to collapse
Did you successfully unlock bootloader? My phone was not locked to any mobile carrier. Please paste a screenshot.
Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
magisk app-debug.apk working, but boot.img from
Model Number : SM-A217M
Region Code : COB
Device Version info :->>
BL version : A217MUBS5CUE2
AP version : A217MUBS5CUE2
DKXC said:
Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
Click to expand...
Click to collapse
Good job. thanks you, i wait updates
Elkingb said:
magisk app-debug.apk working, but boot.img from
Model Number : SM-A217M
Region Code : COB
Device Version info :->>
BL version : A217MUBS5CUE2
AP version : A217MUBS5CUE2
Click to expand...
Click to collapse
Forgot to mention that I used the latest DBT boot image for SM-217F/DSN. Not sure if it works for other models, but there aren't really many models anyways.
DKXC said:
Forgot to mention that I used the latest DBT boot image for SM-217F/DSN. Not sure if it works for other models, but there aren't really many models anyways.
Click to expand...
Click to collapse
For SM-217M Working full
everything is fine for the SM-217F
Im waiting for the twrp so much Good job!
To DKXC:
Hi There Expert,
I Would Recommend You To Upload Your Project To Github,
So Everyone Will Be Able To Give You Feedback
It Will Probably Help You In Developing A Better A21s Community
LonelyCracker said:
Github twrp a21s
Click to expand...
Click to collapse
Flashing this patched_magisk_v23\boot.tar ain't working.
Error displayed on the DL screen:
Only official released binaries are allowed to be flashed (BOOT)
My specs:
Loading ADB module.............OK
Starting ADB module...OK
Searching for SAMSUNG ADB device...OK
Checking device authorization...OK
Reading ADB device information...
ADB Serial Number : R58R52BFNKP
Model Name : SM-A217F
Device CodeName : A21S
Hardware : EXYNOS850 EXYNOS850
Modem Board : SHANNON318
HW Version : MP 0.500
BL version : A217FXXU5CUD6
AP version : A217FXXU5CUD6
CP version : A217FXXU5CUD4,A217FXXU5CUD4
CSC version : A217FOXM5CUD6
Android version : 11
Build date : Thu Apr 29 11:41:41 +07 2021
Country : Poland
IMEI : 35xxxxxxxx691
Serial Number : N/A
Carrier : XEO
Unlock by IMEI : Unknown
SIM State : ABSENT,ABSENT
Debug Level : 0x4f4c
CP Debug Level : N/A
Warranty VOID : 1
SIM operator : N/A
USB Settings : MTP,ADB
SamKEY Team (2017)
Installed app-debug.apk (patched Magisk) onto the phone.
Downloaded original XEO firmware.
Samfw.com_SM-A217F_XEO_A217FXXU5CUD6_fac.zip
Unzipped it.
Found AP file inside unzipped folder:
AP_A217FXXU5CUD6_CL21209953_QB39896814_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Unpacked the AP file.
Contents:
Decoded the boot.img.lz4 file using LZ4 tool:
Copied boot.img file to the phone internal memory.
Opened Magisk and patched the boot.img file, which created magisk_patched-23001_nmETW.img in the phone Downloads folder
Copied patched file (magisk_patched-23001_nmETW.img) from the phone to my laptop - and changed its name to boot.img
Compressed it into boot.tar file using 7zip.
Restarted the phone into DOWNLOAD mode (using SamKey, or adb, or key combinantion, whatever).
Put boot.tar into AP section in ODIN.
Go to Options tab and disable "Auto Reboot", make sure "Re-Partition" is also disabled.
Aaand it fails again.
And the message in phone DL mode says:
Only official released binaries are allowed to be flashed(boot)
Perhaps vsmeta.img also needs to be included into the tar file?
No idea how to move on with this subject.
skazi.chris said:
Installed app-debug.apk (patched Magisk) onto the phone.
Downloaded original XEO firmware.
Samfw.com_SM-A217F_XEO_A217FXXU5CUD6_fac.zip
Unzipped it.
Found AP file inside unzipped folder:
AP_A217FXXU5CUD6_CL21209953_QB39896814_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Unpacked the AP file.
Contents:
View attachment 5336407
Decoded the boot.img.lz4 file using LZ4 tool:
View attachment 5336525
Copied boot.img file to the phone internal memory.
View attachment 5336527
Opened Magisk and patched the boot.img file, which created magisk_patched-23001_nmETW.img in the phone Downloads folder
View attachment 5336541View attachment 5336543
Copied patched file (magisk_patched-23001_nmETW.img) from the phone to my laptop - and changed its name to boot.img
Compressed it into boot.tar file using 7zip.
View attachment 5336545
Restarted the phone into DOWNLOAD mode (using SamKey, or adb, or key combinantion, whatever).
Put boot.tar into AP section in ODIN.
Vá para a guia Opções e desative "Reinicialização automática", certifique-se de que "Re-Partição" também esteja desativado.
View attachment 5336551
Aaand ele falha novamente.
View attachment 5336553
E a mensagem no modo DL do telefone diz:
Apenas binários lançados oficialmente podem ser atualizados (boot)
View attachment 5336559
Talvez o vsmeta.img também precise ser incluído no arquivo tar?
Não tenho ideia de como seguir em frente com esse assunto.
Click to expand...
Click to collapse
Edit3: Use MiracleBox to pass the Prenormal you have to Checking, I had this problem on J7NXT, and I made this post to help.
Edit4: Full AP patch on Magisk, and use full patched on Odin.
First with Unlock, go to developer options and activate Unlock Bootloader, restart in download mode, Press the Vol UP button, if reset only, do it again, Download->VolUP Mode, until formatting, In download mode, with all Unlock, go to Odin. Now with the Magisk patched file modified for the A21s, the entire Magisk .tar, you don't need to unpack boot.img.lz4, After this it is normal to start, it will give you an unlocked system alert, just press the Power button to continue, then an Unofficial System warning will appear and just wait A few seconds it starts normally (first boot takes considerable time)
Some tips:
-With V23 use LsPosed to use Xposed framework, Edxposed has infinite log bugs, which causes conflict and slowdown.
-For SatefyNet, Use MagiskHide only apps needed to avoid unnecessary processes, install Universal SatefyNet Fix module, Only this gets through SafetyNet, you don't need to install additional modules for SafetyNet, it will just slow down the system.
For those who use Lucky Patcher:
-Use in LsPosed, and activate it for System Framework and Play Store, you don't need to activate for each app, it will only slow down. Use CorePatch to go through the signatures as Lucky Patcher cannot do this function on Android 11. Use Lucky Patcher with LsPosed as LP Patch's are not compatible with Android 11 But LSPOSED does, so it can work just fine.
For those who use Game Guardian:
-It is best to use a Virtual System, as its functions on Android 11 are limited as it is not 100% compatible.
All I have from my own experience is:
-Avoid redundant modules as much as possible, as they can affect the battery and the System.
To skazi.chris :
Try Unchecking Re-Partition
Jukmisael said:
Edit3: Use MiracleBox to pass the Prenormal you have to Checking, I had this problem on J7NXT, and I made this post to help.
Edit4: Full AP patch on Magisk, and use full patched on Odin.
First with Unlock, go to developer options and activate Unlock Bootloader, restart in download mode, Press the Vol UP button, if reset only, do it again, Download->VolUP Mode, until formatting, In download mode, with all Unlock, go to Odin. Now with the Magisk patched file modified for the A21s, the entire Magisk .tar, you don't need to unpack boot.img.lz4, After this it is normal to start, it will give you an unlocked system alert, just press the Power button to continue, then an Unofficial System warning will appear and just wait A few seconds it starts normally (first boot takes considerable time)
Some tips:
-With V23 use LsPosed to use Xposed framework, Edxposed has infinite log bugs, which causes conflict and slowdown.
-For SatefyNet, Use MagiskHide only apps needed to avoid unnecessary processes, install Universal SatefyNet Fix module, Only this gets through SafetyNet, you don't need to install additional modules for SafetyNet, it will just slow down the system.
For those who use Lucky Patcher:
-Use in LsPosed, and activate it for System Framework and Play Store, you don't need to activate for each app, it will only slow down. Use CorePatch to go through the signatures as Lucky Patcher cannot do this function on Android 11. Use Lucky Patcher with LsPosed as LP Patch's are not compatible with Android 11 But LSPOSED does, so it can work just fine.
For those who use Game Guardian:
-It is best to use a Virtual System, as its functions on Android 11 are limited as it is not 100% compatible.
All I have from my own experience is:
-Avoid redundant modules as much as possible, as they can affect the battery and the System.
Click to expand...
Click to collapse
Patching the entire TAR with patched Magisk did the trick. Thank you very much!
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
DKXC said:
Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
Click to expand...
Click to collapse
Haha thank you so much bro it worked for M12 too I took the apk file and flashed
Olep84 said:
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
Click to expand...
Click to collapse
Are you sure you unlock Bootloader?
[How To] Unlock Bootloader
How To Unlock Bootloader A21s. *** Disclaimer I am not responsible for any damage you made to your device You have been warned - Go to Settings -> About phone and find your build number. - Tap on your build number 6 times until you see...
forum.xda-developers.com
====#####=======
In relation to the topic, I think that this one will also be abandoned. Eagerly waiting for a developer to look at the A21S/M12 to finally get Magisk working without a patch
Olep84 said:
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
Click to expand...
Click to collapse
Have you used the patched magisk or official one; see official one doesn't work on a21s and m12 i was getting that error before but it solved by using patched one see the first post and download the .apk
I have the SM-A215U. I get the impression this method won't work for me.
I have Developers Options, but do NOT have the OEM option in that menu.
Is there anyway to unlock it without that menu item?
dbreed53 said:
I have the SM-A215U. I get the impression this method won't work for me.
I have Developers Options, but do NOT have the OEM option in that menu.
Is there anyway to unlock it without that menu item?
Click to expand...
Click to collapse
No idea