How To Guide [GUIDE] UNBRICK YOUR HARD-BRICKED MTK

[Addendum_expired]

I attempted to flash a GSI onto my device, but it failed. After restoring from a backup in OrangeFox Recovery, it seems to have not worked as well and gets stuck on the logo screen for a long time. As a result, my only option left is to try re-flashing the ROM using SP Flash since this method has worked for my device in the past. However, it appears that this is not working now.

 

[valbaldemar]

My phone screen is always black with no backlight. According to your instructions, the phone was flashed. Flashtool completed without errors

 

[1lopes]

I think that when I press the volume up (+), volume down (-), and power buttons on my phone simultaneously, it doesn't seem to recognize any device. However, when I only press the volume up (+) and volume down (-) buttons, it recognizes a MTK Preloader USB VCOM port, and during the process, it seems to attempt to connect twice when "Disable Auth" is enabled. In addition, the BootMode displays as BootLoader

You can try different mtk preloader/bootrom drivers if you try searching up in the web

Have you tried filtering the usb connection with libusb?

Please try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451

Could you let the phone turn off by itself and then try to reboot into BROM by pressing all the buttons down and try?
Or unless you have a different model and codename. Do you have the camellia or lilac?

 

[1lopes]

I think that when I press the volume up (+), volume down (-), and power buttons on my phone simultaneously, it doesn't seem to recognize any device. However, when I only press the volume up (+) and volume down (-) buttons, it recognizes a MTK Preloader USB VCOM port, and during the process, it seems to attempt to connect twice when "Disable Auth" is enabled. In addition, the BootMode displays as BootLoader

Ah, nevermind. I see your problem.

You have a phone with MTK 6765. The Camellia has a MTK 6833 chip.

Did you use the drivers offered in this thread? If you did, please install these ones that are for your device:
https://mega.nz/file/YfgSkILT#8ST9kN0hVLaEtviUg1AhrlFnzKzGEAYy63KI6MYDlNE

 

[Addendum_expired]

Yes, I can shut down normally, access fastboot and recovery, and show charging when connected to a charger in a shutdown state. I can also enter all other modes except that when trying to boot into the operating system, the phone keeps getting stuck on the logo screen. I've also tried using libusb to filter USB connections, but it didn't work.

 

[1lopes]

Yes, I can shut down normally, access fastboot and recovery, and show charging when connected to a charger in a shutdown state. I can also enter all other modes except that when trying to boot into the operating system, the phone keeps getting stuck on the logo screen. I've also tried using libusb to filter USB connections, but it didn't work.

If you can access fastboot, then no need to follow this procedure. Your phone is soft bricked, not hard bricked since your phone still boots to fastboot and recovery (a hard brick is where your phone is completely dead that cant boot to nowhere, only to BROM)
Do you know how to peform a fastboot flash? If so, you will be able to boot into system by reflashing with MiFlashPro

Edit: just remembered you have a phone with MTK 6765. Would you mind telling what phone do you have by the way? It could be completely different from this device's forum and I could be mistaken to give you the wrong procedure.

 

[Addendum_expired]

Yes, it's not a Xiaomi phone. My device is Vivo Y3 (PD1901A) with an MT6765 processor. It's not a very popular device.

 

[Addendum_expired]

If you can access fastboot, then no need to follow this procedure. Your phone is soft bricked, not hard bricked since your phone still boots to fastboot and recovery (a hard brick is where your phone is completely dead that cant boot to nowhere, only to BROM)
Do you know how to peform a fastboot flash? If so, you will be able to boot into system by reflashing with MiFlashPro

Edit: just remembered you have a phone with MTK 6765. Would you mind telling what phone do you have by the way? It could be completely different from this device's forum and I could be mistaken to give you the wrong procedure.

Yes, I tried to flash GSI using fastboot flash, but then the device kept rebooting. After restoring the system backup from OrangeFox Recovery, the device is now stuck at the boot logo. I've thought about re-flashing the system.img using fastboot, but the system in this ROM is made up of multiple system.new.dat files.

 

[Addendum_expired]

Yes, I tried to flash GSI using fastboot flash, but then the device kept rebooting. After restoring the system backup from OrangeFox Recovery, the device is now stuck at the boot logo. I've thought about re-flashing the system.img using fastboot, but the system in this ROM is made up of multiple system.new.dat files.

 

[valbaldemar]

Please help me. What am I doing wrong? What firmware to choose? I tried several options. So far no results. Once, when trying to start fastboot mode, there was a multi-colored screen. Flashed V13.0.6.0.SKSMIXM. unsuccessfully

 

[1lopes]

Please help me. What am I doing wrong? What firmware to choose? I tried several options. So far no results. Once, when trying to start fastboot mode, there was a multi-colored screen. Flashed V13.0.6.0.SKSMIXM. unsuccessfullyView attachment 5901993View attachment 5901995

Would you mind sending a photo of your issue?
Anyways, try an older firmware like MIUI 12.0 Android 11, Global (MI) firmware

 

[1lopes]

Yes, I tried to flash GSI using fastboot flash, but then the device kept rebooting. After restoring the system backup from OrangeFox Recovery, the device is now stuck at the boot logo. I've thought about re-flashing the system.img using fastboot, but the system in this ROM is made up of multiple system.new.dat files.

I cant really help you. I understand that the VIVO Y3 is not popular, it doesnt even have a forum, but SP Tool should have worked since its a tool for every MTK device.

Anyways, please try reflashing again, and use these drivers that are for your phone socket:

8.85 MB file on MEGA

mega.nz

Those in the thread are for MTK 6833

 

[Addendum_expired]

I cant really help you. I understand that the VIVO Y3 is not popular, it doesnt even have a forum, but SP Tool should have worked since its a tool for every MTK device.

Anyways, please try reflashing again, and use these drivers that are for your phone socket:


Those in the thread are for MTK 6833

Yes, about a year ago, my device of this model was bricked, but I was able to successfully flash the ROM back onto my device using this tool and managed to get it working again. However, now, after more than a year, it seems that this tool is not working anymore. I'm not sure if it's because the manufacturer has updated the system and patched the vulnerability.

 

[1lopes]

Yes, about a year ago, my device of this model was bricked, but I was able to successfully flash the ROM back onto my device using this tool and managed to get it working again. However, now, after more than a year, it seems that this tool is not working anymore. I'm not sure if it's because the manufacturer has updated the system and patched the vulnerability.

What can I try to help you is the following

Try the thread's MTK Auth bypasser. It works for every MTK device, but worth to take a try

Restart your computer. For the drivers to take proper effect and work correctly, maybe restarting your machine might work (just as the setup utility informed in the video). This is also mandatory for the MTK 6833 drivers

You only need to apply the libusb filter once and not every time you boot your phone into BROM, so no need to waste time on it (incase you have been doing it)

Try to find older firmware for your device and flash it, since 1 year ago you affirm they have done major changes

 

[Addendum_expired]

What can I try to help you is the following

Try the thread's MTK Auth bypasser. It works for every MTK device, but worth to take a try

Restart your computer. For the drivers to take proper effect and work correctly, maybe restarting your machine might work (just as the setup utility informed in the video). This is also mandatory for the MTK 6833 drivers

You only need to apply the libusb filter once and not every time you boot your phone into BROM, so no need to waste time on it (incase you have been doing it)

Try to find older firmware for your device and flash it, since 1 year ago you affirm they have done major changes

I have some good news, I finally managed to start up my device

 

[TheZian]

That is weird, are you able to boot into recovery or fastboot?
Did you get any verified boot error?
Did you use the right firmware? If so, what version (MIUI version (Indonesia/EEA/MI, etc.), Android version and Codename)? If you used the latest one (MIUI 14 Android 13) please try MIUI 13 Android 12 or lower

Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451

I tried the procedure again and in this case it gave me an error about the verified boot, do you have any solution to this problem?

Intenté otra vez el procedimiento y en este caso si me dió un error sobre el verified boot, ¿Tienes alguna solución hacia este problema?

Mod. edit: post translated. alecxs

 

[1lopes]

yes, in the error message, there will be specific partitions that are checking the verified boot. disable the checkboxes on those partitions in the mapping:

si, en la mensaje error, habrá particiones específicas que están comprobando el verified boot. deshabilita las casillas de verificación en esas particiones en el mapeo:

yes, it is bypassable.

you just go to the mapping, and disable the checks on those partitions. it will still boot normally, afterwards, if you want (which is not necessary), you can reflash your phone via fastboot and miflash for those partitions to be flashed correctly
View attachment 5895435

Mod. edit: post translated. alecxs

 

[TheZian]

It has not worked for me, it is still in the bootloop and without giving me access to recovery or fastboot, I really do not know if it is important but the phone bricked after trying the following tutorial:
After putting the command "fastboot reboot fastboot" it entered the bootloop and did not give me access to recovery or fastboot, I don't know if that is important but I'll tell you anyway.

No me ha funcionado, sigue en el bootloop y sin darme acceso al recovery o al fastboot, realmente no se si sea de importancia pero el teléfono se brickeo después de probar el siguiente tutorial:
Después de poner el comando "fastboot reboot fastboot" se metió al bootloop y no me dió acceso ni a recovery o fastboot, no se si sea importante eso pero te lo comento de todos modos

Mod. edit: post translated. alecxs

 

[1lopes]

First of all, forget about GSI. We already have custom roms for camellian. I will come back to that later.

Now, it looks like you are trying to boot into dynamic fastboot (fastbootd), correct?

it mentions that you can't boot into fastboot, but could you do it before putting fastbootd?

After putting the command "fastboot reboot fastboot"

If you currently can't start your phone, flash through this guide.

then if you can start Fastboot, you should use Mi Flash to flash the system on your phone the MIUI.
https://mifirm.net/download/7689
I recommend you try this version of miui (12.5.6)

if you don't know how to proceed with MiFlash tell me



and going back to GSI, just use these custom ROMs of your choice:

Spoiler: original

antes que nada, olvidate de GSI. ya tenemos custom roms para camellian. volveré a eso más tarde

ahora, parece que esta tratando de iniciar en fastboot dinámico (fastbootd), correcto?

mencionó que no puede arrancar en fasboot, pero podría hacerlo antes de poner el fastbootd?

Después de poner el comando "fastboot reboot fastboot"

si actualmente no puede iniciar su teléfono, flash através de esta guia

depues, si puede iniciar Fastboot, debe usar MiFlash para flash el sistema en su telefono la MIUI
https://mifirm.net/download/7689
te recomiendo que pruebes esta versión de miui (12.5.6)
si no sabes como proceder con MiFlash dime



y volviendo sobre GSI, solo use estas custom ROM de su preferencia:

Thread '[ROM][12.1][UNOFFICIAL][xdroidOSS][STABLE] for Camellia/Camellian' https://forum.xda-developers.com/t/rom-12-1-unofficial-xdroidoss-stable-for-camellia-camellian.4584283/

Thread '[ROM][12][Camellia/Camellian] PixelExperience [AOSP] (Unofficial)' https://forum.xda-developers.com/t/rom-12-camellia-camellian-pixelexperience-aosp-unofficial.4572103/

Post in thread '[ROM][12.1][UNOFFICIAL][Camellia/Camellian] crDroid v8.14 [14.04.2023]' https://forum.xda-developers.com/t/rom-12-1-unofficial-camellia-camellian-crdroid-v8-14-14-04-2023.4573661/post-88425331

Mod. edit: post translated. alecxs

 

[TheZian]

Yes, before wanting to enter Fastboot mode I could enter Fastboot mode without problems, but when I wanted to enter Fastbootd mode the cell phone was bricked.

I will try to do the guide again, I only have one question, in the SP flash there is an option that says "Download Only", do I leave it like that or change it to "Firmware Update"?

Spoiler: original

Si, antes de querer entrar al modo Fastbootd podía entrar al modo Fastboot sin problemas, pero al querer entrar al modo Fastbootd se brickeo el celular.

Intentaré hacer la guía de nuevo, solo me queda una duda, en el SP flash hay una opción que dice "Download Only", lo dejo así o lo cambio a "Firmware Update"?

Mod. edit: post translated. alecxs