yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Looks like with that kernel you actually overwrote the aboot which, in fact would have bricked your device.

DO

NOT

USE

THE

FOLLOWING

write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p5"),

mmcblk0p5 is not the boot.img on our device but instead it is the aboot

That partition is one of the partitions that are backed up in the backup images. I don't always expect the phone to fully boot when using this method to debrick your device, however if you have the correct image for your device you should able to boot into download.

4 questions

When you plug your phone into the computer without a battery in it does the red light only come on?

What size microSD card are you using?

How long did you hold the power button to try to get it to turn on?

Which variant of the Galaxy S3 do you have?
[T-Mobile, Samsung Galaxy SIII] kimdoocheol:
1.) Yes.

2.) 16gb

3.) A long time, lol. I tried short bursts and long bursts.

4.) T999. I think? The t-mobile variant for the USA

It is weird. Before when I would plug in my device it would make a sound like it was trying to mount the device, and then make a disconnect sound. This time when I plugged in my chord, tried to boot with the new sd, it tried to install a driver. I know the device is bricked 100% cause it is stuck in that qsubd download mode or whatever.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Based on your answers this method should work to recover your device. Can you take a look on the back of it and see if it is the T999 or the T999L? We are still attempting to get the T999L recovery sd image. I it does take a little bit longer to boot when booting from your sd card, a lot of that is also based on the speed class of the sd card
[T-Mobile, Samsung Galaxy SIII] kimdoocheol:
Yeah, i'm wondering though if it is because Devil Kernel is a bit different. I'm not sure if you are aware of it's functions, but it is a dual boot kernel that allows you to boot two OS simultaneously. I don't use it to boot two OS, though. I just used it because on my N2 it is pretty much the only stable kernel with 4.3 AOSP that has audio mods.

I'm starting to wonder if it is the SD card though, there were some issues when I was loading it in Linux, but it seemed to load the image fine. The card is quite old, it is from my og droid. That is what Doc suggested, at least.

I will try again with a different SD card and let you know.

I was also wondering, it took me a bit to get the card formatted right in Linux because I didn't know what format to initially use in gparted. Do I just make it allocated, Exfat2-4, or FAT32? I know the card gets the image written to it and it is formatted into different formats once the image is written. I'm just wondering if that could initially be a factor.

The only other card I have with me is an 64gb sandisk sd card. I don't think that'd work too well! Haha, plus on laptop I have a SS drive, so it isn't like I can directly back it up.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
The kernel functions itself had no effect of what happened. It was the updater-script inside the .zip that overwrote your aboot with the kernel.

If you wouldn't mind just checking and making sure on your 16GB SDcard that there isn't any files or anything on the disk. That was an issue that I saw when I was checking out a couple of windows applications that were supposed to be able to emulate dd

It could possible be the sdcard. As far as formatting the sdcard prior to writing the image to it is redundant work for you as the whole partition table gets overwritten and any thing that was on there prior would be corrupt anyway. You can try the 64GB card if you want. I didn't list it as a usable one as I don't have one myself and no one else has reported that it has worked. If you want to directly backup your SD card before you nuke it you would just do the following

dmesg | tail (to get the device name i.e. /dev/sdX)

sudo dd if=/dev/sdX of=~/Desktop/sdcard_backup.img bs=2M

Then once you got done with it you would simple do the opposite (without having to wipe anything)

dmesg | tail (just to make sure the device name is the same)

sudo dd if=~/Desktop/sdcard_backup.img of=/dev/sdX bs=2m
[T-Mobile, Samsung Galaxy SIII] kimdoocheol:
I've already backed up the files to my HD on my computer. I'm using a bootable linux live USB, so I just backed it up to my hdd prior.

As far as the files go, I formatted the card to exfat prior to writing anything to it.

I don't know, but I do remember when I mounted the sd card with DMESG | TAIL there were some issues about exfat. I don't recall, cause I tried it again and the message didn't pop up. That is why I assumed Doc might be right and it might be the SD card or the format.

I'm getting an SD card and will have one in the next hour or so. I'll update this post or make another one letting you know what happens.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Yeah, you'll usually see an error or warning in dmesg since FAT16/32/exFat was never actually intended to work with *nix.

Did you happen to see if you had the T999 or T999lL
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If the sd is formatted as exFat, I highly doubt it'll work. Make sure it's Fat32. Maybe it'll do ok as ext4 too, but I'm betting it's either the format, or the overall screwieness of these devices when trying to use 64gb cards.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
The filesystem that it is formatted in does not matter since we are doing a bit for bit low level copy on it. So long as the kernel can actually see the drive itself. And the whole 64Gb thing has to be something with samsung hardware. One of my co-workers has the s4 and can't use his 64Gb cd card. (Which just made me think that we should be doing conv=sync,noerror on the DD we we are copying too and from)

"noerror"

continue after read errors

"sync"

pad every input block with NULs to ibs-size; when used with block or unblock, pad with spaces rather than NULs
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
All I know for sure is the os and recovery require specific drivers to be able to use an exFat formatted disk. And many S3's have had problems with the 64's regardless of that.
[T-Mobile, Samsung Galaxy SIII] kimdoocheol:
Great news. I got it to boot. The SD card was definitely the issue.

I reformatted my SD card back to normal and restored the files on it. I odin'd back my s3 to stock and reinstall 4.3 pac on it.

The file system is screwy, so I wiped everything but it is weird. I can't mount any SD card in the latest TWRP. This was never an issue before, so i'm a bit confused. I've tried all the three sd cards I have and none of them will mount.

But they do mount in the system ROM

EDIT: Also another strange incident. Sometimes when I plug the phone in it pretty much just vibrates, tries to turn on, can't, and vibrates again. It keeps repeating. Sometiems it shows the battery though. I have no clue what is going on haha
[T-Mobile, Samsung Galaxy SIII] Noobiologist:
Don't use the latest TWRP recovery. It's been extremely screwy. Try to find TWRP 2.5.0.2 and flash it. Your recovery should be good then.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
No reason to go that old imo. 2.6.0.0 works fine for me. Some update-binaries may not like the older recovery.
[T-Mobile, Samsung Galaxy SIII] kimdoocheol:
The new SD card was the issue, so I used the old one. No matter how I formatted it, it wouldn't be detected in twrp. I don't know why, but I got everything working. Thanks for all the help guys!
[T-Mobile, Samsung Galaxy SIII] samipsth:
i followed every step made but can't boot up my phone

Any further help would be appreciated

thanks.

My mobile is SGH-T999

i bricked up while installing T999_UVDMD5_firmware_v4.zip from this http://xdaforums.com/show....php?t=2282603
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
[MENTION=3505796]KAsp3rd[/MENTION]

Has the T999N image been verified working? I can't remember and don't have a lot of time right now. If it doesn't I have another on hand.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Can you look under your battery and verify that you have the SGH-T999 or the SGH-T999L?
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
I don't think that it has been verified as working.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
T999N and T999L images added/updated. Let me know the feedback on them please
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
[MENTION=4081205]DocHoliday77[/MENTION] do you still have that image handy? The uploaded the wrong thing... Not an image at all :(
[T-Mobile, Samsung Galaxy SIII] Panamon:
[MENTION=4654635]Chefedogg[/MENTION] I feel your pain.

I found this thread this evening on the very day I got my phone back from jtag repair.

It was dark, I was sleepy, I was dumb.

I accidentally flashed an S2 kernel on to my S3 one night thinking I was holding my Wife's S2 in my hand.

I googled QHSUSB_DLOAD for a couple of days and somehow managed to miss this thread sitting right under my nose.

Eventually I gave up and looked to eBay for a JTAG solution.

Based on his feedback I chose to send it to Patrick Walls for repair and I couldn't be happier with the results.

In less than a week he had the phone back in my hands AND with all my data intact!

I was extremely nervous about sending my phone off in the mail to someone I don't know but my fears were unfounded.

I highly recommend this guy for those of you that have bricked your device and feel that the fix in this thread might be beyond your abilities.

Awesome work guys!

I sure wish I'd seen your work here sooner.

It would've saved me about 35 bucks!
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Thanks for the information and a great reference. Hope it helps others just as we have been able to do.

On another note I'd be willing to do the work for those that cannot or feels this is above their level, just for the cost of shipping, I do not have the means to JTAG if it is needed though.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Good news....

Official firmware for the T999N has been released! I've contacted mrRobinson to see if he will build a root66 version. But for anyone in need of the official you can download from me so you don't have to wait on hotfile.

http://www.androidfilehost.com/?fid=23159073880937022

I'll add to my firmware thread later on too.
[T-Mobile, Samsung Galaxy SIII] Chefedogg:
Most likely could be beyond my abilities, but with vid tutorial, c'mon, should be able to handle it, hope I don't ever have to try though!
[T-Mobile, Samsung Galaxy SIII] N2PC Tech:
Works...to an extent so far!

The Windows image writer worked for me, to an extent! the phone now boots up to the boot recovery mode, but when i try to use Odin, i get PIT partition not found!!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
All PIT files are here:

http://xdaforums.com/showthread.php?t=1848267

Obviously they go in the PIT section of Odin. I just can't remember if you should flash it at the same time as firmware, or flash separately.

Can anyone clear this bit up?
[T-Mobile, Samsung Galaxy SIII] N2PC Tech:
This is what i get whenever i try to use Odin:

<ID:0/006> Added!!

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Set PIT file..

<ID:0/006> DO NOT TURN OFF TARGET!!

<ID:0/006> Get PIT for mapping..

<ID:0/006>

<ID:0/006> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)

:confused:

And this is the error when trying to install ROM via Odin:

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/006> Added!!

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006>

<ID:0/006> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)
[T-Mobile, Samsung Galaxy SIII] N2PC Tech:
i also got a MSM8960 driver install in windows 8, when i tried to use that image wizard. is that suppose to happen?
[T-Mobile, Samsung Galaxy SIII] N2PC Tech:
PIT File not working!

BOOT RECOVERY MODE

CHECK BOOT PARTITION.

COPY FROM T-FLASH.

BOOT RECOVERY..

FLASH WRITE FAILURE

ODIN MODE

PRODUCT NAME: SGH-T999

CUSTOM BINANRY DOWNLOAD: NO

CURRENT BINARY: Samsung Official

SYSTEM STATUS: NONE

QUALCOMM SECUREBOOT: ENABLE

:confused:

Gonna give Heimdall a shot and see if that will work!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Good luck man! I'm sorry no one's been able successfully help you yet.... Will let you know if I think of anything else.

Is there any chance you could try on a different computer? You never know....
[T-Mobile, Samsung Galaxy SIII] N2PC Tech:
Gonna try that next! Do you have a PIT for the TMO SIII? the one I am trying in Heimdall states: Secure check fail: PIT lol:cool:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yup there's a thread in general. Should be toward the top right now. Either check the OP, or on the last page I have a link posted to my repo.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Sorry for the delay in replying. I've been away for a little while with work and real life. Hopefully everything has worked out properly.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Welcome back! Hope it was an enjoyable hiatus!
[T-Mobile, Samsung Galaxy SIII] N2PC Tech:
NO Luck!

Phone is still stuck in recovery boot mode! This BLOWS!! lol
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Once you get your phone booted into download mode remove the microsd card (without restarting) and try to Odin to stock
[T-Mobile, Samsung Galaxy SIII] javichampi:
Hello, I had another T999 bricked, I follow the tutorial without problem and my phone is alive again, so I can install the samsung original firmware in Odin. Everything looks to be ok, but when I take out the microSD card, my phone is not capable to boot properly, when I restart it, it enter on QHUSB mode again. I try installing modem and bootloader separately, with or without microSD card, and erasing nand or repartition in Odin, but without results. Any idea??
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Have you tried booting into download mode then removing the sdcard without restarting and trying to Odin back to stock that way?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If only one could.....

Sd card is underneath the battery. Can't remove without removing the battery.

As to the issues above, I suspect your brick occupied by flashing something to the wrong partition. (Forgive me if you've told me otherwise already, I read/answer way too much to keep track of all the details!)

Anyway, if this partition happened to be the sbl1, or possibly another that is not included in the official firmware, I could see this happening. Basically because you boot from sd and flash firmware, but those partitions would remain untouched, so after removing the sd, you'd still have a bricked device.

If your brick was due to flashing something you shouldn't have, or you are unsure, please post a link to the thread for what you flashed. This is the only way we could determine exactly which partition was overwritten.
[T-Mobile, Samsung Galaxy SIII] javichampi:
Well, I try to install in Odin with and without sdcard. But the first time I notice the problem it was without sdcard.

The wrong file I've installed was the ATT's new modem and bootloader for 4.3. I take a look inside the zip file and I see same file names than T999, so "Let's go to install it!!!". I'm not sure there is a different partition number in any of the files between both devices. I will compare with T999 modem.

Enviado desde mi SGH-T999 mediante Tapatalk

EDIT: The only difference I found is that ATT's installs sbl1.mbn in partition 2. That file is not overwrite by Odin installation?
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
One simply can remove the microSD without removing the battery.... View attachment 2359470

The rest of your post I am in complete agreement with. :D
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
That is correct as sbl1 is not included in any of the Odin files that [MENTION=4081205]DocHoliday77[/MENTION] has posted (IIRC). If there has been an official bootloader release for the SGH-T999 you might be able to recover it. I am not too sure though.

Perhaps someone knows how to extract and repackage sbl1 as an odin package from the recovery images? I'm unsure of how to do that myself.
[T-Mobile, Samsung Galaxy SIII] javichampi:
Maybe can I extract it directly from the official tar.md5 file and flash it trough TWRP? I'm almost sure that it's present on Samsung's .tar, so it's strange it isn't flashed during ROM installation.

Enviado desde mi SGH-T999 mediante Tapatalk
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
As it might be strange to you that it isn't flashed during ROM installation it in fact would be strange if it were. sbl1, sbl2, sbl3 will NEVER be flashed with a ROM. sbl= second boot loader which is signature checked from the PBL buring bootstrap. Flashing these 3 partitions with improperly signed images or images with a different signature from the PBL are the leading cause of bricked devices.

If sbl1 were in fact included in the official tar.md5 then it would get flashed during the Odin install.
[T-Mobile, Samsung Galaxy SIII] javichampi:
[MENTION=3505796]KAsp3rd[/MENTION].OK. I understand. Maybe I'm thinking in another filename that have 3 parts. Anyway I will take a look to the ROM file. And I hope anyone can pull that partition for their device.

Enviado desde mi SGH-T999 mediante Tapatalk

EDIT: I've found this command for run it in terminal emulator or adb:

dd if=/dev/block/mmcblk0p2 of=/sdcard/sbl1 bs=4096

I've found it in a thread for T999V, I supposed it's the same command for our device.
[T-Mobile, Samsung Galaxy SIII] N2PC Tech:
Solution

I called Local TMO....the idiots dont flash phones anymore because of the OTAs now! lol I then called Sammy.....Got an RMA for them to flash software back to my phone, even though its out of warranty (expired).:good:
[T-Mobile, Samsung Galaxy SIII] javichampi:
Well, finally I've done!!! I extract sbl1 partition from debrick img, using diskinternals linux reader program on Windows. I insert it on modem installation .zip, modifying the updater-script of course, and success!!! It can boot without my dear 16 Gb sdcard!!!

Thank you for your help, [MENTION=3505796]KAsp3rd[/MENTION] and [MENTION=4081205]DocHoliday77[/MENTION].
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Cool man! Glad you got it fixed!

[MENTION=3505796]KAsp3rd[/MENTION]

I'll try and create Odin flashable files of each of the other important partitions if you like. I've got a lot going on now though so give me a few days and if I haven't produced, shoot me a PM reminder if you like.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Awesome! Glad to know you got it fixed. Also your trial and error will be credited when Doc gets the Odin packages ready.

No rush man. If you have some time and want to PM me your instructable on how you are creating tar.md5 packages that actually work with Odin let me know and I'll through the packages together with the images that we currently have. Thanks for taking your time to do this.
[T-Mobile, Samsung Galaxy SIII] N2PC Tech:
Question

Is this with your phone all black, with the BOOT RECOVERY MODE in green at the top?:confused:
[T-Mobile, Samsung Galaxy SIII] javichampi:
???? All this process i made was in my PC, not on mobile.

Enviado desde mi SAMSUNG-SGH-T999 mediante Tapatalk
[T-Mobile, Samsung Galaxy SIII] AlexGardunio:
Hi there! Is there any chance of help for a bricked SGH-I747m? Thanks in advance :)
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Is there no similar thread in your forum? Don't use anything here as we only have files for the T999 and variants here.

[MENTION=3505796]KAsp3rd[/MENTION]

Is there an AT&T debrick thread you know of? Or anyone that has the dumps needed for him to attempt this? If not and you need me to, I'll try to help get them.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Follow the link in the OP credits to the original source. There are images in there
[T-Mobile, Samsung Galaxy SIII] AlexGardunio:
As far as Iknow, there's no similar thread for my i747. I know I should not use anything here, a mate at i747 forum gave me a link here for searching. Any help would be awesome Doc. [MENTION=3505796]KAsp3rd[/MENTION] I've follow the source but still looking for debrick image and so. Thanks both of you :good:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Looks like that's just for the I747. The I747M is what is needed. If you can find someone with the same model device who will flash the zip in the OP then this can help. Without that dump though there's nothing you can do. It's the one linked in the green text in the op. It'll dump the needed partitions for this to work.
[T-Mobile, Samsung Galaxy SIII] Shponglized:
Kinda lost :/

I've got a t999L here, I've downloaded Ubuntu (Via the live cd link, I just didn't burn it) and just installed it straight to my laptop,

I've got a 16 GB sd, Formatted, To Fat32, With the t999L unbrick image extracted from the zip and placed on the SD, It's the only thing on there.

It shows up as simply "16 GB file system" in Ubuntu.

I open terminal and run "Dmesg | Tail"

And I'm not getting anywhere near the output I think I should be getting. I'll paste it below.

[13451.636645] wlan0: associated

[13451.636682] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

[13520.828400] wlan0: deauthenticating from 00:22:75:6d:98:ac by local choice (reason=3)

[13520.866596] cfg80211: Calling CRDA to update world regulatory domain

[13525.064173] wlan0: authenticate with 00:22:75:6d:98:ac

[13525.083422] wlan0: send auth to 00:22:75:6d:98:ac (try 1/3)

[13525.085466] wlan0: authenticated

[13525.090334] wlan0: associate with 00:22:75:6d:98:ac (try 1/3)

[13525.092903] wlan0: RX AssocResp from 00:22:75:6d:98:ac (capab=0x401 status=0 aid=1)

[13525.095597] wlan0: associated

Anyone got any help for me?

Note: It was bricked by flashing a ROM from the t0lte, The Galaxy Note II I believe.

It's a friends phone, I'm from the Galaxy Nexus forums, And you can't really mess up with a Nexus.

Edit 2:

this is the output i'm getting now from running "dmesg | tail"

[18517.894602] sd 13:0:0:0: [sdb] Write Protect is on

[18517.894612] sd 13:0:0:0: [sdb] Mode Sense: 03 00 80 00

[18517.895695] sd 13:0:0:0: [sdb] No Caching mode page present

[18517.895702] sd 13:0:0:0: [sdb] Assuming drive cache: write through

[18517.901236] sd 13:0:0:0: [sdb] No Caching mode page present

[18517.901246] sd 13:0:0:0: [sdb] Assuming drive cache: write through

[18518.167837] sdb: sdb1

[18518.171684] sd 13:0:0:0: [sdb] No Caching mode page present

[18518.171695] sd 13:0:0:0: [sdb] Assuming drive cache: write through

[18518.172716] sd 13:0:0:0: [sdb] Attached SCSI removable disk

Does this make sense to anyone?
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
The disk you are looking for is sdb as shown in your edit
[T-Mobile, Samsung Galaxy SIII] Shponglized:
So that's good and i'm on the right track?

I'm sorry to be all noobed out, But... I honestly am at this point.

Where do I go from here?
[T-Mobile, Samsung Galaxy SIII] Balthasar85:
this guide can theoretically operate with a Samsung Galaxy S 4G T699 Relay?

can I create Debrick Image for Relay?
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
Not to sound like a **** but read and follow the OP. There's even a video
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
I cannot answer that honestly.
[T-Mobile, Samsung Galaxy SIII] Balthasar85:
one last question:

I cann't use the "boot.img" on the stock firmware?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
No, that's just the kernel. You need the bootloaders.
[T-Mobile, Samsung Galaxy SIII] Shponglized:
I've read it many many times, And I don't see the video...?? I've looked for it.

I'm not used to the ubuntu command line stuff at all.
[T-Mobile, Samsung Galaxy SIII] KAsp3rd:
There is step by step instructions on the first post and a video on the 2nd post