How easy is this phone to brick?
And by brick I mean point of no return?
Sent from my SGH-T959 using XDA App
I have heard no reports of people bricking it ever.
Sent from my Darkginger CM7 Google Nexus S!
It appears to be rather difficult. I've not seen any validated reports of a brick here yet. One guy acted like he might have bricked his legitimately, but it's not clear what he actually did or if he managed to flash something to it.
As long as you have fastboot working, there should be no issues flashing a recovery image and a rom from there.
Keep in mind Google designed this phone to be easily unlocked and modded with custom roms.
If mine is still working, they have to be pretty hard to brick. Google did an awesome job in making recovery very easy.
byock1 said:
If mine is still working, they have to be pretty hard to brick. Google did an awesome job in making recovery very easy.
Click to expand...
Click to collapse
Indeed. I'm not going to pull a Titanic and claim its unbrickable but I'd say its pretty f°°°ing hard to brick. As distortedloop said, I've not seen a case where someone could not get to the bootloader and if you can do that you can fast boot a recovery and restore a stock nandroid.
Sent from my Darkginger CM7 Google Nexus S!
I haven't heard of bricks either.... its really difficult to brick when u have recovery.
you really have to pull some crazy **** to brick this phone, even then its hard. ive even tried flashing a nexus one and a mt4g rom to it, but it just errored out
lol i did brick my nexus s
i flashed the odin flash image found here and killed my att nexus s so sad
i was trying getting CM7 on it but it wouldnt mount cache nor data so tried to mount them over adb and went crazy and flashed that odin image,
wont boot or anything probably different bootloader and i killed it appart from having different modem, i guess i will go back to my i9000T that wont brick even if i install euro i9000 bootloaders
davioxx said:
lol i did brick my nexus s
i flashed the odin flash image found here and killed my att nexus s so sad
i was trying getting CM7 on it but it wouldnt mount cache nor data so tried to mount them over adb and went crazy and flashed that odin image,
wont boot or anything probably different bootloader and i killed it appart from having different modem, i guess i will go back to my i9000T that wont brick even if i install euro i9000 bootloaders
Click to expand...
Click to collapse
Even then, its probably still not bricked. Sell me yours.
peeturr said:
Even then, its probably still not bricked. Sell me yours.
Click to expand...
Click to collapse
lol really help me getting it back to life i think i have a unique device atm
i cannot boot neither recovery, fastboot or download mode
im thinking on building a jig with the 301k resistor to see if that makes it boot :S
davioxx said:
lol i did brick my nexus s
i flashed the odin flash image found here and killed my att nexus s
Click to expand...
Click to collapse
How did you brick a phone that doesn't yet exist (att nexus s)...?
Nice catch there
nice to notice the ATT nexus s
Brick
benifactor said:
How easy is this phone to brick?
And by brick I mean point of no return?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I think it must be impossible; I've put on roms, kernels, etc., and I don't know what I'm doing. Just play around and it's never broken.
benifactor said:
How easy is this phone to brick?
And by brick I mean point of no return?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
its kind of hard to brick where you cant bring it back. i had bootloops and stuck at the google screen but as far as that goes you can still access your recovery and restore a working rom.
Related
Oh yea, the first brick on the block.
I was experimenting with stock rom modification through ADB and within the OS itself. We still can't flash anything with the "backdoor" CWM that we have at the moment that wasn't even designed for our phone, but it will allow you to do a nandroid backup, so I made sure to back up everything in case I did something stupid. Well, I did something stupid. So stupid in fact that I can't get back into recovery, I just hang at the initial boot screen. So I'm kind of glad an odin TAR file is being worked ok. I think I'm going to need it. Oh well, no progress without failure.
TO THE BACKUP PHONE! *cue the batman music*
I bricked my phone but I got it 7 days after buying it. So being thr horrible person I am o exchanged it and played dumb
Sent from my SGH-T959V using XDA Premium App
aloneinshadow said:
Oh yea, the first brick on the block.
I was experimenting with stock rom modification through ADB and within the OS itself. We still can't flash anything with the "backdoor" CWM that we have at the moment that wasn't even designed for our phone, but it will allow you to do a nandroid backup, so I made sure to back up everything in case I did something stupid. Well, I did something stupid. So stupid in fact that I can't get back into recovery, I just hang at the initial boot screen. So I'm kind of glad an odin TAR file is being worked ok. I think I'm going to need it. Oh well, no progress without failure.
TO THE BACKUP PHONE! *cue the batman music*
Click to expand...
Click to collapse
so did you get odin workin and unbrick?
mavictb said:
so did you get odin workin and unbrick?
Click to expand...
Click to collapse
yep, he was the 1st to unbrick with the stock tar
Thanks to the awesome Krylon. I've actually flashed that tar about 4 times now. :-D
Sent from my SGH-T959V using XDA App
I did the same exact thing yesterday. I forgot to use the stock tar. and my first superbrick ever. Won't even turn on period...Sent in for an exchange to Wal-Martwire dot com. Normally Walmart is cool about taking things back (even if it's torn to shreds.) so we shall see if they're gonna notice.
I actually bricked my Vibrant 4G in like 4 hours of owning it...was rather dissappointing
Hey, i was having trouble with a reoccurring issue with my nexus s: the search button would fire on it own making it almost impossible to use my phone. The nexus was rooted and had clockworkmod installed, so i went ahead and flashed a 2.3.4 version of gingerbread. after the flash was complete, the phone would not turn on whatsoever. not even a boot logo, the screen is just black. cannot even get it into recovery mode.
help would be much appreciated.
Nexus S 3g
Fido
Canada
are you able to boot it into bootloader (vol up + power button)?
Guys i gotta ask...i mean i flash rom soo many times that my phone is bound to get bricked some day...although nothing has happened till now(knock knock).is there any solution to a hard bricked device..?
kevin, thanks, im unable to turn the phone on whatsoever. not even able to get into the bootloader
Can you adb or fastboot it or is it completely gone?
Sent from my Nexus S using xda premium
ferozfero said:
Guys i gotta ask...i mean i flash rom soo many times that my phone is bound to get bricked some day...although nothing has happened till now(knock knock).is there any solution to a hard bricked device..?
Click to expand...
Click to collapse
You have to be pretty unlucky to REALLY brick one of those, assuming you took the proper steps when first rooting it. Nandroid backup + EFS backup = almost bulletproof.
bblawless said:
kevin, thanks, im unable to turn the phone on whatsoever. not even able to get into the bootloader
Click to expand...
Click to collapse
So you don't see any Google logo when you turn it on? Don't get any vibration either?
Could be the BGA failing. That's one of the most common physical problem for the Nexus S, with the power button failure and the softkeys starting to active like they were possessed.
Jeff Dunn said:
Can you adb or fastboot it or is it completely gone?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No I'm unable to do anything, can't even get my computer to recognize the phone, I'm beggining to lose hope I feel like I've tried everything. No boot loader, no recovery, just a blank screen with no response whatsoever. I believe I may have flashed an incorrect rom and corrupter the boot loader or something along those lines, at least thats what
my friend believes
Thanks
You could try the UnBrickable Resurrector
Harbb said:
You could try the UnBrickable Resurrector
Click to expand...
Click to collapse
I attempted using that as well, but it won't recognize the phone. It reads ``no device detected``
bblawless said:
I attempted using that as well, but it won't recognize the phone. It reads ``no device detected``
Click to expand...
Click to collapse
it seems that you're pretty f'ed up...
Is your phone charged..?
Sent from my PG06100 using Tapatalk
crump84 said:
Is your phone charged..?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
yes, it it charged.
bblawless said:
yes, it it charged.
Click to expand...
Click to collapse
Send your phone in for warranty then, or contact Adam directly see what he says could be wrong
Sent from my ice cream powered Nexus S using XDA premium HD app
I install slimroms 4.2.1 stable rom and went to reboot phone and now i cant boot it up. I tried getting into recovery or download mod by holding Home power and volume up or down but nothing happens. The screen just remains off. Is there a way around this or is it done?
Remove then reinstall the battery. Then try again. Cal you get into download mode?
Sent from my Nexus 7 using Tapatalk 2
search for how to fix a hard brick you mightve flashed a rom for a different carrier dude, something like that. if you cant boot into odin than its probably hard bricked. try leaving it for awhile and go back to it later, sometimes technology is weird like that. i doubt it though..
sob372 said:
search for how to fix a hard brick you mightve flashed a rom for a different carrier dude, something like that. if you cant boot into odin than its probably hard bricked. try leaving it for awhile and go back to it later, sometimes technology is weird like that. i doubt it though..
Click to expand...
Click to collapse
Well I'll be honest I looked at SD card and I flashed and i9300 rom on it. I've tried leaving battery and stuff but the phone just won't power on. Screen just remains off. When I plug into computer with battery out a red light comes on and phone tried to install a driver but doesn't install and Odin doesn't see. I have Samsung drivers installed so i don't know what it's trying to install. Am I screwed? Throw phone away? Lol
Google jtag. I don't think there's another way to get your phone fixed. Flashing an international rom is the surest way to hard brick.
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
Google jtag. I don't think there's another way to get your phone fixed. Flashing an international rom is the surest way to hard brick.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I head jtag doesn't work anymore after 2.3 android or maybe it was the jig I was reading about.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Hopefully someone will have another way to fix it but I'm pretty sure jtag is the only way.
Sent from my SCH-I535 using xda app-developers app
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!
ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
3 words: Dropbox Camera Upload.
exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app
iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.
I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app
phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question
okay i upgraded to 4.3 OTA and tried to revert back and soft bricked my phone. I still have access to download mode and the stock recovery. I know now that i can not revert but is there any way of getting it back to 4.3 so i can have a phone again?
thanks for the future help.
This is similar what happened to me. I have never done anything with my phone as far as rooting and I tried reverting to stock 4.1.2. In Odin I kept getting the "Nand Start! Fail (Auth)" because of the locked bootloader I guess. I flashed some other firmware that was unofficial with the locked bootloader and now I get the "unauthorized software detected" and I cant do anything but enter Odin download mode. What should I do?
that is exactly what is happing to me. same error and all.
Once you took the OTA 4.3 you got locked in. No way of going back.
Sent from my SCH-I535 using Tapatalk
I dont want to go back just get rid of the soft brick so i can use it
im having the same problem and need to get it fixed please help anyone???!!!! im leaving for florida in two days and have nothing else. HELP!!!!
If you took the OTA and tried to flash 4.1.2 Odin or unlock bootloader you are Hard bricked , no method or recovering it yet.
If you have stock recovery and download mode , only hope is wait for 4.3 .tar file
Theres no custom recovery I can flash and flash some other software or something?
Elemt said:
Theres no custom recovery I can flash and flash some other software or something?
Click to expand...
Click to collapse
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
jlyle said:
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
Do you know if anyone is working on a fix? or a .tar file of 4.3?
dvdavid2 said:
Do you know if anyone is working on a fix? or a .tar file of 4.3?
Click to expand...
Click to collapse
Thanks for the info. hopefully a fix will be done soon. And do you know how i should keep to see when the work around is finished .
thanks in advanced guys.
This might give you a chance to unbrick.... possibly
http://forum.xda-developers.com/showthread.php?t=2581166
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
ScubaSteev said:
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Any break throughs????
dvdavid2 said:
Any break throughs????
Click to expand...
Click to collapse
None that I have seen
Sent from my SCH-I535 using xda app-developers app
jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
BattsNotIncld said:
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
Click to expand...
Click to collapse
The first time I ever rooted, I was worried about bricking. So i read everything I could find relevant.
Why in the world anyone would flash without reading is beyond me. Every single thread in Verizon Galaxy S3 at least mentions, if not totally devoted, to how bad 4.3 is and if you flash something on it you will brick.
I just don't get it.
Sent from my Last Ever Samsung Device.
If you do a battery pull and start back up in download mode (might take a couple of times to get it to work) then use the Verizon software upgrade assistant it should fix it but you will be stuck with 4.3. Worked for me