Develop Bugs

Soft Brick problem URGENT

Hello fellow xda members!
Im having issues with my soft bricked samsung galaxy s3 AT&T. I tried flashing stock rom after using CM10 nightlies for a while. I totally forgot to fully whipe all data. So i went ahead and tried to flash stock rom using odin. I believe my problem lies in what i did in odin when i was flashing the rom. I followed the HOW TO UNROOT & FACTORY RESET YOUR SGSIII video in the ALL IN ONE NOOBS VIDEO GUIDES post ( http://forum.xda-developers.com/showthread.php?t=1728824&highlight=heimdall ). In the video he told me to make sure i have F. Reset Time dissabled before i flash. I think that this might be the problem.
Also as an attempt to fix this issue, i attempted to follow the how-to on fixing a soft brick (which is what i believe is the problem) on this post ( http://forum.xda-developers.com/showthread.php?t=1840030 ). Odin gives me a nice big FAIL when i attempt to flash the VRALEC bootchain. I followed the guide (so far) to the exact letter, and what i should do if i have problems flashing those files.
One more thing i forgot to mention, the only thing that i can do is boot into download mode. I cant boot into recovery T_T.
Thanks in advance!
ps: let me know if there is anything i have missed to help find the solution!

bump

I rooted my friends GS3 yesterday and he was on Verizon. We had to flash the unlocked VRALEC bootchain. We never do that for AT&T as it's not locked.
Not sure what else I can say, but just make sure you didn't flash anything from the Verizon S3...
EDIT: Yeah man that second thread you linked to is Verizon. They are completely different phones...
Just download the Odin files, put your phone into download mode and make sure you have Samsung USB drivers installed and Windows 7 (mine doesn't work on Win8) and put the odin files into the PDA section and flash.

geoldr said:
I rooted my friends GS3 yesterday and he was on Verizon. We had to flash the unlocked VRALEC bootchain. We never do that for AT&T as it's not locked.
Not sure what else I can say, but just make sure you didn't flash anything from the Verizon S3...
EDIT: Yeah man that second thread you linked to is Verizon. They are completely different phones...
Just download the Odin files, put your phone into download mode and make sure you have Samsung USB drivers installed and Windows 7 (mine doesn't work on Win8) and put the odin files into the PDA section and flash.
Click to expand...
Click to collapse
Thanks brother, i guess i missed that it was Verizon (duh!) i feel stupid. Il try it again, and update.

All you have to do after you flash the stock ROM is go into recovery by powering off the phone and holing the volume up +power + home button and select wipe data/factory reset and it will boot. Hope you didn't do more damage by flashing something from your second link.
Sent from my SGH-I747 using xda premium

GalaxyMaster said:
All you have to do after you flash the stock ROM is go into recovery by powering off the phone and holing the volume up +power + home button and select wipe data/factory reset and it will boot. Hope you didn't do more damage by flashing something from your second link.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I think he should be Okay because Odin said 'failed'. But I think it would be a good idea to Odin back to stock because that will re-partition your phone and I think it would be better overall to just start fresh.

happened to me a few times lol
what you do is
get a stock rom for your phone
go to recovery, wipe everything(data, dalvik, cache)
go to download mode
flash stock rom through odin
done.

pcshano said:
happened to me a few times lol
what you do is
get a stock rom for your phone
go to recovery, wipe everything(data, dalvik, cache)
go to download mode
flash stock rom through odin
done.
Click to expand...
Click to collapse
You see, that would be a great idea, but i cant get into recovery

lemonbox said:
You see, that would be a great idea, but i cant get into recovery
Click to expand...
Click to collapse
You don't need recovery for Odin. It will completely wipe your phone for you.
Here is a link to the AT&T Odin file for the latest release.
http://hotfile.com/dl/182224582/7ad...I747_ATT_1_20121116120521_7p9l4qgqoh.zip.html
Got it from here:
http://forum.xda-developers.com/showthread.php?t=1968625

geoldr said:
You don't need recovery for Odin. It will completely wipe your phone for you.
Click to expand...
Click to collapse
Oh sorry, i thought you wanted me to get into recovery and wipe data first before i flash?

Don't worry about recovery just Odin back to stock. This process will already wipe everything. After successful flash in Odin if it bootloops, then do a factory reset in stock recovery
Sent from my SGH-I747M using xda app-developers app

jbradbury said:
Don't worry about recovery just Odin back to stock. This process will already wipe everything. After successful flash in Odin if it bootloops, then do a factory reset in stock recovery
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thank you !! Hope this will solve my problem.

lemonbox said:
Oh sorry, i thought you wanted me to get into recovery and wipe data first before i flash?
Click to expand...
Click to collapse
jbradbury said:
Don't worry about recovery just Odin back to stock. This process will already wipe everything. After successful flash in Odin if it bootloops, then do a factory reset in stock recovery
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
I never said to go into recovery, somebody else did And yes just Odin back to stock. And just like jbradbury said. If you are still getting a bootloop after you Odin to stock, to a factory reset in the samsung 3e recovery. The stock Samsung 3E recovery will be flashed when you Odin.

*sigh* no luck, i download the stock rom, put my phone into download mode, loaded the rom and flashed it, and maybe 3 seconds later i got FAIL again. Any other suggestions anyone? Also i noticed SECURE CHECK FAIL : aboot in red at the top left of download mode screen.
This is what odins message box told me if it helps:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

lemonbox said:
*sigh* no luck, i download the stock rom, put my phone into download mode, loaded the rom and flashed it, and maybe 3 seconds later i got FAIL again. Any other suggestions anyone?
This is what odins message box told me if it helps:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
flash an ICS rom

Danvdh said:
flash an ICS rom
Click to expand...
Click to collapse
Il give it a shot. I found an ICS based rom here ( http://forum.xda-developers.com/showthread.php?p=29119632#post29119632 ). Before i download and flash, just wanted to make sure i got the right one ^.^ Would that be fine?

question: did you run it as admin?
but it seems to me that the authorization failed
try restore IMEI and flash again

pcshano said:
question: did you run it as admin?
but it seems to me that the authorization failed
try restore IMEI and flash again
Click to expand...
Click to collapse
I just ran odin as administrator and nothing . Also, how does one restore IMEI?

I have successfully unbricked my phone :3 The problem was the rom. Im with virgin mobile aka Bell and from this experience i learned that the I747 does not equal I747M
Thank you all for the help!!!! Seriously.

lemonbox said:
I have successfully unbricked my phone :3 The problem was the rom. Im with virgin mobile aka Bell and from this experience i learned that the I747 does not equal I747M
Thank you all for the help!!!! Seriously.
Click to expand...
Click to collapse
Yes they are different phones. I'm glad you got it figured out.

Please help Can not flash Stock Rom after jtag repair

I have this problem after unrick phone by JTag, can not flash stock rom on T999 after repair boot vby Jtag.
Odin Log:
<ID:0/017> Added!!
<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/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Set PIT file..
<ID:0/017> DO NOT TURN OFF TARGET!!
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> aboot.mbn
<ID:0/017> NAND Write Start!!
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Can you boot normally? Recovery? Do you have the T999 or T999L? What is currently running on the phone?
Sent from my SGH-T999L using XDA Premium 4 mobile app

DocHoliday77 said:
Can you boot normally? Recovery? Do you have the T999 or T999L? What is currently running on the phone?
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My phone is T999 hard bricked but after repair boot loader by jtag phone able to boot up into Download mode only.
Not able boot into recovery, i tried Flash stock firmware with pit file, it is fail the Odin log said like that.
I tried to flash TWRP succeed but still can not go into TWRP to flash custom rom.
I tried to flash stock kernel and stock recovery after succeed with Odin phone still like that.
Only Boot into Download mode. can not go into recovery or TWRP or OS.
T-Mobile lock bootloader T999 via OTA update like I337 with OTA MF3 update ?
Thanks for help.

nguyento1986 said:
My phone is T999 hard bricked but after repair boot loader by jtag phone able to boot up into Download mode only.
Not able boot into recovery, i tried Flash stock firmware with pit file, it is fail the Odin log said like that.
I tried to flash TWRP succeed but still can not go into TWRP to flash custom rom.
I tried to flash stock kernel and stock recovery after succeed with Odin phone still like that.
Only Boot into Download mode. can not go into recovery or TWRP or OS.
T-Mobile lock bootloader T999 via OTA update like I337 with OTA MF3 update ?
Thanks for help.
Click to expand...
Click to collapse
Ok, that makes much more sense! Shouldve included all of that in your op. I've never done a hard brick repair myself, so I'm not sure ill be able to help much.
Its possible that whatever you did to brick the phone screwed up other partitions that are not included in the stock firmware. Where did you send it for the repair? Or did you try this on your own?
If you had someone else do it, I'd contact them and ask why they didn't reload the stock firmware for you.
I always recommend www.mobiletechvideos.com because theyre the only ones I've ever seen people post about In this forum. Everyone who ever posted about them said it worked great and they got their phone back really quick. You may want to look them up.
If I can think of something for you to try, ill post back. I just don't want to tell you to do something that makes it worse! I suspect though that whatever caused the brick may have tried to overwrite the SBL1, param, or some other partitions. These are not included in the stock firmware so just flashing it would not fix it if this were the case. Thats pure speculation, and I could be wrong though.
If I find more info ill let you know. In the meantime, how did you brick it, and how did you jtag it (yourself or a shop)?
Sent from my SGH-T999L using XDA Premium 4 mobile app

[Q] Help Me Please. Soft Bricked SGH-T999

Hello people, here's my situation
I installed a bad Custom Bootloader ROM on my phone from my SD card that bricked my phone and put it in a boot loop.
I had CMW as my recovery and I factory reseted. Still stuck in Boot loop.
So I tried to recover my phone using A SGH-T999 Stock ROM with Odin.
Here's what I see:
Get pit for mapping
NAND Write Start
Boot.img
Complete(Write) Operation failed.
Now when i rebooted it now says that a firmware error occurred.
I wasn't even in a boot loop anymore. The Firmware error happens instead of that. Then i couldn't' go to recovery mode anymore. I Found Root66 for SGH-T999 and tried to flash it.
It failed when it was like 99% done but it restored my phone somewhat…..(I was back at boot loop again but I was able to access recovery mode again, except that it was STOCK RECOVERY now.
Kies doesn't see my phone it just says connecting. Today I left it 7:30AM to 4:15 PM. And it STILL said connecting.
Nothing Will Flash. I all i see is.
Get pit for mapping
Complete(Write) Operation Failed.
That's literally what happens. I don't see no NAND Write Start or anything. It happens every time for pretty much anything.
When I access Recovery, It is Stock recovery and not CMW anymore. So I can't flash anything off of my SD Card. Probably because the ROMS are not signed.
Here is some info from my phone in download mode
ODIN MODE
PRODUCT NAME: SGH T-999
CUSTOM BINARY DOWNLOAD: YES (3 Counts)
CURRENT BINARY: Custom
SYSTEM STATUS:Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit:1
BOOTLOADER AP SWAEV:1
What do I do?
Do I have a $500 Paper Weight? Or is there hope?

What root66 are you trying to flash? 4.3 or below?
Sent from my SGH-M919 using Tapatalk

serio22 said:
What root66 are you trying to flash? 4.3 or below?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Below. It basically went to 99% and failed in ODIN.
It did get rid of the firmware error but my phone was back in the bootloop. At least I was able to get recovery mode back.. Except that it's stock recovery.
As of right now,
Here's what I have
1. The phone is in a boot loop.
2. Download mode is accessible
3. Stock Recovery Mode is accessible
4. Every time I try to flash something onto the phone using odin, it says this before it fails:
Get pit for mapping(I have to wait for like 10 Minutes straight)
Complete(Write) Operation Failed
What do I from here to fix this. All I want is to get the phone running again. I don't care if it's back to stock or rooted.

Download and flash the 4.3 root66.. It won't flash anything lower because i think you have the 4.3 bootloader
Sent from my SGH-M919 using Tapatalk

serio22 said:
Download and flash the 4.3 root66.. It won't flash anything lower because i think you have the 4.3 bootloader
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Ill try it right now and let you know.

serio22 said:
Download and flash the 4.3 root66.. It won't flash anything lower because i think you have the 4.3 bootloader
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Here's what i got
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVUEMJC.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any other idea you can share?

Flash a recovery and then flash a ROM.. Probably not the best solution but worth a shot
Sent from my SGH-M919 using Tapatalk

Got to go to school, Link?

Have I bricked my phone :( - Experts plz help!

Guys,
!!!!! N00B Alert - I am not an expert in what I am doing. Just following instructions from experts like you. I will try to be as technically articulate as possible !!!
I had recently (about a month ago) rooted my phone to install CM 10.2. I love CM.
In an attempt to unlock my phone I wanted to get back to stock ROM. So I googled and bumped into a way to do it from Kies (not sure if it was a good idea). I followed the instructions and boom the firmware initialization failed half way through. Now when I turn my phone on I get this error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". So I tried again multiple times but it won't work.
Then I thought may be there is another way and googled and found this thread - http://forum.xda-developers.com/showthread.php?t=2186967
Followed the instructions to the word, but I see the dreaded FAIL message in ODIN.
Below is the log. (I tried twice in one stretch).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Another thing is I am not able to get to recovery mode. When I try I can only get to the Firmware error screen I mentioned above.
Any help to get out of this mess would be great!

did you make sure you had the LK3 bootloader before trying to flash stock? if so I also had Odin fail while flashing this firmware. only one that worked for me was root66 firmware. i never booted all the way in but i read that you have to uncheck "auto restart" before flashing, once it is done pull battery and boot into recovery and factory reset. if that doesn't work you can do what I did. Odin flash cwm and install a rom from your sdcard
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

andrewjae04 said:
did you make sure you had the LK3 bootloader before trying to flash stock? if so I also had Odin fail while flashing this firmware. only one that worked for me was root66 firmware. i never booted all the way in but i read that you have to uncheck "auto restart" before flashing, once it is done pull battery and boot into recovery and factory reset. if that doesn't work you can do what I did. Odin flash cwm and install a rom from your sdcard
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I didnt know I have to have the LK3 bootloader, may be I missed in the instructions.
Anyway, how do I flash Clockworkmod from Odin? if I can do that I can get back to CM 10.2 and then try paying for unlock code.

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att/philz_touch_6.07.9-d2att.tar.md5
this is what I used but it didn't work for me without first flashing root66 firmware. i will try to find that link and post it also.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

http://click.xda-developers.com/api...747UCDLK3.7z&jsonp=vglnk_jsonp_13911206638286
this is the link to root66 for att.
BEFORE YOU DO ANY OF THIS YOU ARE ON AT&T RIGHT?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.

andrewjae04 said:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att/philz_touch_6.07.9-d2att.tar.md5
this is what I used but it didn't work for me without first flashing root66 firmware. i will try to find that link and post it also.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank You!
andrewjae04 said:
http://click.xda-developers.com/api...747UCDLK3.7z&jsonp=vglnk_jsonp_13911206638286
this is the link to root66 for att.
BEFORE YOU DO ANY OF THIS YOU ARE ON AT&T RIGHT?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I am on AT&T.
After I read your post about flashing CWM with ODIN I researched and found a method. I tried it and it PASSED!. Then my phone restarted and boom it booted directly into CM 10.2. Not sure how, felt a bit creepy. Then I updated to latest Nightly CM 11 build and brough back all my apps and my phone has LIFE right now. Thanks for the tip! :good:

audit13 said:
Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.

mr_legolas said:
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
I believe if you were originally on 4.1 then you still have that bootloader. I dont think OTA updates the bootloader so you should be able to downgrade with the root66 if that is the case.

audit13 said:
Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
when you say "find" an AT&T 4.3 rom, I wish you could give me a link. I am working with a device that was handed to me that was on 4.3 then flashed to a t999 rom. Now I cannot get it to flash ANYTHING AT&T 4.3 (and I've looked all over), neither in odin, nor in recovery, except, oddly enough it will reflash the same t999 image. The radio (modem) also no longer works.

mr_legolas said:
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
This is why your flash to stock failed, lucky for you. The MJB bootloader is not downgradable and if 'successful' is bad news...aka brick, requiring serious hacking if not JTAG service to repair. As far as ROM's go as long they do not attempt to change the bootloader (none i've seen do, but you never know) the worst that could happen is a 'status 7' fail in recovery and no change to your firmware, pertaining to the bootloader that is. There are any number of other reasons why something could go wrong during the process. MJB has been around long enough most customs ROM's have probably adapted their updater-script to include it. If not there are ways around this I (and several others) have documented elsewhere. My advice moving forward, make sure to educated yourself thoroughly before attempting anything that can brick your device and if you are not sure, ask first flash later.

dmplus said:
when you say "find" an AT&T 4.3 rom, I wish you could give me a link. I am working with a device that was handed to me that was on 4.3 then flashed to a t999 rom. Now I cannot get it to flash ANYTHING AT&T 4.3 (and I've looked all over), neither in odin, nor in recovery, except, oddly enough it will reflash the same t999 image. The radio (modem) also no longer works.
Click to expand...
Click to collapse
I assume your can get into download mode. If that is the case, try flashing this in Odin: http://forum.xda-developers.com/showthread.php?t=2498233

audit13 said:
I assume your can get into download mode. If that is the case, try flashing this in Odin: http://forum.xda-developers.com/showthread.php?t=2498233
Click to expand...
Click to collapse
I had tried to flash that via odin without success. What I was able to do to fix the issue was to flash a custom recovery via odin (TWRP). Then use the custom recovery to blind flash (no signature or md5 check) the ATT modem, and then I was able to flash the link you sent. After that it still didnt boot, so i had to reboot in TWRP, dump caches, reboot again, wait, literally like 5 minutes and it came back to life. Whew, what a day.

S3 keeps rebooting into recovery

So this is just a quick question. I've never had a phone reboot into recovery mode before, I've just had them either straight up hardbricked, stuck on logos, not booting, or only booting into Download Mode. From going through other threads (I used the search bar before asking this question. *shock&awe*), I'm gonna assume this is also considered a soft brick.
I'm not sure what was done to the phone because I upgraded to an S5 and passed this S3 down to my little brother who tried to flash another ROM. It was working fine on one of the stable versions of SlimKit before I got the S5 if that matters.
So my questions:
Is this considered a soft brick?
Would flashing stock everything resolve this issue? (reverting back to Stock everything, then reflashing custom ROMs)
Is there a simpler way to resolve this issue to avoid going back completely to stock?
Thanks for looking everyone.

Yes, anytime you can get to download mode or recovery its considered a soft brick. A hard brick will not boot anything at all.
Flashing stock firmware will be the best option imo. But you could just try flashing a rom. You will likely have to factory reset in either case.
If i had to guess, he probably formatted /system and then the rom failed to flash, leaving it with no OS.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

I haven't tried to do anything with it until he gets home, but best bet would be the following? Let me know if something's off or if I should do something another way:
Download stock firmware on the SD card
Factory reset
Flash stock firmware
Flash custom ROM
Reboot
At any point would the phone get unrooted? I'm gonna just make sure everything's set to go when the little bro gets home.

You cannot flash stock firmware from SD. Here is what you should do:
1) download stock firmware to your computer
2) factory reset, wipe cache and dalvik
3) flash stock firmware with Odin and make sure the device boots and works fine
4) flash custom recovery
5) flash custom ROM
6) reboot
Edit: also make sure you flash the correct firmware. For example if the device was ever updated to 4.3 then only flash that 4.3 build, any other that is lower will fail. And yes you will lose root when you flash back to stock but it doesn't mean much at all. You can gain root easily

I keep getting this issue in ODIN when I attempt to flash a stock firmware. Any ideas?
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVUENC2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

Ate you sure you have a T999, not a T999L.
Also, if kies is on your computer, uninstall it.

It's a S3 from T-Mobile directly, so I think it's a T999. I have Kies 3 for my S5 installed, so I'll go ahead and uninstall to try again. Will report back.

Check the sticker under the battery. T-Mobile doesnt sell the T999 anymore, only the T999L. Depends on how long ago you got it.

DocHoliday77 said:
Check the sticker under the battery. T-Mobile doesnt sell the T999 anymore, only the T999L. Depends on how long ago you got it.
Click to expand...
Click to collapse
I love you. Be back after getting the right firmware.

Just fyi in case you didnt know, there is an ota available for the T999L.
After flashing your firmware, go to settings , about device, and tap software update. It should update you to the latest build. (Still just 4.3, but i imagine its a bugfix/security update).
If you are up for putting in a little extra time, i can help you pull the ota (after downloading but before flashing it). If i can get a hold of this ota i can make an easier update method available for other members since no firmware has been released for it.
If you dont want to thats perfectly fine btw. Im sure someone else would get it soon.