Rooting w/ Android 12 (HELP!) - Samsung Galaxy S10 Questions & Answers

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.

Related

After rooting G9+ & installing an unofficial LineageOS 18.1, root was lost & need help getting it back

I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.
Have u tested lineage, is
everything working fine?
UsmanQ said:
Have u tested lineage, is
everything working fine?
Click to expand...
Click to collapse
Everything seems to be there, seems normal. Except root.
doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
Have u tried superoot or something else instead of magisk?
Sapper Morton said:
The ROM that you're using is not meant to be daily driven, Erfan compiled that for experimental purposes, but that aside, there's a few things that you should take in consideration when using Lineage; It's not meant to be used with TWRP, that's why they ship their own recovery (Lineage Recovery). It's still possible to flash custom files with it (That doesn't match their original signature), you just need to skip a warning.
For Magisk, download the latest stable build from here: Download
(The .apk has the flashing script built-in, so just rename that to .zip).
One major difference from TWRP, is that Lineage Recovery doesn't support decrypting userdata, so the files must be flashed using ADB or USB OTG.
Use ADB Sideload as follows:adb sideload magisk.zip
As for me, I didn't unlocked my device yet, so if you could confirm me something: I need to know if I will lose my DRM certification, used for Netflix, Disney+, Prime Video and such.
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
Thanks for the response.
1. I'm using the Github Magisk 23.
2. Lineage Recovery is gone. I reflashed TWRP.
3. Attempting to use "ADB sideload Magisk-v23.0.zip" ADB responds "cannot read 'Magisk-v23.0.zip'"
4. I haven't got Play Store on the phone as I can't flash the aroma package (1.7GB) via TWRP.
UsmanQ said:
Have u tried superoot or something else instead of magisk?
Click to expand...
Click to collapse
I don't know anything about the other methods for getting root. I've always used Magisk.
(I'm working under the idea that as TWRP + Magisk works fine on one phone, they aren't the problem.)
Sapper Morton said:
The idea is to rollback to Lineage Recovery, you can even flash only the boot.img that it's inside the ROM flashable file, instead of reflashing the whole thing again. It's probably in payload.bin format, so you'll need a payload firmware extractor (Easily found on GitHub), in case you choose the first option.
• Aroma is not supported on Lineage Recovery, so I would recommend something smaller, like OpenGapps nano or stock.
Click to expand...
Click to collapse
<rant>
What sort of idiots build in a crap recovery when one has obviously already installed a functional recovery, needed in the process of gaining root and installing LineasgeOS? This unnecessary included recovery wasn't in previous versions of LOS I've used.
Yes, this is an unpleasant surprise and I'm ticked off. I'm an end user who wants a relatively de-Googled phone, but now to maybe get a functional recovery I have to extract stuff from a payload file, but to do that I have to install more crud so that I can run the tool that does the extracting.
And I need Aroma to be able to select what I must have from Google. My partner needs their voice tech. I could dump almost everything else and use Pico. </rant> Sorry.
Is there no way to wipe the slate clean, get rid of this Lineage, and start again?
(I don't understand how installing their recovery could ruin the functionality of another recovery.)
Sapper Morton said:
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
On the second G9+ which I rooted but left the stock ROM, I installed Castro and it indicates L3.
doktorspin said:
I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.
Click to expand...
Click to collapse
take a look at this group of telegram, here they can help you to return
Lolinet [English Only]
Our website: MIRRORS.LOLINET.COM Our channel: https://t.me/lolinetnews Please speak in English
t.me
Lineage is working fine, some details that will be fixed when releasing the new kernel
There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro
The ROM in the O.P. works.​
Folks, I actually made a number of mistakes in this process.
The major one was to muff the fastboot command for flashing TWRP. I had followed instructions which said to boot TWRP, which didn't install TWRP, just loaded it into phone memory. But...
The ROM cited in the O.P. doesn't seem to have any problems that I have noticed in my usage, which is basically as a hand computer, not as a phone.
LineageOS now overwrites recovery with its own recovery, which is pretty moronic, because the user has already had to install a recovery to root the device.
But fortunately, if you have your ADB/fastboot apps handy with TWRP in the same folder it's an easy fix.
You should already have this stuff, but use the following software:
sebastian3367HD has provided TWRP for G9+ users onsight here. I'll assume it's called "twrp.img".
Magisk-v23 here -- put it somewhere easy on your phone.
Also get GApps 11. I used core NikGapps here, select latest date, then the version of GApps you want. (The core version 82MB just gives you Play Store & support software.) Put it the same place on the phone you put Magisk.
Assuming you've flashed the O.P. LineageOS ROM, which overwrites trusty TWRP, put your phone in fastboot mode, either using
1. power button + volume down
until you get the droid image on its back, or get there with your phone on, sending
2. adb reboot bootloader
via the windows command shell.
You're now in fastboot mode. You can now flash TWRP back onto the phone. Note that the phone has two slots of memory, so that the phone can hold two operating systems. If you send
fastboot flash recovery twrp.img
it will be flashed to the current slot, either A or B. To be safe you should flash both:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
That gives you the safety of having TWRP in both slots. (Incidentally, TWRP allows you to changes slots.) (Also remember if you reflash LineageOS you'll have to put TWRP back on if you want a decent recovery program.)
Use TRWP to Reboot to Recovery.
Now install Magisk using TWRP:
Spoiler: (You know this)
a) choose Install
b) if the bottom right button says Install Zip press it and it will change to Install Image
c) if you put Magisk on your external SD card Select Storage to choose the SD
d) find and select Magisk-v23.0.apk, then
e) swipe to flash.
Then install GApps, basically the same as for Magisk.
Reboot to System. You should be rooted now and should have Play Store (and whatever else you opted for).
M.Akram said:
There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro
Click to expand...
Click to collapse
Thanks for the info. My problem was simple to fix, using the right commands!
I haven't installed that rom because afaik the source tree isn't available anywhere which seems kind of fishy, if anyone knows where they are please let us know

Rooting Moto G6 with PPS29-118-15-11. What versions of noverity, twrp, magisk to use?

Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.
SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!

G970F questions for navigating flashing without bricking

Hello,
I purchased a G970F for the second time because I hard-bricked the first one due to not exercising as much caution, and since then, I've learned about the added difficulty the S10 generation has compared to the only other Samsungs I've had the displeasure of working with (S5, S4). I've read a number of guides since then, but I'm not entirely sure which still apply and which do not, since a lot of them are from 2019 / early 2020, and I've somehow managed to only soft-brick it once before bringing it back to current condition.
So, where I stand with my G970F:
Bootloader unlocked, downloaded the latest firmware via Frija (Android 11), patched the AP file, flashed the patched AP, along with BL, CP, CSC via Odin, booted with Magisk, then installed TWRP with SU privileges by downloading TWRP on the Play Store, going through the steps, yadda yadda. I've followed the two official guides (Official installation steps for Magisk by John Wu, and TWRP installation guide for Samsung Galaxy S10e (Exynos), also on the official page.
This is where I get stuck. I've come across some older guides on XDA that mention flashing multi-disabler, as well as mention of disabling FBE immediately after installing TWRP, on the TWRP 3.4.0 for Galaxy s10 Exynos thread on XDA. I don't know if these still apply (they're from 2019), because when I tried disabling FBE and booting to TWRP, it still shows the directories as encrypted hash, and when I tried flashing the multi-disabler on TWRP and rebooting, it gets stuck on Samsung splash (soft bricked), so I had to reboot to TWRP, reboot to download mode via ADB, then reflash the firmware with patched OS to start over. Multi-disabler soft-bricked my device, so I'm guessing it's not compatible with devices with Android 11?
The end goal for me here is to flash a custom rom safely, but I'm concerned about a few things:
The first time I hard-bricked my first G970F, it was during a root attempt, and the last thing I did was wipe data on TWRP, flash a zip, and reboot - and this essentially made it impossible to get into either Download mode or Recovery, it would just vibrate on black screen, stuck in a forever boot loop with no means to turn it off. I had to open the device to manually disconnect the battery.
I'm being extra cautious not to repeat the above scenario, so here is where my concern is: I've read that S10 series only have an A partition which leads to Magisk having to reside in a parasite-like existence with recovery, and the other landmine is that there is a 'VaultKeeper' that locks up the bootloader if an unauthorized OS is detected or some sort? I'm thinking that maybe either of these was responsible for my first G970F being stuck in an unbootable state, so I want to navigate carefully here.
I want to flash one of the unofficial roms linked on XDA by @expressluke , and I have Magisk patched AP + stock firmware + TWRP, only steps I have taken were from the two official guides (not XDA threads) for TWRP and Magisk, which never mentioned 'multi-disabler' nor disabling FBE. From my current state, how do I go about flashing the custom rom without potentially damaging recovery / partitions / triggering some Samsung trap like VaultKeeper? I'm a bit keen to do this, since it looks like having Magisk + stock firmware for some reason only recognizes my storage as 32GB instead of 128GB.

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

Question Updating rooted S21 ultra (stock) to latest Android 13

Hi,
My S21 Ultra (German version) is rooted on stock. I update it manually every month by downloading the firmware, running magisk on it and flashing with Odin using home_csc in order to keep all my apps and not doing a fresh install. I also pass safetynet in order to use all my banking apps.
Question is - if I download the latest update (Android 13) and do the same (run magisk and flash with home_csc), will it work? All the apps will stay installed and safetynet will be passed? Or because it's a new OS, I will need to do a clean install?
sagybp said:
Hi,
My S21 Ultra (German version) is rooted on stock. I update it manually every month by downloading the firmware, running magisk on it and flashing with Odin using home_csc in order to keep all my apps and not doing a fresh install. I also pass safetynet in order to use all my banking apps.
Question is - if I download the latest update (Android 13) and do the same (run magisk and flash with home_csc), will it work? All the apps will stay installed and safetynet will be passed? Or because it's a new OS, I will need to do a clean install
Click to expand...
Click to collapse
Thats a good question, .....in theory it should, Home csc basically tells the device not too wipe the internal data, unsure about safetynet thou, but you can easily reinstall module .
apps should automatically optimise and update once you sign in google....In Theory!!!!!
I did my n20 ultra this morning, Stock A13 rooted , but clean install in preparations for Dr Ketans A13 due to be released. I havent fully set it up as it will be wiped anyway. Just flashed the Universal SafetyNet fix v2.2.1 and im passing Safetynet.
Worse case scenario if it doesn't work.....Clean Install...OH the PAIN !!!!
jays note 2 said:
Thats a good question, .....in theory it should, Home csc basically tells the device not too wipe the internal data, unsure about safetynet thou, but you can easily reinstall module .
apps should automatically optimise and update once you sign in google....In Theory!!!!!
I did my n20 ultra this morning, Stock A13 rooted , but clean install in preparations for Dr Ketans A13 due to be released. I havent fully set it up as it will be wiped anyway. Just flashed the Universal SafetyNet fix v2.2.1 and im passing Safetynet.
Worse case scenario if it doesn't work.....Clean Install...OH the PAIN !!!!
Click to expand...
Click to collapse
Thanks a lot!
I hate hate hate clean installs and try to avoid them so badly.
All those activation QR codes, sign ins, passwords. A few wasted hours of my life.
sagybp said:
Thanks a lot!
I hate hate hate clean installs and try to avoid them so badly.
All those activation QR codes, sign ins, passwords. A few wasted hours of my life.
Click to expand...
Click to collapse
I know!!!!!! Thats why I held off setting my N20 up when i gotta do it again anyway.
Here simple instruction to update rooted device
1 Download atock firmware
2 Extract AP* file and patch with magisk
3 Flash Patched AP for AP slot + BL, CP and HOME-CSC* in respective slots (Using CSC* instead of Home_CSC* will formsat device)
If you are not using TWRP,you are good to go with above. In case you have TWRP - Read below.
Now next steps (4 & 5) are very important and read carefully. If you already having TWRP and you have ran command "multidisabler" after flashing TWRP then this step is for you. If you don't remember you ran "multidisabler" or not then reboot to TWRP and look if you can read files from Internal storage? yes then you have ran multidisabler and your data is decrypted
4 Along with all files mentioned above, select TWRP file for USERDATA slot and flash all togather
5.YOU MUST Reboot to TWRP before booting system (Elese you may needs to wipe data) - Once reboot to TWRP - from terminal type "multidisabler" and complete, read output of command, if it throws error - retype "multidisabler"
Now reboot system and you should be on new firmware with intact root & data
PS :
Still I highly recommend to make backup of important data in case something went wrong.
Remove Lockscreen passord/Pin and samsung account before dirty flashing.

Categories

Resources