I just want to understand what really happens when a phone is hardbricked. Like what is it that keeps it from turning on and why wont it just boot into download mode after the wrong rom is flashed. And what does jtag do that it allows it to boot again also why does it goes into something like qshub dload what is the true purpose for that and how is it that qpst can detect it can anybody answer these questions it would really help thanks
Sent from my SGH-T959V using xda app-developers app
HolyGhostBoy1 said:
I just want to understand what really happens when a phone is hardbricked. Like what is it that keeps it from turning on and why wont it just boot into download mode after the wrong rom is flashed. And what does jtag do that it allows it to boot again also why does it goes into something like qshub dload what is the true purpose for that and how is it that qpst can detect it can anybody answer these questions it would really help thanks
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Hard brick is most commonly achieved by flashing a rom for a different phone than what you have. It rewrites the partitions in the phone to one that the phone can't use. That's why nothing works after a hard brick
JTAG rewrites everything back the way it should be.
Sent from my SGH-I747 using xda app-developers app
HolyGhostBoy1 said:
I just want to understand what really happens when a phone is hardbricked. Like what is it that keeps it from turning on and why wont it just boot into download mode after the wrong rom is flashed. And what does jtag do that it allows it to boot again also why does it goes into something like qshub dload what is the true purpose for that and how is it that qpst can detect it can anybody answer these questions it would really help thanks
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
KorGuy123 said:
Hard brick is most commonly achieved by flashing a rom for a different phone than what you have. It rewrites the partitions in the phone to one that the phone can't use. That's why nothing works after a hard brick
JTAG rewrites everything back the way it should be.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hard Brick can be from flashing or messing with bad bootloaders (or even mixing them) as well. While that doesn't really happen on the S3 (since they made it really hard to brick it at the first place), it's seen a lot of other devices.
Related
I fixed my emmc brick with one of the PIT files circulating around. But I was wondering, when I want to flash with odin in the future, do I always now have to include that PIT file? And are there any Roms that won't be compatible with it? Also what should I do when flashing in CWM in the future? I don't believe there is a way to add a PIT file there...?
I'm pretty sure its just a one time thing to fix your emmc. You shouldn't have to use as long as you don't brick your phone again.
Sent from my SPH-D710 using xda app-developers app
brooksyx said:
I'm pretty sure its just a one time thing to fix your emmc. You shouldn't have to use as long as you don't brick your phone again.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Thank You, kind sir
So I'll do this fast, I ain't a noob with flashing and rooting etc (4 years experience) but today I had a first one in my life that soft bricked my T999V. I've downloaded the LiquidRom for T-mobile to test it, i've wiped all, cache and etc 3 times but the second time in the TWRP console it wrote and error like XXXXX directory not found ... I've never saw this type of error. So I flashed the rom + the latest Gapps , wiped dalvik an rebooted. The rom was blazing fast. But I decided to return to my Rom , so i wiped all again but still getting that error ! I restored the Nbackup and it rebooted wierdly and the rom was completly messed-up. So i close the phone and wanted to restard in recovery... Not existing anymore, gone.. GONE ! But i could boot in download.. I've completly recovert it right now but still this wierd error almost messed up my phon and it wasnt even my fault !
So did it ever happend to your S3 ?
I haven't experienced that yet and I hope I don't lol but at least it was only a soft brick. Thanks for the heads up though just incase someone runs into that problem.
So is everything running good now?
Sent from my SGH-T999 using xda app-developers app
If you would have messed your phone it would have been entirely your fault knowing your flashing custom Roms And Messing Whit These Things
Sent from my SGH-T999 using xda premium
shahkam said:
If you would have messed your phone it would have been entirely your fault knowing your flashing custom Roms And Messing Whit These Things
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
He's not saying it's anyone's fault or anything
Sent from my SGH-T999 using xda app-developers app
daxecutioner24 said:
He's not saying it's anyone's fault or anything
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
He stated he almost bricked his phone and that wasn't even his fault...
Sent from my SGH-T999 using xda premium
shahkam said:
He stated he almost bricked his phone and that wasn't even his fault...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
He means that he didnt deliberately do it. Perhaps he read everything and when he went to flash it it through an error. That happens. Could be a bad download or something
Sent from my SGH-T999 using Tapatalk 2
hey guys i was flashing an arhd rom and after flaw i wanted to romove bloat so i tried mounting by usb to load the file. in the mount section i checked ext/sd card phone went black and dead. does this mean that now only my sd card is read or mountable, can i load a recovery on my sd, put it back in and start from there? i have been flashing and developing for years and evidently to tired to attempt what i was doing. phone is DEAD. NO DWNLD MODE OR RECOVERY i'm thinking its trying to load just off of my sd. i know very stupid mistake, was used to HTC phones. any help much appreciated
shehade08 said:
I haven't experienced that yet and I hope I don't lol but at least it was only a soft brick. Thanks for the heads up though just incase someone runs into that problem.
So is everything running good now?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Yes i've Odin it and good to go !
Hi all at T999 xda dev community, I flashed a wrong ROM as for mistake was in the T999 ROM folder.
It started with AROMA and then after wipe cache / dalvik my T-Mo T999 does not boot at all, not CWM not PC not nothing.
I even try ODIN 3.04 but nothing appears-
Any hint ?
Thanks in advance.
M
What were you trying to flash?
Are you going into download mode before attempting Odin? (Vol down, home, and power)?
Sent from my SAMSUNG-SGH-T999 using xda app-developers app
What were you flashing? Sounds to be a hard brick, if you can't get into download or recovery mode then you're hard bricked.
Sent from my SGH-T999 using xda premium
Yes, it was flashing a S3 I9300 ROM on my T999, specifically the one at http://forum.xda-developers.com/showthread.php?t=1944035
then I tried all CMW options but nothing happend, no any recovery menu appears.
I think the only available option is a physical hardware JTAG reflash. I found some videos and info here,
http://www.youtube.com/watch?v=XnA8Djs55Ds
and at here:
http://androidheadlines.com/2012/10/featured-fix-your-bricked-galaxy-s3-the-official-way.html
any hint?
Yup, you're hard bricked. Sorry. The mist common place we see folks use here is mobiletechvideos.com.
A month or so ago someone mentioned using a different place that was cheaper and was just as good. Can't remember more than that though. Hoping someone else does.
Sent from my SGH-T999 using xda premium
KindMartin said:
Yes, it was flashing a S3 I9300 ROM on my T999, specifically the one at http://forum.xda-developers.com/showthread.php?t=1944035
then I tried all CMW options but nothing happend, no any recovery menu appears.
I think the only available option is a physical hardware JTAG reflash. I found some videos and info here,
http://www.youtube.com/watch?v=XnA8Djs55Ds
and at here:
http://androidheadlines.com/2012/10/featured-fix-your-bricked-galaxy-s3-the-official-way.html
any hint?
Click to expand...
Click to collapse
Gotta learn to read what model s3 the rom is for
Sent from my SAMSUNG-SGH-T999 using xda premium
I used a guy on ebay that had a lot of recent feedback and only charge 35 bucks. He fixed my phone the same day he got it and sent it back the next day.
Sent from my SGH-T999 using xda app-developers app
Hi. Before flashing PA I was on 1317m Rogers but after it switched to n7105. There's no problem with that right? Btw everything is working perfectly.
Sent from my GT-N7105 using xda premium
You can easily change it by editing build.prop using root explorer. Open root explorer, system press n hold build.prop use text editor then change model to l317M.
Thanks!
Sent from my GT-N7105 using xda premium
jon3sh said:
You can easily change it by editing build.prop using root explorer. Open root explorer, system press n hold build.prop use text editor then change model to l317M.
Click to expand...
Click to collapse
But what I'm trying to ask is instead of going to at&t and try to find a Rom that will work for my phone I can go to the GTn7100 and GT n1707 section and flash a Rom without any problems right?
Sent from my GT-N7105 using xda premium
Erichuynh said:
But what I'm trying to ask is instead of going to at&t and try to find a Rom that will work for my phone I can go to the GTn7100 and GT n1707 section and flash a Rom without any problems right?
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Sorry my bad, I would stay away from N7100 and N7105 section. There so many N7100 and N7105 ported rom for our device in att section so just use the ones from here. If read the changelogs of some roms here you will see MF2 roms are originally from N7xx roms.
Edit..
Flashing rom made for N7xx device can mess up your modem, imei etc. I
Thank you much much for this info. I did try to flash a n1700 Rom once and like you said I didn't get any connectivity on my Rogers carrier even when I found a modem to flash, and ended up having to go back to stock plus factory resets which is such a pain
Sent from my GT-N7105 using xda premium
Erichuynh said:
Thank you much much for this info. I did try to flash a n1700 Rom once and like you said I didn't get any connectivity on my Rogers carrier even when I found a modem to flash, and ended up having to go back to stock plus factory resets which is such a pain
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
You could have ended up with a brick.....
Or corrupted imei.
You can't flash n7100 roms
crixley said:
You could have ended up with a brick.....
Or corrupted imei.
You can't flash n7100 roms
Click to expand...
Click to collapse
This is my first Android phone so I didn't know
Sent from my GT-N7105 using xda premium
Erichuynh said:
This is my first Android phone so I didn't know
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Not trying to be rude, but just be very careful!
You don't want to end up with an expensive brick
crixley said:
Not trying to be rude, but just be very careful!
You don't want to end up with an expensive brick
Click to expand...
Click to collapse
Even when it's bricked is it still possible to actually get into recovery wipe all caches and do a factory reset then get back to stock Rom right?
Sent from my GT-N7105 using xda premium
Erichuynh said:
Even when it's bricked is it still possible to actually get into recovery wipe all caches and do a factory reset then get back to stock Rom right?
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Brick like dead screen, not responding to anything or wont show n your computer when connected to usb or simply expensive paper weight. Only way to revive it flash via jtag etc. There is also soft brick where its only black screen but you can still flash roms via Odin and flashing wrong rom can cause soft brick too.
Erichuynh said:
Even when it's bricked is it still possible to actually get into recovery wipe all caches and do a factory reset then get back to stock Rom right?
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
What he said above...
There is also a corrupt efs partition. If you didn't have it backed up you have no imei, and so you have a phone that can turn on but can't connect to any network, this can be permanent and has happened to people from flashing n7100 roms
crixley said:
What he said above...
There is also a corrupt efs partition. If you didn't have it backed up you have no imei, and so you have a phone that can turn on but can't connect to any network, this can be permanent and has happened to people from flashing n7100 roms
Click to expand...
Click to collapse
Yep I did more in depth research about the hard bricked phones and it sucks!
Sent from my GT-N7105 using xda premium
Erichuynh said:
Yep I did more in depth research about the hard bricked phones and it sucks!
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
yeah hard bricked or corrupted efs both suck :/
I have never bricked a phone and been using android since early 2009.
I'm crazy cautious
Back up of EFS is a must too, it is a good habit that you always have nand, modem csc patch and efs back up saved to you external card or computer.
Once your a little more familiar with your phone this is a good thread to check out http://forum.xda-developers.com/showthread.php?t=2018411. For the most part the i317 and 7105 are identical except for modem and gps files DO NOT FLASH A 7100 ROM Unless it has been modded following the posted thread. Personally i have been using Jedi x17 it has everything i want extended boot menu,Lidroid 23 toggles,speed tweaks etc... Now i have made my own modifications as well (status bar,speedometer and ringtones) I also have been working on modding MA3 rom as well in my spare time but really Jedi works just fine. Just my two cents. Good Luck and have fun,Dave
Hi there, I am trying to find a debrick image for I747M from Telcel or instructions on how to compile one, the image I can find is for canadian MK5 and I have MK3, I tried writing and using the MK5 image but get no response at all, any advice would be appreciated
If you're hard bricked you'll have zero response from turning it on. You'll need a JTAG service.
What did you do to brick it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
If you're hard bricked you'll have zero response from turning it on. You'll need a JTAG service.
What did you do to brick it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I tried to flash an MJB bootloader, the only response I get is red led when I plug in usb with no battery for about 30 seconds and then light goes off and nothing from any buttons, I tried the SD Image but can't seem to get it written properly I have tried win32diskimager and dd in ubuntu but neither way has worked or me, I am still in warranty and not so sure I can find someone in Mexico to do the JTAG.
4.4.2 debrick file
KorGuy123 said:
If you're hard bricked you'll have zero response from turning it on. You'll need a JTAG service.
What did you do to brick it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
sir 4.4.2 debrick file needed from ur phone if u can for my i747m rogers