Dotos could be good
three easy reasons: bloatware, optimization, rootingWhy to install ROMs when you have android 12 official support i got the update on my phone
only?
yes just like the same our world it's only : sea , sky and earth
Why dont you try an GSI of android 12About bloatwares there are many threads on XDA and on the internet explaining how to remove Google and Samsung bloatwares with adb command with many lists of apps you can remove or disable by yourself.
For rooting and at present time there is only one way to do it and it's all explained in my tutorial you can find here :
![]()
You can find the latest magisk-v24.0.apk in post #174 so skip the one I posted in OP...
For optimization, as this is a new phone and as no one can propose the kind of optimizations you expect and as rooting is "experimental", you have to do optimizations by yourself... ^^
By "experimental root" I meant root is actually working fine, BUT Magisk is going on a new way as Magisk Hide is missing or not working as it should !!!
I did explain all this in my tutorial.
There is no TWRP available yet for this phone and thus no custom ROM either... ^^
GSI means Generic System Image. These kind of ROMs work on any device running android 8.0 or higher and support A-Only or A/B partitions.This has been fix with my tutorial and @beanbean50 confirms he rooted his Galaxy Fold 3 with his camera working.
I have seen this term many times but still don't understand the meaning of GSI... ^^
You can use Zygisk to hide root from apps i successfully hided my root in magisk v24 from my nexus 5 i had in my drawerAbout bloatwares there are many threads on XDA and on the internet explaining how to remove Google and Samsung bloatwares with adb command with many lists of apps you can remove or disable by yourself.
For rooting and at present time there is only one way to do it and it's all explained in my tutorial you can find here :
![]()
You can find the latest magisk-v24.0.apk in post #174 so skip the one I posted in OP...
For optimization, as this is a new phone and as no one can propose the kind of optimizations you expect and as rooting is "experimental", you have to do optimizations by yourself... ^^
By "experimental root" I meant root is actually working fine, BUT Magisk is going on a new way as Magisk Hide is missing or not working as it should !!!
I did explain all this in my tutorial.
There is no TWRP available yet for this phone and thus no custom ROM either... ^^
no dependancies twrp to custom rom (one can be created without other and vice versa) , indeed are several recovery (lineage,pitch black, orage fox) for custom rom , theoretically could be installed by odin. telephone is not so new (august 2021), has chipset 778 (febraury 2021) . Samsung UI , it's heavy and with some bugs or limitataion (randomly camera not working with bl unlocked, call reacording not enabled if you dont' flash uae rom). You explain so many , many works that custom rom can resolve with snap. That's why good Custom rom always better than other 10000 tiny, boring and time spendig jobsAbout bloatwares there are many threads on XDA and on the internet explaining how to remove Google and Samsung bloatwares with adb command with many lists of apps you can remove or disable by yourself.
For rooting and at present time there is only one way to do it and it's all explained in my tutorial you can find here :
![]()
You can find the latest magisk-v24.0.apk in post #174 so skip the one I posted in OP...
For optimization, as this is a new phone and as no one can propose the kind of optimizations you expect and as rooting is "experimental", you have to do optimizations by yourself... ^^
By "experimental root" I meant root is actually working fine, BUT Magisk is going on a new way as Magisk Hide is missing or not working as it should !!!
I did explain all this in my tutorial.
There is no TWRP available yet for this phone and thus no custom ROM either... ^^
What do you mean by UAE rom?no dependancies twrp to custom rom (one can be created without other and vice versa) , indeed are several recovery (lineage,pitch black, orage fox) for custom rom , theoretically could be installed by odin. telephone is not so new (august 2021), has chipset 778 (febraury 2021) . Samsung UI , it's heavy and with some bugs or limitataion (randomly camera not working with bl unlocked, call reacording not enabled if you dont' flash uae rom). You explain so many , many works that custom rom can resolve with snap. That's why Custom rom it's always better than other 10000 tiny, boring and time spendig jobs
united emirates rom. the only one so far with native call recording .
i live there lolunited emirates rom. the only one so far with native call recording .
here codes
![]()
List of Samsung Galaxy CSC Country Specific Product Code/Region
Here you will get all the official firmware region/country codes used on Samsung devices. It is a long list of country codes. So we recommend scrolling down to your country name and check by the code. Algeria. ALG = ALGERIA ALR = ALGERIA Argentina. ANC = ARGENTINA ARO = ARGENTINA CTI = ARGENTINA...eu.community.samsung.com
Sorry to misunderstand youNOPE !!!
You thought I didn't test Zygist before posting the different variants of Magisk till Magisk v24 ??? lol
Magisks post v23 were mostly written for the Oppo, Xiaomi and then Nexus/Pixel devices, but Samsung Galaxy devices were not taking into account in the devs's priority if not at all !
I follow most of the discussions in the development of the Magisk forks and no one even owns a Samsung devices or even care about Samsung.
There was a bug in Magisk v23 that causes bootloop in most newer Android devices (a fstab story) and instead of simply patching Magisk, they decided to take Magisk all apart with a fork for Oppo, another one for Xiaomi and then one for the Nexus/Pixel all with a different philosophy... Instead of Magisk Hide which was removed, then created new concepts of "Deny List" and/or "White list" but which work differently from the previous Magisk Hide !!!
Zygist doesn't work, or at least not with the Samsung Galaxy !!!
- First, it disables riru framework and EdXposed/LSposed modules and thus all modules based on them won't work anymore such as XprivacyLua, Firefds Kit and some others... Only AfWall++ continues working...
- Then, once rooted with magisk with Zygist on, I couldn't get any protected Samsung apps working such as Secure Folder, Samsung Health is working only partly as I can run it once but I can't access to it anymore unless I reboot the phone. Samsung Health is working in the background as I can see its notification and the number of steps I walked during the day (...), but once again I can't access to the inner of the apps and I don't have access to the health parameters... Samsung Pay also won't work and others I don't use...
ATM I'm still fighting with Android studio to understand how I can build my own Magisk app for the Samsung Galaxy devices...
I will try to build an TWRP for it I will try and upload it here hopefully I suceedI don't know your real english level but you didn't follow all the discussions at all as this is exactly what I said there is no dependencies between TWRP and custom ROM !!! SIC
But you need to build TWRP with the source code from the Galaxy A52S 5G specifically as TWRP for the A52 5G won't work on our device !!! I also tried different TWRP from other brands/models with the same SOC but again they do NOT work !
Then you are confusing between so many things which are not related with TWRP or custom rom such as "camera not working with bl unlocked", call recording and so on...
Many bla bla bla, but what can you do for the community ??? ^^ SIC
Are you able to build a TWRP for the A52S 5G or can you build a custom rom for the same device ???
So STOP TALKING (and criticizing) and DO SOMETHING if you can !!!
i dont'know if your are a troll (your problem). Probably due to your english level comprehension you lost several thread passages, that before your intervention was going smoothly. No one has been criticized and no one say it's easy to build something. Luckily your are not moderator and this forum it's free also for flamer just like you. keep cam and take a chamomileI don't know your real english level but you didn't follow all the discussions at all as this is exactly what I said there is no dependencies between TWRP and custom ROM !!! SIC
But you need to build TWRP with the source code from the Galaxy A52S 5G specifically as TWRP for the A52 5G won't work on our device !!! I also tried different TWRP from other brands/models with the same SOC but again they do NOT work !
Then you are confusing between so many things which are not related with TWRP or custom rom such as "camera not working with bl unlocked", call recording and so on...
Many bla bla bla, but what can you do for the community ??? ^^ SIC
Are you able to build a TWRP for the A52S 5G or can you build a custom rom for the same device ???
So STOP TALKING (and criticizing) and DO SOMETHING if you can !!!
Actually my keyboard is not working righti dont'know if your are a troll (your problem). Probably due to your english level comprehension you lost several thread passages, that before your intervention was going smoothly. No one has been criticized and no one say it's easy to build something. Luckily your are not moderator and this forum it's free also for flamer just like you. keep cam and take a chamomile
Well said...although I'd like to point out that we should use respectful and courteous language.You forget that XDA "Developers" is made for "Developers", it's OK to post projects WIP as long as a disclaimer is posted and users are smart enough to read the disclaimer. Not everything needs to be working perfectly, it's completely fair to post your source and work in XDA even if it's not completed so that hopefully a more skilled developer can lend a hand with some of their experience and not be a complete a**** about it.
And no, I'm not only talking about you. There are some people that love pointing out how unexperienced you are and how you're very wrong about the work you did.
You made your guide to the general public and you made sure everything worked the way it's supposed to, and that's fine too, but don't expect everything posted in this site to be working flawless without any bugs, that's not what this site was created for.
We can all learn from each other and not turn this into an ego battle. We're supposed to encourage more people to learn, not discouraging them by telling them all they're doing is wrong.
You forget that XDA "Developers" is made for "Developers", it's OK to post projects WIP as long as a disclaimer is posted and users are smart enough to read the disclaimer. Not everything needs to be working perfectly, it's completely fair to post your source and work in XDA even if it's not completed so that hopefully a more skilled developer can lend a hand with some of their experience and not be a complete a**** about it.I am just saying the same thing as I said the first time I responded to you : Don't release anything before you tested it yourself and before you are sure your twrp is really working and you shouldn't considered others as your "guinea pig" !!!!
This is not a game or a challenge specially when you have no experience in building such a tool just as you admitted it yourself now !
Just before I published my tutorial on how to root the A52S 5G phone I spent many days in testing it in different ways : rooting it, restocking my phone and re-rooting again and again to be sure I was not doing mistakes.
Even after I was sure it was working I totally updated my tutorial taking into account feedback from users to clear up some parts of the tutorial that was not understood or because the Magisk version and some modules have changed.
I have myself the complete twrp tree to build a working twrp for A52 4G phone and the device tree for A52S 5G but I know there is still a lot of work before I can build a working twrp for our phone as I don't considered this as a competition to be "the first one" ... ^^
I know I have to build this twrp from source code and not by swapping incompatible images as you did.
I also tested the no touch twrp but my phone was bootlooping into this custom recovery and thus I had to re-stock completely my phone and I lost some of my apps and data even though I did a full backup. So I also warned other users not to use it with clear explanation on the risk if they do install it even though some may be attempted to test it themself... ^^
I am a retired developer and sys-admin but that doesn't mean I know everything as building such a tool is also new to me, so I am taking my time to understand the whole logic as I don't want to mess up others' phone !
yes just like the same our world it's only : sea , sky and earth