[GUIDE] Restore Bootloader Bricked S3 to Stock Firmware AFTER 4.3 update. No Jtag

Search This thread

DocHoliday77

Senior Member
May 10, 2011
9,403
6,892
HuntsVegas!!!
I realize this was written several months ago, but since it seems some are still trying to use this I thought id point a few things out. (Nothing intended against the op! I just thought the following is important info for folks to know)

There has since been another update for most (all?) T999 variants. There is also root66 firmware for just about all of them. This means you only need flash root66 from Odin. No need to install twrp or cwm to use the knox removal script.
You can flash official firmware first if you like, but once in download mode you should be able to just flash the root66 version to save time, steps and downloads.

Also, I would warn against flashing using the PIT file and repartition checked in Odin. Unless you are sure of what you are doing, and that it is necessary for your particular problem, you should never use this option!

Just fyi, a class 6 sd card should work fine. It must be 16gb or larger though. Also, the debrick image must be the same or newer than the build currently on your device. As of 4.3, if you use the NC2 debrick image for example, you will only be able to flash NC2 or newer firmware, regardless of what you originally had on the device.

I appreciate the op helping folks out with this, but I just thought some of that is important. Also before doing anything, I highly suggest reading @KAsp3rd's original thread. At least the first page and last few pages! Its stickied in development so you cannot miss it. I believe the vast majority will be able to recover their bricks just by following his original steps. Try the extra ones here if problems are encountered.
Hope that all helps some of you!

Sent from my SGH-T999 using Tapatalk
 

AMANGTAV

Member
Sep 28, 2013
5
0
my tmobile s3 was hard brick

My tmobile s3 was hard brick.I gave it for jtag ,but after a day .It bricked again.Also,the imei no. is erased from the phone.so,what can i do to give life to my s3 ?
And, would your method work?
Please tell me, my s3 is laying dead for about 4 months.
 

DocHoliday77

Senior Member
May 10, 2011
9,403
6,892
HuntsVegas!!!
My tmobile s3 was hard brick.I gave it for jtag ,but after a day .It bricked again.Also,the imei no. is erased from the phone.so,what can i do to give life to my s3 ?
And, would your method work?
Please tell me, my s3 is laying dead for about 4 months.

To debrick, Follow KAsp3rd's original thread as I stated in my post above yours.
His thread is stickied in Android Development section. http://xdaforums.com/showthread.php?t=2439367

Once you have restored your device to working condition, if you still have no imei number, pm me with your device model, current build, details on how it was lost, etc, and ill help you with that.

Sent from my SGH-T999 using Tapatalk
 
  • Like
Reactions: AMANGTAV

AMANGTAV

Member
Sep 28, 2013
5
0
hard brick tmobile s3 , battery % is 0, won't charge,help plz

Thanks for reply.☺
But, how can i charge my s3 battery ?.As, when i last noticed it was only 2% charged . After, the brick, the battery percentage would 0.
if there is anyway to solve it, please reply me?

---------- Post added at 09:00 AM ---------- Previous post was at 08:56 AM ----------

Hey, man
Can you tell me how you charge your battery ?.As, when i last noticed it was only 2% charged . After, the brick, the battery percentage would 0. Tmobile S3.
if there is anyway to solve it, please reply me?
 

AMANGTAV

Member
Sep 28, 2013
5
0
Are you sure without charged battery my s3 will boot up?
I got a sandisk 16gb sdcard class 10.Is it okay?
And , thanks once again .
 

DocHoliday77

Senior Member
May 10, 2011
9,403
6,892
HuntsVegas!!!
Sd card is fine. Either boot up using the sdcard and then plug in, or insert the sd and plug in to charge while turned off. If the debrick.img is working it should charge.

Sent from my SGH-T999 using Tapatalk
 

twolves14

Senior Member
Jun 20, 2010
200
21
This is the error I'm getting:
Code:
<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)

Any advice? Further information here: http://xdaforums.com/showpost.php?p=53503231&postcount=506
 

DocHoliday77

Senior Member
May 10, 2011
9,403
6,892
HuntsVegas!!!
Try redownloading the pit. Also maybe try flashing with only the pit file, no firmware selected. Not sure if this would even work tbh, but might be worth a shot.
 

westlife2206

Senior Member
Nov 19, 2013
58
6
@TronMinecraft
You said in your first post that your phone got hard brick. If it was hard brick, how could you boot it to Download or Recovery mode ?
I did the instruction in @KAsp3rd's thread http:// xdaforums.com/showthread.php?t=2439367 but no luck on my phone.
 

westlife2206

Senior Member
Nov 19, 2013
58
6
What did you flash on your device to cause it to brick?

I downgraded the bootloader at this thread http:// xdaforums.com/showthread.php?t=2282603
Now I can't power up my phone or boot into Recovery, Download mode.
I even followed the instruction here http:// xdaforums.com/showthread.php?t=2439367 but no luck for me.
 

troolplay1

Member
Jul 19, 2014
24
0
Hello, I know there are many threads on restoring a bricked S3, some of them for hard bricks, and some for soft bricks. None of the guides I found by scouring these forums provided all of the answers I needed.

INFO PLEASE READ ALL

Here I hope to outline how I restored my T999 Tmobile S3 to stock firmware after the 4.3 MJC update, and after bootloader bricking the phone. I do assume you are capable of using ADB, ODIN and TWRP. I believe this method will work for other S3 models, but I have no ability to test it. If it will work, firmware and debrick IMGs will have to be found for the specific device. The T999 firmware and IMGs will NOT work with other devices. This will restore to stock UVUEMJC 4.3 firmware. Will not be rooted, but existing 4.3 roots for the device should work.

I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE. THE TOOLS USED IN THIS GUIDE HAVE THE POTENTIAL TO BRICK, OR OTHERWISE DAMAGE YOUR DEVICE. USE AT YOUR OWN RISK


So as context, I had been flashing different ROMS; then I updated to stock 4.3 UVUEMJC Firmware. This updated the bootloader, and installed the Samsung KNOX security upgrade. Both the bootloader and the KNOX are problems regarding rooting, rom installation, and downgrading (which I still have not achieved)

After upgrading, I installed a vanilla rootbox. I then attempted to flash the UVDMD5 bootloader at mnasledov's thread here: http://xdaforums.com/showthread.php?t=2282603

Lacking my present understanding, of the 4.3/KNOX problems, I managed to brick my phone by effectively attempting to downgrade the bootloader. Phone appeared to be hard bricked.

I tried many things to fix the phone, these are what worked:

GUIDE:

1. Get a Class 10 MicroSD card and follow KAsp3rd's guide to boot from the SD card: http://xdaforums.com/showthread.php?t=2439367

You should now be able to boot to download mode, recover, and system if it was undamaged when you bricked your phone.

2. Boot into download mode and install TWRP via ODIN

3. Boot into your new TWRP recovery. Do an ADB sideload of the KNOX removal script found in Kaito95's thread here: http://xdaforums.com/showthread.php?t=2507931 Check the clear cache and clear dalvik recovery boxes. You have to do an ADB sideload, because your SD card is in use as a bootloader.

4. Use ODIN with Download Mode to Re-Partion by flashing the PIT file found in invisiblek's downloads here: http://xdaforums.com/showthread.php?t=1848267

The Re-Partition box will have to be checked, and the PIT file loaded under Re-Partition. This is what I believe corrected the download mod fails I had been getting.

5. Use ODIN and Download mode to flash the original UVUEMJC firmware found in DocHoliday77's thread here: http://xdaforums.com/showthread.php?t=1949687

6. In TWRP do a factory reset, and a fix permissions. Reboot into system, (without the SD card)

If all went well you should be in business!

If you see any error in my guide, or have another correction, please let me know. If I have posted this in the wrong section I'll be happy to move it.

I hope this helps you.

ROOTING:

So after fixing my phone via the steps above, I still wanted to root it. To root it I simply ODIN flashed mrRobinson's rooted/deKNOXED 4.3 stock rom from here: http://xdaforums.com/showthread.php?t=1771687
It seemed very stable to me.

I then decided to use TWRP to install the CyanogenMod 10.2. If you choose to install CM, I believe you must use the 10.2 branch, because it is 4.3 based. Prior versions are not 4.3, and won't work with the 4.3 bootloaders. You can find the appropriate CM download by selecting your device here: http://download.cyanogenmod.org/ The T999 is d2tmo.

EDIT: YOU CAN RUN OLDER VERSIONS AFTER UPDATING TO 4.3.
This was pointed out to me by Adreaver. I personally am using rootbox 4.2.2 after having done the 4.3 official update. Any rom for the device should work, but certain lines may need be removed form the updater script. I am still looking into this.

NOTES

This has been confirmed to work on the T999L, but you need a different PIT file, and different firmware for the model. See @mrspock08 's post on page 2 of this thread for more info on the T999L

THANKS

I could not have debricked my phone or created this guide without referencing and using the work of several fine members of this forum. Particular thanks to:

@mnasledov for providing a thread with information about bootloaders.
@KAsp3rd for providing a way to boot from the SD card, enabling the entire rest of the debrick.
@Kaito95 for the deKNOX script.
@invisiblek for the PIT file for correctly repartitioning the phone.
@DocHoliday77 for the MJC 4.3 Stock Firmware mirror.
@mrRobinson for the rooted MJC Stock firmware
@Adreaver for correcting me that you can run an older version of android
And the threads of many many others who's work I read through while learning about how all of this works.

still not working for me, i have t999 i have followed your directions pretty well, have to mention i lose TWRP after i flash JC firmware. i had to re-flash it through odin, fix permissions, and still can start the phone without the unbrick sd :(( please help. note: boot shows blue "recovery boot" on top left corner. i have tried everything within my knowledge :(
can i just somehow duplicate the debrick img bootload files into the phone's bootload block?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    Hello, I know there are many threads on restoring a bricked S3, some of them for hard bricks, and some for soft bricks. None of the guides I found by scouring these forums provided all of the answers I needed.

    INFO PLEASE READ ALL

    Here I hope to outline how I restored my T999 Tmobile S3 to stock firmware after the 4.3 MJC update, and after bootloader bricking the phone. I do assume you are capable of using ADB, ODIN and TWRP. I believe this method will work for other S3 models, but I have no ability to test it. If it will work, firmware and debrick IMGs will have to be found for the specific device. The T999 firmware and IMGs will NOT work with other devices. This will restore to stock UVUEMJC 4.3 firmware. Will not be rooted, but existing 4.3 roots for the device should work.

    I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE. THE TOOLS USED IN THIS GUIDE HAVE THE POTENTIAL TO BRICK, OR OTHERWISE DAMAGE YOUR DEVICE. USE AT YOUR OWN RISK


    So as context, I had been flashing different ROMS; then I updated to stock 4.3 UVUEMJC Firmware. This updated the bootloader, and installed the Samsung KNOX security upgrade. Both the bootloader and the KNOX are problems regarding rooting, rom installation, and downgrading (which I still have not achieved)

    After upgrading, I installed a vanilla rootbox. I then attempted to flash the UVDMD5 bootloader at mnasledov's thread here: http://xdaforums.com/showthread.php?t=2282603

    Lacking my present understanding, of the 4.3/KNOX problems, I managed to brick my phone by effectively attempting to downgrade the bootloader. Phone appeared to be hard bricked.

    I tried many things to fix the phone, these are what worked:

    GUIDE:

    1. Get a Class 10 MicroSD card and follow KAsp3rd's guide to boot from the SD card: http://xdaforums.com/showthread.php?t=2439367

    You should now be able to boot to download mode, recover, and system if it was undamaged when you bricked your phone.

    2. Boot into download mode and install TWRP via ODIN

    3. Boot into your new TWRP recovery. Do an ADB sideload of the KNOX removal script found in Kaito95's thread here: http://xdaforums.com/showthread.php?t=2507931 Check the clear cache and clear dalvik recovery boxes. You have to do an ADB sideload, because your SD card is in use as a bootloader.

    4. Use ODIN with Download Mode to Re-Partion by flashing the PIT file found in invisiblek's downloads here: http://xdaforums.com/showthread.php?t=1848267

    The Re-Partition box will have to be checked, and the PIT file loaded under Re-Partition. This is what I believe corrected the download mod fails I had been getting.

    5. Use ODIN and Download mode to flash the original UVUEMJC firmware found in DocHoliday77's thread here: http://xdaforums.com/showthread.php?t=1949687

    6. In TWRP do a factory reset, and a fix permissions. Reboot into system, (without the SD card)

    If all went well you should be in business!

    If you see any error in my guide, or have another correction, please let me know. If I have posted this in the wrong section I'll be happy to move it.

    I hope this helps you.

    ROOTING:

    So after fixing my phone via the steps above, I still wanted to root it. To root it I simply ODIN flashed mrRobinson's rooted/deKNOXED 4.3 stock rom from here: http://xdaforums.com/showthread.php?t=1771687
    It seemed very stable to me.

    I then decided to use TWRP to install the CyanogenMod 10.2. If you choose to install CM, I believe you must use the 10.2 branch, because it is 4.3 based. Prior versions are not 4.3, and won't work with the 4.3 bootloaders. You can find the appropriate CM download by selecting your device here: http://download.cyanogenmod.org/ The T999 is d2tmo.

    EDIT: YOU CAN RUN OLDER VERSIONS AFTER UPDATING TO 4.3.
    This was pointed out to me by Adreaver. I personally am using rootbox 4.2.2 after having done the 4.3 official update. Any rom for the device should work, but certain lines may need be removed form the updater script. I am still looking into this.

    NOTES

    This has been confirmed to work on the T999L, but you need a different PIT file, and different firmware for the model. See @mrspock08 's post on page 2 of this thread for more info on the T999L

    THANKS

    I could not have debricked my phone or created this guide without referencing and using the work of several fine members of this forum. Particular thanks to:

    @mnasledov for providing a thread with information about bootloaders.
    @KAsp3rd for providing a way to boot from the SD card, enabling the entire rest of the debrick.
    @Kaito95 for the deKNOX script.
    @invisiblek for the PIT file for correctly repartitioning the phone.
    @DocHoliday77 for the MJC 4.3 Stock Firmware mirror.
    @mrRobinson for the rooted MJC Stock firmware
    @Adreaver for correcting me that you can run an older version of android
    And the threads of many many others who's work I read through while learning about how all of this works.
    2
    Nice guide. I think @DocHoliday77 could use this method because I believe he bricked his phone the same way.

    Oh, and I believe you might have made a typo SDB is actually ADB Android debug bridge.
    2
    Great tutorial. An extreme amount of time went into this I can see. Hopefully it'll be able to get @DocHoliday77 back up and running tho. I miss that guy!

    Sent from my Nexus 5 using Tapatalk
    1
    Of course! You're right, a typo on my part. Thanks for pointing that out!

    No problem, I made more then 1 mistake when I made my first page. So your doing good with only 1.
    1
    If you can find what you flashed when it bricked it'll be a big help. I'm guessing it was probably something not meant for this device and ended up flashing over sbl1 or one of the modemst partitions. But it's just a guess unless we can take a look at what you had flashed.

    Sent from my SGH-T999 using Tapatalk