Galaxy A34 Root Guide (SM-A346E)

Rooting has become quite difficult in the current times. Mobile manufacturers are introducing various restrictions in the name of security. Some phones have even turned off the bootloader unlocking feature! For example, even if you want to root Oppo and Vivo phones, it is no longer possible to root them because there is no official guide to unlock their bootloader.

But many manufacturers still release the source code of their phones, so rooting and flashing custom ROMs are possible on those devices. Nothing, Motorola, Samsung are among them.

I have been using the Galaxy A34 (SM-A346E) device for the last 3 years. One of the reasons for buying Samsung was their good support in the modding community. Although the device is still running well and is getting regular updates, I finally decided to root the phone with the “taste of freedom” :p

In this post, I will show you how to root Galaxy A34 by unlocking the bootloader and flashing a custom kernel within 30 minutes without fear of bricking your Samsung phone, and also take precautions to prevent bricking later.

Let’s get started!

Root pre-planning

Before doing anything, take these precautions:

• Take a backup of your device’s photos, videos, apps

• WiFi password, so that you can connect again after reset

• Back up SMS and call list

• Connect WhatsApp to your Google account and back it up too

• Remove all Google accounts, so that you don’t get FRP lock later

• If possible, remove biometric and lockscreen passwords from the device

That’s it, now you’re ready!

Note: Although the chances of bricking are very low now, try not to root your main device unless absolutely necessary. If you have to reset your phone for some reason, you may lose many important documents, and it may also disrupt your communication with someone. Of course, nothing will happen if you do not do anything yourself.

What you need to Root Galaxy A34

• A healthy, strong Samsung Galaxy A34

• A Windows-supported computer

• Data cable to connect the phone to the PC

• Updated to Android 15 or 16

• Firmware file for Galaxy A34

• Odin3 for Windows

• vbmeta_disabled.tar

• multidisabler.zip

• Kernel 1 | Kernel 2

• TWRP

• KernelSU 1 (extract the zip first) | KernelSU 2

• Anti bootloop module

• Courage and patience

• A strong reason behind rooting, which will add motivation during failure 🙂

• I succeeded using Tool [1], if those don't work, try using Tool [2]. These will work on all variants of A34.

Let's take all the tools, files, and inspiration with us and enter the world of rooting again!

Statutory Warning: Rooting increases the risk of the device facing various attacks. It also voids the manufacturer's warranty. This post will only serve as a brief guideline for rooting. Whatever you do as a user, do it at your own risk, and if you get into any trouble, the responsibility will be entirely on you.

Step #1: OEM Unlocking

Enable Developer Options by clicking on Settings > About device > Software information > Build number 8-10 times.

Then go to Developer Options and enable the Allow OEM unlocking option. If the phone does not have a password, this option may not be available, and you may need to restart the device after turning it on.

If you do not unlock the OEM, the bootloader unlock will fail. So this is the first step to root.

Step #2: Bootloader Unlocking

Now turn off the phone completely. Plug the USB cable into the PC. Then press and hold the volume up and down buttons of the phone together and connect the other port of the USB cable to the phone. After a while, the device will enter download mode.

From here, select the Volume up long press option. This means that if you press and hold the volume up button for 10-15 seconds, another confirmation will be asked, and if you press the volume up again, the bootloader will be unlocked.

Once unlocked, the device will auto-reset, which means all the data on the phone will be deleted. This is a security system of Samsung.

After the phone is turned on, connect to WiFi and go to Developer Options and check if the OEM unlocking option is disabled. The phone will need a net connection to connect to their Samsung server and verify.

Step #3: Custom Recovery Flashing

Enter download mode again in the same way, then press the volume up button only once. And connect the phone to the PC.

Launch Odin3 on the PC and select the TWRP file from the AP slot. And place the vbmeta_disabled.tar file in the USERDATA slot. Then turn off Auto reboot from the Option tab and click Start. The custom recovery will flash in a few seconds.

Now press and hold the Power button + Volume down button until the screen turns off. After it turns off, press and hold the Power button + Volume up button until the TWRP logo appears. If the logo does not appear within a minute, release the buttons and press them again.

Once in custom recovery, format the device by selecting Wipe > Format Data > yes. This is a mandatory step to remove any encryption.

Then select Reboot > Recovery. Now the system should boot into TWRP by itself; this means that the custom recovery flash was successful!

Now select Reboot > System, the device will start normally.

Step #4: Kernel Flashing

Now go to download mode and press volume up once to launch Odin on the PC and connect it.

Place the kernel file in the AP slot, then click start. The phone will auto reboot after the flash is successful.

Note: This kernel is based on Android 15+, so if your device is on 13 or 14, you will need to update the OS version first.

Step #5: KernelSU Installing

Install the KernelSU APK and check if everything is fine. If root access is not installed properly, an error will appear there.

Now install Root Checker and grant it root permission from KernelSU. Root Checker will now show a message that your device is rooted.

Congratulations! You have successfully rooted your Galaxy A34. Feel the power! 🔥

Security Steps

Since you will be using various modules now, it is not uncommon for the device to brick and enter a bootloop. So always keep an anti-bootloop module installed.

Later, if a module breaks the system, you can turn on the phone in safe state by pressing the button combo that you set during module installation. Turn it on and remove the faulty module.

Some common problems and their solutions

• If the phone does not connect in Odin mode, try connecting it to a different port on the PC, and use a good quality data cable.

• If TWRP does not appear even after pressing the power and volume combo, the phone will start normally and TWRP will not install properly. Then flash the custom recovery file from download mode again and boot into TWRP.

• If the phone gets stuck in bootloop after flashing the kernel, press the volume buttons to connect the data cable and flash another kernel + VBmeta from Odin mode again.

• If VBmeta does not flash, flash TWRP > Install > multidisabler.zip. This step is a must to disable storage encryption while rooting Galaxy A34!

• If KernelSU shows an error, install another version.

• If root checker does not work, clear its cache and force stop and check again.

• Since KernelSU modifies the phone's kernel and provides root access, it does not affect other partitions, and there is less chance of bricking. And due to kernel level access, other apps cannot easily detect root.

Note: Although your apps will not understand that you have rooted, Google and Samsung will understand. Google's Play Integrity will no longer work, so it will be difficult to run banking apps. Samsung's encrypted backup will also no longer work. Keep these things in mind and move forward. I have decided to address the Play Integrity issue later, I will post about it another day.

Okay.

May the journey of root continue, may the flag of freedom fly.

With that flag, farewell here like today 🏴‍☠️

Credit: XDA forum, Telegram, and lots of Google search