Database Develop

[ROOT] Samsung SM-A605FN (Android 9.0)

So, about a week ago I tried rooting my A6+ (2018) using TWRP and the latest Magisk build (20.0)
It wasn't the first time, so it was no big deal. Unlocked OEM, installed TWRP (the unofficial version for the A6+, I found it here and in other numerous tutorials), then I hopped on TWRP, formated the data, and I rebooted the phone.
(I followed The***********'s tutorial.)
Then I flashed RMM_Bypass_v3_corsicanu.zip and no-verity-opt-encrypt-6.1.zip. Then I proceeded to flash Magisk (20.0). When I rebooted the phone, there was a yellow text on the top-left of the boot screen saying set guarantee bit: Kernel.
The phone booted as usual, and I got to the setup screen, where I needed to fill all the information (you know, like after you buy a new phone). When I was done with that, there were plenty of strange things going on with the phone:
1) There was no Magisk application installed, and I didn't have root access.
2) Everytime I rebooted the phone it got stuck for a bit and then it went back to the "first boot", (like if it were reseted everytime).
Now, my question is, has this to do with Magisk, the RMM bypass patch, or the no verity opt encrypt one? Were any of those outdated?
In the end, I just flashed the stock firmware and it all works fine.

install magisk manager app. you will get the root access. but it will ruin lockscreen security. with pie samsung f**ked us real hard.

Same here, I bricked it twice and tried all available twrp (3), my main reason for rooting as I am complete noob, was the chance that I could somehow enable camera 2 api. No chance of doing that, if you do, you get message "serious camera error" smh, I had it on J3 but can't have it on much more expensive a6 plus. Anyhow my impression is that problem could be in unofficial TWRP, rather than in those zip files, after all they do work on other devices.

going to back to custom ROMS

hello, I used to be a custom ROM junkie in the past but after some time i got bored and never did it again.
now looking at my current device which i never installed a customer ROM before its quite old as its running Android 8 and i would like to jump to 10 or 11.
I am confident i understand the process but its been a few years and i have some questions:
-for example this is the 1st device i encrypt so i am not sure if this affects.
-the device has no custom recovery so i have to start there but not sure if i have to remove encryption or if its ok.
-Also i would like to see if you have any advice for me or somehting i should pay attention beside install TWRP, format all but storage and install zip file for custom ROM
Thanks

masterchop said:
hello, I used to be a custom ROM junkie in the past but after some time i got bored and never did it again.
now looking at my current device which i never installed a customer ROM before its quite old as its running Android 8 and i would like to jump to 10 or 11.
I am confident i understand the process but its been a few years and i have some questions:
-for example this is the 1st device i encrypt so i am not sure if this affects.
-the device has no custom recovery so i have to start there but not sure if i have to remove encryption or if its ok.
-Also i would like to see if you have any advice for me or somehting i should pay attention beside install TWRP, format all but storage and install zip file for custom ROM
Thanks
Click to expand...
Click to collapse
You've missed all the fun with the upgrade to OOS 9.
So, you'll need to upgrade your firmware to 9.0.6 because all the latest ROMs require it. Take your time and carefully read https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055.
You do not need to remove encryption (depending on how you upgrade your firmware).
If you've got a locked bootloader (which I'm expecting you do), them you need to unlock it so that you can flash TWRP. And unlocking will wipe all data from your phone. So backup everything you want to keep to your PC.
If you don't boot into recovery after flashing TWRP and install a patched boot image (see https://forum.xda-developers.com/on...ty-disable-oxygen-os-t3922324/post79357241)or flash Magisk, and reboot your phone, you'll lose TWRP because OOS automatically restores the stock recovery.
So the order is:
1. Backup
2. Unlock bootloader
3. Flash TWRP
3. In TWRP flash patched boot image (remember you're still on OOS 5.x so use the right one!) or Magisk.
4. Have fun moving to a custom rom.
Sent from my OnePlus 3T using XDA Labs

Rooting w/ Android 12 (HELP!)

OK, guys. I've pressed more buttons than a telegraph operator but nothing seems to be working. Definitely need some help here.
The process of rooting with Magisk has changed since Android 9 and it seems none of the guides are reflecting how to root Android 12. There are warnings about not installing 'unoffiicial' TWRP versions (a change since 2019), that we SHOULD flash an official (beyond1lte) file, that we should not install TWRP until the device is rooted (via the patching methid?), install TWRP via the PlayStore... and so on.
Heck, I'm just having trouble with Magisk. I've patched the AP file but I just can't seem to get beyond that. Can someone please help?
Thanks in advance!

Hello Billlechat, yes it has changed the rooting since 2022 see the end of 2021.
Poue rooted your s10 follow this link then read well, you must use official firmware A12 of your smartphone and odin 3.14.3.
Use magisk 24.3 to modify AP from firmware with magisk, then use adb to transfer AP patched-magisk to pc.
https://topjohnwu.github.io/Magisk/install.html
You can follow the posts here on this topic dedicated to magisk
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com

meric57 said:
Hello Billlechat, yes it has changed the rooting since 2022 see the end of 2021.
Poue rooted your s10 follow this link then read well, you must use official firmware A12 of your smartphone and odin 3.14.3.
Use magisk 24.3 to modify AP from firmware with magisk, then use adb to transfer AP patched-magisk to pc.
https://topjohnwu.github.io/Magisk/install.html
You can follow the posts here on this topic dedicated to magisk
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Click to expand...
Click to collapse
Finally got it all sorted, thanks. However the keypress combo is still not working. to boot into Magisk. The pwr/bixby/vol+ doesn't do it, so there's obviously something going on that's changed.
Do you know what the correct key sequence is?

Hello BillLechat, you connect the cable on your pc just usb cable not smartphone for the moment.
You press bixbyet power on smartphone you plug the smartphone off, it will start in mode onwload then you press volume + long press to unlock bootloader

Yeah, got it. That's a real PITA, for sure. Used to be key presses only. I don't like the idea that my privacy features are disabled if I can't boot with Magisk because there's no PC and USB cable around. Creepy.

Well, similar problem I guess.
@Admin, re-post to appropriate thread if necessary....
I have an SM-G973F that was BL unlocked successfully, but I cannot flash the Magisk modified OEM AP or anything else back via Odin 3.14.1. I tried 3.0.9 also same result. Also extracted PIT file and attempted again via 3.14.1 but that version said to not use it since it would be extracted from the CSC binary.
I tried several different USB cables and different ports on the laptop same result. I only need to root the phone, not looking for custom ROM's at this point. The phone isn't bricked yet, thankfully. Currently in download mode. Odin reports "<OSM> All threads completed. (succeed 0 / failed 1)"
It does appear that Odin sees the phone.
This phone shipped with Android 12 and UI 4.0. I'm not sure there is a recent enough version of Odin to reflash?

Okay, Update.
Got the firmware to flash via Odin 3.0.9 but now stuck in boot loop. What to do now?
SM-G973F/DS
Android 12 One UI 4.0

I'm not an expert, but have been down this path enough times to possibly be helpful.
Be sure you have the right OEM firmware. Be sure to select the correct CSC code for your phone, it will be located in settings-about phone-software information-service provider software version. Look for the 3 letter/number code. In my case, I have one phone that's O2U and another that's XSG.
NOTE: TWRP is not just for installing custom ROMS, it's also used to flash patches for utility files like Magisk and is a mission-critical IMAGING tool to archive your entire system in case you FUBAR something along the way, especially after installing and configuring a whole bunch of system and app settings.
READER'S DIGEST VERSION (use at your own risk, please read carefully)
TOOLS:
Download and extract the latest ODIN
Download and extract Frija
Download and install Magisk
OPTIONAL: Download the Official TWRP
Follow these instructions here:
The Proper Way to root your S10 (10+,10e) Device and get it Right! Tipps & Tricks
Hi Guys :cowboy: Today I want to bring some simple and effektive Insights on proper Device & Software Management and also about Mistakes on the Way and Solutions! :good: ;) So make yourself comfortable and check this out! It will really help...
forum.xda-developers.com
IMPORTANT:
Note that the 'keypress' combination for booting is not the same on Android 12 as on previous versions, we have to ALSO have the phone connected via a USB cable. So it's this way:
Boot to Recovery: pwr/bixby/Vol-USB hold until you see the TWRP splash screen
Boot to Magisk (once installed): pwr/bixby/vol-/USB hold, release as soon as you see the Samsung spash screen.
Hope this helps a bit.

mat68046 said:
Okay, Update.
Got the firmware to flash via Odin 3.0.9 but now stuck in boot loop. What to do now?
SM-G973F/DS
Android 12 One UI 4.0
Click to expand...
Click to collapse
Worst case scenario, you can just flash the OEM firmware to be sure, and start again. Per my message above, do be sure you have the correct CSC (region) code.

BillTheCat said:
I'm not an expert, but have been down this path enough times to possibly be helpful.
Be sure you have the right OEM firmware. Be sure to select the correct CSC code for your phone, it will be located in settings-about phone-software information-service provider software version. Look for the 3 letter/number code. In my case, I have one phone that's O2U and another that's XSG.
NOTE: TWRP is not just for installing custom ROMS, it's also used to flash patches for utility files like Magisk and is a mission-critical IMAGING tool to archive your entire system in case you FUBAR something along the way, especially after installing and configuring a whole bunch of system and app settings.
READER'S DIGEST VERSION (use at your own risk, please read carefully)
TOOLS:
Download and extract the latest ODIN
Download and extract Frija
Download and install Magisk
OPTIONAL: Download the Official TWRP
Follow these instructions here:
The Proper Way to root your S10 (10+,10e) Device and get it Right! Tipps & Tricks
Hi Guys :cowboy: Today I want to bring some simple and effektive Insights on proper Device & Software Management and also about Mistakes on the Way and Solutions! :good: ;) So make yourself comfortable and check this out! It will really help...
forum.xda-developers.com
IMPORTANT:
Note that the 'keypress' combination for booting is not the same on Android 12 as on previous versions, we have to ALSO have the phone connected via a USB cable. So it's this way:
Boot to Recovery: pwr/bixby/Vol-USB hold until you see the TWRP splash screen
Boot to Magisk (once installed): pwr/bixby/vol-/USB hold, release as soon as you see the Samsung spash screen.
Hope this helps a bit.
Click to expand...
Click to collapse
Thanks, "Bill" (funny, your avatar I used for many years also in other places.....) The boot loop issue is resolved, I don't remember how but the phone is fully operational. Noticed Root Checker says the phone isn't rooted but in Settings it says "Custom". Anyway, I should have downloaded TWRP which I will tonight. Since the phone is operational I'll be looking to image as you mentioned. I wanted the OEM ROM which so far seems stable.

Magisk 25.2 severely breaks LineageOS 18.1 on Samsung Galaxy Tab S5e (SM-T725)

For some odd reason Magisk breaks auto-rotation and sets selinux to permissive on boot after updating to 25.2 (from 25.1).
This is not the first time Magisk messes up Selinux rules. I usuall solved this by making a fresh OS install already with patched boot and by installing the managing app afterwards.
However, this time autorotation stopped working for some reason. And when i try to uninstall Magisk using its app -- OS no longer boots, as if it fails to restore initial boot image.
This selinux problem began since v25.
I use latest official build of Lineage OS 18.1. I have TWRP installed, which i use to install LineageOS.
What am i doing wrong? Has anyone experienced such issues?

I posted the same problem here (did not notice/checked SELinux back then and sound is probably also not working), figured out that all sensors do not work, checked with "Sensor Test" app. I was already considering a separate thread, thus I'll continue here, because this issue definitely deserves a separate thread. Documentation is so scattered and sometimes so confusionly described, that it was hard to make sense of it all...
(Disclaimer: Although I have necessary experience with installing custom ROMs etc., everything stated below is at my own understanding ).
My device: Samsung Galaxy Tab S5e LTE
My goal was: TWRP, LineageOS and Magisk. How hard can it be?
Problems are that (most of the) Samsung devices do not have a "ramdisk" partition where Magisk is normally installed, also the increasingly complexity of encryption en integrity checks makes this more annoying.
First, let me retrace my steps, as far as I can.
When reading the TWRP page, we get a clue where to start: "You are therefore strongly advised to first root your device with Magisk and then pre-root a TWRP image before flashing it to recovery", this is because "Both TWRP and Magisk-rooted Android boot using the recovery kernel, with the device's hardware keys used to choose between TWRP and Android at boot time".
(Magisk "hijacks" part of the recovery partition, since the absence of a ramdisk partition.)
Spoiler: later on you learn this is not completely the case any more, but I would still recommend to hold on to this method, because the TWRP page also states that: "The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP. Furthermore, prior rooting of the device with Magisk carries the significant advantage of disabling various device protection mechanisms that you will otherwise need to take care of manually.", and it continues with more scary warnings...
1. Thus followed the Samsung section of the Magisk documentation to have the bootloader unlocked and Magisk installed, but stock firmware is still installed, no problem whatsoever.
Then decipher the already mentioned instruction: "...pre-root a TWRP image before flashing it to recovery". This apparently means that Magisk has to patch the TWRP image, just like as was done with the Samsung firmware.
2. Downloaded the *.tar file of TWRP, extracted the image, patched with Magisk and repacked to the *.tar file with 7-Zip in order to be able to flash it with Odin (see step 4).
*3. I do not recall when I installed the "VBMeta file", although this is instructed in the Lineage OS installation instructions, when following the TWRP instructions it says "...you can now jump to its own section", thus skipping it?? (I did it somewhere in the process...)
Unknown: whether it is still required to patch and flash VBmeta (to disable some verification process)...
4. Flash TWRP recovery, see YouTube video below. This video mentions the use of "multidisabler-samsung", which disables "FBE, proca, Vaultkeeper and auto-reflash of stock recovery on Samsung Pie devices". Current latest version was 3.1, downloaded from this XDA post, I think.
Just as in the YouTube video, I also was stuck at the Samsung logo. After booting into the stock firmware you can check if Magisk still works.
Not sure: "multidisabler-samsung" needed?
5. Install LineageOS (and GApps). The most straightforward step, just install LineageOS, read the instructions. Then install GApps (e.g., BiTGApps).
6. After booting (power and volume + button) and setting up LineageOS, a Magisk icon should be visible in the app drawer, click it and the Magisk app is installed, when opened, Magisk is setting up a few more things and reboots the tablet.
*******************************************************************************************
This is the point were you finally think you made it, but no, here the issues arise.
Issues thus being SELinux permissive status (Xandros Darkstorm), no sound and non-working sensors, thus "auto rotating" feature is not working.
At this point I started to regret my purchase...
In the search of a solution to the problem I stumbled upon the following familiar and solved Magisk issue #4911 (LineageOS 18.1 no sound and no sensors after booting with Magisk), which refers to issue #4394 (Magisk > 21.4 is difficult to install on LineageOS (18.1) with TWRP (Direct Install not enabled unless you use old zip)).
In short: this post mentioned patching the boot image instead of the recovery image.
*******************************************************************************************
I. I extracted "boot.img" from the LineageOS zip file, patched it via Magisk (ramdisk is added to the boot image) and replaced the "boot.img" in the zip file with 7-Zip.
II. Booted into TWRP, flashed an original TWRP image, so recovery is replaced. (Rebooted I guess.)
III. Then wiped previously LineageOS installation and, flashed the LineageOS zip file with patched boot image and GApps and rebooted to system.
IV. After setting up, install Magisk, let is do its thing.
V. I installed "Root Checker Basic" in order to check I gained root checker. It was a PASS! And checked with "Sensor Test" if all sensors worked, they did! And sound also worked .
Yay!
Clearly, all of this can be optimized. Some questions remain, what steps are really necessary and I am also still wondering how to apply a LineageOS update... Anyhow at least it is working.

What resolved
Xandros Darkstorm said:
For some odd reason Magisk breaks auto-rotation and sets selinux to permissive on boot after updating to 25.2 (from 25.1).
This is not the first time Magisk messes up Selinux rules. I usuall solved this by making a fresh OS install already with patched boot and by installing the managing app afterwards.
However, this time autorotation stopped working for some reason. And when i try to uninstall Magisk using its app -- OS no longer boots, as if it fails to restore initial boot image.
This selinux problem began since v25.
I use latest official build of Lineage OS 18.1. I have TWRP installed, which i use to install LineageOS.
What am i doing wrong? Has anyone experienced such issues?
Click to expand...
Click to collapse
What fixed this for me is after re-flashing stock in Odin to get everything working again, just rename the magisk apk to install.zip and flash that in twrp, and open the magisk app once booted, no other steps needed for install, no image patching or anything.
Might be worth seeing if this is the same issue or if there's a more fundamental problem with 25.2

Hi,
I stumbled upon this thread while searching for a way to install Magisk on a S5e.
Following the guide here: https://wiki.lineageos.org/devices/gts4lvwifi/install I already unlocked the bootloader, flashed vbmeta.tar with Odin, flashed lineage-19.1-20221114-recovery-gts4lvwifi.img with Odin and flashed lineage-19.1-20221114-nightly-gts4lvwifi-signed.zip with TWRP-recovery.
Lineage is working fine, but I would also like to use Magisk.
I understood, that the order I follwed is not the recommended order for having both Magisk and Lineage. At least, that is, what you described at the beginning of your post.
But as with your last part you mentioned, that there where issues with sensors, ...
And the solution was to
I. Replace recovery with a patched boot.img of Lineage zip and wipe a prev. Lineage installation
I guess, I might be able to stiull do that though I already have Lineage on the S5e (currently with Lineage/TWRP recovery), right?
I can patch the boot.img from within lineage-19.1-20221114-nightly-gts4lvwifi-signed.zip with Magisk app, right?
Or would I have to patch lineage-19.1-20221114-recovery-gts4lvwifi.img
Is there anything to consider, when zipping the image with the patched boot.img again?
Which TWRP image did you choose to be flashed at step II.?
Barium said:
I. I extracted "boot.img" from the LineageOS zip file, patched it via Magisk (ramdisk is added to the boot image) and replaced the "boot.img" in the zip file with 7-Zip.
II. Booted into TWRP, flashed an original TWRP image, so recovery is replaced. (Rebooted I guess.)
III. Then wiped previously LineageOS installation and, flashed the LineageOS zip file with patched boot image and GApps and rebooted to system.
IV. After setting up, install Magisk, let is do its thing.
V. I installed "Root Checker Basic" in order to check I gained root checker. It was a PASS! And checked with "Sensor Test" if all sensors worked, they did! And sound also worked .
Yay!
Clearly, all of this can be optimized. Some questions remain, what steps are really necessary and I am also still wondering how to apply a LineageOS update... Anyhow at least it is working.
Click to expand...
Click to collapse
Thanks
If this is also a solution, can you please let me know, if there is anyhting to consider, when flashing the stock (got it from SAMMOBILE)? Can the lineage-19.1-20221114-recovery-gts4lvwifi.img still be left on the tab?
After re-flashing the stock, I guess you flashed lineage again, right?
Or did you stay with the stock and just flashed magisk (after renaming the apk to zip)?
Thanks
TheTofu said:
What fixed this for me is after re-flashing stock in Odin to get everything working again, just rename the magisk apk to install.zip and flash that in twrp, and open the magisk app once booted, no other steps needed for install, no image patching or anything.
Click to expand...
Click to collapse

I dared patching the TWRP recover for S5e and flashed it via Odin (AP).
S5e boots up in Lineage, Magisk is working fine.
But when I power off the tablet or restart, Lineage Recovery shows up telling me, that my data would be corrupt.
My only options are to try again or to do a factory reset.
Only way out of this is to re-flash the above mentioned recovery image again.
So how do I get the Magisk patched TWRP recovery permanent?

I wiped system? and re-flashed Lineage via TWRP, got "original" TWRP Recovery for S5e Magisk permanent.
I have to admid, I tried several things and got lucky I did not break something.
I had nearly, what I wanted - TWRP, Lineage and Magisk, but there were issues with the sensors (no auto rotate).
Again I helped myself:
1) flashed the original, unpatched TWRP Recovery for S5e
2) flashed unpatched Lineage for S5e
3) flashed MindTheGapps
4) flashed Magisk-v25.2.apk
No bootloop, original TWRP permanent, Magisks working fine, no issues with sensors.

Tried steps 1, 2 and 4 with the Lineage Recovery and it worked too.

issues flashing combination rom

hello fellas , i have s10 ,problem : always booting up to recovery mode ( couldn`t find solution for it )
,,,, oem is locked and there is no way i can flash twrp or custom rom off course ( btw i am noob)
i tried flashing combination rom using odin ( just to enable usb debugging ) but many msesages of (please get the approval ) for pit ,bootloader, system ...etc
googled the issue , found someone saying it is sort of protection that requires unique key should be requested from samsung
So , how can in bypass it to make successful combination rom flashing ?
any extra files needed plus to the combination rom and pit file ?
please help me out
note : repeat: my phone is oem locked , at flashing stock rom is success but reboots directly to recovery mode ...this is my major problem ,
if anyone can post me sm-g973f (bit15) adb enabler file ?????
it might help
if you guys can hand me in either of those it will be deeply appreciated
thank you all

giants....does combination flashing successful with test points ? and where can i find them inside s10 ?

Hello Rossen, since you have no experience in this area, I know a lot of things that I took the simplest for my S10 exons SM-G973 F. Installation. John WU the official firmware with magisk modify AP official firmware that you transfer to your S10, then once do you transfer magisk patches with Adb to your PC with Adb pull.
Then with Odin you flash the following 4 files BL-AP magisk patched-Cp-Home CSC you let start, you open magisk active Zygisk restarted if rooted...
I forgot TRWP even if I managed once to install it with magisk then bugs and loss of rooting following updating magisk, normally to install TRWP you must already be rooted with magisk then install TRWP either by modify TRWP image with magisk or by the managed TRWP application you directly flash the TRWP image of the application.
https://topjohnwu.github.io/Magisk/install.html

meric57 said:
Hello Rossen, since you have no experience in this area, I know a lot of things that I took the simplest for my S10 exons SM-G973 F. Installation. John WU the official firmware with magisk modify AP official firmware that you transfer to your S10, then once do you transfer magisk patches with Adb to your PC with Adb pull.
Then with Odin you flash the following 4 files BL-AP magisk patched-Cp-Home CSC you let start, you open magisk active Zygisk restarted if rooted...
I forgot TRWP even if I managed once to install it with magisk then bugs and loss of rooting following updating magisk, normally to install TRWP you must already be rooted with magisk then install TRWP either by modify TRWP image with magisk or by the managed TRWP application you directly flash the TRWP image of the application.
https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
thanks for reply , sadly the device can take only the stock rom , any custom will be rejected due to oem lock , and if i flashed stock one it will boot up to recovery not the system ,

So you haven't done the unlocking of oem well you can't do anything, the best thing to do is redo these cleanly you reflash the official rom then you unlock your S10 you press power plus bixby and you connect to the pc, then you press and hold volume up and unlocking is done.
Then you will restart as at the first start you install magisk, activate developer mode about the phone press on low version 7 times then in developer you activate USB debugging.
And you do as I explained.

meric57 said:
So you haven't done the unlocking of oem well you can't do anything, the best thing to do is redo these cleanly you reflash the official rom then you unlock your S10 you press power plus bixby and you connect to the pc, then you press and hold volume up and unlocking is done.
Then you will restart as at the first start you install magisk, activate developer mode about the phone press on low version 7 times then in developer you activate USB debugging.
And you do as I explained.
Click to expand...
Click to collapse
already said when i flash stock rom device turns up to recovery mode not to the system . the only thing i see is flashing combinations which is now impossible without token , is there a trick or workaround to bypass getting in the recovery mode after flashing stock ?

put device in download mode start from scratch with odin official firmware

meric57 said:
put device in download mode start from scratch with odin official firmware
Click to expand...
Click to collapse
like i said before , successful flashing stock rom , after that the mobile goes to recovery mode not to the system

Hello Rose, I had the concern like you these for its that it is necessary to start from zero. I also did like you too when I start with power back TRWP direct, I had to reinstall official rom Android 12, use which TRWP for your S10 exynos the one the twrp-3.6.2_9-2-beyond1lte.img yes or no you know that you have to patch its image with magisk 25.2 then rename it in recovery and replace the one in AP with the recovery modify then flash with odin.
In your quote start with TRWP then you take the boot.img of the AP flashed it then try to restart in recovery.
watch this video

i dont have active android in my device and it can NOT boot up to system if i flashed stock
before stupidly activate oem lock i had zero problems , locked oem and flashed stock and then i got recovery interface , can not log in system

i have LG 4k tv which i messed its software , but managed to reset it all by shorting pins >>> can it be done the same way with my s10 ? if yes , anyone can show me where circuit shorting pins are ?

not at all the only thing to do if you manage to boot trwp recovery in boot do boot download and flash the official rom with csc and not home

meric57 said:
not at all the only thing to do if you manage to boot trwp recovery in boot do boot download and flash the official rom with csc and not home
Click to expand...
Click to collapse
not working ,,,, any instructions or updates to flash factory binary without fail via odin ?

googled to download sboot to fix the whole thing , no luck , can anyone attach it here please ? bit15 (uf protection)

Hello Roseen, so how does your S10 react starting on TRWP or getting stuck on the Samsung logo. I don't see that you tried to do things without having looked at the tutorials on XDA. well a 4G exynos G973F you have the Android 12 UI 4.1 rom.
Does your pc recognize the S10 when it starts up, did you get the message in red safety e and the yellow triangle plus the message, at worst try with another smartphone to film the start-up.
What does your last post mean with bit15.
I put you the link for the tutorial s 10 of the forum
Tutorial : Root Galaxy S10 Series Android 12 One UI 4.1 Stock Firmware
Root Samsung Galaxy S10 Series Android 12, WITHOUT Ramdisk Root Samsung S10+ - S10 - S10e SM-G97xxx, Stock Rom Android 12 - UI 4.1 Latest Version (I tested G970FXXSGHWC2) (Without combination keys for active Magisk after normal restart –...
forum.xda-developers.com