Look guys if your phone can be fixed it is not bricked. One can not fix a brick. Just because you have had negative results, does not always mean you are bricked. If we continue to take this word so lightly it will lose its meaning. Then we will have to come up with other witty way to describe the death of our phones. Anyway think about it.
noobile said:
Look guys if your phone can be fixed it is not bricked. One can not fix a brick.
Click to expand...
Click to collapse
Exactly. It is bricked when its functionality is permanently reduced to that of a brick.
I bricked my phone yesterday. Wouldn't boot into recovery or download mode. Or normal mode for that matter. I am working on getting a replacement, now. I have reflashed a couple of supposedly "bricked" phones, but as long as it will boot to download mode, it usually isn't very tough to flash back to stock.
"It might be bricked but I"m not sure." Maybe, we just need a witty term that defines that! Any ideas?
You mean "semi-bricked"? I think that alone is good enough for "it's screwed up but it might be fixable".
Related
i tried to repartition using heimdall, and i think i bricked my phone. it doesn't respond to anything -- 100% black screen.
should i even bother making a jig or is the wicked witch finally dead?
Why not try a jig?
Sent from my Captivate using XDA Premium App
a.vandelay said:
i tried to repartition using heimdall, and i think i bricked my phone. it doesn't respond to anything -- 100% black screen.
should i even bother making a jig or is the wicked witch finally dead?
Click to expand...
Click to collapse
Worth a shot, a pack of 100k resistors is 99c at radioshack, but I'd put my money on perma-bricked. In almost all cases (I actually have yet to hear of a single case where someone managed to recover from a black screen brick), a completely unresponsive phone, where pressing the power button does nothing, means that the phone has been paper-weighted.
You most likely destroyed your bootloader. If that's the case, your only options are to either buy a riff box and reflash the bootloader and firmware directly onto the chip via jtag, or mail it back to Samsung and let them do it.
Sorry to hear about your rotten luck, dude. Happens to everyone sooner or later :\
Provided that the phone is in good physical condition and none of the water strips have changed colors, Samsung should fix it up under warranty. They will even pick up the shipping. Give them a call.
yep, this thing is a solid brick. i've recovered from pretty horrific things (e.g. the battery falling out during a flash) but never had it completely unresponsive.
i'll try to get a replacement. maybe if i say "i flashed a bad bootloader" the service rep will go along with it .
edit: i had to dig out my iphone 2g to use in the meantime. 1) at&t reactivated my unlimited data plan. 2) i installed gingerbread on it. lolz.
Ok, I know lots of people brick their phones, and like in my case hard-bricked as well. But everycase is unique but I'd really appreciate if you guys could look over what I did and see if my plan of action is the right thing to do.
So, basically I came across ICS on youtube by chance and it looked to be really cool for my S2. I have no experience with romming and such and I'd only ever heard of it. Then after about only 3 hours of research I set to work to romming it. The instructions said I had to get a clockwork mod to flash the drive to get ICS. I think I messed this up as I'm not entirely sure I unzipped the folder properly to get the .tar. on pda.
So, my phone would turn on but only get to the samsung logo with the warning sign. By this time I was fed up and worried and such and decided it was too much effort and just wanted my phone back. So I set out to put the original firmware back on. I downloaded the stuff and put the in their respective slots, pit,pda and mobile I think. I pushed start and it was if odin had frozen (no progress bar either), I couldn't click anything and the log script in the corner showed nothing.
I was quite annoyed and closed odin and unplugged my phone,put it back in download and such to try again. This time the same thing happened and I unplugged the phone first, Big mistake! My phone went completely black and effectively hard bricked.
Okay that's what happened. I just want advice to see if what I'm going to do is right.
1- Imma try to go through the simple workarounds to try to get my phone back into download mode.
2- This will probably fail, so I will purchase a USB jig from amazon, this will give me 3 potential results
one. My phone will get back into download mode and there will be no warning sign under the samsung logo and custom counter at 0.
two. My phone will get back into download mode but there is still the warning sign and the custom counter is at 0
three. Nothing will happen or my counter will be at one
3- okay so if scenario one happens I will send my phone to samsung and they should repair as they have already told me through e-mail they believe it to be a motherboard problem
scenario two, I will send my phone to vodafone,as I've learnt from the forums their techies should not care as much about that kind of thing.
scenario three, I will send my phone to mobile tech videos in Texas from the UK as everyone seems to trust them and they look pretty legit.
Okay, so that's basically my plan of action. All I want is for you guys is to just go "yeah, good idea thats probably right" or show me what I've misjudged or if you are aware of another option for me.
Thanks,
Adam
Bump, please I know some of you guys can help me out
Me and my friend are currently in an argument in what the term "bricked" really means.
I am saying that a bricked device is one that is no longer functioning, like one stuck in a boot loop, BUT it is able to be fixed in many cases.
Example: When I bricked my Droid 2, I flashed a working SBF.
He is saying that when a device is "bricked" it is unable to be fixed, and is far beyond repair.
Example: When my friends mom stomped on his Evo Shift, the phone wouldn't turn on, and the device was bricked.
I understand that both of those examples are bricked (one more extreme than the other) but a device doesn't need to be beyond repair to be technically "bricked">
I would love to hear your opinion on how you view this term.
Bricked means unflashable, and you need jtag or other device to be able to fix, or not flashable or repairable through usb cable or sdcard, also a brick is when you drop it in water and it short circuits and destroys the ics, lcd etc.
Edit: brick also means if you dropped it and it now malfunctions, like lcd cracked and other crazy things happen when your using it.
Soft brick is when its stuck in a bootloop or whatever software problem that can be fixed
Hard brick is when you mess with the bootloader or something and it won't turn on BUT BECAUSE THE SOFTWARE
When its been smashed or physically damaged (ie water damage) I simply call the device "broken"
Sent from my DROID2 using xda premium
http://forum.xda-developers.com/showthread.php?t=1483113
There are two types of bricks: hard bricks are serious and can't be fixed 99% of the time (the phone is useless and might as well be a brick) and soft bricks can be. If you have a hard brick you're probably sol but if you have a soft brick there's no need to panic.
Chancee said:
http://forum.xda-developers.com/showthread.php?t=1483113
There are two types of bricks: hard bricks are serious and can't be fixed 99% of the time (the phone is useless and might as well be a brick) and soft bricks can be. If you have a hard brick you're probably sol but if you have a soft brick there's no need to panic.
Click to expand...
Click to collapse
That's not what he was asking... read the OP again...
Sent from my DROID2 using xda premium
I am somewhat of a n00b when it comes to android phones. I have had my maxx for about a month. Installed the leaked JB version and everything was working fine.
Today I decide to go back to 4.0.4 with the utility and something went wrong. I am stuck in a AP Flashboot loop. It sucks. I have tried everything....at least what I think is everything.
I have tried multiple utilities and RSD lite, etc. with no success.
Am I missing something?
Thank you!
Have you had any success yet?
projekt8e said:
Have you had any success yet?
Click to expand...
Click to collapse
negative.
same issues?
Fortunately no, but I have been searching around a little because I am new to Motorola (fresh out of samsung) and I have had some issues like this in the past that were rather frustrating, but as far as I can tell, considerably less frustrating than what one might experience with our phone.
so for my own sake, since I can't see it, is your phone essentially just going into fastboot and automatically rebooting or can you access any of the menu options?
projekt8e said:
Fortunately no, but I have been searching around a little because I am new to Motorola (fresh out of samsung) and I have had some issues like this in the past that were rather frustrating, but as far as I can tell, considerably less frustrating than what one might experience with our phone.
so for my own sake, since I can't see it, is your phone essentially just going into fastboot and automatically rebooting or can you access any of the menu options?
Click to expand...
Click to collapse
Yes it is extremely frustrating.
Said something about not being able to write to partition. Any option that I pick comes up to the fastboot menu. It seems to fail anytime it attempts to write to the phone.
One thing that I have noticed is that battery level seems to be important. (above 50% specifically)
not that this will fix your problem, but it might be preventative maintenance from further problems. Have you seen this?
http://forum.xda-developers.com/showthread.php?t=1549625
It covers charging in a scenario like yours, because it sounds like it might be nearly impossible to get anything down without a decent charge.
projekt8e said:
One thing that I have noticed is that battery level seems to be important. (above 50% specifically)
not that this will fix your problem, but it might be preventative maintenance from further problems. Have you seen this?
http://forum.xda-developers.com/showthread.php?t=1549625
It covers charging in a scenario like yours, because it sounds like it might be nearly impossible to get anything down without a decent charge.
Click to expand...
Click to collapse
Thanks! Ill keep that in mind. I think I was about 40 percent when I did it..... I doubt if that was the issue. I think as long as you dont lose power you should be OK... well what do I know... I will most definetly keep this in mind and make sure I use a full charge. My replacement phone should be here tomorrow morning...
Yeah, I think as long as you have power it should be ok, this was more of a measure to consider if your battery might be getting too low now after trying to fix it. But I guess if you have a replacement phone on the way, that will be easier, but maybe not as much fun! haha. Do you have to return the bricked one right away then?
projekt8e said:
Yeah, I think as long as you have power it should be ok, this was more of a measure to consider if your battery might be getting too low now after trying to fix it. But I guess if you have a replacement phone on the way, that will be easier, but maybe not as much fun! haha. Do you have to return the bricked one right away then?
Click to expand...
Click to collapse
Yup has to be returned within 5 days. I am making sure the battery is completely dead before i box it up. So they would have to at least charge it before they see the error.
They said something about being charged 299.00 if I messed with the image, software or something like that.... I think that it would be very hard for them to prove that point though in all actuality. Not much option.... Yeah.. not the way I really wanted to go but it is what it is..
fair enough. Yeah, leave it dead.
projekt8e said:
fair enough. Yeah, leave it dead.
Click to expand...
Click to collapse
This is exactly what i needed.
http://forum.xda-developers.com/showthread.php?t=2035131
All is working well. Perfect, perfect, perfect.
right on, so what did you end up doing then, if you don't mind explaining?
SO I thought that I would post an experience I had this morning with flashing my Note 10.1. I am doing this that way if someone does a similar thing they might be able to fix it. First I will say that yes I am an idiot, and I was very lucky I was able to recover my device. I will not say that this was a hard brick. I believe that for it to be a hard brick there is no cure. I did believe for a while that it was a hard brick. Jesus must really love me :angel: I IN NO WAY PRETEND TO BE THAT SMART! This is just here to help other people who may have the same problem.
So like an idiot i flashed a mod onto an incompatible rom.
This made my device not capable of going into TWRP.
I could however get to the first screen of stock (warning of flashing new hardware) but then it would black out.
I installed the GNOTE 10.1 toolkit and proceeded to set that up.
Meanwhile I plugged my tab into the wall (it was at 99%) but I wanted to see what it would do, It went crazy blocky weird screen.
When the toolkit was setup, I told it to flash over TWRP 2.5 and luckily enough my computer recognized my tablet as a generic Samsung device. (with adb and Odin)
Then i flashed it over, and it worked.
I believe I was extremely lucky that this worked, and I do not promise this will work and take no responsibility for what it may or may not do to your tab, life, marriage, the world.
I just thought I should share this incase it can help someone else.
p.s. I think that the file i flashed over somehow jacked up my kernel and recovery. but i am not sure exactly what happened.