Database Info

[A510] New discovery for my bricked A510

Hi all,
my A510 was half-bricked since I run the wipe option of CWM (version 5.8.4) last month. It can not boot to system, just hang at 'Iconia tab' logo if I power it on.
I tried to flash the stock recovery back, and flash the update.zip from SD. Every time it just stuck in 1/4 of the progress bar. (even change the zip or SD card)
{
"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"
}
Then I chose to install the new CWM for A700 ( version 6.0.1.1 ) and success to enter it. All the options can be run without any stuck, except for the wrong picture. I didn't know what to do, so i did all the wipe and format options.
Then it's getting more terrible, it stuck in Acer logo (first screen) after boot, nothing went further.
Last night I tried the SD flash again. I flashed all the roms from this thread, (I tried all the roms and failed to flash any last time)
To my surprise, one of the rom (1.060.00_EMEA_CUS1) can be flashed!
At first it stuck at 1/4 of progress bar as usual, then after a while it went to the 9/10 very quickly!
It reboot a few secs later and I saw 'updating EBT' at the upper left. Then it reboot again.
At the second-time reboot, I didn't see the 'bootloader unlock mode' shown in first sreen anymore, so it seems I made it?:cyclops:
Then I knew I am wrong, it also hang at 'Iconia tab' logo at last. :crying: oh, come on!
I didn't give up and continued to flash other roms. But i was too tired to sleep.:angel:
When i opened my eyes, i saw my tab entered the system finally!
No, wait! What is it?
title: 'XXXX unsuccessful'(my bad, i can't remember the first word)​content: 4 lines of words, about to tell u the tab need to be reset.
So I hit the 'reset tablet' button at lower right corner, then it reboot to recovery immediately. I saw the whole progress bar became very active and went backwards, and i waited it for half an hour, but nothing changed.
'coz that was midnight, i plugged the charger and went to sleep.
When I get up, it just hang there. damn it.
Anybody know what to do next?
p.s. My tab is EMEA-DE version.
Thanks and Regards,
Jokerzlh

Sorry, but I can't help you...
I just wanted to say this was a very entertaining story. You cracked me up. Good luck with your 510. Keep us updated.

ExtremeRyno said:
Sorry, but I can't help you...
I just wanted to say this was a very entertaining story. You cracked me up. Good luck with your 510. Keep us updated.
Click to expand...
Click to collapse
Thanks, it's an entertaining story indeed, but not a happy ending at last.:crying:
If I save my tab oneday then i'll share the method immediately.

jokerzlh said:
Thanks, it's an entertaining story indeed, but not a happy ending at last.:crying:
If I save my tab oneday then i'll share the method immediately.
Click to expand...
Click to collapse
Try this can't hurt anything else.Screwed mine up tried hard reset seems it wasn't doing anything for like 15 minutes then felt it vibrate then booted up back to factory. http://forum.xda-developers.com/showthread.php?t=1747802.

jessejames44 said:
Try this can't hurt anything else.Screwed mine up tried hard reset seems it wasn't doing anything for like 15 minutes then felt it vibrate then booted up back to factory. http://forum.xda-developers.com/showthread.php?t=1747802.
Click to expand...
Click to collapse
Never try the factory reset when the tab was unlocked, rooted and CWM installed.

help please
I have the exact same problem . I can flash update.zip for WW.GEN1 version successfully but it stops at "Iconia Tab" logo . does any one knows how can i fix this ?

yoooohooo
jokerzlh said:
Thanks, it's an entertaining story indeed, but not a happy ending at last.:crying:
If I save my tab oneday then i'll share the method immediately.
Click to expand...
Click to collapse
hi jokerzlh . i unbricked me tablet . :victory: do this step by step :
1. flash the working rom for yours "EMEA_CUS1".
2. Switch off
3. Press Vol-up 'one dot' + Power
4. If display goes on: Release power but hold vol-up
5. Toggle Lock switch (On>Off>On>Off)
Screen will display:
Erasing Userdata..
Erasing Cache..
then it will pass Iconia Tab Screen and will enter OS...
Waiting for your feedback...

DDKP4 - Phone Resets - Select Locale screen

Hello,
I have my phone on DDPK4. However it randomly resets my data and select Locale screen is displayed. I have tried updating software thrice via a local private service center. But this error will not go. While resetting contacts and messages are lost however application i have installed i.e. Whatsapp doesn't get lost. I m fed up of this and visiting again and again to service guy.
Before that when I tried to update to DDFL2, i screwed up my phone and whole motherboard of phone was replaced at cost of my pocket.
One more thing when i connect this phone to kies it takes 10000000000 mins to get connect but does not get connect actually. Windows system tray shows Hardware ID Missing.
Please help me to resolve this thing. Its been couple of months I m trying and no results :crying::crying:

Anyone ?

Maybe a motherboard problem.

it can be motherboard problem. but how did u try to update by kies or odin? can u get into download mode or recovery mode?give more details.

pratik_s said:
it can be motherboard problem. but how did u try to update by kies or odin? can u get into download mode or recovery mode?give more details.
Click to expand...
Click to collapse
Earlier it was on some Froyo build and was behaving weird like it will delete some messages or few apps or battery will drain all of sudden. One of its battery also got swelled and new genuine battery was purchased. When I tried to update it with DDFL2 via ODIN, its Internal memory got corrupt and it was giving error of "E: rfs format failed" on some mmc block. It was going in Download mode but not recovery mode. I tried various methods from XDA to bring it to life again but it all in vain. So gave this phone to service guy he said motherboard needs to replaced, which I got replaced for Rs.4500.
After posting here one of the day it got connected to KIES but when clicked on Firmware update and initialize, Kies says can not initialize and just before that in system tray a message appeared Hardware ID is missing.
But this issue of getting resetting is still continuing.
I m not getting what issue actually is. Is it hardware or software ?
I have sent it again this piece to service guy.

it is a hardware issue ur internel memory has been corrupted.there are two ways of making ur phone work http://forum.xda-developers.com/showthread.php?t=1644797&page=3 and http://forum.xda-developers.com/showthread.php?p=32245355&postcount=5.hope this helps if not then there is no other way than changing ur motherboard.

pratik_s said:
it is a hardware issue ur internel memory has been corrupted.there are two ways of making ur phone work http://forum.xda-developers.com/showthread.php?t=1644797&page=3 and http://forum.xda-developers.com/showthread.php?p=32245355&postcount=5.hope this helps if not then there is no other way than changing ur motherboard.
Click to expand...
Click to collapse
But motherboard is already replaced. :crying:
Well I got phone back with me now.
Also I can not enter recovery mode at present. I m trying it by pressing first Home + Volume Up, after 2-3 seconds pressing power button and holding them till Recovery is entered but phone does not start. Instead when I release all buttons phone starts normally.
1 more observation, I tried to run OTA (from Settings Menu of Phone) but after logging in to Samsung Account It tries to connect to server but in 4-5 secs it says connection failed. This thing is now frustrating me.
Also I am too afraid to do any software update by ODIN or CWM.

when did u get back ur sl after replacing motherboard.how many days before?and for entering in recovery mode u have to press volume up +home +power button simultaneously.are u able to do a factory reset?

If I understand your update on LF2 must be the reason
With odin 1.85 test only full KPE > http://www.mediafire.com/?8v9zi7apx2rc5o5
Without SD SIM battery 50% cold
You have already flashed the bootloader?
if not you must always put the KPE for Gingerbread
{
"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"
}

@LoLaTiOn are u suggesting that we should flash pit files with other files simultaneously with re-partition checked?

Yes full KPE with bootloader from froyo
Without if already gingerbread as the image
Odin 1.85 only !!!

i think u should make a thread on this and should explain how to flash because many people have had the motherboard problem on our sl.i also had the motherboard problem and had to replace motherboard as i was out of warranty and had to pay for it.before i use to flash only pit file by checking the re-partition first and then other files was it wrong.
---------- Post added at 11:59 PM ---------- Previous post was at 11:52 PM ----------
if we get to this stage http://forum.xda-developers.com/showthread.php?t=1735718 can we get our sl working.if yes how to get back.at that time i was able to get in download and recovery mode.thanks for ur reply.

My writing quality does not allow me to make long speeches understandable
I also made ​​the same mistake probably also not the only
I had before blocking with formatting cache because I have not checked the basic differences
not flash the pit only
I will not do anymore for me anyway

I have got my motherboard replaced around a month ago. After that almst on very next day it started acting weird same as it was acting on Froyo. I again ask service guy about this. He would fix all this with firmware flashing. But this cycle have repeated 4-5 times and i m tired of this crap now.
Right now I have left for my lectures hence can not try anything on it. After returning back home in evening I can try something and let you guys know if m able to enter any mode.
Thanks a lot for helping replies.

if the service centre has replaced ur motherboard and if the period is not more than a month then u should ask for a replacement of the motherboard.tell him that the problem is occuring frequently and u want a replacement of motherboard.

I have got it replaced from private service center which is very reputed here in my suburb and have repaired my waterlogged phones which official service guys refused to even tough even on my risk.
Right now phone is with service guy. He is going to use and inspect it thoroughly.
Will update again when I get any update.

Tomorrow evening I will get my phone again in my hand. So from now 18-20 hours to go

[Q] Is it bricked or hardware?

Hey.
So i bought a tf101 and it was never rooted before if you believe the previous owner. I used easyflasher to install, then installed cm10.
So yesterday i was going to bed, open the tablet and boff. Just died.
I could enter the APX mode (i saw it popped up when i connected it to the computer) but nothing else. So since it was late i thought i'l do the unbrick with easyflasher today.
Now i can't even enter APX mode.
So how do i know if it's bricked or hardware issues? Cause i've got ½ year of guarantee left on it.
EDIT: I can now enter APX mode for some reason, tried the unbrick on easyflash. Im using the WW SKU version. The easyflasher seems to have trouble cause the "wheele.exe" get's closed everytime after it uploaded the bootloader to 100%. But the installation still says it's done and no other errors shows up. But still not able to boot anything on the device.

One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?

Lethe6 said:
One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?
Click to expand...
Click to collapse
This is just wierd. Now it will boot, but only if it's in the charger... When i plug it out it dies. The battery says 76% and haven't moved so the battery seems dead?
And i've got the b50.
This is how it looks when i use easyflasher when it's on APX mode (as it was when i flashed recovery with easyflash). But when i boot up the tablet with charger it's still cw10.
{
"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"
}

Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.

Lethe6 said:
Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.
Click to expand...
Click to collapse
I've installed the drivers as wanted by EF. I can browse the internal SD without any problems so i'm not sure about that. Anyway to test that?
I think im gonna download some other rom right to the tablet and try install it. Otherwise i have to go and buy a sd-card thingy for the computer so i can try install stock rom that way i guess.
edIt: Installed Team EOS 4 *JELLYBEAN MR1* but diden't make any diffrence. Now i just need to try get stock and un-root so i can send it to asus :/

So i kinda got it to work out. I think.
I could keep the tablet alive after a while using the keyboard dock after having it being charged for about 10 min. So i had do unistall the "normal" drivers which i could not accsess before and then i worked to make normal rom with easyflash.
But question is:
Is the WW SKU right one for me (im from sweden.)?
Does the recovery go back to orignal also? When i tried to accses recovery all i got was the android green guy who had something wrong with his stomach. Means im back to orginial recovery?
Cause im gonna go back to the store as warranty issue, but i'd like to make it looked as much as possible that it was never rooted or had diffrent roms the the orgiinal.

Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.

Lethe6 said:
Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.
Click to expand...
Click to collapse
I downloaded some "check if rooted" app an it says it was not properly rooted which i guess means there is no root existing. Ty for your help man, been awsome. Just hope i won't get charged by asus somehow

Yeah hope so too! Let us know how it ends up going

Worse comes to worse, use PERI http://forum.xda-developers.com/showthread.php?t=1681155
Sent from my Transformer using Tapatalk HD

Lethe6 said:
Yeah hope so too! Let us know how it ends up going
Click to expand...
Click to collapse
So, just wanna update the thread.
The battery was dead so switched it myself after buying one for 50-60 dollars on ebay. Was quite easy, only painful part was putting on the thing around the screen with the power button etc so it would work.

Sweet, glad you got it fixed

Idol 3- Stuck In Bootloop After Flashing boot.img

Idol 3 Bootloop
I need your assistance
Hi, I have read through all of the posts and tried to find a solution with no luck.
I tend to always go one step too far with my hacking and playing/experimenting.
Alcatel One Touch Idol 3 5.5 6045K
It was booting into TWRP fine.
Then I wrote the non-functioning boot.img (which I thought was the backup of my pre-rooting version) on top of the working twrp recovery image.
So instead of installing the boot.img to the boot partition, I installed it to the recovery partition by mistake.
So now...
My phone just keeps booting and booting.
Alcatel Screen appears
The SuperSU installer starts
runs through its steps
Done!
Cleaning Up....
Will reboot in 10 seconds....
And starts all over again.
adb does not find any devices anymore
I am wondering if it possible at all to format the external sd card so that the phone will boot directly from there.
I have one single ray of hope ( maybe ) . The phone will boot into download mode. (Power off, hole power, volume up and volume down to activate)
The challenge I have now is the USB driver that was working now does not recognize the phone.
I have tried fastboot and I have also tried the OnDemand script. No luck.
I read that the download mode is used for flashing firmware and roms (most likely by the manufacturer)
Has anyone been able to install a rom using the download method successfully?
I am on Windows 10 All-in-One PC
Thanks in advance for any assistance you can provide.
N101BL

More Info
No ideas anyone?
Here is some more info. Hopefully it helps.
So this is what my screen looks like when the phone is turned on. I can only turn it off if it is not plugged in to usb or power.
{
"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 is the Download Mode. (Power off - then hold power button, volume up, and volume down. Let go when splash screen starts)
Download mode makes a connection sound on my PC so I know something is being recognized.
The phone stops bootloop and waits for something?
This is what appears in Devices and Printers Windows
These are the USB Properties for the USB Driver.
I am thinking that maybe there is a secret usb driver that Telus uses or Alcatel uses to push the firmware or rom onto the phone. Not just the default Alcatel usb driver. (not sure)
Even if I could somehow push a ne SuperSu.zip or my original backup files, everything would be good.
Any ideas would be amazing. I know the trials and tribulations of working with a new product. Hopefully you experts can decode this one.
Thank you.
N101BL (Kevin)

CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.

No Recovery Mode
DallasCZ said:
CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.
Click to expand...
Click to collapse
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)

You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.

what about off warranty repair by alcatel service in your country?

N101BL said:
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)
Click to expand...
Click to collapse
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
petrov.0 said:
You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.
Click to expand...
Click to collapse
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.

famewolf said:
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse
Probably but the files must be released in the wild first. I do searches in baidu from time time in case that something interesting pops up. I also must to admit that the translation of these sites is awful in most cases

Update
Well I sent my phone back.. Fortunately it was under warranty!
But now another hopefully minor issue with the replacement phone.
Please see this thread and post if you know what I am missing. I really appreciate your time and efforts!
http://forum.xda-developers.com/idol-3/help/valid-backup-file-t3199797
famewolf said:
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse

Question I hardbricked my samsung a32 5g .

So my litlle brother played with my phone .When it was doing a software update and somehow turned it off.And now when i try to turn it on it shows me some green dots and then shuts down.
When i am charging it it also shows green dots .If someone could help me thanks in advance.
{
"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"
}
VIDEO LINK

download mode or recovery mode doesn't work, it keeps turning on with the green dots on it

I'm afraid that Samsung Support is now your only option, seems like You've tried everything you could do on your own without voiding the warranty. As last resort, try extra dry it since it was in fact left unattended, then try download mode once more after.

NetBos said:
I'm afraid that Samsung Support is now your only option, seems like You've tried everything you could do on your own without voiding the warranty. As last resort, try extra dry it since it was in fact left unattended, then try download mode once more after.
Click to expand...
Click to collapse
Yep, best suggestion for now

Can someone explain what the "green dots" mean?

GalaxyA325G said:
Can someone explain what the "green dots" mean?
Click to expand...
Click to collapse
something to do with corrupt drivers, look at the picture and you will see some green bars

Hold volume up and down plus side key together will take your to download mode don't plug in USB cable

hold v+ v- and side key said:
Hold volume up and down plus side key together will take your to download mode don't plug in USB cable
Click to expand...
Click to collapse
you can't enter download mode without plugging in an USB cable...

my best suggestion is to try to go on download mode and reflash the software using the NAND erase function (refer to my post https://forum.xda-developers.com/t/...ts-functions-explained-noob-friendly.4540331/ )
if you don't succeed, search up "Test Point a32 5g"

Bro, I had the same problem, but mine got bricked when updating via Smart Switch( PC ). The app said it was a new firmware version to be updated, I thought: "Oh, nice, let's update it!", but, bro, it was bad thing, it got a error that something went wrong in the update, so, it was not starting;
Couple of things to know:
The Knox will just get tripped if you flash another recovery, eg: TWRP; to root you need a custom recovery, then we can say that root trips the Knox;
My A326B was OEM LOCKED, and there is no way to unlock it when you don't have access perfectly to android visually saying, you can relax about you data because the encryption of Knox does a good job on protecting your files;
When I tried flashing normally it got the message of failure to write in download mode and so in ODIN as well.
Before doing that consider going to a Samsung Support. Or just ignore this message.
After trying many methods, in case you have some problems in entering the bootloader mode, you can use the "Samsung 300K Tool.exe", it helped me entering my A326B to bootloader mode. After doing many stuff, and many times trying to install the system again, I realized because of the text saying about the bootloader, so a downloaded the exact same version of the firmware, in my case, from Brazil, and I just put in ODIN one file, the BL one, that is, the bootloader one. I got surprised when my smartphone just had awaken from a long journey of trying to relive it and I got impressed, even if all that messy things a tested my data was intact, so, my smartphone booted up working perfectly.
Where to find the firmwares? https://www.sammobile.com/firmwares/
if not, just copy the name of the firmware search it on internet, find somewhere to download.
Try to remember what was the last version( month ) that was installed before the installation or the one that was getting installed.
There's is also a windows app( FRP HIJACKER clicking in softbrick fixer choosing some model there) that can unbrick, or even try, or make you little more towards the door of getting out of this problem. Unfortunately, I could not notice, I was worried that time trying to relive the smartphone and so I don't know if by using this app will trip the Knox.
There's something you must know, I don't know where, when your smartphone got interrupted in installation, in which part of the installation.
Anything I can help you, i'm here.

I didn't know that time that by flashing a custom recovery would trip the Knox, saddddd, but I've learned more things.
Samsung Health, Samsung Pass, Samsung Pay, Samsung Secure Folder, and other apps that use Knox Security Technology will not work if Knox get tripped, and It seems like that google pay don't work with in rooted in this smartphone, even if you use Magisk Zygote.

I said bootloader mode in the post, but it was downloader mode.

Samsung just won't update this guy( A326B ) to Android 14.