Database Develop

Update Available 2.19.401.2

Here you can download OTA, fresh firmware or system image to update your device.
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
firmware.zip only [19.6 MB]
2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip [TWRP] [1.15 GB]
Downloads: mega
​Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer. Don't know, what's that. Looks like a hash or a signature.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed). If you want just firmware, take it. Should be fastboot flashable.
*Additional notes*
Next lines describe my experience before I returned the device state to nearly stock.
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.

city2026 said:
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
Download: mega
Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed).
*Additional notes*
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.
Click to expand...
Click to collapse
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know

TWRP system backup added
csoulr666 said:
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know
Click to expand...
Click to collapse
I tried to update from recent backup (the one before I changed kernel and deleted system apps), but facebook.odex didn't let me.
Finally, the very first backup did it. I took only system and boot, switched twrp recovery to htc, skipped all setup and installed OTA over fresh system.
Here you go. Now you have TWRP image of this update.
BTW, kernel version is different. CL build number is the same.

Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks

ash0r said:
Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks
Click to expand...
Click to collapse
Unfortunately you cannot flash this with TWRP.

Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks

ash0r said:
Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks
Click to expand...
Click to collapse
You can try to restore the TWRP backup in the post. And yes, you will lose every mod since it is a backup of the stock, unrooted firmware.
The main problem of flashing the OTA zip would be that you will have to relock the bootloader before installing . So if you unlock it again, the internal storage will be wiped. The best way is to backup everything(Including the internal storage) and then proceed.

Actually, you can save your data while upgrading from non-worthy stock.
So, you may do this
Full backup, you never know what can go wrong.
Save or make a note of what you changed by yourself in system (from busybox to xposed & various modes.). You may use TB for sys-apps and simple file copying for modes. *
Restore updated system image from 1st post, so you have updated system.
See if it worked out and restore/reinstall your other system stuff.
* Remember, you still may access files of your twrp backup images through some archiver. Like I do using 7-Zip.
It's very important to save backup somewhere, cause it might be that my image can be not absolutely clean or can be not absolute right for your phone (like sell location difference). So it'll be easy to return back to working machine.
For this purposes I also setted up my TB for daily auto-backup of texts and settings and weekly backup of apps.
---
Don't sure about relock for upgrading. It seems to be launching, but it needs pure system and original boot & recovery. Some fastboot-magic helps here. That's how I did it after restoring to the very first backup.

So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful

The Watergod said:
So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful
Click to expand...
Click to collapse
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.

My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.

keninzeg said:
My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.
Click to expand...
Click to collapse
Did you buy your phone from a carrier? Carrier phones get different software updates

csoulr666 said:
Did you buy your phone from a carrier? Carrier phones get different software updates
Click to expand...
Click to collapse
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.

keninzeg said:
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.
Click to expand...
Click to collapse
If it has EE applications then it is an EE branded phone. Your updates will arrive differently and will have a different software number. So using the Europe zip will not help.

city2026 said:
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.
Click to expand...
Click to collapse
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance

The Watergod said:
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance
Click to expand...
Click to collapse
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.

city2026 said:
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.
Click to expand...
Click to collapse
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved

The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Simply flash custom kernel: like liberty sense or stock sense w/ dt2w.
It will unlock the opportunity to write on every partition. I mean system, cache, etc.

The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Hi
I will assume you have the virus I have been seeing lately that wouldn't allow you to reset the phone, where in reset option the automatic restore option remains checked and you can't uncheck it.
The only solution is through TWRP, you need to enter TWRP, erase Cache, Data, System then flash the Lollipop ROM again or stock from here: http://forum.xda-developers.com/one...one-mini-2-t3250020/post63859743#post63859743

So there is no Rom available that's pretty much stock without bloatware that I can install with twrp? If not is there some idiots guide to putting my stock recovery back on thank you all again

Security Update OPSS27.104-92-2

I am getting a nag screen to update to opss27.104-92-2 but I can't because I have rooted the phone. I noticed a similar question about the last update and there was a way to manually do the update. Does anyone know where to get the files for this security update so that I can do a manual install.
Alternative, does anyone know where the file is stored on the phone once it is downloaded? If I can find the file then I can probably unzip it and do a manual install.
Thanks

atomclock said:
I am getting a nag screen to update to opss27.104-92-2 but I can't because I have rooted the phone. I noticed a similar question about the last update and there was a way to manually do the update. Does anyone know where to get the files for this security update so that I can do a manual install.
Alternative, does anyone know where the file is stored on the phone once it is downloaded? If I can find the file then I can probably unzip it and do a manual install.
Thanks
Click to expand...
Click to collapse
You can't unzip it and try to apply it. It doesn't work that way. You either have to wait until a full firmware package with this update in it is released or reflash a stock system that matches the one you're on. You would need to flash the entire stock firmware. Then you can boot back to the system and take the update normally.

madbat99 said:
You can't unzip it and try to apply it. It doesn't work that way. You either have to wait until a full firmware package with this update in it is released or reflash a stock system that matches the one you're on. You would need to flash the entire stock firmware. Then you can boot back to the system and take the update normally.
Click to expand...
Click to collapse
I guess I will have to wait until some is kind enough to post a manual install version.
Thanks

atomclock said:
I guess I will have to wait until some is kind enough to post a manual install version.
Thanks
Click to expand...
Click to collapse
There won't likely be a way to install an update on rooted stock. You have to fastboot flash the firmware you're currently on (to remove modifications to system, boot.img, etc), then take the update. That IS the manual method. It should be stored in /cache. The /cache that's in the root directory of the phone. Which G6 do you have?

madbat99 said:
There won't likely be a way to install an update on rooted stock. You have to fastboot flash the firmware you're currently on (to remove modifications to system, boot.img, etc), then take the update. That IS the manual method. It should be stored in /cache. The /cache that's in the root directory of the phone. Which G6 do you have?
Click to expand...
Click to collapse
When I talked about doing the update the manual way, I was talking about doing it the way it is described in this thread.
https://forum.xda-developers.com/moto-g6/help/security-update-to-opws27-113-45-4-wont-t3818421
Hopefully, someone will extract the relevant files from the update and give instructions on manually doing the update. I really wouldn't call restoring the device to stalk and taking the automated update and then re-rooting the manual way. I would call that the hard way.

atomclock said:
When I talked about doing the update the manual way, I was talking about doing it the way it is described in this thread.
https://forum.xda-developers.com/moto-g6/help/security-update-to-opws27-113-45-4-wont-t3818421
Hopefully, someone will extract the relevant files from the update and give instructions on manually doing the update. I really wouldn't call restoring the device to stalk and taking the automated update and then re-rooting the manual way. I would call that the hard way.
Click to expand...
Click to collapse
That thread literally says install the stock firmware. You have to wait for the entire firmware for the new build to be released. no one is extracting anything from any update package. They are just using the full firmware package in that thread. You just have to wait for the full firmware to be posted on mirrors.lollinet.com the November patch for my G6 play was just posted there yesterday. that's why I asked which version of the G6 you have I will link you to the full firmware.
Or, You just fastboot flash stock, take the update, fastboot TWRP, use TWRP to flash magisk. No data loss, easy peasy.
the only difference in those two ways is taking the update after you flash stock or flashing stock firmware including the update. Either way you have to root your device again.
You can even flash stock with RSDlite using service file.xml instead of flashfile.xml
the file they are flashing with fastboot in that thread is the stock firmware. Just the newer one.

I was browsing for firmware today, the newest build/security patch is available on the lollinet Moto under Ali fw

GotHeart said:
I was browsing for firmware today, the newest build/security patch is available on the lollinet Moto under Ali fw
Click to expand...
Click to collapse
The question is can i use different software channel for my G6? Example 1925-6 to 1925-7 to gain particular service carrier signal

How to update S20 Fe Rooted

Hey guys, im from Brazil. Don't know too much about phones, recovery or root, but the basics.
I recently bought a S20 FE (Exynos) from a importer, but the phone was a showcase version (does not have IMEI). The seller made a customisation (root) so it have a IMEI and can do Calls and other stuff normally, so as it was in perfect state, I bought. I love the phone, it has been very cool to use it, but recently I discovered that another One UI version arrived (3.1 or 3.5, can't remember). Now, I wanna update it, but I don't want to lose my apps and another stuff in the phone, or even the IMEI for the calls and messages. In the Settings App, no update could be found, and I have lost contact with the seller. So, I'm here asking for help. Somebody has any idea?

while you are rooted and as a precaution, look up apps that can back up your apps and data.
the only way you're getting the updated android version by downloading the firmware yourself and using an app called magisk to patch a big file before flashing all that downloaded firmware yourself via an app called Odin.
that's the basics of it. you want to be sure you get the right version of firmware too, something intended for the same region your phone thinks it's from so to speak.
you have a steep learning curve ahead of you.
* google Samfirm and Frija to see what they are, then search for guides here which will hopefully have links to download them onto a PC.
* google what is a CSC so you're familiar and know how to choose the right firmware to download.
* google backup android apps and data to find either a PC app or a phone app (all being well you might not need this part but better to be safe).
* google magisk version 22 and look for GITHUB page by someone called topjohnwu only. don't get it anywhere else!!
* read the instructions on that GITHUB page 3 times and ask any questions you have about it here again. same goes for any other questions that come up.
* follow instructions to patch the AP file with your phone and magisk, it's amongst the firmware you would've downloaded.
* try to flash the downloaded firmware with the patched file also using one file called HOME_CSC and not the other that's just called the CSC file... all being well you should be good.
*** if at any stage you are asked or forced by a procedure to WIPE your DATA PARTITION, you will lose that IMEI that you have and you'll need to be discreet about getting it back. it's illegal to spoof that stuff to my understanding.
folks will help you here if they can so don't be daunted or put off.

how to root , flash custom recovery and custom ROM on galaxy S10 5G (G977N)

Hello folks !
I just bought a galaxy S10 5G G977N and I found it difficult to work my way through all the changes made in rooting/custom roming smartphones (I had a galaxy S7 before that, it was pretty easy).
What I read for now :
How to root with magisk : https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
How to install TWRP : https://twrp.me/samsung/samsunggalaxys105G.html
What I learned :
Rooting device is far more complicated than it was before. If I do so, I won't be able to update stock rom OTA, I'll have to reflash a patched recovery (AP file) for every update. This bothers me because its not convenient, and because messing with odin is way riskier than flashing zip from custom recovery and may brick my phone, so the less I use it, the better I think.
Plus,booting the phone will be a pain in the ass, having to do the right key combination
Installing TWRP will not change that.
What I'm wondering :
I'm a bit confused on how I will be able to update stock ROM (The way I understand it, I'll have to reinstall TWRP after each update)
And I'm even more confused about how all of this will work with custom ROMs.
Let's say I root my phone and install TWRP. If I want a custom ROM and keep it rooted, how will it work ? I'll have to unzip the ROM, patch the AP file with magisk, rezip it, flash it with twrp and voilà ? And I'll have the same key combination issue where I'll have to boot a certain way to access the rooted ROM, and if I don't, I'll boot on an unrooted ROM ?
Thank you a lot for helping. I'm really used to rooted and unbloated ROM (God I've forgotten how bloated stock ROMs are !) but the complexity of the operation stops me for now. I don't want to brick my phone and I'm not sure I'll have the courage to do all of this every 3 month for each update.

Hello!
This thread is a bit old. But since I had to dig the forum to find what I was looking for (and update my knowledge), maybe my answer will be useful for somebody else.
Rooting device is far more complicated than it was before.
Click to expand...
Click to collapse
Yep. That was a shocker for me, coming from a 7 year old phone.
Plus,booting the phone will be a pain in the ass, having to do the right key combination
Click to expand...
Click to collapse
I agree! Thankfully, somebody smarter than me took care of that. You can thank ianmacd for his multidisabler (GitHub project's page; xda thread).
One of its functionality is to disable "Stock recovery auto-restoration".
If you want to see a guide for how to use it (for S10 5G Snapdragon only, but same principle apply for the others), afaneh92 wrote one! Same thing by corsicanu, but with official links to download TWRP (and his repository for the other stuff), and it works with other versions of the S10 too. corsicanu got his tools here if needed.
Be careful, you must format /data after disabling encryption with multidisabler. Back up your data first!
I won't be able to update stock rom OTA
Click to expand...
Click to collapse
No OTA if you root.
You can still upgrade the stock kernel/firmware to a newer Android version manually. Afterwards, flash TWRP, then flash multidisabler again, then run multidisabler in terminal. And, all good!
(Reflashing stock firmware disables "multidisabler")
Check for firmware updates on Samsung's changelog page.
Replace your S10 model number and CSC code in the link below:
doc.samsungmobile.com/YourModelNumber/YourCscCode/doc.html
To know which CSC you have:
Go to Settings > About phone > Software information > Service provider software version
The last line should show the current CSC (three characters), e.g. mine is KTC for Korean KTC devices.
doc.samsungmobile.com/sm-g977b/ftm/doc.html
corsicanu makes it easier for us, here is his github page for the S10.
I'm a bit confused on how I will be able to update stock ROM (The way I understand it, I'll have to reinstall TWRP after each update)
Click to expand...
Click to collapse
To flash the ROM the first time:
Flash the ROM with TWRP (adb sideload), Format data/factory reset. Formating everything will reenable encryption if you had multidisabler installed first. I think. So I guess flash it afterwards, and format data again?
For example, you can follow Lineage OS's guide. But they don't take care of vbmeta, encryption, and other issues. I'm not sure why.
To update the ROM, it's easier: no need to reinstall multidisabler after a dirty flash. (Lineage guide to update their ROM)
I'm dropping some links you might need:
To download the last version of Odin (odin3-v3-14-1_3b_patched-zip as of date): realbbb's XDA thread.
All the versions of TWRP for the beyondx (G977B and N, maybe other letters too )
Ok. That's all for now. Good luck!

How To Guide how to Root Samsung Galaxy S23/S23+

How to Root Samsung S23/S23+ *Newbie Guide*
Attention, FYI:
The Root method was performed and successfully tested with a Samsung Galaxy S23 SM-911B/DS.
I do not guarantee that it will work on the other models, I can not test it because I do not have the devices.
However, it would be nice to hear if you have done it on another device model and it all works out, post here in the forum which model you have rooted.
Spoiler: Galaxy S23 - Model Information
SM-S911B -- Europe / Africa / Middle East / Oceania
SM-S911B/DS -- (assumed same as above, Dual SIM)
SM-S911U -- USA
SM-S911U1 -- USA ( factory unlocked )
SM-S911W -- Canada
SM-S911N -- Korea
SM-S9110 -- China / Taiwan / Hong Kong
SM-S911E -- Latin America
SM-S911E/DS -- (assumed same as above, Dual SIM)
WARNING
Before you root your device you must be aware that
This will void warranty.
As of now you will lose Samsung Pay and Samsung Pass forever if you root once, even unrooting won't help.
There are many features stop working when you unlock bootloader other than S pay/Pass like Samsung Health, Secure Folder, Galaxy Watch pairing issue, Issue connecting old gear watch (S3 or earlier), Google Pay etc but ROM is patched for all these mentioned features. Still you may trouble using some bank apps and these may fixed by adding these apps to Magisk Hide
There may be some knox features there which you may not able to use but I can't list those as I never used. Just Google It
Patched featurs are working today when writing this, No idea if it may stop working next moment/tomorrow or later
Also to note, once you root, you can't go back to "pre-rooted" state completely. It is one way!
OTA won't work once you root device.
Once you root the device, you will forever receive the following message: "Access denied - Unauthorized changes have been made to your phone. To get help, contact Customer Service.". Even if you reset the device back to factory settings and lock the bootloader, the message remains !!!! (with root there is a solution).
ROOT with caution.
You can unroot & Relock bootloader after flashing stock firmware, but still your warranty flag remain 0x1 and most of countries it still voids warranty. Also after unrooting & relocking bootloader, some knox features never work again.
First of all you need the following tools.
*A previously unlocked bootloader is the prerequisite!!*
Download last Samsung Drivers.
Download Odin v.3.14.1. (Thanks to realbbb)
Download Frija or Bifrost (Github Info)
Download Magisk v26.1 (Github Info) (Please use only this Magisk APK.)
1. Go into your Phone to developer mode and activate USB-Debugging
2. Install Magisk v 26.1 APK.
3. Download your (new) Firmware in Frija or Bifrost and Unzip File to PC.
4. Unzip Downloaded Firmware.zip.
5. Take from Unpacked Firmware.zip the "AP" to your Phone and open Magisk.
Go in Magisk to Install (from Device Slot) and take file the "AP- Data" from Storage and patch.
6. After Patch go your Download Folder from Device there is a MagiskPatched .tar Data. (your new AP-Data !)
Take the MagiskPatched.tar Data from your Phone to you Computer. (in same Folder like the Firmware files)
7. Open Odin on PC and turn off your Phone. Once your device is turned off > Hold Vol. UP + DOWN and Connect your USB-C cable from PC to your Phone. (Now start your Phone in Download Mode.) > Klick 1 time Vol. UP to start Download Mode.
Now in Odin your Device must be connected like "0:COM (Number)" in blue.
8. Now take from Unpacked Firmware.zip >
BL to BL
AP to MagiskPatched.tar
CP to CP
CSC to ***Read Attention***
*** Attention important!!! ***
#CLEAN - If you flash the first time Magisk clean on your device you must use the "CSC_OXM". (Accordingly, you lose all data and must set up your device again!!!)
#Update_Firmware - If you already have Magisk on your device and only make a firmware update take only the "HOME_CSC_OXM" !!! With the "HOME_CSC_OXM" you will not lose any data!
Start the Flash in Odin. (it takes 5 - 10 minutes!!!) Make sure that the cable is not accidentally touched / disconnected. It is best to use the supplied cable! Make sure that the cable has no loose contact and is seated correctly!
9. When the flash is finished, Odin says 1/Successful.
Your device will now restart automatically.
10. Once your device is successfully booted, open Magisk-App and you are successfully rooted. (A further reboot is automatically performed by Magisk!)
Finish !!! Gratulation !!!
If you have rooted your device I recommend the following Magisk extensions:
- Magisk Bootloop Protector v1.8.1-10015 - Safe you from Bootloop if u add wrong Magisk Module.
- BusyBox v1.0.4 - must have...
- SafetyNetFix v.2.4.0 > to pass SafetyNet and use Apps like Banking, etc.
- digitalkey_disabler_afaneh92 v1.0 > to FIX pop-up message "Access denied - Unauthorized changes have been made to your phone. To get help, contact Customer Service.". Even if you reset the device back to factory settings and lock the bootloader, the message remains !!!! (with root there is a solution)."
- ***Knox Patch v.0.5.0 (Thanks to BlackMesa123) > to FIX any Samsung Apps.
***For the KnoxPatch you need LSPosed v.1.8.6-6712-zygisk-release + KnoxPatch-APK + the KnoxPatch-Magisk modul.
Attached I have created a folder where I upload more Magisk extensions and APK tools for the S23. I will try to maintain it. If something useful is added I will pin it directly.
Root-Tools-Collection
If I have forgotten something, complement me.
Greetings Ramme

Do you have experience with ROM tool from Dr.Ketan? In this Magisk module there is an AdFree option and a lot customization. I thought that then KnoxPatch isn't needed because the fixes are also included.

waterpolo said:
Do you have experience with ROM tool from Dr.Ketan? In this Magisk module there is an AdFree option and a lot customization. I thought that then KnoxPatch isn't needed because the fixes are also included.
Click to expand...
Click to collapse
Yes, I personally use the Dr.Ketan Pro version. However, I try to work without the ROM-tool this time.
There is the ROM-tool-apk and if you pay the ProTwearks-extension-apk.
The problem is that you have to reset all settings in both tools after each system update, so I personally see no advantage in the ROM tool. With the last firmware update I was a little too hasty and have even shot me the ROM tool.
Unfortunately, Dr. Ketan makes no FULL ROM for the S23/S23+ so you have to live with it.
The Pro version is personally only for debloat.
On the subject of AD-Free, this is a nice extension, but this is a non-configurable AD-blocker, so you can not set personal configurations such as adding exceptions. So the classic and well working way use AdAway.
For AdAway there are some sources, I recommend if you are lazy the GoodbyeAds source + Own Exceptions.
Regarding the Knock Patch, I can't say anything about it, I use the file I pinned + LS-Posed (as a shortcut) and it works fine.
My SafetyNet is PASS.

Hello will this work on galaxy s23 sm-s911n ?
If not, do you have root instructions for sm-s911n

cashmonkey said:
Hello will this work on galaxy s23 sm-s911n ?
If not, do you have root instructions for sm-s911n
Click to expand...
Click to collapse
If you have the possibility to unlock the bootloader, it should work. The steps do not change.
However, I can't guarantee that it will work, so you have to try it at your own risk.
As far as I know, the bootloader cannot be unlocked on the US models, so you have no possibility to root there.

Ramme said:
If you have the possibility to unlock the bootloader, it should work. The steps do not change.
However, I can't guarantee that it will work, so you have to try it at your own risk.
As far as I know, the bootloader cannot be unlocked on the US models, so you have no possibility to root there.
Click to expand...
Click to collapse
Thank you for the prompt reply!
I'm in USA T-Mobile and purchased the galaxy s23 sm-s911n so I can get the 512gb version
I'll let you know when I get the phone and try the rooting to see if it works.
Fingers crossed
Thanks

hello there
after a further reboot automatically performed by Magisk,i lose root again,how to fix it
thanks

zeroabcdezero said:
hello there
after a further reboot automatically performed by Magisk,i lose root again,how to fix it
thanks
Click to expand...
Click to collapse
Did you use Magisk S23 version.
Last week my S23 rooted with the procedure in OP and have still root.

zeroabcdezero said:
hello there
after a further reboot automatically performed by Magisk,i lose root again,how to fix it
thanks
Click to expand...
Click to collapse
I had exactly the same problem, so it is very important to use exactly this Magisk version, which I have linked. Also, after installing Magisk, do not update Magisk for the time being.

Ramme said:
I had exactly the same problem, so it is very important to use exactly this Magisk version, which I have linked. Also, after installing Magisk, do not update Magisk for the time being.
Click to expand...
Click to collapse
Succeded!
Thank you again.

Ramme said:
I had exactly the same problem, so it is very important to use exactly this Magisk version, which I have linked. Also, after installing Magisk, do not update Magisk for the time being.
Click to expand...
Click to collapse
is the APK you linked the same as the canary version from the official Magisk GitHub?

Enddo said:
is the APK you linked the same as the canary version from the official Magisk GitHub?
Click to expand...
Click to collapse
No this is the APK which was posted in the "How to Root" topic by Dr. Ketan. This is currently the only Magisk APK that works with the S23 models.
For more info about the Magisk(KlickME). (Thanks to @BlackMesa123)
I have only uploaded everything separately in my cloud, on the one hand so that I can find the data quickly, on the other hand so that I can always keep the data up to date.

The only thing stopping me from rooting is losing Samsung Pay, which allows me to pay for public transportation without needing to unlock/authenticate.
Is there a way to retain Samsung Pay after rooting?

Gymcode said:
The only thing stopping me from rooting is losing Samsung Pay, which allows me to pay for public transportation without needing to unlock/authenticate.
Is there a way to retain Samsung Pay after rooting?
Click to expand...
Click to collapse
No there is (currently) no possibility to use SPay, there probably won't be.
You can use GPay as an alternative.
But it is also all described above in the topic. Please read it carefully before questions are asked. Alternatively, use a translator...
If new special possibilities come, I will of course share them with you, if you discover important features, please share them with me as well.

Adway is updated:
Releases · AdAway/AdAway
AdAway is a free and open source ad blocker for Android. - AdAway/AdAway
github.com

Hello all,
I'm running into an issue rooting S23 Plus that im not finding any information about online.
My boot loader is unlocked, I've followed the process to root. After installing the patched file from Magisk, the phone boots fine and gives me the setup, but I get an error at the portion where I accept Samsung terms. I just get -45
If I erase the phone back to the default FW, the setup completes without issue.
Has anyone ever seen this error before?

balbosta said:
Hello all,
I'm running into an issue rooting S23 Plus that im not finding any information about online.
My boot loader is unlocked, I've followed the process to root. After installing the patched file from Magisk, the phone boots fine and gives me the setup, but I get an error at the portion where I accept Samsung terms. I just get -45
If I erase the phone back to the default FW, the setup completes without issue.
Has anyone ever seen this error before?
Click to expand...
Click to collapse
Unfortunately not yet seen/had.
Try to reset your device according to my instructions, but for the first time without Magisk. Do not use the Home_CSC, but the normal CSC for the first time.
If your device can be set up and you get into the system, repeat the flash process with Odin, but now use the patched AP file and the Home_CSC file.
Now your device should boot, is set up and it should also have Magisk on it.

Ramme said:
Unfortunately not yet seen/had.
Try to reset your device according to my instructions, but for the first time without Magisk. Do not use the Home_CSC, but the normal CSC for the first time.
If your device can be set up and you get into the system, repeat the flash process with Odin, but now use the patched AP file and the Home_CSC file.
Now your device should boot, is set up and it should also have Magisk on it.
Click to expand...
Click to collapse
Okay, so just to confirm I'm doing this all correctly, since I'm fairly new to rooting.
I've downloaded the stock FW from Samfrew.
It contains 5 files.
AP, BL, CP, CSC, and HOME_CSC
On a clean install, I need to transfer AP to the phone and use Magisk to patch. After patch, I move back to my PC.
In Odin, I should be using AP from Magisk, then BL, CP, and HOME_CSC files from stock FW.
Is this correct?

balbosta said:
Okay, so just to confirm I'm doing this all correctly, since I'm fairly new to rooting.
I've downloaded the stock FW from Samfrew.
It contains 5 files.
AP, BL, CP, CSC, and HOME_CSC
On a clean install, I need to transfer AP to the phone and use Magisk to patch. After patch, I move back to my PC.
In Odin, I should be using AP from Magisk, then BL, CP, and HOME_CSC files from stock FW.
Is this correct?
Click to expand...
Click to collapse
Download your ROM in Frija.
Take out all the data.
Flash as follows:
BL, AP, CP, CSC. ( do not use the magisk-Patched-AP data)
Boot your device, set it up.
Once it's set up, install the Magisk APK version I post above and launch Magisk.(Dont Update Magisk!)
Drag the AP file to your device, patch the AP into Magisk and make it back to your PC.
Now flash BL, (Magisk-AP), CP, Home_CSC.
Then your device should boot normally and magisk is installed.

Ramme said:
Download your ROM in Frija.
Take out all the data.
Flash as follows:
BL, AP, CP, CSC. ( do not use the magisk-Patched-AP data)
Boot your device, set it up.
Once it's set up, install the Magisk APK version I post above and launch Magisk.(Dont Update Magisk!)
Drag the AP file to your device, patch the AP into Magisk and make it back to your PC.
Now flash BL, (Magisk-AP), CP, Home_CSC.
Then your device should boot normally and magisk is installed.
Click to expand...
Click to collapse
I tried this step by step.
After flashing with BL, Magisk-AP, CP, and Home_CSC, the phone will not boot. Eventually it tells me I need to factory reset. If I factory reset, the phone will boot to the setup, but im still met with "-45" when the phone should activate.