[Oppo A5s (AX5s)] ZG_DEV:
As a beginning to this thread : Getting root access for this phone is a great power, but sometimes we can't control this great power, which leads to a bootloop, or maybe bricking the device.

This thread will contain all possible reasons of bootlooping / bricking of this device & how to solve.

Those are the requirements that are needed there:

1- if do you think that your device (oppo a5s) is bricked, a bricked device should not boot or doing any action at all (but it possible to vibrate only when pressing power button as a attempt to be powered on)

2- Patience, patience is the MAIN part here.

3- A pc has windows 10 or older.

4- download these tools :

THE LATEST FLASHABLE OFFICIAL ROM [get it from Here, make sure that u downloaded version a.46 of it]

Note about the ROM : the scatter file which comes with the frimware is corrupted, I have modified it to be better :) (Download : Here)

SP flash tool: Here

MCT MTK Bypass REV4 : Here

Mtk driver installer : Here (note : reboot after installation)

Download these drivers:

VCOM driver

SP drivers

usbDK (optional)

Common bootloop issues + solutions:

1- Got a bootloop after using/installing a magisk module :

you can use custom recovery to wipe that module, modules are usually located in /data/adb/modules, you can also protect yourself from bootlooping that is caused from a module u installed/modules, install this Module (note : will disable all modules)(credits returns for @huskydg)

2- Got a system UI bootloop :

u need to make a factory reset / or reflash stock ROM, to prevent this to happen again, install this Module (Note : will disable the rest of enabled modules)

(note about bootloop protector modules : after you get a bootloop, wait for 3 minutes (after you detect that there is a bootloop), force shutdown it (by pressing all buttons until it shutsdown), these modules will detect that there was a bootloop and disables all other modules in next reboot so u can boot normally and remove the module that caused the problem.

3- bootloop/brick after flashing a partition, or a partition in a wrong path (like flashing system.img in vendor partition) :

eassssy, just flash the correct xxx.img in the specified xxx partition, if BROM mode doesn't work, just boot into META mode (vol.down + release when connected)

4- bootloop after doing nothing ? No problem, check this :

if you are also trying to see the right way to flash, whether your phone is bricked or bootlooping after modification of system or a wrong flash, then you are at the right place !

After downloading tools, stock rom and installing those drivers (also mtk driver auto installer):

● open SP flash tool

●locate the scatter file, all partitions will be located automatically, just untick preloader.bin to prevent bricking the device, keep the tick sign on the partition(s)you are going to flash.

● open mct mtk bypass Rev4 , boot your device into BROM mode (volume up + volume down + release them when connected to pc)

● click bypass and after it shows "ok" , go into sp flash tool and click "download" to start flashing...

What to do if your phone is bricked, or BROM mode is not working (either u want to flash a partition u flashed wrongly before or just booting into it just reboots the phone) :

Easily, boot into META mode !

Press volume down + release it when connected to pc (note that u need to be quick because this mode disconnects after few seconds if there is no response from u )

Steps of flashing through META mode is the same for BROM 🙂

All u need is to use mct mtk bypass before Flashing, then go to SP flash tool and Boom, u have rescued Ur phone from being thrown in the Garbage yard 🙂

NOTE : If you don't understand the whole thread, or a part of it, feel free to say and I and @Anonymous V will reply as fast as we can !

Another note : sorry if the thread is disorganised, editing+ organisation process stills in progress, if u have a question/ a reason of bootlooping/bricking and u want to add it, tell me here (if u have the solution too, that's okay too!)