T-Mobile SIII Bricked

[Abdullah.tariq1988]

Hey,
I had a non-rooted T-Mobile SIII with stock ROM installed. A few days back, it just rebooted automatically and got in a boot loop. I don't know what happened. After that, I tried to install the stock ROM again via Odin but it seems that Odin is not writing anything on it. The download mode shows

ODIN MODE
PRODUCTNAME: SGH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV:1​

WHAT HAPPENS

• The Phone turns on but cannot go further than the "Samsung Galaxy S3" logo
• When I try to go to the recovery mode, the Samsung logo with booting recovery comes and then it just shifts to the boot loop
• I can get to the Download Mode and Odin recognizes the device.
• It shows the PASS status after writing a recovery image but it just doesn't work

WHAT I HAVE DONE UNTIL NOW

• Tried to flash CMW (touch and non-touch both). Odin gives pass but it still boots to boot loop
• Same happens with TWRP
• Tried to flash the Stock F/W but Odin fails every time before even trying

 

[audit13]

What error is shown in the Odin log? Tried using different usb cables and usb ports with Odin?

 

[dangmouse]

T-999 unbrick

By your description, it looks like your kernel is corrupt. It happened a few times with my note 3 stock, as well as my S III back in the day.

The way I unbricked successfully each time, was to feed Odin one piece of the stock ROM at a time, in this order:

1. Kernel
2. TWRP 2.7.0
3. ROM

IMPORTANT: if you end up going this way, be sure to power down the unit after each STEP. I even removed the battery, just to be sure.

DO NOT ALLOW ODIN TO REBOOT THE UNIT.

Last thing, be aware that the stock upgrade you use has to match any firmware upgrade you may have flashed in the past.

This is a way doable solution.

Ping me if you have questions or need links. I'm still a newly registered user on this board and can't post links yet.

Good luck!

Hey,
I had a non-rooted T-Mobile SIII with stock ROM installed. A few days back, it just rebooted automatically and got in a boot loop. I don't know what happened. After that, I tried to install the stock ROM again via Odin but it seems that Odin is not writing anything on it. The download mode shows

ODIN MODE
PRODUCTNAME: SGH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV:1​

WHAT HAPPENS

• The Phone turns on but cannot go further than the "Samsung Galaxy S3" logo
• When I try to go to the recovery mode, the Samsung logo with booting recovery comes and then it just shifts to the boot loop
• I can get to the Download Mode and Odin recognizes the device.
• It shows the PASS status after writing a recovery image but it just doesn't work

WHAT I HAVE DONE UNTIL NOW

• Tried to flash CMW (touch and non-touch both). Odin gives pass but it still boots to boot loop
• Same happens with TWRP
• Tried to flash the Stock F/W but Odin fails every time before even trying

 

[Abdullah.tariq1988]

The way I unbricked successfully each time, was to feed Odin one piece of the stock ROM at a time, in this order:

1. Kernel
2. TWRP 2.7.0
3. ROM

I followed all your steps. I made it sure after every step that my phone powered down. I also removed the battery for a while after every step but it all ends up the same way. The Kernel and The Recovery are successfully written but it gives an error on the ROM. And nothing changes, I still can't boot to recovery or OS
ODIN LOG
<ID:0/011> Added!!
<ID:0/011> Odin engine v(ID:3.1203)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> boot.img
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
<ID:0/011> Added!!
<ID:0/011> Odin engine v(ID:3.1203)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> recovery.img
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin engine v(ID:3.1203)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> sbl2.mbn
<ID:0/011> FAIL!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

 

[audit13]

Are you using the latest stock ROM from sammobile.com?

 

[Abdullah.tariq1988]

Are you using the latest stock ROM from sammobile.com?

Yes, I downloaded the latest firmware available on the sammobile.com

 

[audit13]

Maybe try flashing with a pit file.

 

[Abdullah.tariq1988]

Maybe try flashing with a pit file.

Where can I get the pit file??

 

[audit13]

You'll have to search to find the correct pit file ford your phone's model number and onboard memory size.

Did you flash the stock firmware as a single file in Odin? Tried different usb ports and usb cables?

 

[Abdullah.tariq1988]

You'll have to search to find the correct pit file ford your phone's model number and onboard memory size.

Did you flash the stock firmware as a single file in Odin? Tried different usb ports and usb cables?

Yes I tried one file and different usb ports and cables

 

[audit13]

So you unzipped the file from sammobile only once to get a tar.md5 file?

 

[Abdullah.tariq1988]

So you unzipped the file from sammobile only once to get a tar.md5 file?

Yes I used the tar.md5 file

 

[audit13]

If you can find a pit file and it still doesn't work with the pit file, the memory chip in the phone may be damaged.

https://www.androidfilehost.com/?w=files&flid=6471

 

[Abdullah.tariq1988]

Maybe try flashing with a pit file.

Same result after trying with a pit file.

 

[audit13]

Based on everything you have tried and the end result, I think the memory chip is damaged.

 

[Abdullah.tariq1988]

Based on everything you have tried and the end result, I think the memory chip is damaged.

Is there anything I can do 'bout that?

 

[audit13]

I don't think so. The simplest solution may be to find a used phone with a damaged screen and working motherboard.

 

[Abdullah.tariq1988]

I don't think so. The simplest solution may be to find a used phone with a damaged screen and working motherboard.

Thanks for your help man. It seems that the memory chip is fried. Searching for a motherboard now

 

[voiceferous]

In your first post you said you can get into download mode.

As last resort I'd try ADB. Try flashing recovery and or boot or even the entire ROM (sideload) via adb (and not Odin). Plenty of tutorials here and on the web and you seem knowledgeable enough to do that yourself.