Question about Hardbrick

Search This thread

Narakunizer

Member
Mar 21, 2023
12
0
Hello guys I was trying to install TWRP and custom rom on my samsung a10 (SM-A105FN) I sucessfully installed twrp using odin and resurrection remix (it was an offical rom for phone) but after a while I tried to install lineage rom (unoffical rom) Opened TWRP did as the following
  1. format data
  2. advanced wipe (ticked all mark)
  3. installed the lineage then gapps
  4. both of them did a wipe cache /daviak
  5. Rebooted to system
but the phone won't power on , can't access the twrp or bootloader , doesn't indicate me how much is charging , it only power on using power and vol down and then power off

so my questions
  1. Is that a hardbrick ?
  2. is there is way to fix that like vising some fixing center ?
  3. and that most important thing that I want to learn to not repeat that again is that was cuz the rom was unoffical or something I did wrong in twrp ?
 

Narakunizer

Member
Mar 21, 2023
12
0
To clarify only:

Hardbrick - as the term implies - has occurred when a part of phone's hardware no longer works, whereas Softbrick - as the term implies - has occurred when either phone's bootloader or Android OS ( both are software ) no longer are working for whatever reason.
sorry about my misunderstanding that right but what should I do to solve the softbrick I can't access to the recovery mode or the boodloader
 

jwoegerbauer

Senior Member
Dec 11, 2022
692
3
138
Freestate of Bavaria, Germany
A Stock ROM always is the best solution, IMO, because manufacturer have a R&D devision who know what is best ROM for the devices they sell: they after all want to survive in the competition

Personally never installed on the devices I have / had in use a Custom ROM nor a Custom Recovery.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    To clarify only:

    Hardbrick - as the term implies - has occurred when a part of phone's hardware no longer works, whereas Softbrick - as the term implies - has occurred when either phone's bootloader or Android OS ( both are software ) no longer are working for whatever reason.