Database Info

[Easy_Root/Unroot][Any_Oreo/Nougat_Firmware_V4_Bootloaders][Tmp_Twrp_Recovery]

EASY ROOT/UNROOT FOR S7 OR S7E ALL NOUGAT OR OREO STOCK ROMS
THANKS @klabit87 FOR OREO ROOT
TEMPORARY TWRP RECOVERY VIA ADB THANKS TO @afaneh92​
This is for AT&T, T-Mobile and Verizon and Sprint running V4 bootloaders only!​
This tool will allow you too easily root any stock rom allowing you to make any modifications you might want then easily unroot for better performance
This will Also give you a fully functional TWRP recovery that can be accessed via adb. TWRP is fully functional on OREO Roms but is limited on Nougat roms
The initial setup does require a data wipe.​
S7 G935A Edge Odin Factory FIrmware Downloads
G935AUCU4CRI2_8.0_4File_USA (AT&T).7z
ADB_Root Temporary Twrp Tool Download
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z
S7 G935 Edge Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G935_EDGE_OREO.7z
SM_G935_EDGE_NOUGAT.7z
S7 G930 Flat Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G930_FLAT_OREO.7z
SM_G930_FLAT_NOUGAT.7z
Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask
10. Now in cmd window choose Option(8) Push Root.zip to Phone
11. Now in TWRP choose install and select the Root.zip
12. After zip is installed reboot and go through setup.
13. Once through setup make sure you are rooted
To Unroot Your Phone
1. In the Root Control app choose phone settings and unroot phone make sure phone is connected to computer
2. Now depending on the type of root you choose your phone will reboot to download if you chose system root or stock recovery if you chose systemless root. If your phone reboots to download mode skip to number 5
3. If your phone reboots to recovery once your phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
4. In cmd window choose Option(3) Unroot phone will reboot too download mode
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
To Reroot Your Phone
1. Reboot to download in Odin AP slot flash AP_ROOT_G93***.tar
2. Phone will reboot then will reboot one more time and you will be rerooted
To Enter TWRP When Rooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Manually reboot phone to recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP
2. To Exit TWRP simply choose reboot
To Enter TWRP When Unrooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Put phone in download mode In Odin AP slot flash AP_ROOT_G93***.tar force phone to reboot to recovery. If you let phone boot it will reroot and you will have to run the unroot from the root control app.
2. In recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP.
3. Do whatever you need too do
4. To exit Twrp choose reboot to Download
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar

Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good

jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
Nice maybe I can ditch the Ufirmware now and get rooting to squeeze some extra life out of this phone.
If I'm on Ufirmware I'm prob on newer bootloader I can flash back to v4 sry for newbies question been a long time since I tinkered with phones prior to this one.

dincdoes.me said:
Nice maybe I can ditch the Ufirmware now and get rooting to squeeze some extra life out of this phone.
If I'm on Ufirmware I'm prob on newer bootloader I can flash back to v4 sry for newbies question been a long time since I tinkered with phones prior to this one.
Click to expand...
Click to collapse
Ufirmware is still V4 for now and the answer to your question would be no. You cannot downgrade bootloaders

jrkruse said:
Ufirmware is still V4 for now and the answer to your question would be no. You cannot downgrade bootloaders
Click to expand...
Click to collapse
Ok good to know do you think I should switch to stock AT&T Oreo Rom Via Odin before following your guide? I don't see you mention if being On the latest UFirmware would cause any issues with this rooting method.
The BL I currently am on will show in Odin correct? Once again thank you for all your help =)

dincdoes.me said:
Ok good to know do you think I should switch to stock AT&T Oreo Rom Via Odin before following your guide? I don't see you mention if being On the latest UFirmware would cause any issues with this rooting method.
The BL I currently am on will show in Odin correct? Once again thank you for all your help =)
Click to expand...
Click to collapse
The bootloader is always the 5th to last number in the build number
G935XXXX4XXXX as for your first question it doesn’t matter
Sent using some kind of device I modified

Added ATT factory firmware to the OP

So if it is a fully functional TWRP, can we install other zips?

Would this work on the G935U?

JosephXDA1 said:
Would this work on the G935U?
Click to expand...
Click to collapse
It will work on any firmware that is still v4 bootloader. If you have taken V8 bootloader update it’s probably the end of the road for custom anything on the s7/s7edge
Sent using some kind of device I modified

I've used this to root and make changes except for install exposed. On restart I get an error saying my phone failed and needs to be reset. I just get back to twrp and launch the xposed uninstaller. The old beta installs but won't work. The v90 beta 3 gives that boot error. Is it dm verity? Would please explain how to get xposed working?

When unpacking "S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z"
Trojan:Win32/Bluteal!rfn
SEVERE |Detected with Windows Defender Antivirus
Sounds ominous enough...Not sure whether to continue or not. Please advise.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I reported this as a false positive in hopes that they would correct and debunk it but seems they did the opposite...

bumrocks said:
I reported this as a false positive in hopes that they would correct and debunk it but seems they did the opposite...
Click to expand...
Click to collapse
Thanks for doing that I didn't read your full comment at first and was like really dude are you really going to post its a virus lol thanks for helping the OP and whom ever uses the package out in Windows 10
=)

How do I block this update I seen your comment about it and is the only thing I can do is to push install later everyday?
Must be some type of way to block OTA.
Thank you

having trouble with step 5
How do I flash the AP_ROOT_G93*tar in the odin ap slot?

cruz1923 said:
How do I flash the AP_ROOT_G93*tar in the odin ap slot?
Click to expand...
Click to collapse
You put your phone in download mode then your question contains the answer. I suggest a google search on how to use odin if you don’t know what load the file in the AP slot means. I don’t mean to be abrasive but this is basic stuff too know if you are going to be messing with your phone
Sent using some kind of device I modified

jrkruse said:
You put your phone in download mode then your question contains the answer. I suggest a google search on how to use odin if you don’t know what load the file in the AP slot means. I don’t mean to be abrasive but this is basic stuff too know if you are going to be messing with your phone
Sent using some kind of device I modified
Click to expand...
Click to collapse
Sorry I've jailbroken my I phone 6 before and rooted my HTC m8 it's just been a while since I've messed with this type of stuff I'll look more into it

hello! i rooted my smg935 att (oreo) and everything is fine except that my hotspot wont work anymore..
i have an unlocked s7 edge and im on vodafone greece.
prior to rooting the hotspot worked fine, but now when i try to turn it on, it looks like its loading for a few seconds and then goes back to off.
I tried to change the apn settings like a saw on some tutorials but when i try to add "dun" to the apn type it says this apn is not allowed on this device... anyone who can help?
edit: factory reset fixed the problem

I realize I am a little late to the game here, but does this process still work smoothly for the AT&T SM-G35A Variant?
And a couple of questions.
1: Will it get rid of the AT&T bootup logo and sound?
2: Will it get rid of the Security Notice "Unauthorized actions have been detected" messages?
3: Will it make the phone work with other carriers such at MetroPCS?
Thanks! It's been a while since I've used ODIN, and I'm a little nervous.
PM

[Guide] TWRP and ROOT for A20e (A202f) [Updated]

My way of installing TWRP and ROOT on A20e (only tested on a202f).
Everything is working both on TWRP and MAGISK.
Versions:
-Magisk (v26.1)
-MagiskManager (v26.1)
-TWRP (3.6.1_9.0)
_________________________________________________
Download attached files:
-TWRP and ROOT(magisk) Odin is included!
_________________________________________________
#Factory reset is recommended!
#Make sure BOOTLOADER is unlocked!
#If you don't need MAGISK stop at step 6 and reboot to system
[TWRP Installation]
1. Extract required files, open ODIN (as Administrator) click on the "AP" button and choose TWRP-3.6.1_9.0.tar file.
2. In the "Options" menu untick "Auto-Reboot" .
3. On your phone boot into the "Download Mode" then in ODIN you can press the START button. (make sure you are connected to PC)
4. If everything is fine there should be green "PASS!" text in ODIN.
[ If your flashing failed make sure the bootloader is unlocked and check if cable is properly connected ]
[Don't let the phone boot into system because it will replace TWRP with stock recovery.img]
6. Boot into TWRP and FORMAT DATA (Wipe/Format Data) to remove encryption.
# If you don't need MAGISK you can reboot to system. Otherwise continue reading the guide.
[MAGISK Installation]
7. From TWRP reboot into RECOVERY again.
8. Connect your phone to PC or if you moved Magisk-v26.1.zip and Magisk-v26.1.apk to SD card then use SD card.
9. Flash the Magisk-v26.1.zip file and reboot to system.
10. When you boot into system install the Magisk apk.
11. Open it and finish the installation process.
12. Reboot
ENJOY!

[UPDATE]
-Updated versions of both TWRP and MAGISK
# TWRP 3.5.2_9-0 --> TWRP 3.6.1_9-0
# Magisk v23 --> Magisk v24.3
-Remodifed VBMETA
For ANY help contact me on Telegram: https://t.me/SerbianGeek

does encryp work on this ? dont need to backup just hide data part if fone is stole

This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"

/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
No problems on my end, pal.

SerbianGeekster said:
No problems on my end, pal.
Click to expand...
Click to collapse
this phone is really a PITA. every time i try to do something it's 1 step forward and 2 steps back. never suffered so much. i flashed it like 20 times. all i want is a working twrp on stock rom and pass safetynet

/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
to bypass this error:
1. connect to wifi
2. change the date to 2 august 2019
3. boot into download mode
4. flash twrp

Thank you! It worked! No problems got me.
I kinda feel like idiot that I couldn't install it with that ease before

OH **** IT WORKED !!!
I've been at this for hours, thank you so much !!!

Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version). I would like to install twrp and then to root it. I tried several tutorials (Odin, OEM unblocked, USB debugging, time change) but twrp installation fails with message 'custom recovery blocked by frp'.
Can anyone help me?

I duckduckgoed, and found this XDA thread, where the second post says the following :
Nemirtingas said:
FRP: https://www.samsung.com/us/support/frp/
FRP Just locks your phone if you alter the boot or recovery image and you had a google account registered. To unlock it you have to wipe data (factory reset) and reflash stock boot.img and recovery.img before using it again. If your cousin wants to flash my ROM (lineageos-13.0) he'd better not, its not stable and he will encouter random reboots and codecs bugs. The best thing to do is to remove FRP from his phone and flash Magisk (a root manager like SuperSU) and debloat it.
For more information, find the Grandprimevelte group on Telegram.
Click to expand...
Click to collapse
The rest of the posts mention the need for a modified boot.img, else your phone would brick after adding a Google account, but I don't know about that... I have MicroG on mine with a Google account and no problems.
Anyway, frp seems to be a related to having a Google account on your phone.

fjunk said:
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version) /.../ Custom recovery blocked by frp'.
Can anyone help me?
Click to expand...
Click to collapse
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?

fjunk said:
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
Click to expand...
Click to collapse
Indeed, my issue is that in download mode I can only do a volume down button and power button to reboot in system mode. No option to unlock bootloader.

I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, odin) ?

lPolarisl said:
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, od
Click to expand...
Click to collapse
Many thanks for your update. Attached are pictures of the mobile and the Odin result. The error is an OEM issue (red text on the top of the mobile screen). In other forums, I can see that the download mode has an option to unlock OEM bootloader. I can't see it on my phone.

Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?

lPolarisl said:
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
Click to expand...
Click to collapse
Thanks for your reply.
That's sure that it doesn't really help to hide the error message. Usb debugging is enabled (I am able to run adb commands) and OEM is unlocked on the preference setting. I did the test with Odin 3.13 but same results with newer version. I installed an A11 firmware (a202fxxu4cvk1).
Don't t know how to go ahead. It seems that I don't have the possibility to unlock OEM in the download mode interface....

Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)

lPolarisl said:
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
Click to expand...
Click to collapse
I bought a refurbished mobile phone (blackmarket). It came with a 9.0 version. I tried to update to a custom rom without success so I installed the latest 'official' version
Download Samsung Galaxy A20e SM-A202F XEF France A202FXXU4CVK1 firmware
Fast download latest Samsung Galaxy A20e firmware SM-A202F from France with A202FXXU4CVK1 and Android version 11
www.sammobile.com
I uploaded this version using Odin. I also tried the patched Odin version. I read that the patched version only works with a10 version.

Huh...
I have no idea how that behaves, but I hardly see why it would cause a problem.
What else could you try... Restore factory settings maybe ?
Pressing volume up when starting in download mode ? (Note, this supposedly relocks the bootloader if it has been unlocked, if that happens and your phone isn't 100% on stock, it will brick.)

Question Stuck (Only Download Mode Working)

Hello everyone,
Got the Phone of the Son of my Sister. I have no clue what he tried to install but it's Stucked/don't Boot/no recovery i can only Start the Download mode.
I tried already to Flash it with Odin with the Samsung Firmware but i am not able because i get always these OEM Errors, and i'm not able to deactive it because the Phone doeasn't Start
View attachment 5662237
View attachment 5662231
Here is what Odin tells me Complete(Write) operation failed.
about the Phone:
Model : SM-A326B
CSC : LUX
AP version : A326BXXU3AUH5
FWVER : 0007
Unique number : 2C0121194E4DAF30B732
Storage : 128
I already tried different solutions and Firmwares from samfw Older/Newest and from Frija-v1.4.4 but i get always the same error.
Smart Switch / Samsung Kies etc...
Would be happy if someone can help me find a Solution i searched already the last 15 hours.
(p.s Sorry for my bad English)

it seems that the bootloader is locked, you should unlock it to be able to flash custom rom, like the samsung rom.
View attachment 5662231 it says "Custom binary blocked by OEM lock".
Try to see if he installed a custom recovery like TWPR, but 90% the phone doesn't has a recovery.
try to unlock the bootloader by entering fast-boot mode.
>Now turn off your device completely.
>Press and hold the Volume UP and DOWN button on your Galaxy A32 and connect it to your PC
>This will boot your device into Download Mode.
>Once in the Download/Recovery menu, press and hold the Volume Up key until you can see the “Unlock Bootloader” >screen.
-Unlock your bootloader.
-Download A32 5G: a32x.
-Put the TWRP TAR for your device with Odin in the AP slot.
-vbmeta_disabled_R.tar in USERDATA slot and click start.
-Start flashing the recovery.
-Then enter onto the custom recovery.
-"Wipe"-->"Format Data"
-Install custom rom !!make sure to have the stock kernel,vendor!!
-to install rom search xda guide for you a32 5g

Hey Topo thank you for the reply
So i turn off my device i hold Volume + and - and then 1x Up to Enter Boot Mode so i hold Volume Up again for like 10 seconds but nothing happens

KedonLux said:
Hey Topo thank you for the reply
So i turn off my device i hold Volume + and - and then 1x Up to Enter Boot Mode so i hold Volume Up again for like 10 seconds but nothing happens
Click to expand...
Click to collapse
is the bootloader unlocked?
Because if yes you can skip this step

Just enter download mode and go to odin and install twpr
-Download A32 5G: a32x.
-Put the TWRP TAR for your device with Odin in the AP slot.
-vbmeta_disabled_R.tar in USERDATA slot and click start.
-Start flashing the recovery.
-Then enter onto the custom recovery.
-"Wipe"-->"Format Data"
-Install custom rom !!make sure to have the stock kernel,vendor!!
-to install rom search xda guide for you a32 5g

KedonLux said:
Hello everyone,
Got the Phone of the Son of my Sister. I have no clue what he tried to install but it's Stucked/don't Boot/no recovery i can only Start the Download mode.
I tried already to Flash it with Odin with the Samsung Firmware but i am not able because i get always these OEM Errors, and i'm not able to deactive it because the Phone doeasn't Start
View attachment 5662237
View attachment 5662231
Here is what Odin tells me Complete(Write) operation failed.
about the Phone:
Model : SM-A326B
CSC : LUX
AP version : A326BXXU3AUH5
FWVER : 0007
Unique number : 2C0121194E4DAF30B732
Storage : 128
I already tried different solutions and Firmwares from samfw Older/Newest and from Frija-v1.4.4 but i get always the same error.
Smart Switch / Samsung Kies etc...
Would be happy if someone can help me find a Solution i searched already the last 15 hours.
(p.s Sorry for my bad English)
Click to expand...
Click to collapse
Odin is refusing to flash your Firmware, and it happens because you (or someone) flashes TWRP but after that accidently turns off Developers Option resulting in Disabling of OEM Unlock.
Odin is telling you "CURRENT BINARY : CUSTOM"
To fix that you will need to flash Stock ROM, or odin will refuse to flash your device.
and Bootloader downgrading isn't allowed so odin will not flash.
download latest rom for your device (OLDER ONE WILL NOT WORK) and flash it using odin

I downlaoded the last one with Frija-v1.4.4 with Android 12 but still refuses
And thats what Odin tells me when i try to make what Topo says
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 28 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> vbmeta.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

SweenWolf said:
Odin is refusing to flash your Firmware, and it happens because you (or someone) flashes TWRP but after that accidently turns off Developers Option resulting in Disabling of OEM Unlock.
Odin is telling you "CURRENT BINARY : CUSTOM"
To fix that you will need to flash Stock ROM, or odin will refuse to flash your device.
and Bootloader downgrading isn't allowed so odin will not flash.
download latest rom for your device (OLDER ONE WILL NOT WORK) and flash it using odin
Click to expand...
Click to collapse
He says <I tried already to Flash it with Odin with the Samsung Firmware but i am not able because i get always these OEM Errors, and i'm not able to deactive it because the Phone doeasn't Start>

i will update you soon

The bootloader is unlocked so it's a good news

TRY THIS
-------------------------------------------------------------------------
Download: https://droidfilehost.com/download/download-samsung-galaxy-a32-5g-twrp-recovery-file/
vbmeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
-------------------------------------------------------------------------
Once you have downloaded, reboot your device into download mode.
Flash the vbmeta_disabled_R.tar in the USERDATA slot and click start.
Now the device will boot into recovery mode prompting you to wipe data.
Wipe data and reboot to download mode again
Open Odin and add the TWRP Tar file in the AP slot and click start to flash.
Once it is done, you can reboot to recovery via recovery key combo (Vol UP + Power button + USB connected).
In your TWRP Recovery menu, disable encryption:
Go to Advanced > Terminal, type: multidisabler.
If the vendor complains about free space left on the device, will attempt to resize the vendor. and it asks to - Run multidisabler again!.
Type: multidisabler again and you will see - Finished. when done.
Go back to Wipe > Format Data > type yes.

Thank you Topo but still not working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Topo's said:
las
Click to expand...
Click to collapse
KedonLux said:
Thank you Topo but still not working
View attachment 5662913
View attachment 5662915
Click to expand...
Click to collapse
Ia have the same issue.
I tryed every possible combination but still I cannot flash:
"Custom Binary Blocked By OEM Lock".
As I am not the only one having this isuue, I can assume it is a software/firmware problem. Last I remember, I upgraded to the latest stock ROM and the issue happened the next time i restarted the device (a couple of days later after the udate).

Anyways, as there are a couple of ywears since I last used Odin (I recently changed back to Samsung), can someone please tell me where can I download an official ROM and how should I flash it via Odin?
Many thanks in advance!

Hello @wiseman911 i downloaded/used Frija

Also, is there a way to:
- format just the Cache partition
and/or
- format all data/factory reset
just via Odin?
I've tried both Adb and FastBoot but my device is not listed. The only thing that works is Download mode (Vol Up + Vol Down + Power Btn) but only if connected to a computer.
It will not enter recovery mode via Vol Up + Power Btn so I'm kind of stuck.

stock rom: https://www.sammobile.com/samsung/
guide:

Topo's said:
stock rom: https://www.sammobile.com/samsung/
guide:
Click to expand...
Click to collapse
Many thanks!

wiseman911 said:
Also, is there a way to:
- format just the Cache partition
and/or
- format all data/factory reset
just via Odin?
I've tried both Adb and FastBoot but my device is not listed. The only thing that works is Download mode (Vol Up + Vol Down + Power Btn) but only if connected to a computer.
It will not enter recovery mode via Vol Up + Power Btn so I'm kind of stuck.
Click to expand...
Click to collapse
if you format data it will delete only /data partition, you need to format dalvik, cache, system, data but whit odin you cannot format these things, only way is installing twpr

@KedonLux fully watch the yt video and in the minute 7:45 it talks about your problem

How To Guide Unlocking and Rooting Xiaomi 12S Ultra (Twrp/Magisk)

A very well known disclaimer : your warranty is void after doing this. And I am not responsible for any damage caused on your device. It's all on you.
Make sure to have your google play store apk downloaded somewhere.
Unlocking the bootloader will wipe all data AND your play store.
but you don't have to use xiaomi google play service installer or such.
This phone has built in google service, and just the play store goes away by factory reset.
1.Mi Unlock - link​Download the tool on pc, enable developer options on your phone
(My device - All specs - tap miui version 7 times).
Go to dev options(Additional Settings) and enable OEM unlocking.
Right below, there is Mi Unlock Status.
Link the device to your Mi account.
From this moment, you have to wait 168 hours
WITHOUT logging out Mi account on your phone
or adding another device on your Mi account.
Else, the counter will reset.
The counter is server-sided.
No need to worry about restarting or turning off the device during this period.
Goto Mi account and add your PHONE NUMBER to the account.
Else, you will face loading loop on Mi unlock tool after typing in the verification code.
Once that is done, boot to fastboot
(turn off device, then hold power and volume down, or use 'adb reboot fastboot')
and use Mi unlock tool to make sure you see
"try again after 168 hours" message.
That's it. Come back after 168 hours(1 week) and unlock your phone using the tool.
Your bootloader will be unlocked now.
ADB/Fastboot - just in case you don't have it
go setup fastboot for later steps.
2.Rooting​There are two ways of rooting now that we have a twrp.
/
Method A : (TWRP Root) way easier.​TWRP - please refer to my post
download twrp, and use fastboot.
fastboot boot twrp-3.6.2_A12-thor-unofficial.img
(or your img name)
Once you boot into twrp,
go to "Advanced" and "flash this twrp."
when it's done, do not reboot,
go back and in the same Advanced menu, install magisk(not alpha). That's it!
Now reboot to the system,
you will see brown magisk app that basically does nothing but infinite download,
ignore the app and get yourself a magisk app below,
once installed and opened it, magisk will tell you to reboot once more.
Now you are fully rooted!
Magisk - link​/
Method B : (Magisk root)​if you are going to use twrp, just follow method A else you have to go back to the bootloader again and do all that stuff. Twrp method does all at once.
Magisk patched boot img - 13.0.7 Latest (Magisk original 25.2)
or the same file attached below.
Magisk Patched boot.img - 13.0.5(Magisk canary)
Basically download the ROM, get boot.img out of it, and use Magisk to patch it.
Now put your device to fastboot mode, place boot.img to your ADB folder (C:/adb) and type these one by one.
fastboot flash boot_ab boot.img
fastboot reboot
now you have a rooted device!
3. Safetynet Fix -link updated.​Apply this patch via Magisk
Enable Zygisk, enforce DenyList,
and then toggle these options in cofiguration.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you should be able to pass the Safetynet test.
Also add you banking apps or anything it shouldn't detect root and Magisk.
Feel free to leave any questions below.
For advanced Users, I am testing out Konabess since they added SD 8+ gen 1 support. Let me know your thoughts! I can confirm that the tool works, but havent tested enough to verify if it acutally works.
Go use KonaBess if you are into serious tweaking! It works

Excellent share! Thank you.

Wondering why in your ADB commands guy flashed 2 boot images. Can you expand on why? Shouldn't it be fine just flashing the patched boot?

GodKingKnight said:
Wondering why in your ADB commands guy flashed 2 boot images. Can you expand on why? Shouldn't it be fine just flashing the patched boot?
Click to expand...
Click to collapse
The 2 commands are there to ensure that the patched image is flashed on both the A and B slots of the device. Mismatched boot images on the 2 partitions often cause bootloops or related issues.

Much appreciate the clarification. Thanks again!
oddlyspaced said:
The 2 commands are there to ensure that the patched image is flashed on both the A and B slots of the device. Mismatched boot images on the 2 partitions often cause bootloops or related issues.
Click to expand...
Click to collapse

Thanks for sharing but without safetynetfix I don't pass safetynet test...others can confirm or not? Thanks.

Nabicook said:
A very well known disclaimer : your warranty is void after doing this. And I am not responsible for any damage caused on your device. It's all on you sir.
Unlock bootloader - patch boot.img - fastboot flash.
These are the steps.
Make sure to have your google play store apk downloaded somewhere. Unlocking the bootloader will wipe all data AND your play store.
1.Mi Unlock - link
Download the tool on pc, enable developer options on your phone(My device - All specs - tap miui version 7 times).
Go to dev options(Additional Settings) and enable OEM unlocking.
Right below, there is Mi Unlock Status.
Link the device to your Mi account.
From this moment, you have to wait 168 hours WITHOUT logging out Mi account on your phone or adding another device on your Mi account. Else, the counter will reset. The counter is server-sided so you dont have to worry about restarting or turning off the device during this period.
Goto Mi account and add your PHONE NUMBER to the account. Else, you will face loading loop on Mi unlock tool after typing in the verification code. Once that is done, boot to fastboot(turn off device, then hold power and volume down, or use 'adb reboot fastboot') and use Mi unlock tool to make sure you see "try again after 168 hours" message.
That's it. Come back after 168 hours(1 week) and unlock your phone. Your bootloader will be unlocked now.
ADB/Fastboot - just in case you don't have it,
go setup fastboot for later steps.
2. Magisk - link
Magisk patched boot img - 13.0.7 Latest (original 25.2)
or the same file attached below.
Magisk Patched boot.img - 13.0.5(canary)
Basically download the ROM, get boot.img out of it, and use Magisk to patch it.
Now put your device to fastboot mode, place boot.img to your ADB folder (C:/adb) and type these one by one.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
after you see success each time,
fastboot reboot
now you have a rooted device!
3. Safetynet Fix -link
Apply this patch via Magisk
Enable Zygisk, enforce DenyList,
and then toggle these options in cofiguration.
View attachment 5678797
Now you should be able to pass the Safetynet test.
Feel free to leave any questions below.
For advanced Users, I am testing out Konabess since they added SD 8+ gen 1 support. Let me know your thoughts! I can confirm that the tool works, but havent tested enough to verify if it acutally works.
Click to expand...
Click to collapse
I have to login to download you patched file

GodKingKnight said:
I have to login to download you patched file
Click to expand...
Click to collapse
Hi, I changed to google drive. Now you can download without logging in

I got Magisk and root successfully. Thanks a lot. Also using your patched twrp.
By the way how did you get safety net pass?
Nabicook said:
Hi, I changed to google drive. Now you can download without logging in
Click to expand...
Click to collapse

GodKingKnight said:
I got Magisk and root successfully. Thanks a lot. Also using your patched twrp.
By the way how did you get safety net pass?
Click to expand...
Click to collapse
basically step 3.
download and install universal safetynet fix magisk module.
Then enable Zygisk, add deny list, then reboot.
you should be able to pass

did you fix netflix l1 after root ?

hoangtu2410 said:
did you fix netflix l1 after root ?
Click to expand...
Click to collapse
not yet, miui seems to be difficult to edit build prop or at least there are other ways to do.
simply editing build prop with root permission won't work btw

Updated
1. TWRP method
2. Safetynet fix

Brown-Magisk does infinite download because it is being blocked by MIUI Optimizations, which can be disabled in dev settings.

linamus said:
Brown-Magisk does infinite download because it is being blocked by MIUI Optimizations, which can be disabled in dev settings.
Click to expand...
Click to collapse
Does it still have the infinite loop issue? I don't want to disable the miui optimization

arinpsycho said:
Does it still have the infinite loop issue? I don't want to disable the miui optimization
Click to expand...
Click to collapse
You can enable it right back after installing third party apps. But id recommend eu rom anyway.

Guys, I *probably* screwed up and need advice:
After update to latest MIUI stable I've lost root and decided to regain it.
(1. but, I've messed up with cmd prompt and flashed twrp image for recovery while in fastboot
2. Later on I've flashed correct fastboot image of twrp)
After twrp loads, it requires me to enter password to mount data. I fogot/never set it (used graphics lock all way long).
When I press cancel and reboot - I get constant bootloop
Default passwords don't work, deciphering graphic password into numbers also
TWRP doesn't offer me to use graphic password
Flashing stock boot.img and recovery doesn't help, I just get boot to stock recovery.
Pls help me get out of this constant bootloop
Obviously, I don't want to wipe data and do clean reflash

Use the twrp from the EU forum here https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/thor/
You need to boot twrp, not flash it. fastboot boot twrp.img
Hope it helps

Sathelp said:
fastboot boot twrp.img
Click to expand...
Click to collapse
Thanks, but if I use that command I get
FAILED (remote: 'Failed to load/authenticate boot image: Bad Buffer Size')

joiliko said:
Thanks, but if I use that command I get
FAILED (remote: 'Failed to load/authenticate boot image: Bad Buffer Size')
Click to expand...
Click to collapse
Oh, and when I use MiFlash to flash recovery rom latest v.11, it gets stuck at 4.99% and then reboots
So I guess there's only fastboot flash option left?

[Updated September 2022] How to root A7 2018

Disclaimer​
Do this at your own risk as I will not be responsible for your bricking the phone or rendering it unusable. Proceed with caution!
Click to expand...
Click to collapse
If you want to root stock and for some reason want to have the latest security update, you have a problem and I'll help you do it.
What I did below is tested on an A7 SM-A750GN/DS but any A750x should work as well.
Prerequisites​
Latest magisk zip
Latest firmware from anywhere you like (my personal favourite is a toll-free website samfw.com)
Latest firmware from 2020
Latest Odin
Working custom recovery: tested on OrangeFox
DM-Verity disabler zip file
Time, a lot!
Unlocking bootloader​Steps:
Go to developer option > Software information > Tap on the build number 7 times to unlock developer option
Go to developer option and enable OEM unlock
Proceed as prompted and it will reset the phone
Set up as normal and move on to the next section
Rooting the phone​Steps:
Turn off the phone
Plug in the cable to the computer (Leave it plugged in for the remaining of the process)
Hold all 3 keys (up down volume, and power) at once and when the turquoise-ish screen pops up, press volume up key
Extract and get files from downloaded firmwareS [AP, BL (Take the BL file from the 2020 firmware, the latest BL will not allow any current custom recovery to function properly), CP, CSC]
Add the corresponding files to its boxes (AP_A750xxx to the AP slot; BL_A750xxx to the BL slot and so on)
Flash it
When the screen goes black, quickly hold all buttons again to re-enter Download mode
Uncheck all BL, CSC, CP, leaving AP
Add the recovery.tar file to the AP slot and press start
Boot to recovery
Flash magisk zip and then the DM-Verity disabler zip file
Go to wipe > Format data > Type "yes"
Reboot, et Voilà your phone is now rooted on the latest security update
If your phone is showing [Installed: N/A; Ramdisk: No] then reboot, there might be some error with the magisk app.

Reserved !

Reserved !

So I need to flash a stock firmware from 2020?

LadyAmy said:
So I need to flash a stock firmware from 2020?
Click to expand...
Click to collapse
No, just the bootloader because the latest custom recoveries of our devices support BL up to 2020 only.

Edit: Never mind, just realized, that there is a November 2020 Binary 5 Firmware.

Ronan Hansel said:
Disclaimer​
If you want to root stock and for some reason want to have the latest security update, you have a problem and I'll help you do it.
What I did below is tested on an A7 SM-A750GN/DS but any A750x should work as well.
Prerequisites​
Latest magisk zip
Latest firmware from anywhere you like (my personal favourite is a toll-free website samfw.com)
Latest firmware from 2020
Latest Odin
Working custom recovery: tested on OrangeFox
DM-Verity disabler zip file
Time, a lot!
Unlocking bootloader​Steps:
Go to developer option > Software information > Tap on the build number 7 times to unlock developer option
Go to developer option and enable OEM unlock
Proceed as prompted and it will reset the phone
Set up as normal and move on to the next section
Rooting the phone​Steps:
Turn off the phone
Plug in the cable to the computer (Leave it plugged in for the remaining of the process)
Hold all 3 keys (up down volume, and power) at once and when the turquoise-ish screen pops up, press volume up key
Extract and get files from downloaded firmwareS [AP, BL (Take the BL file from the 2020 firmware, the latest BL will not allow any current custom recovery to function properly), CP, CSC]
Add the corresponding files to its boxes (AP_A750xxx to the AP slot; BL_A750xxx to the BL slot and so on)
Flash it
When the screen goes black, quickly hold all buttons again to re-enter Download mode
Uncheck all BL, CSC, CP, leaving AP
Add the recovery.tar file to the AP slot and press start
Boot to recovery
Flash magisk zip and then the DM-Verity disabler zip file
Go to wipe > Format data > Type "yes"
Reboot, et Voilà your phone is now rooted on the latest security update
If your phone is showing [Installed: N/A; Ramdisk: No] then reboot, there might be some error with the magisk app.
Click to expand...
Click to collapse
where's the link for the needed files?

welp I can root my phone properly, but if I put a lock screen it gives me this loop when booting up, that's why I have to do a factory reset and right now I don't have a lock screen on my phone
https://imgur.com/a/VSYYQKB

SafetyNet doesn't pass (Response payload validation failed)
Tried version 25.2
EDIT: this helped:
[GUIDE] Passing Safetynet
This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders or custom verified boot keys. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021...
forum.xda-developers.com

Thank you for this guide! It worked perfectly on my SM-A750FN variant. I've used the latest Android 10 ROM for the AP, CP & CSC files and the BL file from the last 2020 Android 10 ROM, OrangeFox recovery as well, but flashed Magisk v23.0, since any newer version uses Zygisk and it doesn't really work with my device (Tried v25.2 but can't use modules and the app displays: Installed: None, Ramdisk: No etc.).
If anyone wants to download the files I used here they are:
Download the roms for your device from here (NOTE: You need registration to download).
OrangeFox recovery from here (NOTE: PBRP should work as well, but do NOT use TWRP).
If you want you can download only the ".tar" files for the recoveries from here: OrangeFox or PitchBlack.
Magisk v23.0 from here (Optionally you can set your update channel to custom and paste this channel URL: https://raw.githubusercontent.com/topjohnwu/magisk-files/afe2c304e59f631280cc26ccc6d40a7cf04f7f37/stable.json in the Magisk app settings to prevent you from updating the it accidentally ).

Pozdrav evo provadim 5 dana na rutovanju telefona samsung A750G ul.2 i nemoze . Ako ima neko da je to odradio nek se javi i objasni.

Hey do I have to flash the complete firmware or just the BL. I'm currently running the July 2022 patch and I downloaded the firmware from 2020, so do I flash the entire firmware or just the BL from 2020
Please help, I have awful battery life and I'm trying to get as much improvement by rooting

Holding Volume up, down and power boots the phone normally, not in recovery mode.

This is what worked for me :