yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] ndwgs:
[MENTION=3505796]KAsp3rd[/MENTION] [MENTION=4081205]DocHoliday77[/MENTION] [MENTION=4851668]foreverthewolf2012[/MENTION]

Guys... especially Kasp3rd and Doc... I was skimming thru articles about why the sbl3 would eventually brick you... But I did stumble upon an old article about "eFuse" why it worked. Interestingly enough, the article had a "Update 3" at the bottom where the person contacted Motorola about eFuse.

I wondered if there's a way to "Force" push the full tar / pits into the phone? That way the "system" would see and check that "it is the approved appropriate software" and "unbrick" the situation? I mean, the hardware is not like back in 2008 when they're testing this eFuse on hardware of the phone (unlike computer rigs or microsoft that has known to have used this "kill switch" for hackers in my day).

Here's the old

article

, more to come, i'm reading more to this. I mean think about it.... I still have the old phones of the mid 2001's, where Nokia's the flagship of the day, and opened them up, compared to the newly redesigned hardwares of the now... BIG difference in the manufacturing. Phones now are actual miniaturized size of computers. Not just soldered residual memory chips of before. Then they spotted efuses in the Motorola's? Motorola, back in the droid days, are manufactured HERE, where the CEO have collaborated with big whigs such as Intel/NVidia/Microsofts to "Revolutionize" the cellphone industry.

It's seriously worth the shot. I don't think it is fully bricked. If we can still manage to brick, dibrick, semi brick, i think there's a way. I'm gathering my age old computing knowledge and see it in a hacking eyes, how "they got around the fuse switch" that made hacking and redistributing Microsoft software easy. I'm sure it's the same way for these phones now.

/JustAThought

Edit:

Maybe another reason, in my belief, that SBL3 is the "Kill Switch"
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
There is a way however without the appropriate files needed for qpst there is nothing we can do as far as forcing the software into the device.

However as I've been successful in the past with secondary booting from sdcard I still have hope to bring doc and forever back from the graveyard.
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
Man I hope so lol
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
[MENTION=4851668]foreverthewolf2012[/MENTION] [MENTION=4081205]DocHoliday77[/MENTION] Here's a backup of the 4.3 bootloaders https://copy.com/7ICfKXMC3ccr
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
Im download mode now gonna flash stock 4.12 thank you soooooooo mucccccchhhhhhhhhh you rock I would totally kiss you but yeah lmfaooooooooooooooooooooooooooooooooooooooooooo
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Don't think you'll be able to flash 4.1.2 bootloaders but you can try lol

[MENTION=4081205]DocHoliday77[/MENTION] your turn to tell us some good news.
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
Yeah no luck with flashing the 4.12 so I guess imam have to go back to 4.3 o.o lol but hey atleast it will work huh hehe
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
You can flash a custom 4.1.2 ROM can't you?
[T-Mobile, Samsung Galaxy SIII] scifan:
But at least your phone is back from the dead even if your stuck on the 4.3 firmware...

It's a start
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
OMG where is the link to 4.3 tar file I can't find it lol
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
I don't know if there is one yet... Lucky for you I know where one was :) http://www.hotfile.com/dl/255688050/412267d/T999UVUEMJC_T999TMBEMJC_TMB.zip.html

It's posted by samfirmware and it's kies software so it should be the full thing
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
What I flashed

http://www.androidfilehost.com/?fid=23212708291679687 there's the link to what I flashed 4.3 and thur odin and thank you all for all of the help on getting my baby fixed and Good LUCk DOC I hope this work's for you as well
[T-Mobile, Samsung Galaxy SIII] calexchelse:
Doc I'm anxious to here weather it worked our not.

TW 4.3 WITH A TOUCH OF KITT KATT
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Question, did you try the one I posted yesterday? Looks the same as the new one.
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
O.o

Now im stuck in fricking recovery mode firmware upgrade encountered a problem and Im trying to get kies to see the phone but it wont God this never ends does it lol
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
He got recovered with an updated debrick image I made from a stock 4.3 device. I'll post it in the OP when I get back to a PC
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
Yeah but now Im stuck in recovery download mode it encountered a problem and kies just keep's scanning n scanning but won't find it Man I don't know what the heck is going on lol Im sure it's nothing more than a User error on my part but shesh Ive never had these kinda issues before
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Can you use the kies file in Odin?
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
When you get it into download mode you might have to take the sdcard out so it will write to the phone properly. I had another user that had to do the same thing.
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
Well I can't get out of the recovery screen now lol it just keep's rebooting back to it and I have the sdcard out and still nothing
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Are you in download mode? I'll see what I can do to make a tar.md5
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
It say's Firmware upgrade encountered an issue please select recovery mode in kies and try again witch I have done already and it ask me for some code that I don't have lol and if I reboot the phone with the debrick software again it just take's me right back to that screen

---------- Post added at 03:42 AM ---------- Previous post was at 03:41 AM ----------

It failed when I was using the tar file using odin back to stock 4.3 and then this poped up on my phone and won't go away and kies just keep's running ive reinstalled the drivers twice now and restarted the PC and still nothing
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Try holding the keys to get into download mode (I think it's voldown and home)
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
I just did that and now got it back into download mode and this time im trying it with the sd card not in the stuiped thing lmao

---------- Post added at 03:50 AM ---------- Previous post was at 03:47 AM ----------

I think it's gonna work this time lol it's like half way and last time when it messed up it was only like a 1/4 into it lol

---------- Post added at 04:01 AM ---------- Previous post was at 03:50 AM ----------

YAY lol It's ALIVE bwahahaha lol Thank you so much DOC and K for all of ya'll help n so fourth and yeah it does help to read ugh my downfall lol but yes flashing the debrick to sdcard then booting up to download mode and using the tar file I linked in this thread with Odin and then taking out the sdcard before using Odin and then clicking Start in Odin with that file and low and behold BAM it's back up and running with stock 4.3 YAY
[T-Mobile, Samsung Galaxy SIII] anil2653:
Thanks to our Great XDA developers.

With this we hope we will be able to counter with this Knox and whatever SAMSUNG is getting to cut own customer database and surely it is going to harm Samsung.

Thanks again.
[T-Mobile, Samsung Galaxy SIII] ndwgs:
Good stuff. I knew it wasnt bricked. Just like a computer. Great work [MENTION=3505796]KAsp3rd[/MENTION]!
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
Bwahahahahaha Now we just need some one out there to figure out a safe way of getting us all off this 4.3 rom and back to a stock 4.1.2 lol
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Doubt that is doing to happen given the fact that I'm pretty sure when 4.3 hit there was something in the updated boot loaders that "blew" an efuse or set to force a version check
[T-Mobile, Samsung Galaxy SIII] ndwgs:
Yup [MENTION=3505796]KAsp3rd[/MENTION]. My suspect is one of the sbl. Flashing in sequence, like what Doc did, spark chain of events. Sbl3 easy to suspect, but... Who knows
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
Well dammit man lol guess Im stuck with this ****ty ass rom until I save up and go buy me a new phone lol Maybe I can trade this one off on craigslist for a nother s3 lmfao
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
You should be able to flash a custom rom. Do a nandroid and try to flash a custom ROM. Not an official one. Hell even a stick deodexed ROM should work.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
OP Updated with the 4.3 debrick.img as well as instructions for using Windows.
[T-Mobile, Samsung Galaxy SIII] scifan:
So [MENTION=4081205]DocHoliday77[/MENTION] did you manage to resurrect your phone?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Negatory.

I'm starting to wonder if the sbl3 dumpfile might've been corrupt, and if so could it have screwed up my partition layout. I really just don't know what's up with this blasted thing! Absolutely zero response! Gonna try one more thing and call it the end of days for this particular device....

Perhaps it could also be that it's mixed firmware now too. Sbl2/3, system, modem are MJC, kernel is MJ2, aboot, rpm, tz are all LJC! With all the b.s. "security" Sammy built in, it may be confused or something! Leave it to me to do the one thing they never took into account when building it!

Nearly a week now with no phone....talk about booorrring!!!
[T-Mobile, Samsung Galaxy SIII] norm182:
Great to hear of success! Excellent job xda!
[T-Mobile, Samsung Galaxy SIII] scifan:
That's disappointing.
[T-Mobile, Samsung Galaxy SIII] jmcoffey:
This worked fantastic! I had a little trouble finding the SD card but that fixed me right up!
[T-Mobile, Samsung Galaxy SIII] ad.hoc:
[MENTION=3505796]KAsp3rd[/MENTION] I just wanted to thank you for posting this guide and helping me unbrick my phone, but I have another problem now and i'm not sure you can help me. When I wrote the image to my 32gb microsd card, it erased everything(like you said it would) but now only shows 52mb of total space. I tried to format numerous times but refuses to go back to 32gb. Is there anything I can do?
[T-Mobile, Samsung Galaxy SIII] javichampi:
You can use gparted on Linux or Minitool Partition Wizard on Windows to remove all partitions and create only one partition with your 32 gb.

Enviado desde mi SGH-T999 mediante Tapatalk
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
You can use windows Sd formatter program it's very simple and worked like a charm you can do full erase and it was done in about 10 sec's and back to working great
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sdcard.org has the sd formatter tool for Windows.
[T-Mobile, Samsung Galaxy SIII] Vigz:
*sigh* Well, the old debrick image didn't work for the phone, however, the new 4.3 debrick image did. I hate to say this, but there seems to be no way to revert back to the MD5 bootloader. For anyone who wants to root their phone and avoid losing warranty, I think it is recommended to avoid updating to 4.3 through OTA or via Odin.
[T-Mobile, Samsung Galaxy SIII] ad.hoc:
So, I followed all of the directions, wrote the correct debrick image to my sd, booted into download mode, downloaded the correct stock rom so I can flash through odin, but every time I try to, Odin says fail. Anyone know why this is happening? BTW, I was on Carbon 4.3 when my phone decided to brick on my a few nights back, and I had CWM recovery, though I don't know what help this info will do.
[T-Mobile, Samsung Galaxy SIII] foreverthewolf2012:
At some point n time you have official 4.3 touchwiz rom on your phone so you will have to odin back to stock 4.3
[T-Mobile, Samsung Galaxy SIII] pbpatel1981:
hi

I have T999L hard brick any debrick file on it? link would be nice
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Its in the op
[T-Mobile, Samsung Galaxy SIII] akure1831:
Bricked sch-r530m

I have a bricked SCH-R530M anyone have a link for a 4.3 Debrick Image?
[T-Mobile, Samsung Galaxy SIII] netsmagic:
seek argument

I get an invalid seek argument error when i try to display the partition table after writing the image. Is there a fix for this?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Check the Sprint forums. You should find all the R530 users there. No one with that device will see your post here unless you get very lucky!

You talking about this command?

sudo parted /dev/sdX print

And this step is just to check. If you got no write errors and it showed number of records in/out, just try it out.
[T-Mobile, Samsung Galaxy SIII] netsmagic:
Yes it does happen at that command, but when I try to verify the disk in gdisk, i get an error because there are some partitions written outside the range of the card. It appears to be a few sectors short of space. I tried testing this theory by writing the image to a flash drive with more space just to see if I still got the error and it ran fine with no such error. Does this mean i simply need to get a bigger microsd card?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Minimum of 16gb required.
[T-Mobile, Samsung Galaxy SIII] netsmagic:
Yes, I understand that, but the thing is that the card I have is advertised to have 16GB, but in reality, it comes up to around 14.63GB. Which apparently is just a little short. Is there a specific format I can use where I can get a little more memory squeezed out of the card? Or would changing from 512 sector size make a difference?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Have you formatted the card using the sd formatter tool from sdcard.org?
[T-Mobile, Samsung Galaxy SIII] netsmagic:
Yes sir. And it comes out to 14.63 GB. I feel like it should be a little more though. Is something wrong with the card? I mean I already needed a new one anyways so I ordered a larger one already, but I am just curious.
[T-Mobile, Samsung Galaxy SIII] serio22:
14.63 gb is normal
[T-Mobile, Samsung Galaxy SIII] netsmagic:
hmmm, then I dont know why I'm getting this read error then. It won't show me partition table. It just quits. I guess it this specific card that has an issue. Because when I do the same procedure on a storage device of bigger space, i have no problems.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Try putting the card in your phone anyway.
[T-Mobile, Samsung Galaxy SIII] netsmagic:
I have. Well now I have my new card: a 32 gb class 10. Everything copies just fine and when I put it in the phone actually vibrates as if it booting (it didnt before), but the screen remains blank.

EDIT: After I charge my phone a little bit everything loaded up and I was able to download the firmware back onto the phone!! =D =D . Thanks for your help and Doc too! This was a life saving thread!
[T-Mobile, Samsung Galaxy SIII] Acesohigh:
Windows Instructions

are there any detailed instructions for windows posted? Like what is the minimum sdcard size needed? Details peoples. Thanks xD
[T-Mobile, Samsung Galaxy SIII] Abskurity:
is there anyway to write this directly to the phone without the SDcard?

ive asked everyone i know and i cant afford a 16 GB class 10 card right now.

someone suggested i try using QPST.

im pulling my hair out over here this is my only phone.
[T-Mobile, Samsung Galaxy SIII] Acesohigh:
When I tried earlier with a class 4 8GB sdcard it didn't fully work. It no longer said qhusb when connected to PC as instead the PC didn't do anything when connected as if nothing was connected at all. And it also would not power on into Download mode, recovery anything like it had only a dead battery. But when the sdcard is removed its back to saying qhusb when connected like a hard brick. Using windows like the majority of humanity that owns a PC.
[T-Mobile, Samsung Galaxy SIII] Abskurity:
I Think Theyre Saying You Need A Minimum of 16GB SDcard in order for this to work,becuase from what im understanding the sdcard needs to emulate the phones actual filesystem.

if youre using windows,theres a link somewhere for win32diskimager from sourceforge somewhere in this thread.i think you download the DEBrick image and load that into the win32diskimager,then select your 16GB sd fro the menu in that program.if you bricked from attempting to downgrade your bootloader from 4.3 like i did,youre gunna need the 4.3 Debrick file.

this,of course,assumes youre running a T999 on USA Tmobile.

best i can do man,lol,im still waiting on finding an sdcard as i speak.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
You pretty much hit the nail on the head. Some notes to that though, you cannot downgrade the bootloader. Few have tried, all have failed. You do in fact need at least a 16G card. Doesn't need

To be class 10 though I did it with a class 4.

There is a brief windows explanation/tutorial in the OP with the link to win32diskimager.
[T-Mobile, Samsung Galaxy SIII] ChinoSupreme23:
I did everything but the only response I get from the phone is the camera flash flashes once really fast nothing else and it only does it once in a while

---------- Post added at 02:25 PM ---------- Previous post was at 02:17 PM ----------

I'm getting the same error, won't show me partition table either. Did you find a fix ?
[T-Mobile, Samsung Galaxy SIII] Acesohigh:
I did everything in the windows section of the OP. And yes I have the US T999 and T999L. I just think it didn't work because the lack of space. I accidently flashed my aboot(bootloader) from my 4.3.1 T999L onto the 4.0.4 T999 as well as partitions 10 and 11.
[T-Mobile, Samsung Galaxy SIII] Abskurity:
I Just want to confirm that this method worked for me also on the T999 USA TMobile Variant.Thank You Guys So Much,esoecially OP!You're a life saver!
[T-Mobile, Samsung Galaxy SIII] netsmagic:
Just used a bigger card. was using 16 n swiitched to a 32 thats all
[T-Mobile, Samsung Galaxy SIII] Acesohigh:
So...will 16Gb work? My friend is beating me up cause I don't have it fixed yet
[T-Mobile, Samsung Galaxy SIII] Abskurity:
Yes,A 16GB Will In Fact Work.i went and picked up a 16GB class 6 at my local target and used Win32diskimager to do the trick.OP has the instructions.follow them from the windows instructions down to a T,it wokred for me.:victory:

my 16GB SD in all actuality showed

.

if it doesnt show that,its prob a formatting issue.

i downloaded the SDCard Formatting tool v4 from This Site

if you do a proper format it Should show 14.9 GB.

also,to note,after the process use the same tool again,becuase it will show something crazy like 59MB total space after using the Debrick Image.
[T-Mobile, Samsung Galaxy SIII] Acesohigh:
Thanks bruh bruh. Dude now I can relax lol. Thanks again all. This s3 stuff is totally different from an S-Off HTC device.
[T-Mobile, Samsung Galaxy SIII] ChinoSupreme23:
Just picked up a 32GB and it worked like a charm, now I just need the 4.3 firmware to flash in Odin can't seem to find a link
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
http://www.androidfilehost.com/?fid=23212708291679687
[T-Mobile, Samsung Galaxy SIII] ChinoSupreme23:
Would flashing a rom through recovery fix the bootloader ?
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Negative. You need to flash an Odin package with the proper bootloaders
[T-Mobile, Samsung Galaxy SIII] scifan:
And this is still a one way flash right?
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
If you bricked with <4.3 bootloader then you can use the 4.1 debrick and restore back to 4.1. However of you bricked with 4.3 bootloaders installed then you can only recover and reflash 4.3 bootloaders
[T-Mobile, Samsung Galaxy SIII] scifan:
That's pretty much what I thought...
[T-Mobile, Samsung Galaxy SIII] akure1831:
Any one have a debrick image for metropcs GS3 SCH-R530M bricked on 4.3??
[T-Mobile, Samsung Galaxy SIII] cLogic:
pssst

hello ... I've been away from the forums for awhile (waves to Doc) so I just saw this thread today

I have an SGH-T999V on Videotron (VTR)

it was on stock 4.1.2, rooted and de-bloated, and then I flashed the 4.3 update from samsung-updates.com via Odin on pc

however re-rooting was not successful .. samsung enforced SElinux was blocking superSu and superSu was closing immediately

so I restored My nandroid backup and reverted to 4.1.2, rooted and de-bloated

some research has shown Me that rooting with a version of superSu that is Not the latest possibly allows superSu to actually launch without being blocked so that it can ask to update it's binary and this allows the foot in the door to update, reboot and bypass the block and gain successful root ... I will try this method this weekend

so ... My version is 4.1.2 however My baseband is MK5 which is the T999V 4.3 baseband .. and My device status says ****ed ... hehehe, just kidding, it says Modified :laugh:

see screenshot for device info

do you still need any images?

is Mine useful?

lemme know what you'd like Me to do

cheers
[T-Mobile, Samsung Galaxy SIII] cLogic:
forgot the screenshot, doh! :eek:
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Actually a 4.3 V boot loader would be awesome to add to the collection. In the OP there is a link to the boot loader backup.zip that creates the Unbrick.zip (that contains the debrick.IMG). If you could flash that and upload the Unbrick.zip it would be a nice addition.
[T-Mobile, Samsung Galaxy SIII] cLogic:
ok ... but WARNING ... My "warranty bit" is now 1 and so is the SW flag ... sure you want it?
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Yeah, that is fine. It won't bother those that need it.
[T-Mobile, Samsung Galaxy SIII] cLogic:
ok, just downloaded your backup zip .. gonna boot into recovery and do it now ... where would you like Me to upload it?

I'll check your response once I reboot system :)
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Anywhere of your choice. You can shoot me the the link in a pm or post it here.
[T-Mobile, Samsung Galaxy SIII] cLogic:
uploaded, link sent, check your pm
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
OP updated and thanks again for the upload.
[T-Mobile, Samsung Galaxy SIII] gonzalo8642:
not working?

I downloaded ihackers miui rom and i didn't notice that it was for the international version.

I was on liquid smooth (4.3 i think) before i flashed iharker's roms. I tried both brick images, non 4.3 and 4.3, and none of them work.

I followed the steps correctly and i used the windows instead of ubuntu

Can anyone help me out?

here is the link to iharker's rom

http://xdaforums.com/showthread.php?t=2477138
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Can you provide a little more information? What is your phone actually doing? Which exact model do you have?
[T-Mobile, Samsung Galaxy SIII] gonzalo8642:
I have a tmobile t999 and I am pretty sure it is hard bricked. I wanted a miui ROM but I ended up flashing ihackers international ROM.

The reason ik that it is a hard brick is because I have soft bricked it before and the logo would show up with the menu key and back key lighting up. Now the phone doesn't go to the boot logo, no sound, no keys lighting up, and I can't get into recovery or download mode.

When I take off the battery and plug my phone into my computer the notification lights up red. My computer also makes the sound something is connected. If I hold the power button (as it is connected through the USB cable) to hard reboot, my computer does the same sound as if the phone works

Also thanks for the quick reply
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Okay, you have hard bricked. You are positive that you have the t999 and not the t999l or t999v? Also, what size sdcard are you attempting to use to restore the debrick image to?
[T-Mobile, Samsung Galaxy SIII] gonzalo8642:
Ya I'm using the t999. I am using a 2 GB sandisk SD card. I also have a 32 GB but I didn't wanna lose everything on it
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
You need at least a 16g SDcard. You can copy everything from the 32gb to your computer before you restore the debrick.IMG to it and when you are done restoring your phone you can copy everything back.
[T-Mobile, Samsung Galaxy SIII] sonwon:
2GB will not work, read the OP it says 16GB or 32GB. The OP should update the text to make that clearer.