Related
Hi,
I have a somewhat general question about different OTA update application methods for OOS when Magisk and potentially TWRP is involved.
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Going forward, I'd like to be in a state where I have a Magisk-rooted phone, able to use TWRP, and receive OTA updates. Generally I've seen these two methods being recommended:
1) With TWRP:
a) download full image from OP site;
b) boot to TWRP, flash said image, followed by re-flashing TWRP as flashing full image restores stock recovery;
c) wipe dalvik & cache
d) reboot to TWRP & flash Magisk
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Now, my questions:
1. Which of the two methods above should be preferred?
2. Could either of the two methods used for OTA updates without losing data nor apps/settings?
3. Is there anything inherently different between flashing full image as in method 1) vs. going for the regular incremental OTA update as in method 2)?
4. for option 2), should b.1 OR b.2 be used? Magisk tutorials page seems to be recommending the latter.
I like to keep things simple, so if I'm going to install TWRP, then that's what I use for updates.
There's no benefit in swapping recoveries, especially since you end up with the same result.
By the way, it's been a long time since TWRP stopped patching kernels to prevent it being replace by the stock recovery. So, your step 1 is simpler:
a) download full image
b) flash it in TWRP
c) flash Magisk
And that's it. There's no need to wipe Dalvik or cache. I've not wiped either of these for years (and I've updated countless ROMs) and I've never had an issue requiring me to wipe them.
Sent from my OnePlus 3T using XDA Labs
Thanks for the reply.
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Any specifics re. Android P releases, or old flashing methods should work the same?
laur89 said:
Hi,
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Click to expand...
Click to collapse
There is nothing stopping you from installing an Oreo version OOS (such as the latest stable 5.0.8). Who knows when stable P is coming. Maybe soon, maybe not that soon?
Just download the full zip, flash in TWRP, and flash Magisk right away (do not reboot before flashing Magisk). Same process BillGoss suggested in a previous reply.
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
laur89 said:
Hi,
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Click to expand...
Click to collapse
I wouldn't mess with any of this. The phone is modded, and it seems that the above process is just trying to "trick" the system into thinking it has never been modded, so you can do an incremental update. For no actually benefit, and just making a much more complicated process.
Full zip makes for a cleaner install than incremental, anyway. You can keep your user data in either case, so again, you aren't gaining anything with incremental (versus full zip) OTA.
---------- Post added at 01:03 PM ---------- Previous post was at 12:55 PM ----------
laur89 said:
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Click to expand...
Click to collapse
Well, are you encrypted, or not?
I've always had the phone encrypted, so can only say for certain about that condition. If it is encrypted, it will stay that way. There are a few TWRP builds that don't play well with encryption. But for the most part, just flash the update as stated previously, and you don't need to worry about encryption.
If decrypted, I believe flashing by TWRP will keep it that way. If you flash an update by stock recovery, I think it will force back to being encrypted. But again, I can't say for certain, as I've always been encrypted.
laur89 said:
Any specifics re. Android P releases, or old flashing methods should work the same?
Click to expand...
Click to collapse
The community beta P release is having issue with devices which are bootloader unlocked and encrypted. If the device is just one of those (or neither) and not both, then it seems to work fine in most cases.
For the stable P release, I'm guessing it will work the same as the "old flashing methods" which has been described above. But we won't know for certain, until a stable P build is released.
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.
Hi,
My S21 Ultra was rooted and I used to flash the regular updates manually by patching the AP and flashing everything with HOME_CSC.
Today I did all that with the December update (UI 4.0, Android 12). It all went smoothly, but when the phone rebooted, I have lost root access. I have no root, Safetynet doesn't pass and basically I don't know what to do now.
I guess that wiping the phone and doing a clean install with the patched version is an option, but I would really want to keep all the data I have. Is there anyway around this?
did a clean install, my phone wont really boot up with a patched boot image. have you had any luck?
Other users with unlocked devices have stated root access is blocked after updating to One UI 4.0, Android 12.
Don't know what is causing your issues, I'm using my S21U on December (actually now January) image. Patched with Magisk Alpha (23016), works like a charm here.....
Oh, I'm on DBT/998B-version with Exynos - just in case if this matters
PS: procedure is the same as outlined in OP.
On a sidenote I had numerous issues with transferring the full AP-Image between PC and phone, in the end I just extracted the boot.img.lz4 and the vbmeta.img.lz4 into a new tar, transferred that to the phone, patched it and copied the resulting tar back to the PC.
Then I copied all remaining files from the original AP into the Magisk-patched tar and flashed the result in Odin......
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.
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.