Database Develop

dead on arrival, no more fastboot

Hi,
today I received my Mi A2. I unlocked developer options and enabled OEM unlock.
Then I rebooted to fastboot via power + vol down and executed
fastboot flashing unlock_critical
as fastboot oem unlock didn't work (command unknown).
I got the bootloader unlock screen and commited by "unlock bootloader" + power button.
Until then the phone booted up. However I wasn't able to boot TWRP-3.2.3-jasmine-20180804.img or a magisk patched_boot.img, both attempts just hung without progress.
Now I'm stuck at the android one logo and nothing happens or at fastboot logo with no device detected.
I suspect it's bad RAM.
anyone else?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
meltbanana said:
Hi,
today I received my Mi A2. I unlocked developer options and enabled OEM unlock.
Then I rebooted to fastboot via power + vol down and executed
fastboot flashing unlock_critical
as fastboot oem unlock didn't work (command unknown).
I got the bootloader unlock screen and commited by "unlock bootloader" + power button.
Until then the phone booted up. However I wasn't able to boot TWRP-3.2.3-jasmine-20180804.img or a magisk patched_boot.img, both attempts just hung without progress.
Now I'm stuck at the android one logo and nothing happens or at fastboot logo with no device detected.
I suspect it's bad RAM.
anyone else?
Click to expand...
Click to collapse
try with this
http://en.miui.com/download-353.html
https://rmtxpg.db.files.1drv.com/y4...ubZwX8fw6A?width=463&height=739&cropmode=none

tzadkiel2 said:
try with this
http://en.miui.com/download-353.html
https://rmtxpg.db.files.1drv.com/y4...ubZwX8fw6A?width=463&height=739&cropmode=none
Click to expand...
Click to collapse
fastboot doesn't work, it's stuck at "waiting for device" and fastboot devices shows a blank space, though I see the mi bot logo.
I'll return it.
for me every single attempt to flash a file failed though it showed the unlocked logo for the few times it booted.
it even showed random behaviour (fastboot returned unknown command, etc.), took several times for fastboot reboot or did nothing, it's defective.

meltbanana said:
fastboot doesn't work, it's stuck at "waiting for device" and fastboot devices shows a blank space, I'll return it.
for me every attempt to flash a file failed though it showed the unlocked logo for the few times it booted.
Click to expand...
Click to collapse
Change port USB, remove driver's and begin cero.
Si entiendes algo de expañol, elimina los drivers del pc y comienza como si estuvieras comenzando desde cero, cambia de puerto USB y conecta con el teléfono en fastboot se debería de instalar el driver.
Prueba también a Agregar hardware heredado, y ya sea por puertos COM o por otros lados Android Bootloader Interface.
Como yo lo desbloqueé fue con fastboot oem unlock.
Le he dejado en peores condiciones en varias ocasiones no he visto manera de pasar al Sistema después de instalar TWRP, así que me ha tocado recuperarlo en bastantes ocasiones.

tzadkiel2 said:
Change port USB, remove driver's and begin cero.
Si entiendes algo de expañol, elimina los drivers del pc y comienza como si estuvieras comenzando desde cero, cambia de puerto USB y conecta con el teléfono en fastboot se debería de instalar el driver.
Prueba también a Agregar hardware heredado, y ya sea por puertos COM o por otros lados Android Bootloader Interface.
Como yo lo desbloqueé fue con fastboot oem unlock.
Le he dejado en peores condiciones en varias ocasiones no he visto manera de pasar al Sistema después de instalar TWRP, así que me ha tocado recuperarlo en bastantes ocasiones.
Click to expand...
Click to collapse
cannot even reach it under ubuntu via fastboot
it's impossible that I broke it cause I wasn't able to flash a kernel (boot.img) or something else
and I wasn't able to switch a slot: "this device doesn't support slots". when I entered fastboot set_active a it returned
this device only support slots
a
b
it acted as if it was infected with an ART rootkit or had bad memory.

meltbanana said:
cannot even reach it under ubuntu via fastboot
it's impossible that I broke it cause I wasn't able to flash a kernel (boot.img) or something else
and I wasn't able to switch a slot: "this device doesn't support slots". when I entered fastboot set_active a it returned
this device only support slots
a
b
it acted as if it was infected with an ART rootkit or had bad memory.
Click to expand...
Click to collapse
In my case I was trying to flash MIUI 10 the third time then it fails I was using Android One rom September update and it was working flawlessly without any problem.
After miflash tool fails to flash my phone wont be detected either of my PC and Mac
I am thinking using deep flash cable to enter EDL but is it possible for MI A2 hopefully it is because I don't want my phone to be opened, ITS NEW :crying:
Am I still covered by warranty? If not I have to send my phone to repair shop to just enter EDL mode and to be able to flash stock or miui again
About me flashing MIUI I did follow instructions to avoid Anti Rollback (Never flashed MIUI 10 via twrp instead I flash custom roms)

johnsci911 said:
In my case I was trying to flash MIUI 10 the third time then it fails I was using Android One rom September update and it was working flawlessly without any problem.
After miflash tool fails to flash my phone wont be detected either of my PC and Mac
I am thinking using deep flash cable to enter EDL but is it possible for MI A2 hopefully it is because I don't want my phone to be opened, ITS NEW :crying:
Am I still covered by warranty? If not I have to send my phone to repair shop to just enter EDL mode and to be able to flash stock or miui again
About me flashing MIUI I did follow instructions to avoid Anti Rollback (Never flashed MIUI 10 via twrp instead I flash custom roms)
Click to expand...
Click to collapse
Same thing happened with me no fastboot no edl .
Then I flashed my phone using test points method.
And yes you need to open your phone for that.

ARNOB XENON said:
Same thing happened with me no fastboot no edl .
Then I flashed my phone using test points method.
And yes you need to open your phone for that.
Click to expand...
Click to collapse
Then I guess I need to open mine too
Is it guaranteed that the phone will work again?
Have you tried it yourself?

johnsci911 said:
Then I guess I need to open mine too
Is it guaranteed that the phone will work again?
Have you tried it yourself?
Click to expand...
Click to collapse
Yes It will work 100%....Best of luck ..Open it very carefully..Must watch some videos in YouTube how to open Mi A2.

Does it work with deep-cable? Or another option before open it? I prefer return to Amazon than open...

Fix it?
meltbanana said:
Hi,
today I received my Mi A2. I unlocked developer options and enabled OEM unlock.
Then I rebooted to fastboot via power + vol down and executed
fastboot flashing unlock_critical
as fastboot oem unlock didn't work (command unknown).
I got the bootloader unlock screen and commited by "unlock bootloader" + power button.
Until then the phone booted up. However I wasn't able to boot TWRP-3.2.3-jasmine-20180804.img or a magisk patched_boot.img, both attempts just hung without progress.
Now I'm stuck at the android one logo and nothing happens or at fastboot logo with no device detected.
I suspect it's bad RAM.
anyone else?
Click to expand...
Click to collapse
Did you fix ir?
I hace the same issue but Idk how to fix it, Any help?:c
---------- Post added at 03:16 PM ---------- Previous post was at 03:13 PM ----------
tzadkiel2 said:
Change port USB, remove driver's and begin cero.
Si entiendes algo de expañol, elimina los drivers del pc y comienza como si estuvieras comenzando desde cero, cambia de puerto USB y conecta con el teléfono en fastboot se debería de instalar el driver.
Prueba también a Agregar hardware heredado, y ya sea por puertos COM o por otros lados Android Bootloader Interface.
Como yo lo desbloqueé fue con fastboot oem unlock.
Le he dejado en peores condiciones en varias ocasiones no he visto manera de pasar al Sistema después de instalar TWRP, así que me ha tocado recuperarlo en bastantes ocasiones.
Click to expand...
Click to collapse
Yo intenté todo eso, el problema es que ningún PC reconoce el Xiaomi mi A2 aún cuando está en modo fastboot, lo único que sale es esperando dispositivo, no más no lo reconoce.

Did anyone solved this problem?
I've bricked my device and I can get on fastboot mode but the PC won't recognize the device.
I've tried several computers and systems, windows, ubuntu, debian...
Did the deep flash USB cable work?

Mi A2 Hard Bricked (Anti-Rollback on October update?)

Hello.
I was on the September update, unlocked and rooted, but I wanted to update to the october one, so I uninstalled magisk and flashed the september boot and system images.
Unfortunately that didn't work (I still couldn't install the OTA), so I' ve decided to flash manually all the images of the october update (I got them on the OTA thread).
After that my device went on bootloop, so I decided to flash again all the images of the September update (V9.6.13.0).
When I run "fastboot flash system_a system.img" I got the error "Invalid argument" and after that my device turned off.
Now IT IS TOTALLY BRICKED, I can't turn it on and I can't even enter fastboot.
I really don't know what to do, do you have any idea?

If you have working fastboot try to Flash full September update with Mi flash tools, wipe everything and Lock bootloader.
After that you will receive ota from October.
Sent from my Mi A2 using Tapatalk

tomgv said:
If you have working fastboot try to Flash full September update with Mi flash tools, wipe everything and Lock bootloader.
After that you will receive ota from October.
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
As I've said, I can't enter fastboot mode.
My device is bricked

Lurensu said:
As I've said, I can't enter fastboot mode.
My device is bricked
Click to expand...
Click to collapse
Open your phone and flash through EDL mode by shorting test points...

Yep, your last hope is attempt to flash through edl mode by shorting those pins, that's why I always re-install stock rom using Mi flash through edl mode booted from fastboot

Thanks guys, I hope to find a method which doesn't require to open the device.. if I fail I'll try the test points one.
However my device is still recognized by Windows and by MiFlash as Qualcomm QDLoader 9008 and I've read that some people managed to flash a fastboot rom in this mode (on the Mi A1).
Isn't this EDL mode already?
Looking at this guide it looks like the whole point of "test points" is to get the device recognized as QDLoader 9008, isn't it?
https://forum.xda-developers.com/redmi-note-5-pro/how-to/edl-mode-redmi-note-5-pro-t3779267

Lurensu said:
Thanks guys, I hope to find a method which doesn't require to open the device.. if I fail I'll try the test points one.
However my device is still recognized by Windows and by MiFlash as Qualcomm QDLoader 9008 and I've read that some people managed to flash a fastboot rom in this mode (on the Mi A1).
Isn't this EDL mode already?
Looking at this guide it looks like the whole point of "test points" is to get the device recognized as QDLoader 9008, isn't it?
https://forum.xda-developers.com/redmi-note-5-pro/how-to/edl-mode-redmi-note-5-pro-t3779267
Click to expand...
Click to collapse
When phone is recognized as qualcomm it means it's bricked so it entered edl by itself, you can use mi flash to get back to september patch, then boot into fastboot and flash it again, then ota
EDIT: anti rollback is still not activated in october patch

Nebrassy said:
When phone is recognized as quallcomm it means it's bricked so it entered edl by itself, you can use mi flash to get back to september patch, then boot into fastboot and flash it again, then ota
EDIT: anti rollback is still not activated in october patch
Click to expand...
Click to collapse
Whoaa that's great! (well, obviously it isn't, but at least I don't have to open the phone)
Are you sure about the anti rollback? So am I safe flashing the September fastboot images?
Thank you very much, I really appreciate your help

Lurensu said:
Whoaa that's great! (well, obviously it isn't, but at least I don't have to open the phone)
Are you sure about the anti rollback? So am I safe flashing the September fastboot images?
Thank you very much, I really appreciate your help
Click to expand...
Click to collapse
Yes, all A2 firmwares got ARB set to 2, I'm on 9.6.15
also, I was on first october build 9.6.14 but I had modified vendor, so I flashed september patch then got the ota to 9.6.15 so I'm sure, there's no ARB yet

Nebrassy said:
Yes, all A2 firmwares got ARB set to 2, I'm on 9.6.15
also, I was on first october build 9.6.14 but I had modified vendor, so I flashed september patch then got the ota to 9.6.15 so I'm sure, there;s no ARB yet
Click to expand...
Click to collapse
Thank you so much, I'll try to flash the september update then, let's hope everything goes right!
EDIT:
well, everything went smoothly and I'm now on the october update

I can enter un fastboot mode but my PC doesn't recognized my device, Someone can help me?
I have all drivers installed but always the same issue.

Hi guys.. Thanks for this article!!!. It was very useful. I had my Mi A2 bricked, I was in QDLoader 9008 state, but I didn't need to disassemble the MI A2, I think as Lurensu my device was already in the QDLoader state. I reached this state trying to manually update to the November patch, then "fastboot" didn't flash the aboot_b image, yes sure; I didn't realize this until the reboot.
I had the error "Cannot receive hello packet" with fails trying to flash with MiFlash, but the solution finally, was to have pressed the Power button for various seconds then the device was again ready for flash, and finally this was flashed to the September patch. I had this image files from some tools for rooting and updating.
Thanks again!...
---------- Post added at 01:14 AM ---------- Previous post was at 01:06 AM ----------
kevin2546 said:
I can enter un fastboot mode but my PC doesn't recognized my device, Someone can help me?
I have all drivers installed but always the same issue.
Click to expand...
Click to collapse
I'm pretty sure your problem is more simple than you think. Perhaps this is not the more adequate Thread, you need the windows drivers for Mi A2. This trouble is easily "googleable" :good:

yisao said:
Hi guys.. Thanks for this article!!!. It was very useful. I had my Mi A2 bricked, I was in QDLoader 9008 state, but I didn't need to disassemble the MI A2, I think as Lurensu my device was already in the QDLoader state. I reached this state trying to manually update to the November patch, then "fastboot" didn't flash the aboot_b image, yes sure; I didn't realize this until the reboot.
I had the error "Cannot receive hello packet" with fails trying to flash with MiFlash, but the solution finally, was to have pressed the Power button for various seconds then the device was again ready for flash, and finally this was flashed to the September patch. I had this image files from some tools for rooting and updating.
Thanks again!...
---------- Post added at 01:14 AM ---------- Previous post was at 01:06 AM ----------
I'm pretty sure your problem is more simple than you think. Perhaps this is not the more adequate Thread, you need the windows drivers for Mi A2. This trouble is easily "googleable" :good:
Click to expand...
Click to collapse
hola amigo me puedes dar una mano tengo mi a2 en estado EDL no prende solo lo reconoce

gian789 said:
hola amigo me puedes dar una mano tengo mi a2 en estado EDL no prende solo lo reconoce
Click to expand...
Click to collapse
Con la herramienta Mi Flash de Xiaomi lo puedes recuperar fácilmente, todo está en Google. En parte es tener el programa MiFlash y que te bajes una ROM OEM de este sitio, lo flashees y queda como nuevo; todo esto suponiendo que no tenga un daño peor, pero eso es raro

Lurensu said:
Hello.
I was on the September update, unlocked and rooted, but I wanted to update to the october one, so I uninstalled magisk and flashed the september boot and system images.
Unfortunately that didn't work (I still couldn't install the OTA), so I' ve decided to flash manually all the images of the october update (I got them on the OTA thread).
After that my device went on bootloop, so I decided to flash again all the images of the September update (V9.6.13.0).
When I run "fastboot flash system_a system.img" I got the error "Invalid argument" and after that my device turned off.
Now IT IS TOTALLY BRICKED, I can't turn it on and I can't even enter fastboot.
I really don't know what to do, do you have any idea?
Click to expand...
Click to collapse
09

[bricked] Slot _b is unbootable

So I ended up in the brick wagon, basically doing this:
- Tencent CN version converted to WW by vendor.
- Rooted / uptaded from root folder
- Changed fingerprint to WW
- Decided things got buggy here and there, did a factory reset
-> Slot _b is unbootable / Bricked
I tried flashall_AFT.cmd from both WW and CN raw firmware, both by clicking and command prompt, nothing happens (windows either disappear or stay still).
Phone does still answer to .\fastboot devices with powershell cmd.
Could somebody put me out of my misery ?

duck from space said:
So I ended up in the brick wagon, basically doing this:
- Tencent CN version converted to WW by vendor.
- Rooted / uptaded from root folder
- Changed fingerprint to WW
- Decided things got buggy here and there, did a factory reset
-> Slot _b is unbootable / Bricked
I tried flashall_AFT.cmd from both WW and CN raw firmware, both by clicking and command prompt, nothing happens (windows either disappear or stay still).
Phone does still answer to .\fastboot devices with powershell cmd.
Could somebody put me out of my misery ?
Click to expand...
Click to collapse
This happens when we root the phone.. so basically when you factory reset, phone tries to boot to recovery and doesn't work.. this is a known issue.. just get stock boot image for your versionand flash it using fastboot...

Thanks a lot !

duck from space said:
Thanks a lot !
Click to expand...
Click to collapse
Did it work OK flashing boot stock?

Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).

duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse
Does the cmd window pop up briefly and go again? If so, try removing or deleting the original zip from that folder, the one with the same name as the raw. Cmd gets confused /conflicts and crashes out...

Thanks for your help dude, yes that's what it does. I already done most known tricks to solve that issue to no avail. Might try on another PC now.

duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse
i have same problem too.

Experienced that as well at first, flashall_aft.cmd not doing at all. But I got it work by putting the extracted raw folder to the root of my C: in my pc.

ram4ufriends said:
This happens when we root the phone.. so basically when you factory reset, phone tries to boot to recovery and doesn't work.. this is a known issue.. just get stock boot image for your versionand flash it using fastboot...
Click to expand...
Click to collapse
if we flash stock boot image, are the phone still rooted..?

ghayathok said:
if we flash stock boot image, are the phone still rooted..?
Click to expand...
Click to collapse
No, you need to update Magisk after ota or flash root boot

I can't flash the stock boot image. It says my phone is locked. I tried relocking the bootloader and it gave me the Slot_b is unbootable message as well. Any advice?
---------- Post added at 09:12 PM ---------- Previous post was at 08:36 PM ----------
Schramx4 said:
I can't flash the stock boot image. It says my phone is locked. I tried relocking the bootloader and it gave me the Slot_b is unbootable message as well. Any advice?
Click to expand...
Click to collapse
Nevermind, I figured out I could switch the boot image over to Slot_a and that worked for me.

Just flash the raw full rom with bootloader by pc

How to do

Ajmi24 said:
How to do
Click to expand...
Click to collapse
Download the RAW firmware version you want, then;
'Extract the file on your PC. Boot the phone into fastboot mode (hold volume up then press and hold power button, Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...) connect to the side port and run "flashall_AFT.cmd" wait for it to finish and the phone will restart itself (it will take a number of minutes to complete, with the cmd window open all the time. If the cmd window only flashes up and closes down, then check the rest of the notes with this step).
NOTE: you need to remove or delete the original zip from the raw folder once extracted as it confuses the Flashall_AFT.cmd with the raw rom and zip having the same name. Also, it can help to extract to the root of C drive.'
Taken from my guide;
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279

duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse

BOA TARDE AMIGOS
ESTOU TENDO O MESMO PROBLEMA APÓS INSTALAR O TWRP
APAGO O TECIDO ROM WW ANDROID 10
REINICIALIZE O SISTEMA E APENAS LIGA E DIZ ESTAS INFORMAÇÕES (Slot _b não pode ser inicializado) VOCÊ PODE ME AJUDAR ONDE EU ENCONTRAR A IMAGEM DE BOOT, POSSO ENTRAR EM FASTBOOTON SMATPHONE MAS NO PC DE DISPOSITIVO DESCONHECIDO

Bootloop Redmi 9 (lancelot)

Hello i have flash TWRP on my Redmi 9
and on my computer i have typed this command
"fastboot reboot fastboot"
for acces to the fastbootd mode
and now i have
REDMI
Powered By Android
black screen
and
Redmi
Powered By Android
and this loop
my english is very bad
bye

I have this problem too!!! could you fix it? it happened to me when I did this too

try to hard reset

I had the same problem after trying to flash the TWRP custom recovery on my Redmi 9 (lancelot).
In case that someone still needs to know, following was my solution:
I needed to flash back the stock firmware on my device with SP Flashtool. For that you of course need to download the firmware and take the scatter file of it. Then grab a custom Download Agent File and an authentication file from the web.
Also you need the MTK_bypass utility with the right payloads from the github website (Redmi 9 is MT6768, just take the master collection payload, it worked for me). You need that tool to disable the DAA und SLA protection on your Redmi 9. (Except you have access to an authorized Mi account of course, then you can just flash it with Mi Flash tool, but usually, one doesn't have that.) Follow the instruction on the web, there are detailed ways how to install the right drivers and run the bypass utility correctly.
In my case I had to format my device with the automatic flashing in SP Flashtool before the flashing worked, but that was it - my Redmi 9 is working fine again.

thank you for the input as it really cleared my head after i took a break at trying to get this thing out of a bootloop.
this does work, using sp flash tool but the device will auto detect through usb and you've gotta have the scatter file and firmware for the device. after using the brom utility don't restart the phone, you will reverse the process.

iReebu said:
I had the same problem after trying to flash the TWRP custom recovery on my Redmi 9 (lancelot).
In case that someone still needs to know, following was my solution:
I needed to flash back the stock firmware on my device with SP Flashtool. For that you of course need to download the firmware and take the scatter file of it. Then grab a custom Download Agent File and an authentication file from the web.
Also you need the MTK_bypass utility with the right payloads from the github website (Redmi 9 is MT6768, just take the master collection payload, it worked for me). You need that tool to disable the DAA und SLA protection on your Redmi 9. (Except you have access to an authorized Mi account of course, then you can just flash it with Mi Flash tool, but usually, one doesn't have that.) Follow the instruction on the web, there are detailed ways how to install the right drivers and run the bypass utility correctly.
In my case I had to format my device with the automatic flashing in SP Flashtool before the flashing worked, but that was it - my Redmi 9 is working fine again.
Click to expand...
Click to collapse
if my phone is bootloop and can't go into recovery mode either fastboot mode, can it be done ?
my phone bootloop after installing twrp and there you go bootloop until the end. can't go any mode also can't turn off the phone. any suggestion ?

daniel04222 said:
if my phone is bootloop and can't go into recovery mode either fastboot mode, can it be done ?
my phone bootloop after installing twrp and there you go bootloop until the end. can't go any mode also can't turn off the phone. any suggestion ?
Click to expand...
Click to collapse
I had the same issue, I was not able to enter neither recovery mode nor fastboot mode. But you are able to enter EDL mode, the Emergency Download Mode - in my case at least. From there I was able to unbrick the phone. I was able to enter EDL mode without opening the phone and using test points. Turning the phone on and connecting it to the computer in the same second as the screen goes on let me enter for some seconds, it was enough to let me run the tool to bypass the DAA and SLA protection of the device. Then I was able to flash back the stock firmware with SP-Flashtool. In my case I needed to format the device before the flashing worked, but then it booted back up alive.
Just be aware you probably need to install the proper drivers first to bypass DAA and SLA protection with LibUSB.

I have the same problem, help
I already tried all the methods in this post, my phone cannot access fastboot or recovery mode, and when I connect it via usb it starts immediately

iReebu said:
I had the same issue, I was not able to enter neither recovery mode nor fastboot mode. But you are able to enter EDL mode, the Emergency Download Mode - in my case at least. From there I was able to unbrick the phone. I was able to enter EDL mode without opening the phone and using test points. Turning the phone on and connecting it to the computer in the same second as the screen goes on let me enter for some seconds, it was enough to let me run the tool to bypass the DAA and SLA protection of the device. Then I was able to flash back the stock firmware with SP-Flashtool. In my case I needed to format the device before the flashing worked, but then it booted back up alive.
Just be aware you probably need to install the proper drivers first to bypass DAA and SLA protection with LibUSB.
Click to expand...
Click to collapse
Can you tell us how did you unbricked your device step - by - step? Sorry I am a newbie and do not know how to do it.

Alfredo_One said:
Tengo el mismo problema, ayuda
Ya probé todos los métodos en esta publicación, mi teléfono no puede acceder al modo de arranque rápido o de recuperación, y cuando lo conecto a través de USB, se inicia de inmediato.
Click to expand...
Click to collapse
Si hablas español podría ayudarte, te dejo mi FB
Log into Facebook
Log into Facebook to start sharing and connecting with your friends, family, and people you know.
www.facebook.com
Cualquiera que tenga ese problema en cualquiera de los dispositivos Xiaomi que hable español puede comunicarse conmigo y con gusto los ayudaré

How To Guide [GUIDE] TWRP + LineageOS | A33

WARNING!
There is no official / stable release neither for twrp nor lineageos, that being said on my device the A33 5G SM-A336B-DSN *everything* works so far.
I do not take any responsibility for any damage that might happen to your device, same goes for the developers regarding unofficial twrp and lineageos releases.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This Guide will provide instructions how to install TWRP and LineageOS, the Kernel will not be modified.
• After unboxing, complete the initial setup of the Phone
• In Phone Settings press 7 times on "Build Number" to enable Developer Options
• In Developer Options enable OEM Unlock and USB Debugging
• Power Off the Phone
• Boot the Phone in OEM Unlocking Mode, for that you must:
• Hold volume up and volume down while the Phone is powered-off
• While holding the buttons connect the Phone to the PC via USB Cable
• Keep holding the buttons untill Phone is booted to OEM Unlocking Mode
• In OEM Unlocking Mode hold volume up for few seconds - This will unlock OEM and ERASE all Data
• After Erase, Complete again the initial setup and enable Developer Options aswell as USB Debugging
• Download TWRP and vbmeta_disabled_r on the PC (Credits go to Zillion for TWRP and afaneh92 for vbmeta_disabled_r)
• Boot phone in OEM Unlocking Mode and press vol-up to continue to Download Mode
• On the PC download Odin and Samsung USB Driver
• Install USB Drivers and connect the Phone to PC via USB Cable, then start Odin
• In Odin klick on AP and select a33x_experimental_twrp-tar
• In Odin klick on USERDATA and select vbmeta_disabled_r-tar
• Klick start to flash TWRP on the A33 Phone
• Download LineageOS GSI 20.0 Light Version on the PC (Credits go to Andy Yan)
• Extract the downloaded LineageOS GSI to get the .img
• Copy the "LineageOS_GSI.img" on any SD Card or USB Drive
• Insert SD Card to Phone or connect Phone to USB using USB Adapter
• Boot Phone in Recovery Mode (TWRP)
• In TWRP select INSTALL then press SELECT STORAGE, select SD Card or USB
• Choose INSTALL IMAGE and flash "LineageOS_GSI.img" to System
Note: When i first flashed Lineage, instead of booting to system the phone kept booting to recovery (twrp), i can't tell you why but it did not work.
Same happened with Andy's 19.1 Lineage GSI's.
I ended up re-flashing LineageOS GSI 20.0 Light Version again, and it suddenly worked, the phone booted to system (lineage).
If you have similar issues i suggest keep trying untill it works, like it did for me.
Many thanks to V0latyle for helping me getting twrp and lineageos running on the A33

Is it compatible with the A336M?

jejexd said:
Is it compatible with the A336M?
Click to expand...
Click to collapse
I don't know the differences between A336B and A336M
Just try it i would say. Probably will work, if not simply flash stock firmware.

• Update - For anyone following this guide, you can probably replace the TWRP listed in the original post with this one:
[RECOVERY] [OFFICIAL] [a33x] TeamWin Recovery Project 3 for Galaxy A33 5G (exynos)
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...
forum.xda-developers.com
I have not personally tested it.

Privacydroid said:
I don't know the differences between A336B and A336M
Just try it i would say. Probably will work, if not simply flash stock firmware.
Click to expand...
Click to collapse
May I PM you?

have you tested the lineage os? does it run better and smoother than samsung ui?? if it does then imma do this

perfect brother. thank you soooo much it works perfectly. even tho i had some issues with twrp install it works now

jejexd said:
Is it compatible with the A336M?
Click to expand...
Click to collapse
Si, es compatible.

How did you install gapps? if I try to flash it will complain there is insufficient space. Do I have to take the lineageOS containing gapps already or is there a way to flash it without the space error ?

rgaxiola said:
Si, es compatible.
Click to expand...
Click to collapse
Vale, gracias. Ya tengo el teléfono rooteado, me gustaría la custom ROM y TWRP pero, creo ando genial con el móvil tal cuál cómo va.
Gracias por confirmar nuevamente. Tan pronto como vea viable tener LineageOS, lo instalaré.

jejexd said:
Vale, gracias. Ya tengo el teléfono rooteado, me gustaría la custom ROM y TWRP pero, creo ando genial con el móvil tal cuál cómo va.
Gracias por confirmar nuevamente. Tan pronto como vea viable tener LineageOS, lo instalaré.
Click to expand...
Click to collapse
Honestamente no te lo recomiendo si manejas aplicaciones de bancos, tuve muchos problemas, ni con Magisk pude lograr que dichas aplicaciones no detectaran el teléfono como rooteado y potencialmente peligroso.
Tuve que regresar a Samsung One UI.
Saludos

Privacydroid said:
that being said on my device the A33 5G SM-A336B-DSN everything works so far
Click to expand...
Click to collapse
Are you sure? Have you tested things like USB tethering, MMS, SMS, calling etc.? Many people just simply don't bother to test these & then say "everything works"; had a problem like that on my previous phone where I couldn't send or receive MMS despite the ROM being considered "stable"

Sithhy™ said:
Are you sure? Have you tested things like USB tethering, MMS, SMS, calling etc.? Many people just simply don't bother to test these & then say "everything works"; had a problem like that on my previous phone where I couldn't send or receive MMS despite the ROM being considered "stable"
Click to expand...
Click to collapse
WIFI thethering at 5 Ghz is broken and no NR band, and I think game are not running at 90hz. I tried to contact Andy who just ignored my message so I guess the phone is too "young" for custom rom yet

My phone is stuck in the lineageOS bootscreen, i cannot access either TWRP or OEM download mode as the button combinations do not work, can anyone help me on how may i be able to fix that issue? I used TWRP from this post because the link on this one is down

i once got stuck on the charging animation and i just held both the side buttons and the power button, it phone should then boot off

Dryfty said:
i once got stuck on the charging animation and i just held both the side buttons and the power button, it phone should then boot off
Click to expand...
Click to collapse
It does boot off, but then it boots back to lineageOS charging animation, I have tried using button combinations to open twrp and download mode

Sithhy™ said:
Are you sure? Have you tested things like USB tethering, MMS, SMS, calling etc.? Many people just simply don't bother to test these & then say "everything works"; had a problem like that on my previous phone where I couldn't send or receive MMS despite the ROM being considered "stable"
Click to expand...
Click to collapse
I don't use a simcard so i haven't tested mms/sms, anways sms is a very insecure way of communication.
For chatting i would use one of these, Briar, Element, Session.
Neither have i tested usb tethering.
The only "bug" i experience is, when charging the phone while it is powered-off, it does not charge the battery, and the screen goes on showing that it's charging but it does not show the percentage...
I'm forced to power-on the phone everytime i want to charge it, otherwise charging doesn't work, it's annoying but i'm afraid there's nothing i can do.
So that's just my personal opinion, i preffer a "relatively stable" operatingsystem which is privacy oriented rather than a fully functional privacy invasive operatingsystem.

DiegoRuiz said:
My phone is stuck in the lineageOS bootscreen, i cannot access either TWRP or OEM download mode as the button combinations do not work, can anyone help me on how may i be able to fix that issue? I used TWRP from this post because the link on this one is down
Click to expand...
Click to collapse
Hello, i had the same issue.
As DiegoRuiz said, you should be able to poweroff the phone by holding all buttons at the same time.
Then when powered off, immediately hold the buttons to boot into downloadmode and try reflashing the os again.
The process seems somewhat broken, but as i said in the original post i managed to install lineage after all.

DiegoRuiz said:
My phone is stuck in the lineageOS bootscreen, i cannot access either TWRP or OEM download mode as the button combinations do not work, can anyone help me on how may i be able to fix that issue? I used TWRP from this post because the link on this one is down
Click to expand...
Click to collapse
Did you install the custom kernel as described in this post?
"Gabriel260BR - if you don't flash the custom kernel, the system will NOT boot!"

Privacydroid said:
Did you install the custom kernel as described in this post?
"Gabriel260BR - if you don't flash the custom kernel, the system will NOT boot!"
Click to expand...
Click to collapse
Yes i did, i flashed the custom kernel and it booted correctly, it was when I installed lineageOS that I started to have this problem