I downloaded Odin3 and Heindall, Samsung A01 core stock rom, and pacthed the AP file with magisk (https://topjohnwu.github.io/Magisk/install.html). My phone is Samsung A01 core, have OEM disabled, and have Ramdisk. I am using usb 3 and a official samsung usb cable.
i had Patched the Boot.img from AP file, and Patched the whole AP file on Magisk . so i tried to flash Boot.img with "fastboot" and tried to flash AP file on download mode with odin. Fastbot is not working to flash the "Boot.img", because the command `fastbot boot Boot.img` is not recognized (FAILED (remote: unknown command)), i had try `fastbot flash:raw boot boot.img` with no sucess too, giving me the same error.
so i am tried Jodin3, and keep trying to flash the whole magiskAP file. following the tutorial above, and Jodin3 always tell .PIT is corrupted (even generated by heimdall or using the .pit inside CSC file). but is not to work, Jodin3 keep give me errors, it say .pit is corrupted.
Some versions of ODIN for windows, don't ask for .PIT... so what i can do? Can i regenerate a PIT from a "patched AP" ?
Hey! As I see that no one has responded to you in two years, I will give you some tips.
First of all, I need to warn you that the Samsung system does not have fastboot, unlike other devices, so there is no way to use commands like that on any Galaxy device.
And secondly, I noticed that you are a Linux user. From my own experience, I recommend you try using Odin on Windows, as I've tried several times to use Jodin, and I've only had problems.
As for the .PIT, I don't know how to help you, since I don't remember anything about the procedure.
I hope I was helpfull. If you're still trying, try my tips and let me know if it worked!
adonisSMS said:
I downloaded Odin3 and Heindall, Samsung A01 core stock rom, and pacthed the AP file with magisk (https://topjohnwu.github.io/Magisk/install.html). My phone is Samsung A01 core, have OEM disabled, and have Ramdisk. I am using usb 3 and a official samsung usb cable.
i had Patched the Boot.img from AP file, and Patched the whole AP file on Magisk . so i tried to flash Boot.img with "fastboot" and tried to flash AP file on download mode with odin. Fastbot is not working to flash the "Boot.img", because the command `fastbot boot Boot.img` is not recognized (FAILED (remote: unknown command)), i had try `fastbot flash:raw boot boot.img` with no sucess too, giving me the same error.
so i am tried Jodin3, and keep trying to flash the whole magiskAP file. following the tutorial above, and Jodin3 always tell .PIT is corrupted (even generated by heimdall or using the .pit inside CSC file). but is not to work, Jodin3 keep give me errors, it say .pit is corrupted.
Some versions of ODIN for windows, don't ask for .PIT... so what i can do? Can i regenerate a PIT from a "patched AP" ?
Click to expand...
Click to collapse
This is working for me on Ubuntu.
OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux​
OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux
Try out my new Linux flash tool called Thor - https://forum.xda-developers.com/t/dev-thor-flash-utility-the-new-samsung-flash-tool.4597355, which has all the features of this tool + extras, like the usual Windows Odin ones which are missing in...
forum.xda-developers.com
Related
Hi Friends,
I flashed my samsung galaxy S5 with custom boot.img updated custom zImage, But after flash its not able to boot. Its always going in download mode. Friends on download mode screen i am seeing that "QUALCOM SECUREBOOT: ENABLE". Is it mean that bootloader is locked and for flashing i have to unlock it first but same time i have doubt if bootloader is locked then how i am able to flash.
Kernel i am downloading from samsung website for my specific phone model number. So i have less doubt on that. Atleast it should have to boot with that kernel.
arvind3023 said:
Hi Friends,
I flashed my samsung galaxy S5 with custom boot.img updated custom zImage, But after flash its not able to boot. Its always going in download mode. Friends on download mode screen i am seeing that "QUALCOM SECUREBOOT: ENABLE". Is it mean that bootloader is locked and for flashing i have to unlock it first but same time i have doubt if bootloader is locked then how i am able to flash.
Kernel i am downloading from samsung website for my specific phone model number. So i have less doubt on that. Atleast it should have to boot with that kernel.
Click to expand...
Click to collapse
Did you also put the correct rom?
[B]How to disable QUALCOM SECUREBOOT[/B]
blentavi said:
Did you also put the correct rom?
Click to expand...
Click to collapse
I extracted default boot.img from phone, Checked this boot.img by flashing in phone, its working fine. I updated this boot.img with custom zImage and then i flashed phone with this boot.img using ODIN tool.
I have more doubt on "QUALCOM SECUREBOOT: ENABLE", feels like its not allowing to boot with custom boot.img. My doubt is beacuse Original boot.img and custom boot.img hash values are different, might be this "QUALCOM SECUREBOOT:ENABLE" feature is stoping custom boot.img with different hash value to flash. Please help me if you know how to disable it.
arvind3023 said:
I extracted default boot.img from phone, Checked this boot.img by flashing in phone, its working fine. I updated this boot.img with custom zImage and then i flashed phone with this boot.img using ODIN tool.
I have more doubt on "QUALCOM SECUREBOOT: ENABLE", feels like its not allowing to boot with custom boot.img. My doubt is beacuse Original boot.img and custom boot.img hash values are different, might be this "QUALCOM SECUREBOOT:ENABLE" feature is stoping custom boot.img with different hash value to flash. Please help me if you know how to disable it.
Click to expand...
Click to collapse
live.samsung-updates.com/index.php?device=none
look there !! there are the latest FW for Samsung mobile.
Download it (maybe unzip?)
Which version of Odin are you using?
Put your phone into download mode. Pull the battery. Reinsert it. Press and hold Volume Up+Volume Down(press in the middle)+Power Button until it reboots.
Launch Odin by right clicking it and selecting Run as Administrator. Ensure that nothing Samsung related is running in the background of your PC. Check the Task Manager.
Select the PDA slot in Odin and target the firmware you unzipped earlier.
Plug your phone in to the PC using the factory supplied USB cable. Do not use hub. Odin should detect your phone. Your PC may install some drivers.
Press start in Odin.
Let the phone fully reboot. Perform a factory wipe.
blentavi said:
live.samsung-updates.com/index.php?device=none
look there !! there are the latest FW for Samsung mobile.
Download it (maybe unzip?)
Which version of Odin are you using?
Put your phone into download mode. Pull the battery. Reinsert it. Press and hold Volume Up+Volume Down(press in the middle)+Power Button until it reboots.
Launch Odin by right clicking it and selecting Run as Administrator. Ensure that nothing Samsung related is running in the background of your PC. Check the Task Manager.
Select the PDA slot in Odin and target the firmware you unzipped earlier.
Plug your phone in to the PC using the factory supplied USB cable. Do not use hub. Odin should detect your phone. Your PC may install some drivers.
Press start in Odin.
Let the phone fully reboot. Perform a factory wipe.
Click to expand...
Click to collapse
Thanks for your reply,
I searched firmware for my phone model number which is SM-G900R7, But its not there. But i think your post bring closer to my soltution. Thanks again
maybe this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=900r7
or maybe
http://alchemistar.blogspot.de/2014/06/sm-g900.html
blentavi said:
maybe this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=900r7
or maybe
http://alchemistar.blogspot.de/2014/06/sm-g900.html
Click to expand...
Click to collapse
Thanks for your replies,
Upper link i tried already, from there u can get source code for kernel and source code for file system for S5.After compilation u will get zImage and system.img. system.img i dont want to flash for now but zImage compiled from here i updated in defualt boot.img but its not booting because of KNOX feature SECUREBOOT ENABLE. So i feel i should have to flash with some unlocked firmware or KNOX disabled firmware image first.
Lower Link what you mentioned is not having binaries related to my model number, my model number is SM-G900R7. I have to get a KNOX disabled firmware for my model number SM-G900R7.
live.samsung-updates.com/index.php?device=none
I feel above link you posted earlier i can something from there. I have to try it tommorow. Here its 1 o'clock night. Going to sleep.
Thanks for your replies.
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.
Hello everyone.
I've been trying to root my Note 20 Ultra 5G (N986B/DS) running on android 12 using different instruction on YouTube and other websites, but so far I haven't had any lock and it's driving me crazy.
Here's what I have done so far:
1) I activated developer mode/unlocked OEM/activated debugging mode
2) Via Recovery Mode unlocked the bootloader so after doing a factory reset, when device turns on, there is a warning sign telling me that the bootloader is unlocked.
3) Downloaded the exact android 12 stock rom running on my device. (February security patch - XSG-N986BXXU3EVA9-N986BOXM3EVA9)
4) Extracted the rom in my computer (there are two different steps from two different sources):
4-1-1) Transferred the AP_N986BXXU3EVA9_N986BXXU3EVA9_MCL23524635_MQB48657513_REV01_user_low_ship_MULTI_CERT_meta_OS12.tar.md5 file to the device.
4-1-2) Using latest canary build of the Magisk installed on the device, I patched the ap file and then transferred it back to computer. (I also tried with the recent stable version of Magisk and the same occurred)
4-1-3) Put the device in recovery mode and then loaded BL/CP/CSC slots of the Odin3 v3.14 with the rom files and the AP slot with the patched file and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) since the operation didn't finish, I had to flash original stock files via Odin in order to boot to my device.
4-2-1) Extracted the AP file and changed the format of the file boot.img.lz4 to .tar file using 7zip and then transferred the file to my device.
4-2-2) Using latest canary build of the Magisk installed on the device, I patched the boot.img.tar file and then transferred it back to computer.
4-2-3) Put the device in recovery mode and then loaded the patched version of boot.img.tar file into AP slot of the Odin3 v3.14 and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) failing the flash process doesn't break the device and I was able to boot to my device.
Please if anyone has a clue, tell me the solution. I'm so desperate now. I've tried different workarounds in internet and non worked. I even tried installing unofficial version of TWRP and still the same message appears.
UPDATE:
I found a solution to install twrp using adb and fastboot commands. I got the device to be recognized by computer. but unfortunately "fastboot flash recovery boot.tar" command doesn't work and it sticks in sending the image state. So this method isn't working either.
UPDATE 2:
I found this post on xda dating back to 2018. According to this post I should wait 7 days (like "the ring" movie!) so that the message i referred to is gone and I can flash whatever I want.
I have had a galaxy s7 edge for some time now and I have experienced a lot of flashings with that device and never came across sth like this. Now I have to wait and see unless someone or me come up with a better solution.
P.S. I have some trust issues and I can't give team viewer or anydesk access to those who are able to help. So please don't ask for any. I kindly ask you guys to help me in anyway possible under this thread. If more information is required I will make sure to provide you with that.
Thanks in advance.
codenamefred said:
Hello everyone.
I've been trying to root my Note 20 Ultra 5G (N986B/DS) running on android 12 using different instruction on YouTube and other websites, but so far I haven't had any lock and it's driving me crazy.
Here's what I have done so far:
1) I activated developer mode/unlocked OEM/activated debugging mode
2) Via Recovery Mode unlocked the bootloader so after doing a factory reset, when device turns on, there is a warning sign telling me that the bootloader is unlocked.
3) Downloaded the exact android 12 stock rom running on my device. (February security patch - XSG-N986BXXU3EVA9-N986BOXM3EVA9)
4) Extracted the rom in my computer (there are two different steps from two different sources):
4-1-1) Transferred the AP_N986BXXU3EVA9_N986BXXU3EVA9_MCL23524635_MQB48657513_REV01_user_low_ship_MULTI_CERT_meta_OS12.tar.md5 file to the device.
4-1-2) Using latest canary build of the Magisk installed on the device, I patched the ap file and then transferred it back to computer. (I also tried with the recent stable version of Magisk and the same occurred)
4-1-3) Put the device in recovery mode and then loaded BL/CP/CSC slots of the Odin3 v3.14 with the rom files and the AP slot with the patched file and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) since the operation didn't finish, I had to flash original stock files via Odin in order to boot to my device.
4-2-1) Extracted the AP file and changed the format of the file boot.img.lz4 to .tar file using 7zip and then transferred the file to my device.
4-2-2) Using latest canary build of the Magisk installed on the device, I patched the boot.img.tar file and then transferred it back to computer.
4-2-3) Put the device in recovery mode and then loaded the patched version of boot.img.tar file into AP slot of the Odin3 v3.14 and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) failing the flash process doesn't break the device and I was able to boot to my device.
Please if anyone has a clue, tell me the solution. I'm so desperate now. I've tried different workarounds in internet and non worked. I even tried installing unofficial version of TWRP and still the same message appears.
UPDATE:
I found a solution to install twrp using adb and fastboot commands. I got the device to be recognized by computer. but unfortunately "fastboot flash recovery boot.tar" command doesn't work and it sticks in sending the image state. So this method isn't working either.
UPDATE 2:
I found this post on xda dating back to 2018. According to this post I should wait 7 days (like "the ring" movie!) so that the message i referred to is gone and I can flash whatever I want.
I have had a galaxy s7 edge for some time now and I have experienced a lot of flashings with that device and never came across sth like this. Now I have to wait and see unless someone or me come up with a better solution.
P.S. I have some trust issues and I can't give team viewer or anydesk access to those who are able to help. So please don't ask for any. I kindly ask you guys to help me in anyway possible under this thread. If more information is required I will make sure to provide you with that.
Thanks in advance.
Click to expand...
Click to collapse
EXACTLY AFTER 7 DAYS I WAS ABLE TO ROOT MY DEVICE FOLLOWING THE FIRST METHOD, AND THERE WAS NO ERROR THIS TIME. THANKS XDA.
DEAR MODERATORS CAN DELETE THIS POST.
Patching AP.tar with magisk doesn't seem to work...
What do you mean it's not work? What error message do you get? Got a screenshot? Thanks
When I flash patched AP.tar, I get "error verifying vbmeta: HASH MISMATCH" error. I followed the official instructions for installing magisk.
I also tried flashing patched boot.img, but I get another error saying that only official firmware is allowed to be installed.
I never installed magisk this way, so I don't know if this procedure worked on previous Android versions (or if I'm even doing it right considering it's Samsung...).
umh..I made the mistake of connecting my M21 2021 Edition to internet and it updated something in the blink of an eye and then when I checked Developer Options the OEM Unlock button disappeared. I cant flash TWRP-ODIN-patch-file anymore , it shows Secure Download error in Download Mode also Custom Binary Blocked error. Without TWRP I cant flash anything. I'm dead!
I am also getting same error, I downloaded my firmware from samfw.com (SM-M215F / Android 12 / Binary 3), then I extracted it to my PC. Then copied AP file from PC to my phone, Patched it using Magisk v25.2 (From Github). Copied patched file from phone to PC. Flashed it using Odin v3.14.4 (BL, AP, CP, CSC). Getting error that VBMETA ERROR HASH_MISMATCH (3).
Has anyone found solution for it?
xyncronix said:
I am also getting same error, I downloaded my firmware from samfw.com (SM-M215F / Android 12 / Binary 3), then I extracted it to my PC. Then copied AP file from PC to my phone, Patched it using Magisk v25.2 (From Github). Copied patched file from phone to PC. Flashed it using Odin v3.14.4 (BL, AP, CP, CSC). Getting error that VBMETA ERROR HASH_MISMATCH (3).
Has anyone found solution for it?
Click to expand...
Click to collapse
You dont want to use Custom Recovery?
xyncronix said:
I am also getting same error, I downloaded my firmware from samfw.com (SM-M215F / Android 12 / Binary 3), then I extracted it to my PC. Then copied AP file from PC to my phone, Patched it using Magisk v25.2 (From Github). Copied patched file from phone to PC. Flashed it using Odin v3.14.4 (BL, AP, CP, CSC). Getting error that VBMETA ERROR HASH_MISMATCH (3).
Has anyone found solution for it?
Click to expand...
Click to collapse
I have successfully rooted my m21 with Android 12 . Watch the
Follow the process described here . Root will be successful.
OldNoobOne said:
You dont want to use Custom Recovery?
Click to expand...
Click to collapse
Custom recovery is good but to flash we can use Odin by samsung. Official samsung software.
Flashing the whole AP feels pretty big. All you actually need is the boot image. Extracting it from the stock rom can be pretty annoying though. If patching ap isn't working for you there's two ways to go. Either flash the magisk apk from recovery (this still works for m21) or patch just the boot image and flash it using Odin or recovery.
You can get the boot image of your respective stock rom from here inside the AP folder.
1. Patch the boot image using the magisk app and rename the patched boot image to "boot.img"
2. Add boot.img it to a tar archive
3. Flash the tar file to AP in Odin
Something you need to note is that magisk no longer patches some stuff from v25.0, so there's a small chance it might bootloop. So ideally, patch using magisk 24.x and then you can update later on using the magisk app.
.
Hi
I tried to install stock Android 12 on my samsung A31. Due to some error in the PC the installation stopped halfway.
I used FRP hijacker tool to get back to download window. However now the error shows "Partitions prism. Reason prism: Error verifying vbmeta image : invalid vbmeta header(6) "
And when I tried to flash using odin again it says setup connection. Complete failed.
Is there no way to get this phone working? Please help!!
Repartition definitely should be off. Also make sure you have the right file to flash, I know there are some different Note 10 tab models. Easiest way to download the latest firmware version is Frija, it doesnt have the limited download speed like Sammobile. The .enc4 file it will give you can easily be extracted just like a .zip file omegle xender .
You shouldt need the .pit file when repartition is off
Junkun007 said:
Hi
I tried to install stock Android 12 on my samsung A31. Due to some error in the PC the installation stopped halfway.
I used FRP hijacker tool to get back to download window. However now the error shows "Partitions prism. Reason prism: Error verifying vbmeta image : invalid vbmeta header(6) "
And when I tried to flash using odin again it says setup connection. Complete failed.
Is there no way to get this phone working? Please help!!
Click to expand...
Click to collapse
You're trying to flash a firmware with an older RP rev than the one stored in your device, you can see it from the error "Fused 2 > Binary 1". Download a firmware with RP rev 2 or higher (more info here)