[Samsung Galaxy A52s 5G] ShaDisNX255:
FAQ
​

Q: Will this work on A52 4G or A52 5G?

A: No, I included A52s 5G specific vendor with hw libs. This will only work on A52s 5G

Q: Will this work on A73 5G?

A: I have no clue. I've been told HW is very similar with a few lib exceptions but I honestly have no interest on supporting this device. Anyone else is free to try and flash and fix it for A73, you've got my support.

Q: How can I report a bug?

A: Try and be as detailed as possible on how you encountered the bug. If you can include a logcat then even better. The more information provided the more likely it is to get the bug fixed.

Q: I'm getting a bootloop, what can I do?

A: There are 2 common fixes for this. If you were on stock ROM, then it's most likely you didn't do a format data. Please note that doing a full format of data and doing a simple data wipe are 2 completely different things. Make sure you're formatting. The other common fix for this is flashing either a custom or stock kernel. This usually happens when you were previously using an AOSP ROM like Lineage, PE or crDroid and you installed NcX without going to stock ROM first.

Q: Can I flash this ROM without wiping my phone (dirty flash)?

A: There have been reports of this being successful, but I never do it myself. I always try to use the same bases to make the ROMs so in theory it can be done similar to an OTA update. All up to you, a clean wipe is always recommended for the best performance.

Q: Help, I'm getting "secure check fail :" what should I do?

A: This is usually an error produced by mismatch in bootloader and the ROM images. To fix this, the easiest way is to install the latest stock firmware or the firmware best close to the version of the ROM you want to install (install February 2023 firmware if you want to install NcX February 2023 or install stock March 2023 firmware if you want to install NcX March 2023...etc...)

Q: Why aren't OTA updates installed automatically?

A: There's a bit of unfortunate news regarding this. Current OTA updates depend on TWRP's openrecoveryscript which seem to be broken on the latest TWRP official releases on both my A52s and A52. I don't like bothering TWRP devs or maintainers so I've passed on reporting it because it's really not widely used and for some reason stuff like crDroid OTA works fine on it. It could be that I'm working with outdated code but I'm not skilled enough to fix it.

If you want to keep using the latest TWRP, the way you install OTA's is following:

Download the update when available

When pressing Install, it should reboot to recovery. If it doesn't because you don't have Magisk installed, reboot to recovery manually

Once in recovery, select Flash on TWRP or directly navigate to the following directory with OrangeFox

sdcard/Android/data/com.mesalabs.ten.update/files

Flash the zip in the directory and wait for update to finish

[Optional] Wipe cache and dalvik cache

Reboot to system

If you want to use an outdated TWRP with openrecoveryscript working fine (which I really don't recommend unless you only want to use NcX and not any other ROMs), you can install the attached TWRP build which is unofficial and should not be used for any AOSP ROMs. The only benefit you'll get is that OTAs will get installed automatically.

This may be fixed in the future but for now, this is the current state of OTA updates

I don't do this for monetary compensation. I have fun making edits and personally using my own creations. I don't mind sharing my work for all to use. If you want to invite me a coffee, you can give a small donation to my PayPal or Wise account. It motivates me to improve my work and I like coffee :)

Donate to:

PayPal:

Wise: rayo.ivan255@gmail.com