Database Info

Bricked my Skyrocket

I was flashing a new rom last night and it stopped right in the middle of it. Now when I turned it on the only thing I get is the samsung logo. I can't get into recovery mode to install my rom again. Any suggestion anyone?

If you cant get in to cwm than Go to download mode and using odin go back to stock. Reroot again.
Dude research you will find 10 threads about soft brick.
appdroid said:
These will set you back to Stock and Unroot Your phone.​
Welcome Finally You have made it here. Well now I know that you are little worried bout your phone but Let me tell you that there is noting to worry about.
Make sure you are relaxed because if you are tensioned than you will most likely screw things up. Do me a favor and watch this video. Relax get beer or Watch Funny videos on Youtube.
“Never ever unplug your phone when you are Flashing”
Drivers You will need!
! Odin 1.85
!! USB Drivers
!!! Skyrocket Stock Recovery.tar file ATT Or Rogers
Extract the contents of odin-185.zip and the 7zip archive.
Run Odin3+v1.85.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options.
Install Usb Drivers and Unzip the Recovery file and put it to safe place.
Main Process.
Try to get in Download Mode.
) Connect USB to computer but not your Phone.
))Take out and put back in the battery.
)))Then, hold Vol + and Vol - , now plug in USB and you will at the following screen that’s in picture.
))))Press Volume Up button now.
{
"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"
}
Finally You have made it to Download mode.
If in case this does not work for you than and you are still luck enough to go into CWM than do factory reset and flash any stock rom. And do all this steps again.
Ok so after getting into Download Mode.
-Go ahead and Go to Odin (Check "auto-reboot", and uncheck all other options).
--In Odin check PDA and find the recovery.tar file that you downloaded.
Now Press Start (Check "auto-reboot", and uncheck all other options.)
When you are done Your screen will look like one below.
It should now reboot to recovery and delete cache and data. Then, it will boot.
Click to expand...
Click to collapse
Rocketing on Sky Ics¡
digitalnrg said:
I was flashing a new rom last night and it stopped right in the middle of it. Now when I turned it on the only thing I get is the samsung logo. I can't get into recovery mode to install my rom again. Any suggestion anyone?
Click to expand...
Click to collapse
Rocketing on Sky Ics¡

digitalnrg said:
I was flashing a new rom last night and it stopped right in the middle of it. Now when I turned it on the only thing I get is the samsung logo. I can't get into recovery mode to install my rom again. Any suggestion anyone?
Click to expand...
Click to collapse
Put it in download mode and flash back to stock with odin
Sent via smoke signal

thanks guys. I was able to flash it back to stock based on above instruction

Instead of making a new thread, figured i would try here first.
Long story short, my skyrocket wont boot into recovery or cmw. I've tried both countless times, and all i can ever get is a quick flash of a battery icon. It still vibrates (gosh i hope thats a good sign of life) and has been plugged into the wall with stock cable/charger for about an hour now.
Basically, flashed the phone via cmw, waited 30+ minutes for it to reboot, it wouldnt, and now i have the problem described above. Battery was at about 40% when i flashed, but was plugged into my computer.
Any help? Maybe i need an external battery charger?
---------- Post added at 04:30 AM ---------- Previous post was at 03:38 AM ----------
GOT IT! took out battery, left it out for 15 mins. got right into cwm.
whew

teeg07 said:
Instead of making a new thread, figured i would try here first.
Long story short, my skyrocket wont boot into recovery or cmw. I've tried both countless times, and all i can ever get is a quick flash of a battery icon. It still vibrates (gosh i hope thats a good sign of life) and has been plugged into the wall with stock cable/charger for about an hour now.
Basically, flashed the phone via cmw, waited 30+ minutes for it to reboot, it wouldnt, and now i have the problem described above. Battery was at about 40% when i flashed, but was plugged into my computer.
Any help? Maybe i need an external battery charger?
---------- Post added at 04:30 AM ---------- Previous post was at 03:38 AM ----------
GOT IT! took out battery, left it out for 15 mins. got right into cwm.
whew
Click to expand...
Click to collapse
can you get the phone into download mode? unplug phone, pull battery and reinsert, press vol up/down at the same time and plug usb into phone, contine holding vol up/down until download mode arrears, basically have you followed the instructions in the post mentioned above?

Yes, I did try that, with no luck.
I actually got it, though. I pulled the battery countless times, did the whole download mode thing, cwm thing, and let it charge for an hour... so on, with no luck.
As an almost last resort, i ended up pulling the battery and leaving it out for 15 minutes after charging it for another hour. Once i reinserted it, i got it go into cwm, mounted my card, downloaded/flashed a new rom and I'm good to go.
Thanks for your help tho!
whew.

[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

Galaxy S6 0mb TWRP / no OS! Help wanted, i do not want an brick

I have Galaxy S6 and when i tried to install new ROM via usb-otg stick something strange happened and now my whole phone is unusable.
TWRP just says 0mb for internal storage and i cannot install anything since i cannot mount anything. I have looked pretty much all the "fixes" but nothing has helped so far :\ I have tried to format, wipe, change partition type, install, etc. And nothing has helped me so far. So if there are any ideas left please help :]
I think i still have root and when entering TWRP it does not ask password since i have done dm-verify long time ago.
Here is video showing some of the things: https://youtu.be/wXVVRBmRROU

go to download mode and flash stock firmware with ODIN. than flash twrp, enter recovery (twrp) before system. and boot to stock.
than try again.

HowJesNo said:
go to download mode and flash stock firmware with ODIN. than flash twrp, enter recovery (twrp) before system. and boot to stock.
than try again.
Click to expand...
Click to collapse
Hi!
I got stock firmware from Updato and then began to flash with Odin and it seemed that it would work since it was actually doing something at first (while trying to flash ROM's Odin crashes) but then it gave an error and stopped :\ Here is an picture of Odin's log.
{
"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"
}

I guess you had better restore factory image, make sure the system comes back. then flash updated version OS.
You can trying to use ODIN to do that. or using fastboot flash .....
https://gs6.gadgethacks.com/how-to/unroot-restore-samsung-galaxy-s6-back-stock-0162155/
Hope to it is helpful.
DARKKi said:
I have Galaxy S6 and when i tried to install new ROM via usb-otg stick something strange happened and now my whole phone is unusable.
TWRP just says 0mb for internal storage and i cannot install anything since i cannot mount anything. I have looked pretty much all the "fixes" but nothing has helped so far :\ I have tried to format, wipe, change partition type, install, etc. And nothing has helped me so far. So if there are any ideas left please help :]
I think i still have root and when entering TWRP it does not ask password since i have done dm-verify long time ago.
Here is video showing some of the things: https://youtu.be/wXVVRBmRROU
Click to expand...
Click to collapse

Okay, i have new problem. After i tried to flash with odin now i got only one place i can boot into and it looks like this:
I downloaded Smart Switch and entered emergency recovery but i was met with this screen and i have no idea from where to get the code.

in smart switch emergency upgrade and initialization, if will ask model and S/N.
model is SM-G920F and S/N in on the back of the phone. all caps.

HowJesNo said:
in smart switch emergency upgrade and initialization, if will ask model and S/N.
model is SM-G920F and S/N in on the back of the phone. all caps.
Click to expand...
Click to collapse
Smart Switch did not even have that option but i tried it with Kies and got this

smart switch should have same option. I found googling that in never versions that option was not functional due to Samsung not wanting people to debrand their phone. so older version is needed.
just got mine in a similar bootloop.
can u get into download mode?
If phone can't turn off do this:
- hold volume down + power, (that is reboot)
- as the screen goes black move finger to volume up + home key.
that should get you to download mode. now use odin to flash stock firmware.

HowJesNo said:
smart switch should have same option. I found googling that in never versions that option was not functional due to Samsung not wanting people to debrand their phone. so older version is needed.
just got mine in a similar bootloop.
can u get into download mode?
If phone can't turn off do this:
- hold volume down + power, (that is reboot)
- as the screen goes black move finger to volume up + home key.
that should get you to download mode. now use odin to flash stock firmware.
Click to expand...
Click to collapse
I tried that before and i tried it now again and same result:

is that firmware higher version than one previously installed?? i had that issue once!
G920FXXE5EQJ1........ try with any other with higher number. UK (BTU) is G920FXXU6ERC9

The problem is hidden.img file.
Search in google "galaxy s6 hidden.img fail" and solved.

HowJesNo said:
is that firmware higher version than one previously installed?? i had that issue once!
G920FXXE5EQJ1........ try with any other with higher number. UK (BTU) is G920FXXU6ERC9
Click to expand...
Click to collapse
Hi! I got the Model name but for some reason i cannot find S/N in the box or anywhere else
vindau said:
The problem is hidden.img file.
Search in google "galaxy s6 hidden.img fail" and solved.
Click to expand...
Click to collapse
Thanks a lot for this! I was able to install stock rom.
---
But then trouble started again. Boot screen came up and then text and mount problems like "failed to mount efs (no such file or directory)" :crying:
Here is the video about it, anything i could do now? I installed TWRP and it still says internal storage 0mb and formatting has no effect.
Video - https://youtu.be/OBfhTRWUZeU

I got little progress. I found the S/N from back of the phone with torch which i could not see without (Thanks for Augustin @ XDA Discord for this!) and then i tried to use Smart Switch but it does not recognize the phone and only option is "Emergency Firmware Recovery" and it needs some recovery code.
Then i tried Kies and it does not detect the device either and i tried the option "Firmware Upgrade and Initialization" and typed out model and S/N and after that it said "SM-G920F" does not support initializing"
So anyone knows what i could do now? Seems like i am running out of options here
Augustin also said that i should try pit but i have never used that feature in Odin so help with that would be awesome if it can remedy this situation somehow

You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459

allensd.cordero said:
You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
Click to expand...
Click to collapse
Thanks a lot! I will begin investigating and learning!
Hopefully this would solve this damn problem
And thanks a lot for this info!

allensd.cordero said:
You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
Click to expand...
Click to collapse
Thanks a lot! Finally using pit got the partitions right and phone is working like a charm now! :]

This might be a bit late but I am also currently in the same situation with my S6. Somewhere in the thread it said something about pit files but I don't really understand what to do. For reference, my issue is the exact same as OP's with the unmountable partitions and unbootable system. Would someone be kind enough to help out? My device is a SM-G920F from Vodafone (UK)

I may have bricked my new oneplus6

I got the phone yesterday, I rooted and today I tried to disable fused location, but when I did it and reboot, it shows me a screen, not bootloop, only a screen with asian characters which I don't understand except 'rf' in the middle.
{
"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"
}
So what I can do? I treated like a hard brick? I tried downloading the package-restrictions.xml file and change from disable to enable but that didn't work.
I was thinking than maybe installing the system from 0 could help but I suppose the zips from here don't work since it doesn't rewrite the data partition, and most probably the fail is there no?
EDIT: More information, seems the error is about an RF test https://forum.xda-developers.com/oneplus-x/help/stuck-rf-test-boot-t3610400

If you have an unlocked bootloader use this to restore to stock. This has saved my phone once.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

set92 said:
I got the phone yesterday, I rooted and today I tried to disable fused location, but when I did it and reboot, it shows me a screen, not bootloop, only a screen with asian characters which I don't understand except 'rf' in the middle.
So what I can do? I treated like a hard brick? I tried downloading the package-restrictions.xml file and change from disable to enable but that didn't work.
I was thinking than maybe installing the system from 0 could help but I suppose the zips from here don't work since it doesn't rewrite the data partition, and most probably the fail is there no?
EDIT: More information, seems the error is about an RF test https://forum.xda-developers.com/oneplus-x/help/stuck-rf-test-boot-t3610400
Click to expand...
Click to collapse
If post above does not work use the msmtool

I tried the method of miket674, first with "flash-all-partitions-fastboot" and then with "flash-all-partitions" without luck.
I'm trying with your method now, but the part of USB_BULK is not working, or nothing appears or a Oneplus without drivers recognized appear in device manager.
EDIT: I followed the guide, but it showed me an error of sahara communication failed, so I unplug, I tried to power on, but now it don't listen to the power on button.....
EDIT2: Seems now it can wake up or do anything at all, so the guide for fixing hard brick, let the phone worse than hard brick xD I contacted with oneplus support and they told me they need to perform an Inspection but maybe they fix the phone like it were in warranty.
EDIT3: After pressing power on + vol down like 10s or more it boot up to the error from before.
EDIT4: At the end I finished to do all the steps of MsmDownloadTool V4.0 but nothing, he finished, auto booted and the same chinese words with rf in the middle.
EDIT5: Weirdest thing happened, I went to sleep, and 3h later I tried to turn it on and the error was not there, and it welcome me with a clean OOS.... so not sure what fixed it, if the first method or the second, but seems fixed...
EDIT6: Aaaand the error came back when I rebooted because the step of "Adding finishing touches" never ended.

in TWRP
/data/system/users/0/ rename package restriction to .old
this resets your apps that have been disabled to enable incase you break something disabling apps in TIBU
---------- Post added at 02:49 PM ---------- Previous post was at 02:48 PM ----------
why dont you format /data in recovery?

After EDIT6 I tried to format /data from recovery but didn't work, also i think the first method already wipe all the partitions. And I can't access TWRP because now the recovery is the standard one
EDIT: Seems that if I wait more than 10 minutes with the phone turn off and then I boot it, then it goes to a clean OOS, although is the second time getting stuck in "Adding finishing touches", and this time instead of reboot it, I'm going to let it until it wants to end.
EDIT2: 30 minutes later the phone finished with the "Adding finishing touches", so now I'm updating to OOS 5.1.9 and I'll try to reboot it, but I think it will happen as before and it will show me the error, it may possible be happening this because of the 2 partitions? Maybe when I wait 10 minutes to start it boot the other partition which don't have the error.

YOU NEED TO DOWNLOAD MSM TOOL FOR ONEPLUS 6 GO TO QUALCOMM MOD BY PRESSING VOL DOWN + POWER BUTTON DOWNLOAD QUALCOMM TOOL ON
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892

set92 said:
I tried the method of miket674, first with "flash-all-partitions-fastboot" and then with "flash-all-partitions" without luck.
I'm trying with your method now, but the part of USB_BULK is not working, or nothing appears or a Oneplus without drivers recognized appear in device manager.
EDIT: I followed the guide, but it showed me an error of sahara communication failed, so I unplug, I tried to power on, but now it don't listen to the power on button.....
EDIT2: Seems now it can wake up or do anything at all, so the guide for fixing hard brick, let the phone worse than hard brick xD I contacted with oneplus support and they told me they need to perform an Inspection but maybe they fix the phone like it were in warranty.
EDIT3: After pressing power on + vol down like 10s or more it boot up to the error from before.
EDIT4: At the end I finished to do all the steps of MsmDownloadTool V4.0 but nothing, he finished, auto booted and the same chinese words with rf in the middle.
EDIT5: Weirdest thing happened, I went to sleep, and 3h later I tried to turn it on and the error was not there, and it welcome me with a clean OOS.... so not sure what fixed it, if the first method or the second, but seems fixed...
EDIT6: Aaaand the error came back when I rebooted because the step of "Adding finishing touches" never ended.
Click to expand...
Click to collapse
It is more than likely a hardware issues then if it came back for no reason at all, I would send to oneplus

Just try to lock the bootloader back which will make your device normal as it came from box then you can unlock it again

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.