Hello everyone!
I saw that there's always some confusion about these terminologies. I wasn't able to find thread on XDA regarding to it so I decided to write about this.
This thread won't help you to recover from Hard Brick and Soft Brick situation!
●Why word 'Brick' in Android terminology was used?
When Android phone isn't operation in anyway, there was a need to name that terminology. Since Android phones are usually in shape of a brick, and since now it isn't fixable in any way, it is as good as a brick. So in that condition, it is called a "Bricked Device".
●Then why there's variations Soft Brick and Hard Brick?
Some people, without understanding history of the word brick in Android terminology, started using it when phones gets into bootloop or boots but ends up at fastboot or recovery. In these kind of situations, phone is fixable. They started opening thread naming "My phone is bricked, help please!" After some people ask in detail it comes to know that phone is suffering from bootloop problem. For them, brick situation was divided into soft brick and hard brick.
So basically Soft Brick is nothing but the problem of bootloop or all type of fixable problems that don't let you boot in to your Android OS.
●Which is common? Hard brick or soft brick?
Hard brick is very very very rare. That shows that soft brick is common. But saying phone is bricked without using word 'Soft' is totally wrong and nooby side. People need to understand why 'Brick' terminology was kept. If your phone is bricked, it is as good as a brick. So even though if chance of hard brick get less than 0.00001% it is totally WRONG to speak word brick for a soft brick.
Source: I wrote it on my own
You CAN copy this and share it WITHOUT giving me credit. It's okay for me. BUT copying this and pasting on your website to EARN MONEY is completly UNFORGIVABLE!
I hope you understand: )
Similar thread by me: https://forum.xda-developers.com/android/general/difference-noobie-newbie-t3598352
Related
A weird thing happened, my Galaxy Ace got Hard-Bricked after flashing a rom (i was too lazy to read instructions, as flashing roms is what i do 5 times a day!), and it couldn't go into backup/recovery/download mode. It just happened once, my PC recognized it and Odin detected it, but odin froze, so i unplugged it and repluged it, and that's when it never went in recovery mode again...
I need urgent help asap, as my warranty is already voided.
Cheers,
John Freeman
Well look here for help if it is a soft-brick:
http://forum.xda-developers.com/showthread.php?t=1071970
If it is a hard brick then you need to use a JTAG service:
http://forum.xda-developers.com/showthread.php?t=1429491
Good luck.
if it is still under warranty take it to the service center and tell the you are doing an OTA and your connection was distrupted. thats what I told at the service center
It should nearly always be possible to enter the bootloader of the device. So if it comes hard you can use "power button, vol down" to enter it and flash a system image directly with the fastboot tool.
Thanks a Bunch!
Thanks a bunch, guys! I sent it to a friend (she knows more about JTAG services than i do) who helped me out.
I followed instructions this time...
Thanks a lot,
John Freeman
Hello,
thank you for taking the time to read and try to help.
I got an Asus Padfone X from At&t and the refused to unlock it
Asus didnt help either.
not to bore you with details
but here is my noobish mistake tool form, i flashed the asus kernel .zip file to the bootloader using twrp.
now phone wont boot into recovery or bootloader
got the minimal tool which as you know include fastboot and ADB
but it wont detect the device ( it detected it before when i rooted the phone )
I made a backup before i flashed , but the problem i cant flash it to a device that wont go to bootloader or recovery
and wont be detected by ADB.
please guide this lost noob.
Hello Ultimician,
If your device cannot boot into recovery or bootloader it's a hardbrick. Flashing the wrong kernel will cause your device to hardbrick.
You probably still have a warranty, I'd go to your service provider and play dumb: "One day my phone just didn't turn on, I've tried everything even charging it."
If you know of someone that could JTAG your device you could go to them that might work, what the manufacture usually do is they replace the whole motherboard. ( What Samsung did when I bricked my device in any case.. )
Otherwise you could refer to these threads, be careful though they are not necessarily for your device. ( But they might be of help )
[GUIDE] Z Ultra and Z1 HARD BRICK RECOVERY
[Galaxy S III][IMPORTANT] GT-I9300 Hard Brick Fix
[GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG)
Best of luck mate!
thanksfor the swift assistance
thank you kindly
amazon offered me a refund
i will take my chances
Carefully when they send a device back to the maker they can often pull information.like last install and all of that. If you had a back up. I would try to flash the stock firmware. They are ways to do this with jig and other tools. I would try to flash stock every way I could before I take it back. I had s3 and bricked it long time ago.after many hours of reading I fixed it. Please always when flashing make sure it's for your device. Wish you luck2
Hey guys, I've accidentally hard bricked this tablet (SGH-i497) by flashing the wrong recovery image. No download mode or recovery, black screen only. Computer only sees it as qhsusb_dload.
What I'm wondering (obviously short of a JTAG repair) is if anyone could potentially make a working backup of their model using QPST as a last ditch effort? I want to see if this can restore it, and I know it's a long shot.
I just wanna know... Does anyone have a definitive answer? Is this fixable? Or am I wasting my time?
If more details are necessary please let me know and I'll get everything I know ASAP.
Long story short, got distracted while unlocking after a successful 6.0 upgrade and I'm not sure what happened. I decided panic was my best course of action and tried to install the original 5.1.1. That's when I got in the qsb qloader 9008 (not exact but something like that) mode where it doesn't turn on, no recovery, no download mode, doesn't show up as a drive on my pic and won't even charge a battery. To me, it appears as though it's completely wiped clean. Dead (but honestly IDK).
I've read and read and read for weeks. About using a small pin to short (force) it into download mode, about something called boarddiag, and a lotta code about partitions I do not quite yet understand.
I thought I read that these were unbrickable but I see there's a lot of people with this problem but only fague and incomplete answers scattered on almost every forum I've read.
I'm not a noob, but this is noob to me. Please help and share your experiences.
Hello,
Hello, you can try this way.
https://forum.xda-developers.com/tmobile-g4/general/lg-g4-h811-complete-unbrick-guide-100-t3461629
I have same problem on LG G4 Stylo MS631, I try with SD card (64GB) which wrote system.img.
My computer recognize phone LGE Android port (COM 41).
Then I try with LGUP, but LGUP unknown it.
Anyone can help me !
Thanks a lot
I've heard something about a "boardiag" but still researching.
I have no idea what happened beside the battery completely drained and I was left hard bricked. I only have the blinking led. No mode beside EDL. Was rooted, stock rom android 11 and stock recovery. Phone had been stolen and possibly had someone trying to get in it. Appeared fine and in working order before it died though.
I have tried 3 different version blankflash files. I have been using sofiap. A few times (tried about 50x) they went all the way through to "fastboot reboot", but fastboot NEVER opens. Just same situation as before. May be an issue with singleimage.bin? Since blankflash doesn't seem to be effective, can I use another program (Qualcomm programs, Flash tools or other)? I have tried finding a solution, searched endlessly and have the same brick I had.
Please advise and help with the exact files, links, etc. The easiest way would be awesome. I would greatly appreciate any/all assistance.
Jaymi
jayleemcnabb81 said:
I have no idea what happened beside the battery completely drained and I was left hard bricked. I only have the blinking led. No mode beside EDL. Was rooted, stock rom android 11 and stock recovery. Phone had been stolen and possibly had someone trying to get in it. Appeared fine and in working order before it died though.
I have tried 3 different version blankflash files. I have been using sofiap. A few times (tried about 50x) they went all the way through to "fastboot reboot", but fastboot NEVER opens. Just same situation as before. May be an issue with singleimage.bin? Since blankflash doesn't seem to be effective, can I use another program (Qualcomm programs, Flash tools or other)? I have tried finding a solution, searched endlessly and have the same brick I had.
Please advise and help with the exact files, links, etc. The easiest way would be awesome. I would greatly appreciate any/all assistance.
Jaymi
Click to expand...
Click to collapse
Hard bricked mine too.
Metro G Stylus 2021.
acrinym said:
Hard bricked mine too.
Metro G Stylus 2021.
Click to expand...
Click to collapse
I Switched to Slot B and now it doesn't do anything except go into EDL.
Hey @sd_shadow, any idea what we could do to fix this mess? This is a phone I'm supposed to return.
I'm still stuck with a brick. Have been for months. Took it apart (why not it doesn't work anyway) and tried the points thing to put it in edl and still nothing. WE NEED ADVICE PRETTY PLEASE.
Thanks in advance,
Jaymi
acrinym said:
Hey @sd_shadow, any idea what we could do to fix this mess? This is a phone I'm supposed to return.
Click to expand...
Click to collapse
If it's a warranty return it shouldn't matter