Develop Bugs

Possibility of bricking & how to avoid it..

Is anyone manage to brick the phone already?
How likely/ or stupidity you need to actually bricking the phone?
What is a NO NO and how to avoid it?
That's the question.. thanks!

Main thing is read as much as you can before you do any changes, it helps to check what few sites say.
When I rooted my phone I could not get it to run the update part, tried time and time again, one site said "rename the file to update.zip and paste it" then I read on another site to just call it update as it is already a zip file.....and then it worked, small bit of detail like that stopped it working to start with so if I was you I check a few sites and get all the info you need, but also as many would say if you are that unsure dont take the risk and wait for samsung updates with Kies.

voodoochild2008 said:
if you are that unsure dont take the risk and wait for samsung updates with Kies.
Click to expand...
Click to collapse
Kies actually failed to update my phone, I have the Korean Galaxy S SHW-M100S, and it showed an update was available. So, I thought I was bricked for about 30 mins, kept trying to get it to work itself out of the problem in recovery mode, after about 4 tries (1 reboot of Windows, plus changing USB ports and 2nd try with this static new config) eventually it did, thank God.

Do not remove usb while in the middle of flashing with odin
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****

amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?

madjsp said:
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
Click to expand...
Click to collapse
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....

delete. ......

amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.

yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)

andrewluecke said:
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
Click to expand...
Click to collapse
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)

amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
Similar happened to me,although I didnt pull the battery, the phone just disconnected halfway through the flash.
Had half hour of panic,where I thought it was bricked.
Had to do a few battery pulls,restart PC a couple of times and mess around with different USB ports,but finally got it working.
Have flashed a 3 times since without a problem.

chluk2425 said:
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
Click to expand...
Click to collapse
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.

zenkinz said:
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
Click to expand...
Click to collapse
Are you sure that flashing (through ODIN) in any case never touch that "Download Mode" piece of code ? Even you select all the options in ODIN ?
Can anyone confirm this ? Actually I want to play with Kernel and RFS (have some ideas to try) but afraid of full bricking. So if this download mode is always present then I can play with it without any problem.
Waiting for response.

amerikian said:
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
Click to expand...
Click to collapse
Believe me! you can still access the download menu

The bootloader is almost always writeprotected and cannot be overwritten. You would probably have to connect a cable to some internal port like Jtag to be able to reflash the bootloader section. Atleast that is the case in 99% of all bootloaders. Im very certain that you cannot cripple the bootloader.
Sent from my GT-I9000 using XDA App

jackiechan8 said:
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
Click to expand...
Click to collapse
gosh man, thanks correcting me but if that's the case, what should i do if it doesn't reboot by itself?

take out the battery, wait for 30 to 60 secs, put the battery in and start phone with vol down + menu + power

Don't disconnect the usb or do anything else while flashing!!!
I removed the usb cable when it started flashing (i thinked it was stuck, happens sometimes), and since it does not boot anymore. I press the power button, volUp + home + power, volDown + home + power... nothing happens.... it's dead, doesn't turn on at all...

after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home

jodue said:
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
Click to expand...
Click to collapse
well, mine doesn't boot at all, and i flashed (technically not, because i removed the usb cable at the very start) with the RIGHT odin version
Maybe if it fails when flashig sbl (secondary boot loader ) you can't go into download/recovery mode...

[HELP] Stuck in qualcomm diagnostic mode

So while trying to get wifi working on my CM7 install I tried to install the radio update from http://forum.xda-developers.com/showthread.php?t=1363547
It was successful but when I reboot I get stuck in what people call "Qualcomm Diagnostics Mode." I'm not even sure of that though, when I turn it on it vibrates 3 times, no LED or anything. I've tried the following solution:
http://forum.xda-developers.com/showthread.php?t=1345273
but it doesn't work.
I have my microsd, I tried putting my old ROM on there but that didn't do anything. I don't have access to the internal storage as I can't turn on the phone. ._.
And for me turning the phone on while holding vol - NEVER worked to go into the bootloader, I'd have to reboot from the OS into the bootloader. I have a backup of all my files.
Is there any way I can recover it?
Unfortunetly rooting it voided my warranty, though I'm sure they wouldn't even know about it if I sent it to HTC?
I'm running it on virgin mobile unactivated...
EDIT: I bought the phone from ebay.

Try the 5th post (i think) it should say something about this mess you're in and click thanks if I was able to help
http://forum.xda-developers.com/showthread.php?t=1432425
Sent from my HTC_A510c using Tapatalk

Alright I'll try that but what sucks is I tried something like that but when I hold volume down and power it would never go into the bootloader, I had to do adb reboot bootloader. (but obviously I can't do that when I can't connect to the device, maybe with the mem card?)

Kingherring said:
Alright I'll try that but what sucks is I tried something like that but when I hold volume down and power it would never go into the bootloader, I had to do adb reboot bootloader. (but obviously I can't do that when I can't connect to the device, maybe with the mem card?)
Click to expand...
Click to collapse
did you follow all the steps as described, putting out your memory card, formating, putting the file on it then continuing to follow steps, and patiently waiting ?

Yes I did all of those steps. My friend advised me to just sent it back to HTC.
(But they say that they can detect if it is rooted)

Kingherring said:
Yes I did all of those steps. My friend advised me to just sent it back to HTC.
(But they say that they can detect if it is rooted)
Click to expand...
Click to collapse
well, if you gave that a shot... i read somewhere that there is a way to go out of qualcomm diag mode, i can't find it... you just send it back to your service provider, and act dumb... hopefully they will have too much job and won't bother checking too much your phone...

[Q] htc wildfire s boot loop problem

So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:

a bit more info plz
alemale said:
So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
Click to expand...
Click to collapse
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue

rishr4 said:
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
Click to expand...
Click to collapse
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.

alemale said:
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
Click to expand...
Click to collapse
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
2. There is a possibility that you could "brick" or bootloop your phone. There are two types of brick: soft (recoverable) and hard (non-recoverable). With a soft brick, the phone will not boot or keeps rebooting ("bootloop"), but it can be started in bootloader mode which allows repair of the ROM. With a hard brick, the phone won't even boot into bootloader after holding the power button for 10 seconds and the phone must be returned to HTC for service.
Click to expand...
Click to collapse
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the
PROCEDURE 1
Click to expand...
Click to collapse
then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.

rishr4 said:
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
Click to expand...
Click to collapse
I tried to unlock the bootloader but it wanted 2.3.5 so i tried to install the new version. now it can't do anything. Well this didn't broke my heart because the phone is pretty worthless . now i have to buy new phone sooner than i planned but still all help is still accepted.

Hi, exactly the same for me : I bought the phone 2 years ago and immediately unbranded it with a goldcard, but never tried to unlock it because it was my wife's and I didn't want to risk anything.
Now she got a new phone, I wanted to play a little with the Wildfire S ^^.
In order to unlock the phone on htcdev I had to update it from 2.13.401.2 to 2.13.401.3, with RUU because can't update with OTA (different CID), with goldcard inside.
After the RUU finished, it says "congratulations everything went well", but actually the phone does not boot, stocked in a loop "quick flash / turns off", can't access bootloader, no USB detection for ADB.
Can't send it to HTC because the 2 years warranty is expired, how ironic ! :laugh:
So... if anyone does know or see any trick that could help to boot anything on this "seems to be hard-bricked" kid... huge thanks to you

My HTC M8 Stuck at ONE Logo once restarted. No Recovery, No DWNLD mode available.

I've seen already this thread suggested by XDA thread locator.
https://forum.xda-developers.com/htc-one-m8/help/verizon-htc-one-m8-stuck-htc-logo-t3163088
But I'd try to explain as simple as possible the whole situation which happened hours ago.
Don't know what happened but my mothers phone went off and restarted with htc one logo on it and nothing else later.
Power button itself doesnt work and is not responding.
Configuration PWR + VOL UP gives me restart but no recovery mode, giving me sound effect of restarting phone and ONE logo on it without any other reaction whatsoever.
PWR + VOL DWN zero reaction
PWR + VOL UP & DOWN pressed together restarting the phone and then gives me HTC ONE LOGO and nothing else.
when Phone is plugged in to the computer and I'm forcing the phone to restart it shows me new Device on the computer as a CD Driver every time.
So I think there is still hope to get this guy back to life.
It's running on custom rom but unknown version because it was purchased as a refurb from ebay 2 years ago and it was running just fine utill this very day.
I'm absolutely noob with flashing twrping etc so please ELI5 if possible, any type of help will be much appreciated.
Thanks in advance.

Hey, I had this same problem a couple of days ago. Here's what I did to get the phone into fastboot, from where you can install a recovery, factory reset etc.
1. Hold the power button + vol up button for about 10-20 seconds. This should shut down the phone.
2. Hold the power button + vol down button to restart the phone back into fastboot.
If you can get into fastboot, there are plenty of guides which can help you flash a twrp image. If you want me to give you some instructions on that just reply and let me know. Good luck!

Note that this phone doesn't have download mode (as some other Android devices do); nor is there a button combo to go directly to recovery. But you can almost certainly still get to bootloader, and from there boot recovery. In the current condition, you can get to bootloader by:
1) Hold Power+ vol up (as you have been) to restart the phone.
2) Once the screen goes dark (signaling it is about to reboot) let go of the buttons, and only hold vol down
3) Don't let go of vol down until the bootloader screen appears.
4) If the above sequence fails, its virtually always because the user just didn't get the timing right (either started pressing vol down too late, or let go too early). Just repeat steps 1-3 until you get to bootloader.
Once in bootloader, try to reflash the ROM, or restore a TWRP backup (if you have one). Spontaneously stuck on HTC logo screen is often a result of the OS/ROM becoming corrupt or otherwise damaged, and flashing/restoring the ROM will often fix it.

Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
It's my mom's phone so basically reliabilty and robustness over flashing lights and numerous unnecessary functions.
Version of android doesn't really matter.
Thanks again for help so far.
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
TWRP might be extra helpful or the recovery it's functions are just fine?

Shewie said:
Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
Click to expand...
Click to collapse
I'd need to know more about the phone in order to give any suggestions.
With the phone connected to computer, boot into fastboot mode, and (assuming you have fastboot setup on your computer) do the command: fastboot getvar all
Then post the results (delete IMEI and serial number before posting).
Also, what version TWRP (if that is the recovery installed)?
Shewie said:
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
Click to expand...
Click to collapse
You will be able to flash a ROM from the SD card, if using TWRP.
Shewie said:
TWRP might be extra helpful or the recovery it's functions are just fine?
Click to expand...
Click to collapse
Not sure what is being asked here (can't quite understand). Are you saying that another recovery besides TWRP is presently installed?

@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
I wouldn't mind link to the pack with "must have" to complete the process

Shewie said:
@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
Click to expand...
Click to collapse
You have what is called the "stock recovery" or official HTC recovery.
You can't flash anything but OTA updates, or other official (HTC) signed zips with this. You need a "custom" recovery like TWRP in order to flash things like custom ROMs. So I'm curious what you meant before when you posted:
Shewie said:
Thanks [MENTION=660462]Sadly reflashing/factory reset failed few times due corrupted files.
Click to expand...
Click to collapse
What exactly were you trying to "reflash", what were the exact steps, and the results (specific error messages, etc.).

I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.

Shewie said:
I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.
Click to expand...
Click to collapse
Okay, so you're confusing the terms. Factory reset doesn't flash/reflash anything (flash meaning to install some firmware or software to the device). The only thing that factory reset does is wipe user data.
At this point, I'd suggest the best/easiest course of action in the current conditions (stock recovery, locked bootloader) would be to run the RUU intended for your device. Your device is the AT&T version, so the RUU can be found at the bottom of the page (and instructions on how to install): http://www.htc.com/us/support/htc-one-m8-att/news/
RUU is a complete factory image. You download to a PC (PC required, won't work on Mac or Linux) connect the phone (booted into bootloader-fastboot mode) then just run the RUU, and it will do the rest.
I'm confidant this will get the phone up and running. Your mom may not like all the AT&T branding and apps, if it wasn't there before, and AT&T is not her carrier (one of the main reasons for these devices to have custom ROM - to remove carrier branding). But we can cross that bridge (if need be), after we get the phone working.

Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?

Shewie said:
Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?
Click to expand...
Click to collapse
It just gets stuck sometimes. Just kill the process, and start the RUU again. It will probably work fine on the next try. It's a bit scary, as it says not to stop the process or disconnect the phone while it's running. But if it gets stuck like this, there isn't anything else you can do.

Good News, it's working. But it's bloated to the bones. How I can get rid of the carrier unnecessary software?
I was to afraid to kill the process during update to avoid scenario of bricking my phone completely.
But It's working!

Question A52s random “Can’t load Android system.” when rebooting

Hi all,
I am encountering this strange bug randomly: sometimes the device Is rebooting itself and it goes automatically in recovery mode, sometimes after a reboot it does the same. The error is always: Can’t load Android system. clicking on “try again” solves the issue (sometimes at the first retry, sometimes after some retries).
I’m attaching the error screens, also because the error message is not every time the same (Attaching also a normal way to enter recovery).
Has someone encounter this bug?
Any hints on how to solve this? I haven’t already do a full reset of the phone, but i think it wilL be the next step I’ll do if the phone is continuing like this.
Thanks!

Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.

Arobase40 said:
This mostly happens when you did some tricky things on your phone. lol
If full reset is not enough (specially when the system is missing....) you'd have to restock it with an official Samsung firmware... ^^
Click to expand...
Click to collapse
Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.

Arobase40 said:
Well ok, in your case try to flash back a stock firmware from Samsung with Frija or Samfw (don't forget to supply the correct model and CSC) using PC Odin.
If that don't fix the problem then get in touch with your local Samsung website and you should find a phone number for the after sale service and they will give you the nearest Samsung official repair center from your home.
They should fix this issue very quickly using most probably the same tool which is PC Odin.
If you go to the repair center don't forget to backup all your apps and data, remove your scard if you have one and also your sim card...
Click to expand...
Click to collapse
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)

IvanCattaneo95 said:
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)
Click to expand...
Click to collapse
Idk, seems like a hardware issue to me. Try and have a go at where you've bought it and have them check it over.

My first thought too is hardware.
A few years ago I had something similar with a different phone (Moto G) - as a last ditch effort I popped out the SIM and SD cards and reseated them and it worked perfectly after that. If you have an SD card you might even want to leave it out a few days just to see.
Not saying this is your issue but couldn't hurt to try!