There are dozens of threads about "bricked" phones. It's not always clear if the OP(s) managed to recover.
Just out of curiosity. Did anyone manage to brick their phone? It seems like it's fairly difficult to do so.
if you break the ROM. use recovery, if recovery is broke, use lg recovery or flash tool, if that doesn't work then you did something wrong or hardware issues
So afaik no hard bricks
Since I own android phones, I have not hard brick any. If you hard brick an android phone, you should not own an android phone, you A. did not read instruction B. did not follow instruction C. think your smarter than the instruction by skipping it.
I thought as well that it's not that easy to brick the phone. I am comming from GNex, there were not that many threads from people asking how to recover, so I thought that maybe something is different with G2
There is a HUGE difference between hard brick and soft brick. Most people soft brick their devices and that is normally pretty easy to recover from(if you can get into recovery just restore back up, or just use the native tool from your hardware manufacturer). Most posts come from people who soft brick their devices and don't know how to recover from it. The people who hard brick normally flashed wrong kernels(from other phones) or were playing around with something they shouldn't have been playing with. I have owned a lot of phones (see my sig) and hacked every one of them(well... the ones that could be, the dumb phones didn't offer much for hacking) and have not hard bricked a single one. I have soft bricked some and some took all night to recover from but never hard bricked
joshuadjohnson22 said:
There is a HUGE difference between hard brick and soft brick. Most people soft brick their devices and that is normally pretty easy to recover from(if you can get into recovery just restore back up, or just use the native tool from your hardware manufacturer). Most posts come from people who soft brick their devices and don't know how to recover from it. The people who hard brick normally flashed wrong kernels(from other phones) or were playing around with something they shouldn't have been playing with. I have owned a lot of phones (see my sig) and hacked every one of them(well... the ones that could be, the dumb phones didn't offer much for hacking) and have not hard bricked a single one. I have soft bricked some and some took all night to recover from but never hard bricked
Click to expand...
Click to collapse
True, the only case of a legitimate hard brick where the user wasn't at fault was back in the og EVO forums where an early/beta build of TWRP may have been able to corrupt/damage the nv partition. But of course even that was fixable, just out of the op's range of abilities.
rokfor2000 said:
There are dozens of threads about "bricked" phones. It's not always clear if the OP(s) managed to recover.
Just out of curiosity. Did anyone manage to brick their phone? It seems like it's fairly difficult to do so.
Click to expand...
Click to collapse
i did...not paying attention. doing too much too fast...
http://forum.xda-developers.com/showthread.php?p=48080169#post48080169
tornamac04 said:
i did...not paying attention. doing too much too fast...
http://forum.xda-developers.com/showthread.php?p=48080169#post48080169
Click to expand...
Click to collapse
Still work in progress so hopefully you'll find the way to sort it out, before you become first hard brick case
joshuadjohnson22 said:
... The people who hard brick normally flashed wrong kernels(from other phones) or were playing around with something they shouldn't have been playing with. ...
Click to expand...
Click to collapse
Flashing kernel from another phone, not another variant of the same phone, right? Flashing D801 kernel on D802 is still recoverable? Just curious because I think, I've seen a thread where someone did it.
I have another question though. Does it mean that kernel developers are at constant risk of hard bricking their phones? Are there any other "safety" mechanisms available to them?
rokfor2000 said:
Still work in progress so hopefully you'll find the way to sort it out, before you become first hard brick case
Flashing kernel from another phone, not another variant of the same phone, right? Flashing D801 kernel on D802 is still recoverable? Just curious because I think, I've seen a thread where someone did it.
I have another question though. Does it mean that kernel developers are at constant risk of hard bricking their phones? Are there any other "safety" mechanisms available to them?
Click to expand...
Click to collapse
That really depends on the hardware of both models.. If they are the exact same you may be ok.. Just be careful when flashing and don't be the guinea pig and wait to here if there are any issues first
Sent from my LG-D800 using Tapatalk
rokfor2000 said:
Still work in progress so hopefully you'll find the way to sort it out, before you become first hard brick case
Flashing kernel from another phone, not another variant of the same phone, right? Flashing D801 kernel on D802 is still recoverable? Just curious because I think, I've seen a thread where someone did it.
I have another question though. Does it mean that kernel developers are at constant risk of hard bricking their phones? Are there any other "safety" mechanisms available to them?
Click to expand...
Click to collapse
yes I done it, just enter recovery and flash your kernel
@Fma965, my lg g2 got hard bricked pl help me
pls
Related
I've read up on a lot of people bricking their Vibrants and quite frankly they're scary. Also I'm new so cut me some slack if I put this in the wrong thread :{D
Compared to the G1, the vibrant is easily bricked if you don't follow directions.
It is also extremely easy to recover. It's not like hard bricking a G1.
this thing is a tank .. most people end up with soft bricks.
if anything and i mean anything on thep hone works.
meaning the lights light up at the bottom, your good.
if nothing turns on no lights, no screen logo anything, then your hardbricked, we've been getting hard bricks this month a lot, but its because of user fault, follow correct instructions and then you'll be good to go.
REMEMBER; IF THE OP HASN'T SAID "NO NEED TO DISABLE VOODOO" then disable it. voodoo not being disabled when going to another rom is probably 95% of the reason of soft bricks.
vetvito said:
Compared to the G1, the vibrant is easily bricked if you don't follow directions.
Click to expand...
Click to collapse
That is SO FAR off base. The Vibrant is nearly impossible to Brick (HARD brick....).
Thank you and also I read that you cant upgrade to certain things or root certain things from stock or else your phone will get bricked. Is that true or..?
I think what you are referencing is when people performed a lag fix (converted the file system to EXT2 or 4)... and then flashed a rom on top of it without disabling the lag fix first. THIS would cause a soft brick (its not a brick, but people call it one.... makes NO sense).
Alll you would do is just use ODIN to get back to stock.... not hard at all. Really, really hard to brick this phone for good.
Haha, thanks. Also would you recommend any ROMs? I'm totally lost with all of these choices.. And would you recommend using a one click root or the zip? Or any other root method; I'm so lost!
The g1 was scary easy to brick. The vibrant is a tank in comparison. Flash away with confidence.
It's easily bricked. I bricked my first Vibrant because I fergot to disable voodoo before flashing a different rom and it wouldn't even turn on after
Urukiora said:
It's easily bricked. I bricked my first Vibrant because I fergot to disable voodoo before flashing a different rom and it wouldn't even turn on after
Click to expand...
Click to collapse
Now, whos fault is that for not disabling voodoo?
You probably did something else too, because just that doesn't cause a hard brick. EVER.
This thing has a brick proof coating applied. If you mess up you can Odin back to a stock image 123.
Don't blame me, blame my keyboard's autocorrection algorithm.
The only time my phone bricked(soft) was when Tmo sent an update a while back...lol...otherwise, I have never bricked(soft nor hard) my vibrant...with the newest ROMS all have the voodoo that you you can just install on top of another so my suggestion is to just stay with ROMS that have voodoo...besides it provides the best experience...also, ODIN back to stock before switching ROMS by different chefs...if its just a newer version of the same ROM just Wipe Data and Wipe Davlik then flash and you'll be good...happy flashing!!!
p.s. I recommend Axura by Master...its awesome and he consistently updates it
Thank you! One last thing If I use odin to get back to stock before I unlock the device to work on At&t am I not going to be able to unlock it? Or is there some magical way to get the unlock codes?
s15274n said:
That is SO FAR off base. The Vibrant is nearly impossible to Brick (HARD brick....).
Click to expand...
Click to collapse
This is correct. The G1 Is way easier to really screw up. The vibrant is so forgiving. It is imho the best phone to learn to modify, because it takes a REAL moronic action to brick it.
oka1 said:
This is correct. The G1 Is way easier to really screw up. The vibrant is so forgiving. It is imho the best phone to learn to modify, because it takes a REAL moronic action to brick it.
Click to expand...
Click to collapse
"moronic action" ....that is so full of win.
Well said and true though.
Greetings Ok friends this is my situation I think my phone is a brick as hard and tried everything mentioned in these 19 pages and even http://forum.xda-developers.com/showthread.php?t=848737 fails to go into download mode, the situation is that the phone is not even the lights on if the screen and does absolutely nothing, leading to a repair shop in my country and I say tried to make a JTAG and the phone does not respond, any suggestions?
this guy sounds promising http://www.youtube.com/user/MobileTechVideos#p/search/0/lzh7cbND-lo
knew, had seen the video, it was my last option in case you can not recover myself
http://www.xda-developers.com/android/unbricking-your-captivate-gets-even-easier/
Last but not least, AdamOutler is asking for volunteers to borrow devices from that are equipped with a CORTEX-A8 processor in it will do. It does not have to be functional as the dev will need it to remove the processor from it. The dev promised to return it once he is done. You can find a list of devices in this thread. So, if you have a broken phone from this list laying around in your house/office and would like to put it up for a good cause, now is your chance.
Looking into this method right now as Im hard bricked myself!!!
Link: http://forum.xda-developers.com/showthread.php?t=1220181
dseldown said:
Looking into this method right now as Im hard bricked myself!!!
Link: http://forum.xda-developers.com/showthread.php?t=1220181
Click to expand...
Click to collapse
thanks will try this method now
could you please tell me how to get the (boot.bin) or give me a download link
the vibrant
The only way to fix a hard brick is make a jig.
try this http://forum.xda-developers.com/showthread.php?t=1242466....I know it is for captivate but since vibrant and captivate are both galaxy s variant...doesn't hurt to try after all sorry.. if I sound rude but how worse can it get?
onasri15 said:
The only way to fix a hard brick is make a jig.
Click to expand...
Click to collapse
TECHNICALLY, if you can use a JIG, its not a hard brick.
a hard brick is a solid brick. nothing can solve it except the... urghhhhhh i cant get the word in my mouth but its a something "box" i think
thats the only way out of hard brick as far as i know.
Great. I, like a dumbass, decided to try and root my new phone without a backup plan. I have had no luck using the XDA video, and now I'm stuck with the "Please select recovery mode in Kies" screen. Kies doesn't recognize it, and I have no way to restore the stock ROM. Is my only option to wait until a stock firmware ROM is released, like it was for sprint?
Based on the information we're currently provided with, I think it'd be safe to say you're screwed for now. Why you would even try to root a device that doesn't currently have any rooting methods is beyond me. You should definitely read up before you try anything you're not sure of.
The only other option you'd have at this point is taking the phone into Verizon, showing them the screen and telling them that this is how it has looked since it came out of the box. Although it's a lie, and you bricked it out of your own neglect, the reps can't really turn you away.
Can you return it?
Sent from my SCH-I605 using xda premium
I did some research, and nobody had any negative things to say about the rooting process, especially with all the videos and forums on it. I searched for how to root the Samsung note 2, versus the model number, which is different for different carriers.
MedicMillan said:
I did some research, and nobody had any negative things to say about the rooting process, especially with all the videos and forums on it. I searched for how to root the Samsung note 2, versus the model number, which is different for different carriers.
Click to expand...
Click to collapse
Every carrier is different. You must be new here.
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
MedicMillan said:
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
Click to expand...
Click to collapse
You will need to wait until the boot loader is unlocked to flash a rom, only way I can think of.
MedicMillan said:
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
Click to expand...
Click to collapse
At this point in time, you can't flash anything, you can't root, and there are no recovery images to return to stock with. You either have to wait it out, or try to exchange it at Verizon.
You can exchange, they will not know the difference
Sent from my SCH-I605 using Tapatalk 2
Just take it to Verizon play dumb and get it replaced. It's within the 14 days so it will be swapped on the spot. They wont/don't care what's wrong with it.
The suggestion of just return it to the store, they won't notice, is a really **** move and I'm not saying that in defense of Verizon. I'm saying it that it is things like that that in the end cause more harm to the end user than good. They up costs and add charges, create obscene policies, etc. It may not negatively impact you immediately, but when multiple people do this all over the country it adds up.
DaRkL3AD3R said:
The suggestion of just return it to the store, they won't notice, is a really **** move and I'm not saying that in defense of Verizon. I'm saying it that it is things like that that in the end cause more harm to the end user than good. They up costs and add charges, create obscene policies, etc. It may not negatively impact you immediately, but when multiple people do this all over the country it adds up.
Click to expand...
Click to collapse
I have to say I agree 100%. If people just used common sense, or read up a bit, situations like these could be entirely avoided.
MedicMillan said:
Great. I, like a dumbass, decided to try and root my new phone without a backup plan. I have had no luck using the XDA video, and now I'm stuck with the "Please select recovery mode in Kies" screen. Kies doesn't recognize it, and I have no way to restore the stock ROM. Is my only option to wait until a stock firmware ROM is released, like it was for sprint?
Click to expand...
Click to collapse
Check the development section. There is a leaked ODIN .tar file that you can flash. It is a prerelease, but at least you will have a functioning phone until a proper root/unlock solution is found.
bork.it.consulting said:
Check the development section. There is a leaked ODIN .tar file that you can flash. It is a prerelease, but at least you will have a functioning phone until a proper root/unlock solution is found.
Click to expand...
Click to collapse
This Odin file fails. It will not flash. Someone was trying to flash it last night with the same screen you are on.
just odin the stock image in the dev section and you will be back up and running...do not I repeat do not anybody try any root methods for the other gn2 variants!
http://samsung-updates.com/device/?id=SCH-I605
if it fails then your screwed until the latest odin image is release, which im sure wont be too long.
Nit3mare said:
I have to say I agree 100%. If people just used common sense, or read up a bit, situations like these could be entirely avoided.
Click to expand...
Click to collapse
I'm not saying that everyone should go flash happy, attempt to root without knowing what they are doing destroy their phones and take them back to Verizon then rinse and repeat the process. But there have to be a few that are a tempting to get root for everyone else there is bound to be some hard bricks. Should they be out 700, and that's kinda harsh.
Check out this link for a fixed brick....
http://forum.xda-developers.com/showthread.php?p=34862234#post34862234
mrlaigle said:
I'm not saying that everyone should go flash happy, attempt to root without knowing what they are doing destroy their phones and take them back to Verizon then rinse and repeat the process. But there have to be a few that are a tempting to get root for everyone else there is bound to be some hard bricks. Should they be out 700, and that's kinda harsh.
Click to expand...
Click to collapse
But with a little reading in the correct forum, people could avoid owning a $700 paperweight. It's really not that difficult, and any issues that arise from lack of research are due to their own ignorance. I can't feel sympathy for anyone who flashes blindly.
Nit3mare said:
But with a little reading in the correct forum, people could avoid owning a $700 paperweight. It's really not that difficult, and any issues that arise from lack of research are due to their own ignorance. I can't feel sympathy for anyone who flashes blindly.
Click to expand...
Click to collapse
I'm not disagreeing with you. If you do not know what you are doing or if this is your first time you shouldn't be attempting to root an un rooted device. But there will always be those guinea pigs...
Sent from my SCH-I605 using Tapatalk 2
This is exactly the reason why everyone else who follows commense is punished with locked bootloader.
I have taken a recent interest in making roms, specifically ports for the note 2. Currently I only have one note 2 so what should I do in order to test my roms without bricking my phone?
Ps: If anyone knows of a good beginners guide for building roms that would be great but it is not my concern.
Thanks in advance.
Sent from my Galaxy Note 2
Leave it stock.
Best way? Read the OP/Intructions carefully. That's all. You will never brick your phone if you read the instructions. Also, if you feel uncomfortable doing something with your phone that may result in a brick, don't perform it. But there's always a way to unbrick a phone and you have a community that has your back so you're set for any bricking
Provided you're only flashing test roms and not kernels, it's pretty much impossible to brick. Just make sure you have a backup!
Sent from my SCH-I605 using Tapatalk 2
BennyJr said:
Leave it stock.
Click to expand...
Click to collapse
That's what I was thinking also.
I used to play around with building ROMs back in my Windows phone days (I don't have time to do that anymore) but I always kept a spare phone around for "bricking" purposes.
I don't think I would want to use my only phone as a test dummy for new ROMs (especially if you aren't REALLY experienced at it)
I think I'm going to try with my old samsung fascinate, It would be less of a hassle if I broke that phone.
Thanks guys.
Sent from my Galaxy Note 2
Don't be stupid. The only way to really brick a phone anymore is if you're being dumb and doing stuff beyond your knowledge. Knowing what you're flashing and making sure it is compatible with your phone will help. Also, don't flash anything in Odin unless you're restoring to stock (or unlocking).
Well. My curiousty led to a hard-bricked phone
It's definetly official. I am not going to install any more custom roms after this. To make my story breif. I aquired a motorola atrix 2 phone, and had read it could accomdate a custom rom, so I used a one click root method program and the program said it had done its job. I booted into the recovery and installed the rom, which ended in an infinite reboot. Great, so I read more on how to revert back to firmware using rsd lite. I did this, but the battery was dead. so I went out and purchased anther battery, attempted the restore, phone restart, then BOOM. it stayed black and now it wont come on. wtf.
Can any please recommend the proper cable I have to order to get the phone back working>?
Sunaj1 said:
Well. My curiousty led to a hard-bricked phone
It's definetly official. I am not going to install any more custom roms after this. To make my story breif. I aquired a motorola atrix 2 phone, and had read it could accomdate a custom rom, so I used a one click root method program and the program said it had done its job. I booted into the recovery and installed the rom, which ended in an infinite reboot. Great, so I read more on how to revert back to firmware using rsd lite. I did this, but the battery was dead. so I went out and purchased anther battery, attempted the restore, phone restart, then BOOM. it stayed black and now it wont come on. wtf.
Can any please recommend the proper cable I have to order to get the phone back working>?
Click to expand...
Click to collapse
Did you flashed rom with stock recovery?
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
Did you flashed rom with stock recovery?
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried to. Unless i acidentally downloaded the wrong file.
Sunaj1 said:
Yes, I tried to. Unless i acidentally downloaded the wrong file.
Click to expand...
Click to collapse
You should flash roms with custom recoveries that built for your device like clockworkmod or twrp recovery.
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
You should flash roms with custom recoveries that built for your device like clockworkmod or twrp recovery.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Yes, I am aware of that. The problem is now my phone is hard bricked and it wont turn on at all, not even to display an error message.
How can I fix this? whats that special cable That i need?
I would love to help you but I don't have the device and I think you should ask to your device's q/a forum. It will more helpful for you.
Sent from my Sony Tablet S using xda app-developers app
Sunaj1 said:
Well. My curiousty led to a hard-bricked phone
It's definetly official. I am not going to install any more custom roms after this. To make my story breif. I aquired a motorola atrix 2 phone, and had read it could accomdate a custom rom, so I used a one click root method program and the program said it had done its job. I booted into the recovery and installed the rom, which ended in an infinite reboot. Great, so I read more on how to revert back to firmware using rsd lite. I did this, but the battery was dead. so I went out and purchased anther battery, attempted the restore, phone restart, then BOOM. it stayed black and now it wont come on. wtf.
Can any please recommend the proper cable I have to order to get the phone back working>?
Click to expand...
Click to collapse
Hi, I guess you can use THIS LINK to try and fix your problem. Thank you for consulting the forums, and have a nice day.
ATkeneiville said:
Hi, I guess you can use THIS LINK to try and fix your problem. Thank you for consulting the forums, and have a nice day.
Click to expand...
Click to collapse
Thank you. But an experienced repair guy said my phone wasn't responding to neither the USB jtag or the fast boot. So my phone is dead forever? Should I start digging its grave?
Sure sounds this way, and you shouldn't be doing JTAG through the USB port anyway unless your phone is something special I've never heard of
But in truth rooting your phone won't damage it, it just gives someone the opportunity to do so. I'm a firm believer in rooting all androids so long as they read and understand what they are doing, its very hard to brick a phone if you know what you're doing
So although this phone may be dead forever (unless you find someone who for sure knows the proper way to JTAG it) then still consider rooting your next one, just be sure to completely understand what's going on, and try to stay away from one click roots, its hard to learn anything from this
Best of luck on your next phone
*side note, if you still have warranty and your phone is completely unresponsive chances are you will get your warranty exchange, just play dumb and say "I was playing angry birds and it just froze, now it won't turn on"
Sent from my Nexus 4 using Tapatalk 2
I wish I had warranty on this thing. I got it second hand from craigslist. However i've managed to acquire an HTC inspire 4G, what an upgrade from a motorola cliq xt! I would love to install jelly bean on this thing but after messing up the Atrix 2 i'm scared I will F*ck this one up too. I can never find clear and concise instructions on the internet. Every web page I visit, it seems to be someones personal way of doing it. Steps not mentioned, or instructions written for intermediate users. For example, Every video or piece of instruction i've watched on youtube regarding booting into the fast boot on the atrix 2, said something about holding volume up and power button upon booting and I would see something on the top of the screen. However that did not work, First I had to use the volume down and power button, then I would get to this fastboot screen where those recovery options werent available, from there I had to hold both volume buttons down and press the power button twice which would bring me to the recovery options screen. thats just one example, and even then for some reasons I didn't have all the recovery options the instructions spoke of... for example. Very annoying and frustrating. On a side note, is there anyone on this site who lives in the US that can unbrick my atrix 2? The guy who repair phones I took it to said theres a device for 250.00 bucks he's waiting to get that can unbrick any device. However he doesnt have the funds and had gotten laid off work. I am just having a hard time believing a simple soft user error could permanently damage my device forever and that as sophiscated as our technology has gotten there's absolutely no way to revive it.
demkantor said:
Sure sounds this way, and you shouldn't be doing JTAG through the USB port anyway unless your phone is something special I've never heard of
But in truth rooting your phone won't damage it, it just gives someone the opportunity to do so. I'm a firm believer in rooting all androids so long as they read and understand what they are doing, its very hard to brick a phone if you know what you're doing
So although this phone may be dead forever (unless you find someone who for sure knows the proper way to JTAG it) then still consider rooting your next one, just be sure to completely understand what's going on, and try to stay away from one click roots, its hard to learn anything from this
Best of luck on your next phone
*side note, if you still have warranty and your phone is completely unresponsive chances are you will get your warranty exchange, just play dumb and say "I was playing angry birds and it just froze, now it won't turn on"
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I can't attest to the videos you saw, but for most androids this is the best site with the most info, I only suggest being sure how to root before you do it, and to understand how the method works as well. When your not understanding this is when bricks happen.
I know it can be lots of reading and lots of questions but in the long run its worth the time
As for the JTAG equipment there are many who have it and you can easily spend less than 250 on getting the proper stuff.
Every logicboard is different so maybe this machine he speaks of has a wide variety of cables that come with it, but he's still paying too much
Anyway, most people seem to charge 50$ or so to JTAG it back, if that's more than the phone is worth to you just sell it on eBay for parts
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
I can't attest to the videos you saw, but for most androids this is the best site with the most info, I only suggest being sure how to root before you do it, and to understand how the method works as well. When your not understanding this is when bricks happen.
I know it can be lots of reading and lots of questions but in the long run its worth the time
As for the JTAG equipment there are many who have it and you can easily spend less than 250 on getting the proper stuff.
Every logicboard is different so maybe this machine he speaks of has a wide variety of cables that come with it, but he's still paying too much
Anyway, most people seem to charge 50$ or so to JTAG it back, if that's more than the phone is worth to you just sell it on eBay for parts
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Can you link me to clear and concise instructions on how to upgrade my 2.3.7 ( i think) to jellybean on an htc inspire 4g? and is there anyone here who can fix my phone that you know of?
HERE IS YOUR PHONES FORUM
you will find links to all the guides you need here, always read the stickies in each section, this tends to have the important info you need
then anything your not sure about should be asked in the proper place within this forum for the best answers
example, question on how to root should be asked in the how to root thread for best chance of a good answer, question on how to flash a new radio should be asked in a thread pertaining to this
im sorry but i dont know enough about your phone specificly to help further but hopefully the members in your device specific forum will
best of luck!