issues flashing combination rom - Samsung Galaxy S10 Questions & Answers

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

Related

[ROOT] MediaPad M3 10 BAH-L09 Success!

First- I am NOT Responsible if you brick your Device! You do everything at your own Risk!
As I cannot find successfull thread here guiding to root this tablet I am posting the success with rooting with Magisk, all is seen on Russian forum 4pda,but the firmware I am on is not here ,it was little hard to find it(paid) but at the end it works, I have full root:
1 .You must have UNLOCKED BOOTLOADER!!! You can do it here are 2 threads guiding to it,mine was with DC_unlocker-4USD;
2. You must download Magisk from its original thread :Link
3.You must Look at which firmware you are,download the patched ones :С170B003
С170B253
C100B270
Or you can download you full Rom, extract it using Huawei Firmware Extractor extract the BOOT.img from UPDATE.APP file transfer it to your tablet and using Magisk--> install choose boot.img and patch it, then copy the patched_boot.img from folder "Downloads" in the internal memory back to PC,rename to boot.img.
4.You must have installed ADB and fastboot.
5.Using fastboot command on PC install the patched boot.img to tablet:
-First on your tablet enable Developer Options, thick Enable OEM Unlock,thick USB Debugging on,when connected to PC must ask for Fingerprint Security Rsa key,thick Always Trust to this PC"
-Second Tunoff Tablet, then hold volume Down button and connect to PC with USB Cable,Fastboot menu must appear: With green at bottom must be written that it is not FRP locked! If so -dont do proceed disable remove Huawei Account if you have one!
-Third-copy patched boot.img to folder where is located ADB and fastboot, then hold shift and right click mouse button and click Open Command Prompt here.
Now on fastboot menu enter following:
fastboot.exe flash boot boot.img
At the end everything must be OK!
Reboot with power button and check in Magisk !
Regards
I just wanted to confirm that this method works for my tablet. My Huawei Mediapad M3 10.1" BAH-L09 had bootloader unlocked. Emui5.1.2 and OS 7.0. Following these instructions, I extracted the BOOT.img from the stock ROM, then used Magisk Manager app (6.0.1) to create the patched-boot.img. Flashing this patched-boot.img using fastboot mode with command:
fastboot flash boot patched_boot.img
My tablet now is ROOTED without any problems (camera works normally). In short, just follow exactly these instructions and your tablet will be ROOTED
This works for me on BAH-L09 with Build Number BAH-L09C100B270. My Tab ist now rooted with Magisk 17.1 installed. Next i do flash special version of TWRP from the TWRP Builder site. I took the version for the BAH-W09 (WIFI version of the tab) on my own risk. I KNOW thats not the correct version, so please dont criticize.
Installation via fastboot worked. I can boot into Huawei recovery (Power+Vol-up) and TWRP (Power + Vol-Up and Vol-down same time). System boots without problem too. Also i can flash back the original huawei rcovery.img in fastboot mode.
But there is an issue in this TWRP recovery version 3.2.1-0. It does not decrypt data. I tried to format data and flash "no-verity-opt-encrypt". But there is still an Huawei secure mechanism, that wants me to format data in Huawei recovery again. Without format data my tab do not boot into system.
Next step i tried to get TWRP for my device on TWRP-builder app. but no succes because the build queue ist full. So i have to wait...
Sorry but how did you unlock the bootloader?
DragonautMk said:
Sorry but how did you unlock the bootloader?
Click to expand...
Click to collapse
I used dc-unlocker (you can google for). Its easy but it costs ca. 4 €.
Does this method still works on latest ota ?
The4anoni said:
Does this method still works on latest ota ?
Click to expand...
Click to collapse
My M3 10 lite was on latest frmware C100B270 as i used dc-unlocker. Unlock worked well for me.
Does rooting enable you to install Google Services on the tablet? Is so, how?
Is there an international ROM that can be used (with Google tools)
Thanks! Worked for my Mediapad M3 lite 10 (BAH-L09), but now... How can I update Magisk? The Magisk manager doesn't support the version installed.
Can't install twrp either
---------- Post added at 08:40 PM ---------- Previous post was at 07:51 PM ----------
ossizwei said:
This works for me on BAH-L09 with Build Number BAH-L09C100B270. My Tab ist now rooted with Magisk 17.1 installed. Next i do flash special version of TWRP from the TWRP Builder site. I took the version for the BAH-W09 (WIFI version of the tab) on my own risk. I KNOW thats not the correct version, so please dont criticize.
Installation via fastboot worked. I can boot into Huawei recovery (Power+Vol-up) and TWRP (Power + Vol-Up and Vol-down same time). System boots without problem too. Also i can flash back the original huawei rcovery.img in fastboot mode.
But there is an issue in this TWRP recovery version 3.2.1-0. It does not decrypt data. I tried to format data and flash "no-verity-opt-encrypt". But there is still an Huawei secure mechanism, that wants me to format data in Huawei recovery again. Without format data my tab do not boot into system.
Next step i tried to get TWRP for my device on TWRP-builder app. but no succes because the build queue ist full. So i have to wait...
Click to expand...
Click to collapse
The same for me. Have you got the appropiatte twrp recovery?
wanlus said:
Thanks! Worked for my Mediapad M3 lite 10 (BAH-L09), but now... How can I update Magisk? The Magisk manager doesn't support the version installed.
Can't install twrp either
The same for me. Have you got the appropiatte twrp recovery?
Click to expand...
Click to collapse
This is an old post. Development has going forward. Look here:
For a LineageOS rom
https://forum.xda-developers.com/mediapad-m3/development/rom-t3945684
For TWRP
https://forum.xda-developers.com/mediapad-m3/development/twrp-t3914531
For the first step use the 3.2.0 version of TWRP if you are in Huawei's stock Rom.
For me its the best for this moment. Only issue is, that camera dont work in this early lineage rom. But developer is working on it.
ossizwei said:
This is an old post. Development has going forward. Look here:
For a LineageOS rom
https://forum.xda-developers.com/mediapad-m3/development/rom-t3945684
For TWRP
https://forum.xda-developers.com/mediapad-m3/development/twrp-t3914531
For the first step use the 3.2.0 version of TWRP if you are in Huawei's stock Rom.
For me its the best for this moment. Only issue is, that camera dont work in this early lineage rom. But developer is working on it.
Click to expand...
Click to collapse
Ok, thank you so much. I've got installed Twrp properly, and it boots ok... but no more. Now it stays on the recovery home screen. I'll try again

I need help to Root my SM-M105F

Hello i have the Samsung Galaxy M10 SM-M105F.
I need to root the Phone for make Custom Rom or Edit the Scripts.
I have OEM Unlock the Bootloader and install the Unofficial TWRP with Odin From here
https://forum.xda-developers.com/ga...p-3-3-0-twrp-recovery-samsung-m10-sm-t3925243
TWRP work, but the System is in Bootloop.
Pls i need help to root My Device with working TWRP, System boot and Root
BlacklightMG said:
Maybe try flashing 'no-verity-opt-encrypt' and 'RMM Bypass' zip files?
EDIT: Flash Magisk zip too (it removes dm-verity), and format the data partition
Click to expand...
Click to collapse
It'll be rooted when you flash Magisk. And install the Magisk Manager APK too, to allow root control.
I actually rooted without TWRP by flashing the patched boot image generated from Magisk, and then performed a factory reset because file integrity couldn't be verified. But the Magisk binaries worked.
Amazing, can you pls Upload your Modified Bootloader for me and all People here ?
For make the Galaxy M10 open for users and Dev's.
Sorry for the late reply, but it's always better to do it yourself depending on what OTA update you are currently on. Download the firmware, extract the boot image and patch it with Magisk Manager. Then flash it with ODIN or Heimdall while in download mode. Then I had to factory reset because file integrity could not be verified. But the root was preserved.
BlacklightMG said:
Sorry for the late reply, but it's always better to do it yourself depending on what OTA update you are currently on. Download the firmware, extract the boot image and patch it with Magisk Manager. Then flash it with ODIN or Heimdall while in download mode. Then I had to factory reset because file integrity could not be verified. But the root was preserved.
Click to expand...
Click to collapse
Can you show us how to extract the boot image and patch it with magisk manager ?
I have on my SM-M105FD the Firmware 8.1.0 and Working Root.
Download the Firmware 8.1.0 on the PC and the AP File put on the Phone.
Download and install magisk apk on your Device and patch the AP in Magisk file.
flash the Firmware full with Odin but put on the AP Option the Patched AP file flash and work.
I have with Magisk install the Xposed Framework and install nice plugins.
My phone became stuck in a boot loop so i tried to go back but whenever i try to flash the stock rom through odin it says sw REV. Check fail (Bootloader) Device: 2, Binary 1
Iam Facing A Problem Kindly Guide Me Samsung Galaxy M10 Smm105f U2 Installed Twrp Rec
Iam Facing A Problem Kindly Guide Me
Samsung Galaxy M10 Smm105f U2
Installed Twrp Recovery With Odin
Wiped Data
Flashed Successfuy
No Verify Opt
Rmm State Bypass
And Magisk
Now I Want To Boot In System But After Booting In System Process Device Asking Me For A Password
"Ur device Is encrypted For Security Plz Type ur Pswrd "
Even I Haven't Locked Phone With Any Kind Of Privacy
And I Have Also Flashed A New Firmware But Problem is same it's Not Booting in System
It won't work on android 10, you have to switch to android 8.1,then try ?
DJSAJJAD said:
Iam Facing A Problem Kindly Guide Me
Samsung Galaxy M10 Smm105f U2
Installed Twrp Recovery With Odin
Wiped Data
Flashed Successfuy
No Verify Opt
Rmm State Bypass
And Magisk
Now I Want To Boot In System But After Booting In System Process Device Asking Me For A Password
"Ur device Is encrypted For Security Plz Type ur Pswrd "
Even I Haven't Locked Phone With Any Kind Of Privacy
And I Have Also Flashed A New Firmware But Problem is same it's Not Booting in System
Click to expand...
Click to collapse
It won't work on android 10, you have to switch to android 8.1,then try ?

Magisk with stock Android 10 / 11, MicroG with Android 10 stock

After some time I got a second Axon 10 and I spend some time figuring out what was possible with this phone in terms of root, custom ROM etc.
My results are as follows.
What is working:
Android 9 + Magisk and TWRP
Android 9 + TWRP + Custom ROMs (LineageOS 16 and patched GSI)
Android 10 + Magisk and TWRP
Android 10 + Magisk and MicroG flashed via Magisk (= stock ROM without Google Services)
Android 11 + Magisk
What is not working:
Android 11 + Magisk + TWRP (TWRP logo flashes randomly but TWRP does not load).
Android 11 + Magisk + MicroG (the nanolx patching script does not work with Android 11 as of yet)
Encryption in Custom ROMs
Method to flash files via EDL
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
Unlock Bootloader:
Before you try any of the files, you MUST unlock your bootloader!
BACKUP of your data as it will be lost!
Download the EDL tool from this Thread
If your phone is not on android 9, you must go back to Android 9 first. e.g. by using my Android 9 1.9 backup.
After you restored it, restart while holding the volume + key and do a factory reset / format data.
Boot into EDL again and unlock the bootloader.
Now you are on android 9 with unlocked bootloader.
From here you can follow the other guides in the form and install TWRP or lineageos. Or flash one of my files below.
Flashing EDL files:
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
I put all my files into this MEGA account: MEGA
Android 10 version 2.9 Magisk + TWRP
Android 11 version 3.5 stock
Android 11 version 3.5 Magisk
Android 10 version 2.10 stock
Android 10 version 2.10 Magisk (TWRP can be flashed with Magisk)
Install MicroG:
Only works on Android 9 and 10.
Before you install MicroG you must patch the stock ROM to allow for signature spoofing.
The patcher script I used is on https://downloads.nanolx.org/NanoDroid/Stable/ When I write these lines the up-to-date-version is NanoDroid-patcher-23.1.2.20210117.zip
Reboot.
Install MicroG from the Magisk repository.
After a restart there will be error messages that google apps keep crashing. With each warning, disable the apps one by one.
When you reboot again, no errors should appear and MicroG should report that it is fully working.
You can add the Bromite Framework and give F-droid system rights. Both are available from the Magisk repo.
Updates will likely install the Google apps again and uninstall Magisk...
Revive phone:
Not really related, but I bricked my phone several times.
If your phones does not boot anymore or hangs in a bootloop, try accessing the EDL mode.
The easy way:
Boot while holding volume -
The hard way:
Old Volume +, volume - and power until you end up in EDL. The screen will be black, so it helps if you have the Phone connected to Windows and can hear the system sound when the USB sees a connection.
In anyway you can then use the EDL tool to restore / flash an EDL image.
On custom ROM support:
Well there is LineageOS 16 by Unjustified Dev. https://forum.xda-developers.com/t/rom-unofficial-zte-axon-10-pro-9-lineageos-16-0.3992127/ It works well. But has a patch level that is outdated by now.
On top of it you can install the GSI ROMs created by Rafyvitto. The latest one is Resurrection Remix https://forum.xda-developers.com/t/...nofficial-resurrection-remix-q-8-6-7.4172527/
with a security patch level of mid 2021. Which is recent enough to use. The stock roms are not much better.
With both Custom ROMs, encryption is not working which poses a privacy/security risk when your phone is stolen. Do not forget that your phone does not only contain your photos and data but also your passwords to your accounts.
Added Android 10 2.10 files.
Its nice to see anything new for this phone. I wish I can use these roms but I have the American version.
Hi and thanks for your work and your files.
I'm stuck on "Loading the programmer: prog_ufs_firehose_sdm855.elf >>>", if I try to recover your edl files with EDL Tool, v 3.25.
I have to choose option 2: "Restore Full EDL from backup", right?
Is there a way to check if the bootlaoder is really unlocked?
Thanks in advance
OK, I was able to solve the problem with the "programmer" and try the backups. The next step was almost clear. The device is stuck in bootloop. I've already tried all the backups I could find on Mega. After the EDL Tool has done its work and the device has restarted, the mobile phone goes into the boot loop. And now? So the starting position was: Android 9 with an open bootloader. Maybe someone has an idea?
After I couldn't get the device out of the bootloop, I flashed the A2020G_PRO_V1.6_FULL_EDL via MiFlash and then did an OTA update to 1.8.
Then I tried unlocking the bootloader again, which unfortunately didn't work. The flash is carried out without errors, but the device then apparently does not start in the desired Fastboot mode.
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
brian117 said:
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
Click to expand...
Click to collapse
Maybe you need to switch the slot in TWRP. It sounds as if you install it to the other slot (like A) an then boot B. Or vice versa.

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.

Can't flash custom rom after installing TWRP on S10e with Android 12

Hi all,
I always had custom firmware on my phones but last 3 months i tested android 12 stock firmware unrooted.
Now i want to go back to custom rom but it is not possibe ?
what i did an/or tested :
- first download and install official s10e firmware with Odin
- create a patched AP firmware file with magisk on the phone, copy back to pc and flash it with Odin
- make the phone rooted with magisk
So far so good, phone is rooted.. Next
- try to install twrp 3 ways
A) directly with the TWRP app on the phone
B) install twrp in Odin (stuck in download mode until i flash AP file again)
C) create a patched version of TWRP on the phone and flash with Odin on pc again
-> whatever i try, the firmware and files are corrupted after this so the phone needs to format DATA -> Type YES and do complete reset and delete all files from phone.
-> i now have empty phone with only a TWRP folder
-> when i setup custom firmware it looks as if everything is installing but when finished there is nothing to find. phone is still empty an can not be started (bootloop because there is nothing to find)
Sorry for my bad english but i hope someone can tell me what i am doing wrong or help me , i spent 2 days searching and still no working solution

Categories

Resources