Hi all
I was always under the impression that Samsung Phones are pretty hard to brick. I mean truly brick where you cannot get into download mode.So Im curious about a handful of things.
Is it true how hard/easy is it to brick a Samsung Note 2 or other Samsung phone?
What are the most common ways to brick the phone?
What is actually happening to the phone that causes it to brick? What should stop the phone from even getting to download mode?
PS. Im trying to up my post count so I can actually comment in threads where its releavant. ie ROM Dev threads.
The most common way to brick imo is to flash wrong bootloaders. You need jtag then.
But no need now. They brick their self
Sent from my GT-N7100 using xda premium
mariosraptor said:
The most common way to brick imo is to flash wrong bootloaders. You need jtag then.
But no need now. They brick their self
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I did laugh out loud -)
Sent from my GT-N7100 using xda app-developers app
TheDatabug said:
Hi all
I was always under the impression that Samsung Phones are pretty hard to brick. I mean truly brick where you cannot get into download mode.So Im curious about a handful of things.
Is it true how hard/easy is it to brick a Samsung Note 2 or other Samsung phone?
What are the most common ways to brick the phone?
What is actually happening to the phone that causes it to brick? What should stop the phone from even getting to download mode?
PS. Im trying to up my post count so I can actually comment in threads where its releavant. ie ROM Dev threads.
Click to expand...
Click to collapse
beware! of the sds bug. you may not be affected but heed my warning.
soljakid said:
beware! of the sds bug. you may not be affected but heed my warning.
Click to expand...
Click to collapse
According to the checker you can get on play store I don't have the offending chip. I also wonder if the Note 2 LTE version is affected it being a newer device?
Sent from my GT-N7105 using xda premium
I think all Exynos4 devices can be affected by super bricks if I'm not much mistaken. There was a lengthy post on this topic in Nov by one of the elite developers on this issue.
Sent from my GT-N7100 using xda app-developers app
SenK9 said:
I think all Exynos4 devices can be affected by super bricks if I'm not much mistaken. There was a lengthy post on this topic in Nov by one of the elite developers on this issue.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Wrong. Exynos were affected by the exploit not brick.
Only the affected nand chips had the brick bug but had nothing to do qith the CPU's.
Sent from my GT-N7100 using xda premium
In Note 1 and SGS2 we had the eMMC "Super Brick" bug. It triggered when you wiped data using stock ICS rom that had the bug.
In Note 2 and SGS3 we're dealing with defective eMMC chip that can randomly brick itself, so your phone just dies suddenly. It appears though that only the eMMC revision 0xF1 is affected by this bug. You can check yours with the eMMC check app from Play market.
Related
This dude over on t989 forums is soliciting a bricked device to be able to try to build his mod for them? Should we get him to do it for us too?
http://forum.xda-developers.com/showthread.php?t=1358401
Sent from my SPH-D710 using Tapatalk 2
satur9ine said:
This dude over on t989 forums is soliciting a bricked device to be able to try to build his mod for them? Should we get him to do it for us too?
http://forum.xda-developers.com/showthread.php?t=1358401
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Those guys sound like assholes. They basically run people off when they act like that, he is trying to help people out and they don't care.
*If* what I've been told is true then even flashing by USB cannot fix the bricks happening on Sammy devices. Stay tuned though by reading more on the following thread:
http://forum.xda-developers.com/showthread.php?p=25883319
Hey guys i have been having some real trouble working with sgs2 its a real pain now...I have a corrupted hard disk and its write protected doesn't allow to flash anything and i have tried every damn procedure even pushing it through the adb but the administrator does not allow to read it. I can flash nothing on it and the worst part is i cant even brick it even through odin. My friend who is a developer himself and works at telus wasnt able to do anything himself...Tried that even.. The phone is rooted and running Juggernaut 5.0 along with darkside kernel. It has been almost two months now since this problem has persisted...Is there any way i can brick my phone like hard brick that the phone does not turn on or just show black screen i want to get it replaced still have warranty..i paid 590 bucks for this phone and cant even sell it since i cant erase the memory. Please help me out with it.
Thanks
You've posted this same problem twice before. Posting it a third time isn't gonna help you.
Sent from my SGH-T989 using xda premium
JPOKeefe said:
You've posted this same problem twice before. Posting it a third time isn't gonna help you.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well he still has not received help. Why would you make a ****ty post like that. Help the guy or don't post.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
If you want to brick it flash an Odin kernel package from different phone.
Edit: I missed that you tried Odin already on my first read through.
Really strong magnets, maybe?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
billydroid said:
Well he still has not received help. Why would you make a ****ty post like that. Help the guy or don't post.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
He has received answers in his other posts and I only said what I said up there because double/triple posting is against the rules and I didn't want him to get in trouble.
Sent from my SGH-T989 using xda premium
billydroid said:
If you want to brick it flash an Odin kernel package from different phone.
Edit: I missed that you tried Odin already on my first read through.
Really strong magnets, maybe?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Its flash memory not a HDD
Sent from my SGH-T989 using xda premium
can you get into CWM at all??
http://forum.xda-developers.com/showpost.php?p=24362630&postcount=14
You can brick your device by flashing junk to the sbl1 block
http://forum.xda-developers.com/showthread.php?t=1578184
JPOKeefe said:
He has received answers in his other posts and I only said what I said up there because double/triple posting is against the rules and I didn't want him to get in trouble.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well i did receive answers and they were very supportive as well but it did not solve the problem and to be honest i did not even know the nature of the phone until now. I believe it would not harm anyone.
I just need a little help and i will be willing to donate as well.
Damn, still? That sucks dude!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
As of right now, the roms for your S3 are not meant to be used on other S3 variants. Bricks might happens or a soft one might happen. Before flashing a Rom make sure you are in the right development section an you read the entire op, twice. Until other devs or experienced users find a way to make them cross compatible, please refrain from using other carriers S3 roms.
I am working on this so that all roms will work on all carriers
http://forum.xda-developers.com/showthread.php?t=1735482
Man 90% of the time memebers don't read the "everyone read this" thread on any forum
Mostly cause its just filled with rules and etiquite
How have to capture there attention with the title
Sent from my SPH-D710 using xda premium
Tell me about it, I guess you just be glad you did and move on
Lol it was my idea I just pmed it to Mr.highway
Sent from my SPH-D710 using xda premium
incubus26jc said:
I am working on this so that all roms will work on all carriers
http://forum.xda-developers.com/showthread.php?t=1735482
Click to expand...
Click to collapse
That's slick!:good:
hard brick - a pretty paperweight (tonight)
should have been more careful, soft bricked the phone, 2 times trying to change the dpi.
once trying to flash a rom - the rom flash, took it to QHSUSB_DLOAD mode, not impressed but i'll take this downtime as a time to relax.
Another way to avoid a brick; Don't use a mod, theme, tool or ROM until it's confirmed by multiple people in the community that it's working properly. Read the last 3-4 pages of a thread
Sent from my SPH-L710 using Tapatalk 2
fergie716 said:
Another way to avoid a brick; Don't use a mod, theme, tool or ROM until it's confirmed by multiple people in the community that it's working properly. Read the last 3-4 pages of a thread
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
What fun is that?
piiman said:
What fun is that?
Click to expand...
Click to collapse
lol
Sent from my SPH-L710 using xda premium
Simple...
Do like we all have done: read everything you can find and then ask an intelligent question. Otherwise, XDA denizens get grumpy... :cyclops:
Aint' that the truth, I'm one of them!
gtuansdiamm said:
Man 90% of the time memebers don't read the "everyone read this" thread on any forum
Mostly cause its just filled with rules and etiquite
How have to capture there attention with the title
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I agree with you, I ended up with a soft brick stuck at the samsung glowing logo after trying to unroot because I got a crack the front plastic near the headphone jack. I managed to reset the flash counter and install the rom but odin failed at the end. Now I'm hesitant to flash another ROM. Anyone else here waiting for JellyBean Rom? Definitely take your time and always make sure your computer installs the drivers before doing anything! I got BB to exchange it for me since they couldn't get it to boot and the mystery crack wasn't my fault. I only had it for like 3 days IN A CASE TOO. Happy Flashing dudes.
I'm just glad i saw a forum for the gs3. I would've bricked my phone after i got it.
Another bricker my own fault went to unroot to take in for service and went and loaded a wrong .tar file of the stock system. Anyway...not looking for sympathy..just wanted to say thanks for the forum that gave me the tools to fix my mistake :thumbup:
Sent from my SPH-L710 using Tapatalk 2
Just a question that seems to pertain to this thread, what's the difference between sprint sgs3 android development and original android development?
Sent from my SPH-L710 using xda app-developers app
xblackvalorx said:
Just a question that seems to pertain to this thread, what's the difference between sprint sgs3 android development and original android development?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Original is usually built from scratch/source. Android development is based from stock, leaks or ports
Shadefactor said:
Original is usually built from scratch/source. Android development is based from stock, leaks or ports
Click to expand...
Click to collapse
So as long as it's in the Sprint sgs 3 forums it's safe?
Sent from my SPH-L710 using xda app-developers app
You are correct sir!
biglos201 said:
I agree with you, I ended up with a soft brick stuck at the samsung glowing logo after trying to unroot because I got a crack the front plastic near the headphone jack. I managed to reset the flash counter and install the rom but odin failed at the end. Now I'm hesitant to flash another ROM. Anyone else here waiting for JellyBean Rom? Definitely take your time and always make sure your computer installs the drivers before doing anything! I got BB to exchange it for me since they couldn't get it to boot and the mystery crack wasn't my fault. I only had it for like 3 days IN A CASE TOO. Happy Flashing dudes.
Click to expand...
Click to collapse
Mystery crack is the best
The Archangel said:
As of right now, the roms for your S3 are not meant to be used on other S3 variants. Bricks might happens or a soft one might happen. Before flashing a Rom make sure you are in the right development section an you read the entire op, twice. Until other devs or experienced users find a way to make them cross compatible, please refrain from using other carriers S3 roms.
Click to expand...
Click to collapse
I think I just made that mistake...wrong directory in a mirror...
ANyhow I ended up with a QHSUSB_DLOAD device...looking hard to unbrick...
My Galaxy s3 is now what appears to be a hard bricked phone. The only response I get is a red light when I plug it in and a bing when I plug it into the usb port. No recognition by the computer though.
This was caused by me trying to flash the kernel to a very common one (siyah) and after it completed successfully I did a reboot, now it won't turn on or go into CWM recovery or basic android recovery.
I've exhausted every possibility I can think of /googled to solve it such as.
1) Taking the battery out
2) Trying to make Odin recognize it
3) Trying to boot into the various recoveries
4) Trying many a different button combos
5) Leaving it to charge for a while
The only think I can think of that I haven't tried is a USB jig.
My question is, what now? Help me, please.
Well your first issue is that we don't have a siyah kernel for the i747. So, yeah.
You might need to try a jig. I if that doesn't work then you will need to send it off to get jtag fixed.
Sent from my SGH-I747 using xda premium
d3athsd00r said:
Well your first issue is that we don't have a siyah kernel for the i747. So, yeah.
You might need to try a jig. I if that doesn't work then you will need to send it off to get jtag fixed.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
+1 with sending the device to jtag
Sent from my SGH-I747 using Tapatalk 2
Since you flashed an i9300 kernel, likely with bootloaders, and it won't do anything you will need to send it off for JTAG repair.
JTag time. You've flashed a kernel not meant for our device.
Thanks guys, I figured that was probably my only option. And I feel really dumb now. I'm used to jailbreaking, rooting it seems, requires you to be much more vigilant.
Thanks again.
kshawn123 said:
Thanks guys, I figured that was probably my only option. And I feel really dumb now. I'm used to jailbreaking, rooting it seems, requires you to be much more vigilant.
Thanks again.
Click to expand...
Click to collapse
I'd say it requires common sense. Don't flash something that's not meant for your phone!
mbc663 said:
I'd say it requires common sense. Don't flash something that's not meant for your phone!
Click to expand...
Click to collapse
ding ding ding
Sent from my SGH-I997 using xda premium
mbc663 said:
I'd say it requires common sense. Don't flash something that's not meant for your phone!
Click to expand...
Click to collapse
Not helpful.
task650-JTag time. You've flashed a kernel not meant for our device.
Helpful
kshawn123 said:
Not helpful.
task650-JTag time. You've flashed a kernel not meant for our device.
Helpful
Click to expand...
Click to collapse
What is jtag and what does it do? Just curious lol
Sent from my SAMSUNG-SGH-I747 using xda premium
Smittyzz said:
What is jtag and what does it do? Just curious lol
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Youtube and research my friend. Nearly can fix any phone no matter how bad you mess it up. Very rare that a JTAG can't fix a phone.
xThe Enforcer said:
Youtube and research my friend. Nearly can fix any phone no matter how bad you mess it up. Very rare that a JTAG can't fix a phone.
Click to expand...
Click to collapse
sure you can't get into download mode? try this? http://forum.xda-developers.com/showthread.php?t=1727443 (that link is for AT&T only)
xThe Enforcer said:
Youtube and research my friend. Nearly can fix any phone no matter how bad you mess it up. Very rare that a JTAG can't fix a phone.
Click to expand...
Click to collapse
Thanks for the reply, shouldn't have been so lazy lol, headed to youtube now
Sent from my SAMSUNG-SGH-I747 using xda premium
chaos2oo2 said:
I have another question:
currently there are two ways to return from whatever back to stock rom:
Mentioned here:
http://forum.xda-developers.com/showthread.php?t=2543350
http://forum.xda-developers.com/showthread.php?t=2471370
This involves the LG Tool to restore the image from their servers. Does this mean the G Pad is virtually unbrakeable (unbrickable)? So that I always can do the Factory reset when I messed something up during root/flash? Or are there any chances I can do something that really brakes the G Pad and makes it unusable?
Kind regards,
Michael
Click to expand...
Click to collapse
No one replied to this persons thead, and i have the same question, so i made a new thread
henrikpw said:
No one replied to this persons thead, and i have the same question, so i made a new thread
Click to expand...
Click to collapse
Nothing is unbrickable, it all depends how badly you screw it up.
Check the v510 conversion thread for details, but nobody will tell you universally a device is unbrickable, and if they do, they are liars.
All devices are brickable if you really screw things up. But most devices are really hard not to save. Normally you have to do something major like flash something not meant for the device. I know of a member in this forum who bricked his V500 and has yet to recover. Doesn't mean he wont just means it will be hard to. Just read carefully and follow the instructions and you will be fine
Sorry @Sean09 didn't mean to say the exact same thing in my first line . One of those times you post before you read everything.
It is unbrickable. Even if you have messed with the rom and the recovery the lg mobile support tool can flash the stock recovery and rom as long as you can enter into download mode though. Now if things get worse you can send it to lg and they ll unbrick it for sure with a jigkick battery or something like that, but you may have to pay as it may not be covered by the warranty.
If you physically damage the hardware, you'll probably end up with a brick. However, LG devices are very recoverable. Wkparks tool for the O3D put severe bricks into download mode and allowed you to reflash a ROM.
Sent from my GT-I9300 using xda app-developers app
I like to think that anything can be bricked. Recently I totally bricked my BIOS for example and those things are extremely hard to fix so the same thing goes for mobile platforms. Anything is brickable and that is where you shouud put the line on, however with the community help that we have today a lot of problems can be solved by others like for example here on xda!
Sent from my LG-V500 using Tapatalk
katsika said:
It is unbrickable. Even if you have messed with the rom and the recovery the lg mobile support tool can flash the stock recovery and rom as long as you can enter into download mode though. Now if things get worse you can send it to lg and they ll unbrick it for sure with a jigkick battery or something like that, but you may have to pay as it may not be covered by the warranty.
Click to expand...
Click to collapse
See that is the thing, if you mess it up you won't be able to get into download mode. That is what happened to androiduser after flashing the V510 recovery, modem and firmware to his. He sent it to LG and the told him tough luck and sent it back. Be very careful
Sent from my LG-D800 using XDA Premium 4 mobile app
joshuadjohnson22 said:
See that is the thing, if you mess it up you won't be able to get into download mode. That is what happened to androiduser after flashing the V510 recovery, modem and firmware to his. He sent it to LG and the told him tough luck and sent it back. Be very careful
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well i had the impression that the guys at the service center could unbrick the device no matter what has happened to it but i could be wrong.
joshuadjohnson22 said:
See that is the thing, if you mess it up you won't be able to get into download mode. That is what happened to androiduser after flashing the V510 recovery, modem and firmware to his. He sent it to LG and the told him tough luck and sent it back. Be very careful
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
from what i read, not being an expert to it though, AndroidUser is giving the process of recovery to his gpad a new try:screwy:
Sent from my Thrive using Tapatalk 2