noun/verb. Describes when a phone or other device has been made totally useless, in a form that is unrecoverable through normal methods.
(This excludes methods that would require specialized hardware or technology from the original device manufacturers.)
Examples:
"Man, my phone is bricked and now I have to get a new one."
"Did you ask the people at XDA-Developers for help?"
"Yeah, man. They tried but I think my phone is perma-bricked."
"If you don't follow the directions in this step VERY carefully, you could end up with a permabrick."
"My new Samsung Galaxy S2 is a permabrick now, but it works great as a cupholder."
I perma-bricked my head when I was upgrading it's kernel.
... ... ...
bconover93 said:
I don't see how a SGS2 can be used as a cupholder. Maybe a coaster.
Click to expand...
Click to collapse
Just think about it, you'll figure it out eventually
Sent from my MB860 using xda premium
ehh..
no.
If you brick. It's unrecoverable. That IS the meaning of a brick.
When a phone has the same use as a brick. It's bricked.
What bricked is used for today is what is a bootloop. Or a recoverable "soft-brick".
Perma-Bricked and Bricked = The same.
TheDeadCpu said:
ehh..
no.
If you brick. It's unrecoverable. That IS the meaning of a brick.
When a phone has the same use as a brick. It's bricked.
What bricked is used for today is what is a bootloop. Or a recoverable "soft-brick".
Perma-Bricked and Bricked = The same.
Click to expand...
Click to collapse
I wouldn't consider bootlooping a soft brick. Just an inconvinience. It was a problem for me when I had a boot loop Nd no volume keys to get to recovery
Sent from my MB860 using xda premium
ExKuze me...
Can we reflash a perma bricked phone with Box?
can guarranties fix that?
TheDeadCpu said:
ehh..
no.
If you brick. It's unrecoverable. That IS the meaning of a brick.
When a phone has the same use as a brick. It's bricked.
What bricked is used for today is what is a bootloop. Or a recoverable "soft-brick".
Perma-Bricked and Bricked = The same.
Click to expand...
Click to collapse
But right now brick become generalized word..so its consist of permabrick and softbrick
Sent from my SPH-D710 using xda premium
Soft-bricked means you can reflash system and use without problem
So we can use Hard-brick as in X10 thread ( rarely cause just some guys broke the phone with wrong firmware lol) means your phone now has new ability to keep paper or use to threw at a wild dog....
I guess I'll leave my sig to talk for me...
Sent from my HTC Sensation
You are always a great help sir dexter for your unbricking project
a lot of people are having headaches with their phones turning into cupholders
Wow, I enjoy the buzz this generated
Yes, "brick" means "brick unrecoverably" but I figured we should be defining it in a more accurate fashion, based on how people use the word on this site. "I've bricked my phone; help!" means "I think I have bricked my phone, help!"
So yeah, while the official word for "brick" means "turn into something unusuable for a phone" most people use it as a synonym for "broke" instead. But "bricked" sounds more kitschy.
good info!!
Related
Hey guys I have a question. I was trying to create more space on my HD2 a few months ago and my phone went dead. The light doesn't come on to show it's charging and it doesn't show any signs of turning on. I just left the phone but now I think I want to have the phone back on. Is there any way to unbrick the phone to get it back at least working. I was trying to put a new radio on it but I put the wrong version and it complete killed the phone. Any help or suggestions to getting this problem fix.
Thanks
kasualnupe2 said:
Hey guys I have a question. I was trying to create more space on my HD2 a few months ago and my phone went dead. The light doesn't come on to show it's charging and it doesn't show any signs of turning on. I just left the phone but now I think I want to have the phone back on. Is there any way to unbrick the phone to get it back at least working. I was trying to put a new radio on it but I put the wrong version and it complete killed the phone. Any help or suggestions to getting this problem fix.
Thanks
Click to expand...
Click to collapse
1) where did you get the idea that flashing a radio created more space?
2) If you flashed an incompatible radio then there is no unbricking except jtag
Orangekid is right the only fix it to have it JTAGed. Contact me via PM and I can reffer you to someone that offers this servos if you want it unbricked.
Edit: Sorry I had not checked my inbox yet and read your message.
orangekid said:
1) where did you get the idea that flashing a radio created more space?
2) If you flashed an incompatible radio then there is no unbricking except jtag
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=668347
some have unbricked it using that method
no jtag necessary. if not jtag is your option
domineus said:
http://forum.xda-developers.com/showthread.php?t=668347
some have unbricked it using that method
no jtag necessary. if not jtag is your option
Click to expand...
Click to collapse
that relies on being able to get into bootlaoder.
domineus said:
http://forum.xda-developers.com/showthread.php?t=668347
some have unbricked it using that method
no jtag necessary. if not jtag is your option
Click to expand...
Click to collapse
The title of that thread needs to be changed. A truly bricked HD2 will not even turn on which means you can not get to the bootloader. A truly bricked HD2 is bricked because the SPL of bootloader has gotten screwed up and it cannot boot any of the software. Hence the phone can not turn on, hence the term "brick" because it is a useless brick. If someone has a phone that that they can still get to bootloader with it is not bricked. A phone like that is just havering software or user difficulties and can in most cases be fixed, unless it is a hardware problem. Even then it can be fixed just not by flashing different software.
domineus said:
http://forum.xda-developers.com/showthread.php?t=668347
some have unbricked it using that method
no jtag necessary. if not jtag is your option
Click to expand...
Click to collapse
Dude, If you can get into the bootloader its not "bricked" obviously.
When you flash a EU radio to a US HD2 you do a "real" brick not just a n00by flashing problem.
orangekid said:
1) where did you get the idea that flashing a radio created more space?
Click to expand...
Click to collapse
Most likely got mixed up between RAM and ROM and thought that it would enable more storage instead of ram.
Either way he deserves the brick for not reading/researching properly before messing about with his device.
you do realize that thread was made for exactly what everyone is referring to right?
when someone flashes a eu radio/rom on their device right and renders it useless...its an old thread but some users have reported success.
however if it is a bl issue it won't work
I should've said that
domineus said:
you do realize that thread was made for exactly what everyone is referring to right?
when someone flashes a eu radio/rom on their device right and renders it useless...its an old thread but some users have reported success.
however if it is a bl issue it won't work
I should've said that
Click to expand...
Click to collapse
I think we do realize that thread was started to try to help people. But that does not change the fact that if you flash a x.xx.51.xx radio (which are EU radios) or a 2.04.50.xx or a 2.05.50.xx radio (which are test radios) to a TMOUS HD2 it will, not maybe, but will brick a HD2. This is a Bootloader issue when you do this. So again that threads title needs to be changed and it is useless to the OP.
As T-Mac said, this is a physical brick. That phone is not going to power on again until it get's JTAG resurrected.
Hi everybody, this what happened:
I tried to flash my atrix with Atrix 1.26 Retail SBF through RSDLite.
After that it shut down and when i try to turn it on it says :"Failed to boot 0X1000" then it shuts down again. It doesn't even give me any option.
For the record, my phone was up to date (i got that wifi only system update by att). Also, this phone is unlocked and I have no warranty with any carrier.
I hope I didn't brick it.
Please give me simple solutions if there is any. Your help will b very much appreciated.
Thank you so much.
i'll let others break down the news to you..
Sorry bud, but I believe you now have a nice set of glass upon to look at.
Sent from my MB860 using XDA
Can't believe people are still doing this with all the warnings in the forums.
You tried to SBF back to 4.1.26 (Froyo) on a bootloader unlocked phone. You now have a very expensive reflective beer coaster!
I think Nottach recover "failed to boot 0x1000"
also take look here
http://forum.xda-developers.com/showthread.php?t=1165154
klobass said:
I think Nottach recover "failed to boot 0x1000"
also take look here
http://forum.xda-developers.com/showthread.php?t=1165154
Click to expand...
Click to collapse
Sorry man, like the others said, it's bricked...
I have tried this before on 3 different bricked phones and it didn't work... I wish it did though...
klobass said:
I think Nottach recover "failed to boot 0x1000"
also take look here
http://forum.xda-developers.com/showthread.php?t=1165154
Click to expand...
Click to collapse
This error also comes up with soft bricks which you can fix as you gave options to choose from and can recover. This guy has no options.
Sent from my MB860 using xda premium
Alaq said:
Sorry man, like the others said, it's bricked...
I have tried this before on 3 different bricked phones and it didn't work... I wish it did though...
Click to expand...
Click to collapse
Mashina khaye, there must b smthn to do about it!
Aerie fel website hayda! Everybody's being so negative!
Come on guys. I really need help.
For those who think i was doing it 4 fun, i need it for work and i just wanted to fix it asap that's why i screwed up.
7oucem said:
Come on guys. I really need help.
For those who think i was doing it 4 fun, i need it for work and i just wanted to fix it asap that's why i screwed up.
Click to expand...
Click to collapse
People are being helpful...by telling you sorry. If you need it for work, you'll probably just need to go buy a new phone ASAP. Like others have said, there are plenty of warnings and instructions on what/what not to do on your phone. Unfortunately, you missed those. Hope you can find another phone for cheap...
You have a hard brick, never try to downgrade. Nottach was able to fix his because he got a brick by upgrading, and he was lucky enough to figure it out. Downgrading on the other hand ruins your device, every time
Sent from my MB860 using xda premium
7oucem said:
Come on guys. I really need help.
For those who think i was doing it 4 fun, i need it for work and i just wanted to fix it asap that's why i screwed up.
Click to expand...
Click to collapse
We are helping you, by telling you that there's nothing that you can do. Your phone is hard bricked. There is absolutely no way to recover from a hard brick, period. You need to replace the phone. That is the reality, and there is no getting around it.
I was running CM9 on my Atrix when my digitizer went bad and I got a dead spot. I submitted it for warranty and before I sent it I tried to put it back to normal. I did something wrong I guess and ended up with a different boot error (didn't even give me an error code the screen was black unless I plugged it in I just got the NV flash thing). Anyways, I sent it in and the same phone came back completely working with a fixed screen. I think when they get it they hook it up with a factory cable and flash it back to stock with the SBK, which we don't even have access too. Just send it in for warranty saying it has software problems, and I can almost guarantee you it will come back working.
BravoMotorola said:
Just send it in for warranty saying it has software problems, and I can almost guarantee you it will come back working.
Click to expand...
Click to collapse
He has no warranty.
CaelanT said:
He has no warranty.
Click to expand...
Click to collapse
Possible he does with motorola. OP there is a tool on motorola website to see if its under warranty. Maybe give that a shot.
Bro do some reseatch that error message is a soft brick I believe I ran into a similar issue when I first roote it last year
Just thought I would weigh in that I received this same error code after an attempted SBF flash of zomgunlock-lite.sbf, and thought all hope was lost, but then I found this post: http://forum.xda-developers.com/showpost.php?p=27158667&postcount=153
The instructions there helped me un-brick my phone, and I'm a happy camper once again
What happen if we frequently flash our SGY?does it brick the fon permanently afterwards?
blackpanther2209 said:
What happen if we frequently flash our SGY?does it brick the fon permanently afterwards?
Click to expand...
Click to collapse
i don't remember how much time i hv flashed my phone.......i don't think bro it bricks the phone permanentaly.....
anmolsharma1293 said:
i don't remember how much time i hv flashed my phone.......i don't think bro it bricks the phone permanentaly.....
Click to expand...
Click to collapse
i agree with u but i read something from other site that maybe it will brick the board...
blackpanther2209 said:
i agree with u but i read something from other site that maybe it will brick the board...
Click to expand...
Click to collapse
lets hope it does'nt gets dead due to frequent flashing.....or else we will be no longer able to play with our little device...
No. You flash however more times you want, it won't get permanently bricked. Just don't flash a new rom every five minutes for 2-3 hours continuously!
Sent from my GT-S5360 using xda premium
Hi Guys,
I havent used this site in years but recently I bought a Galaxy S4 outright from JBHIFI.
Before you guys give me alot of crap, I have a very bad feeling that I may have hard bricked it.
It doesnt turn on anymore, not even in recovery or download mode. I am very new to android as I was using an iPhone before and couldn't resist attempting to root my phone (stock program were killing my battery)
I hadn't even had the chance to flash a custom rom on there as far as i know i just grated root access.
Funny thing is it was doing the same thing the other day. But randomly it decided to charge and turn on. Now it is definitely not charging or turning on and i have no idea what to do... it just sucks cause i havent ever this phone for a month and its already useless! :crying:
I was using it for about a week after i rooted and now im just stuck with a brick.
Any help would greatly be appreciated, feel free to ask any questions.
Send back t store and thel t workers that just whont turn on.Dhont thel that is rooted or somthing
Sent from my GT-I9505 using xda premium
yeah thats what im planning to do its about exactly a month since i had it today... i just didnt want to mention anything cause i know you guys and moderaters dont condone that kind of behaviour! thanks though, im pretty much screwed arent i? ill be heading into jbhifi on my lunch break will go ahead with that plan haha.
ill tell you guys how it goes.
Have you tried a battery pull?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
sorry... is that just taking the battery out? LOL if so, yes ive tried it quite a few times.
at one stage it was turning on but only loading the splash screen... so i pulled the battery out. even if i tried to start it in recovery mode, it would only load the blue text at the top of the screen and then freeze.
i have a mate who also got an s4 so i was going to meet up with them and see if i could use their battery because it seems the phone has even lost its capability to charge.
Dead boot http://forum.legija.net/showthread....g-galaxy-S4-(i9505-and-similar)-via-USB-Cable
Sent from my GT-S5360 using xda app-developers app
that seems very useful, but to use it i would have to be in download mode atleast right? problem is i cant even turn on phone to get into download mode
didnt go jbhifi today had to fix my rims instead LOL, trying other solutions and finding a spare battery to see if its just that... maybe then it will beable to atleast boot in download mode
raintouchpad said:
that seems very useful, but to use it i would have to be in download mode atleast right? problem is i cant even turn on phone to get into download mode
didnt go jbhifi today had to fix my rims instead LOL, trying other solutions and finding a spare battery to see if its just that... maybe then it will beable to atleast boot in download mode
Click to expand...
Click to collapse
No, you don't have to be in download mode. Install right driver, connect your phone to pc and run the program. Then it will be in download mode, so flash firmware with pit file
Sent from my Galaxy Nexus using xda premium
well so far... i tried this at work and no luck, so i went home and tried it there... still no luck.
you mentioned i need to install the right driver? is that the QHSUSB drivers? (where can i find them and are they specific for the S4) anyway when i plug my phone into the computer there is no indication that it is being detected at all.
just hoping to try out more suggested solutions before i attempt to take it back into the store and have em tell me that my warranty is cooked
Hi just an update.
Took my phone to samsung because it was just completely screwed. They replaced the motherboard and camera but didnt find out that my phone was rooted which was good.
Thanks for your help everyone
*edit*
After they said they replaced my camera i am now getting the "camera app failed" message, wheres theres a black screen and the app doesnt work... ive had it with this phone now... going to walk into samsung and lose my ****.
raintouchpad said:
After they said they replaced my camera i am now getting the "camera app failed" message, wheres theres a black screen and the app doesnt work... ive had it with this phone now... going to walk into samsung and lose my ****.
Click to expand...
Click to collapse
Don't bash the phone for nothing ...
Somehow I doubt that they didn't test the camera after replacing it.
Next time, take it easy, and what ever you do, read carefully the instructions.
same issue
My galaxy S4 is "hard bricked" as well after trying to flash OMEGA ROM onto the device. My guess is that somebody mislabeled the ROM and it was intended for the octal-core processors and not the US quad-core ones.
Does anyone have a link for the qualcomm drivers that are needed? I'm at a loss currently in regards of which direction to take.
Thanks in advance,
Fickl3
fickl3 said:
My galaxy S4 is "hard bricked" as well after trying to flash OMEGA ROM onto the device. My guess is that somebody mislabeled the ROM and it was intended for the octal-core processors and not the US quad-core ones.
Does anyone have a link for the qualcomm drivers that are needed? I'm at a loss currently in regards of which direction to take.
Thanks in advance,
Fickl3
Click to expand...
Click to collapse
see my sig for dead boot and Qualcomm driver
samersh72 said:
see my sig for dead boot and Qualcomm driver
Click to expand...
Click to collapse
Does this process work for hard bricked phones as well?
fickl3 said:
Does this process work for hard bricked phones as well?
Click to expand...
Click to collapse
it should :good:
---Repair dead boot I9505 via usb cable--- Thanks to legija from JTAG team.
QHUSB Qualcomm driver download
Click to expand...
Click to collapse
I also hard bricked my S4 but with the utility Im able to get in Download mode, flash .pit and stock Samsung firmware but after flashing is succesfully done it goes into qhusb again and It again is dead.
how to install the driver?
samersh72 said:
it should :good:
Click to expand...
Click to collapse
How exactly do we install the driver? The download is a zipped file and I don't know how to install the extracted contents.
rsndetre said:
Don't bash the phone for nothing ...
Somehow I doubt that they didn't test the camera after replacing it.
Next time, take it easy, and what ever you do, read carefully the instructions.
Click to expand...
Click to collapse
i know... its just frustrating... i pretty much got it when it came out and convinced all my mates that it was the best phone out there at the moment (all the features are pretty nifty and its powerful ill admit)
funny thing was the camera was working perfectly before i took it in and didnt even think it needed replacing. the camera worked when i got it back the first time i opened the app but it had smearing (pink vertical lines on bright objects). after that it the app didnt open again and just has the "camera app failed" error.
as for the hardbrick guys i think the qualcomm drivers work but only if you can get your phone to turn on or enter d/l mode. mine was so fried out that it wouldnt show any signs of life even after getting the drivers.
samersh72 said:
it should :good:
Click to expand...
Click to collapse
well thats od not for me
Aerys said:
I also hard bricked my S4 but with the utility Im able to get in Download mode, flash .pit and stock Samsung firmware but after flashing is succesfully done it goes into qhusb again and It again is dead.
Click to expand...
Click to collapse
givin me a little hint?
LastStandingDroid said:
well thats od not for me
givin me a little hint?
Click to expand...
Click to collapse
He probably means this: http://forum.legija.net/showthread....g-galaxy-S4-(i9505-and-similar)-via-USB-Cable
This was also samersh72's suggestion when i bricked mine. Problem is, there was no way for me to acces that qhusb mode thing as the phone was totally dead and doesn't even charge.
Jtag could probably revive it though.
Anyway, sent mine for repairs with
custom binary status and the samsung guys accepted it as there was no way for them to revive the phone(the motherboard was replaced). They didn't found out that it was modified.
Sent from my GT-I9505 using Tapatalk 4
Hey guys ;
I just wanted to ask , how do you recover from a hardbrick that is caused by a wrong rom flash or something similar. I know zips are usually marked with the device model on the updater script but say somebody mislabeled it. JTAG is "not" an option. I myself never did something like this but i'm curious as to how because my old p920 was virtually unbrickable. Without battery on , the phone could function as a development board which enabled us to emulate JTAG from the usb port. If i remember correctly.
How come Nexus 4 doesn't have something like this considering there used to be hordes of developers working on this device ?
So no access to recovery or fastboot?
boltthrower56 said:
Hey guys ;
I just wanted to ask , how do you recover from a hardbrick that is caused by a wrong rom flash or something similar. I know zips are usually marked with the device model on the updater script but say somebody mislabeled it. JTAG is "not" an option. I myself never did something like this but i'm curious as to how because my old p920 was virtually unbrickable. Without battery on , the phone could function as a development board which enabled us to emulate JTAG from the usb port. If i remember correctly.
How come Nexus 4 doesn't have something like this considering there used to be hordes of developers working on this device ?
Click to expand...
Click to collapse
First of all, how could you download a ROM for another phone AND install it on a Nexus 4?
Secondly, can you boot into Bootloader?
Thirdly, check the first... oh god....
Konstantinos said:
First of all, how could you download a ROM for another phone AND install it on a Nexus 4?
Secondly, can you boot into Bootloader?
Thirdly, check the first... oh god....
Click to expand...
Click to collapse
My phone is not bricked dude.
I was just curious. I know it's very unlikely but it is possible and it happens on samsung galaxy devices a lot because of the variations between international and US versions and some carriers. Somebody mislabels something and poof. dead.
Say the same thing happened to a Nexus 4. How would you recover from it , short of using a Riff Box?
boltthrower56 said:
My phone is not bricked dude.
I was just curious. I know it's very unlikely but it is possible and it happens on samsung galaxy devices a lot because of the variations between international and US versions and some carriers. Somebody mislabels something and poof. dead.
Say the same thing happened to a Nexus 4. How would you recover from it , short of using a Riff Box?
Click to expand...
Click to collapse
If you were to flash the wrong rom and could not get into the bootloader or recovery then the only way I know is jtag.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you were to flash the wrong rom and could not get into the bootloader or recovery then the only way I know is jtag.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That's what i figured , thank you.
You can also use download mode, aside from JTAG
boltthrower56 said:
My phone is not bricked dude.
I was just curious. I know it's very unlikely but it is possible and it happens on samsung galaxy devices a lot because of the variations between international and US versions and some carriers. Somebody mislabels something and poof. dead.
Say the same thing happened to a Nexus 4. How would you recover from it , short of using a Riff Box?
Click to expand...
Click to collapse
You need not JTAG it. I recovered my hard bricked Nexus 4 which doesn't enter into download or bootloader or adb... It didn't show anything except led blinking 10 times. But, your phone needs to be seen as Qualcomm QHUSB device and a software. I can't post link to that post here.