Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy A53 5G (Exynos)

Search This thread

Lowkeys

Member
Jul 11, 2022
16
2
Go into TWRP and wipe your "data" partition. Then try again. Data is encrypted by default and this makes it unencrypted.
Let me know if this works for you.
Same thing, I went to twrp wipe then advanced wipe, to then wipe the data partition. The same thing happened its stuck on the lineageos bootloop. I guess the idea is to not update lineage os software, but to flash it through twrp when a new os version comes out?
 

aximut

Member
May 15, 2022
25
13
Same thing, I went to twrp wipe then advanced wipe, to then wipe the data partition. The same thing happened its stuck on the lineageos bootloop. I guess the idea is to not update lineage os software, but to flash it through twrp when a new os version comes out?

Hmm yeah then it has something to do with missing A/AB partition support. I remember getting it somehow to work but I don't recall the steps.
It's anyway cleaner to just flash from TWRP now that we have the luxury of having it on our devices.
 

Lowkeys

Member
Jul 11, 2022
16
2
Hmm yeah then it has something to do with missing A/AB partition support. I remember getting it somehow to work but I don't recall the steps.
It's anyway cleaner to just flash from TWRP now that we have the luxury of having it on our devices.
Can you recall the steps please that would really help. As I think that maybe we just have to repartition the device from twrp, is my best guess as to how to go around this. Idk I just read about it from here:
Edit: Thanks for the help you gave me lol, I much appreciate it as I think it'll take like 6-12 months for any official os to support the A53 as a legacy phone.
 
Last edited:

aximut

Member
May 15, 2022
25
13
Can you recall the steps please that would really help. As I think that maybe we just have to repartition the device from twrp, is my best guess as to how to go around this. Idk I just read about it from here:
Edit: Thanks for the help you gave me lol, I much appreciate it as I think it'll take like 6-12 months for any official os to support the A53 as a legacy phone.

Maybe later, this is not a priority for me now since I don't update the device very often anyway. And updates can potentially break things that were working, so it's anyway much safer to do a twrp backup before.
 

szinyo1048

Member
Jun 7, 2012
19
1
Hello! Please help! i have A53 5G, A536B/DS, i installed TWRP, and installed in TWRP magisk. And i have custom install.zip,
this overwrite the font and system/media/audio/ui files. But not working...
i try also: Magisk rooted system, and totalcommander / SuperUser Permission manual overwirte, but i received Error 36 ( Read only /system )
I want help, please get me any idea :(
 

randhackr

Senior Member
Oct 13, 2016
93
28
Is it also possible to make system/product partitions RW optional? That would be great for debloating/removing GOS.
 
  • Like
Reactions: crazyut

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    home.png
    backupname.png

    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    Code:
     * Your warranty is now void.
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or your getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.

    Supported Models:
    Galaxy A53 5G A536B, A536E, A536N & A5360

    Download & Guide:
    1. Unlock your bootloader.
    2. Downloads for A53 5G: a53x twrp and kernel
    3. Reboot to download mode
    4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
    5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
    6. Disable encryption:
    - Go to Advanced > Terminal, type: multidisabler.​
    If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​
    - Type: multidisabler again. will see - Finished. when done.​
    - Go back to Wipe > Format Data > type yes.​
    - Reboot to recovery.​
    7. Flash custom kernel and magisk apk in twrp.
    8. Reboot to system, Enjoy.

    Support:
    Live support is available via #twrp on Freenode with your IRC client or just click this link.

    Telegram:
    https://t.me/twrp_a_m_series

    Bugs:
    - Encryption not fully working.

    Thanks:
    TWRP team
    @MaloyZV on telegram for testing
    @ianmacd for multidisabler
    @Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
    Donators

    Sources:
    Kernel tree
    Device tree
    2
    OK thanks. What partition does the multidisabler actually patch to disable encryption? System? Or boot?
    Vendor is ro, it convert it to rw then patch vendor/etc/fstab.exynos****
    2
    The GSI has no support for userdata encryption, which means that the internal data can't be encrypted (and should be unencrypted in /data). Otherwise I would not be able to boot into the ROM. But maybe I am wrong on this.

    So if I reformat my data and run the multidisabler, does that mean I can access data in TWRP even having a custom ROM?
    Yes after running multidisabler and formatting data. You might able to boot GSI without custom kernel but not stock
    1
    Changelog:
    12.07.2022 - Initial Release.
    1
    Is it also possible to make system/product partitions RW optional? That would be great for debloating/removing GOS.