Develop Bugs

[HELP]Bricked....Again..

So I Was Installing a New Rom[blah blah blah]. It wont go into recovery mode, only Download mode. While trying to fix this issue using Odin I get
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
The first time I unbricked my phone was last month and I just flashed the stock recovery on Odin but now it's not working. Any Suggestions?

On The Phone it Says
Product Name: SGH-1747
Custom Binary Download: Yes (5 Counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
and after I try flashing the VRALEC.bootchain.tar.md5 it adds
Secure Check Fail: aboot

Mistive said:
On The Phone it Says
Product Name: SGH-1747
Custom Binary Download: Yes (5 Counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
and after I try flashing the VRALEC.bootchain.tar.md5 it adds
Secure Check Fail: aboot
Click to expand...
Click to collapse
if yu can access the download mode, flash the 4.3 bootloader/modem and rom and hope it boots up
1st clean -up then flash without odin
edit: if yu upgraded to mjb bootloader downgrading is impossible
its not hard bricked then its still alive, keep trying, DONT RUSH or Panic or over-do-it if it doesnt (IT WILL ONLY MAKE THINGS WORSE) i have being there and i actually hard bricked my 1st time rooting

Help
winosxbuntu said:
if yu can access the download mode, flash the 4.3 bootloader/modem and rom and hope it boots up
1st clean -up then flash without odin
edit: if yu upgraded to mjb bootloader downgrading is impossible
its not hard bricked then its still alive, keep trying, DONT RUSH or Panic or over-do-it if it doesnt (IT WILL ONLY MAKE THINGS WORSE) i have being there and i actually hard bricked my 1st time rooting
Click to expand...
Click to collapse
Hi everyone nice to meet you I write from Colombia, I was triying to flash a ROM Wicked Sensations Rom doing what the post says but now I have a problem with my phone because I can not enter download mode, my model is SHG i747 and had installed a ROM 4.2.2 avatar, I did the flashing uding TWRP with all the steps of making a clean flash and when the reboot did not return to light and now I need a little help to try turn on download mode, Might help me with this?
This is the post: http://forum.xda-developers.com/showthread.php?t=2650039
Thank you
[email protected]

Don't use Odin to install a stock ROM if you have the 4.3 bootloader and it may brick your phone.

audit13 said:
Don't use Odin to install a stock ROM if you have the 4.3 bootloader and it may brick your phone.
Click to expand...
Click to collapse
Will brick your phone.
Sent from my SGH-I747 using XDA Premium 4 mobile app

mbrian27 said:
Will brick your phone.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
agree with mbrian and audit, check if yu can access the download mode, if not then try a JTAG, to force it into download mode
or try to get it in recovery mode

Hey guys. Not sure if I should start my own thread but after reading through many this seems to be the closest to my situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get the same message as the OP. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED

[Q] Please help!! M919UVUAMBF baseband?

I tried rooting my phone on 4.2.2 but ended up bricking without having a nandroid backup. So i downloaded stock UVUAMDB tar from k0nane thread and it flashed without any issues through odin. However, my baseband version now is UVUAMBF and my build number is UVUAMDB. Is this normal? I also can't connect to wifi and every other rom i flash fails on ODIN. I can flash any recovery but can't flash any other rom except the MDB tar file. Also tried downloading the UVUAMDL and flashed it but still failed on ODIN. Can someone please help with this? I have been trying to fix for 2 days now. Please help!!

What is your model number?

serio22 said:
What is your model number?
Click to expand...
Click to collapse
It is SGH-M919. Thanks for responding. Hope my phone is not totally useless now.

Can you link to the firmware you flashed? That build and baseband isn't even for the M919.. Have you tried flashing latest NB4 firmware?

serio22 said:
Can you link to the firmware you flashed? That build and baseband isn't even for the M919.. Have you tried flashing latest NB4 firmware?
Click to expand...
Click to collapse
I flashed the stock tar from this thread:
http://forum.xda-developers.com/showthread.php?t=2258628
I have attached a screenshot of the about device section of my phone.

hyperenigma said:
I flashed the stock tar from this thread:
http://forum.xda-developers.com/showthread.php?t=2258628
I have attached a screenshot of the about device section of my phone.
Click to expand...
Click to collapse
Go to Sammobile.com.........get the Official MDL 4.2.2 Firmware. Then you will be fine.

The Sickness said:
Go to Sammobile.com.........get the Official MDL 4.2.2 Firmware. Then you will be fine.
Click to expand...
Click to collapse
Alright. Thanks very much. I'm downloading right now and I'll post back regarding the outcome.

The Sickness said:
Go to Sammobile.com.........get the Official MDL 4.2.2 Firmware. Then you will be fine.
Click to expand...
Click to collapse
So i tried installing the official MDL 4.2.2 via odin but failed. I got this;
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sbl2.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any reason why? Thanks once again

Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?

serio22 said:
Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?
Click to expand...
Click to collapse
In download mode, it says,
ODIN MODE
PRODUCT NAME: SGH-M919
CUSTOM BINARY DOWNLOAD: YES
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
That's all it says. Recovery and everything else flashes in ODIN except modems and roms. Also in custom recovery using TWRP, it says error can't mount system. Don't know what's wrong. Plug into kies and says that's the latest firmware. Trying to update ota but can't because of my flash counter I think.

serio22 said:
Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?
Click to expand...
Click to collapse
Also, something weird happened in that I tried rooting using CF ROOT and I succeeded but when I click superuser, it says KNOX is enabled and that it will disable it. Am I supposed to have KNOX on 4.2.2? These all makes no sense to me.

serio22 said:
Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?
Click to expand...
Click to collapse
Please help. I don't even know what else to do right now. Can I flash a kernel or pit file or something. Just bought this 3 days ago.

Uninstall kies and flash MDL firmware, also try different Odin versions, USB ports, even computer if that doesn't work. What was the initial root method you used?

serio22 said:
Uninstall kies and flash MDL firmware, also try different Odin versions, USB ports, even computer if that doesn't work. What was the initial root method you used?
Click to expand...
Click to collapse
I downloaded the CF root file for the tmobile s4. I'll try your suggestions above and get back to you. Thanks.

serio22 said:
Uninstall kies and flash MDL firmware, also try different Odin versions, USB ports, even computer if that doesn't work. What was the initial root method you used?
Click to expand...
Click to collapse
I just tried everything you suggested above and stil no luck. Switched USB ports, switched computers and switched USB cables. Guess I am stuck with this.

hyperenigma said:
I just tried everything you suggested above and stil no luck. Switched USB ports, switched computers and switched USB cables. Guess I am stuck with this.
Click to expand...
Click to collapse
Is all that you want root or do you intend on flashing custom ROM?

serio22 said:
Is all that you want root or do you intend on flashing custom ROM?
Click to expand...
Click to collapse
I just want a ROM that could work with my Samsung gear since it doesn't work on 4.2.2.

hyperenigma said:
I just want a ROM that could work with my Samsung gear since it doesn't work on 4.2.2.
Click to expand...
Click to collapse
Ok and you say you can't flash ROMs with any recovery correct? And they are latest? If so then only thing I can suggest is to see if you can flash 4.4.2 with Odin, search for fenny's NB4 firmware and flash that, after that you can flash recovery and hopefully be able to flash ROMs without issue.. Just remember that it will trip Knox counter once you flash recovery

Im extremely curious where that baseband came from. Cause MDB was the firmware that shipped with the m919 on release. And according to your last 2 Letters of your baseband you have a modem from a firmware that came before MDB that was never shipped with the m919 but the rest MDB. I mean MBF isnt even on Samsungs open source site for ANY m919 variant. So that means MBF wasnt even released to the public or someone like me would of emailed for release of the source like I just did for GNG8.
You said you got it 3 days ago right? Did it come from a Samsung or Tmobile employee or something?
Anyways. Your getting the notification about knox cause theres a few knox files on 4.2.2 just basically not doing anything and SuperSu is detecting them. Your odin is failing on the bootloader (SBL/Samsung Boot Loader) Just for curiosity purposes can you download android terminal emulator and type getprop ro.bootloader and press enter post what version it says?
Since odin is failing, Id try Heimdall.

ShinySide said:
Im extremely curious where that baseband came from. Cause MDB was the firmware that shipped with the m919 on release. And according to your last 2 Letters of your baseband you have a modem from a firmware that came before MDB that was never shipped with the m919 but the rest MDB. I mean MBF isnt even on Samsungs open source site for ANY m919 variant. So that means MBF wasnt even released to the public or someone like me would of emailed for release of the source like I just did for GNG8.
You said you got it 3 days ago right? Did it come from a Samsung or Tmobile employee or something?
Anyways. Your getting the notification about knox cause theres a few knox files on 4.2.2 just basically not doing anything and SuperSu is detecting them. Your odin is failing on the bootloader (SBL/Samsung Boot Loader) Just for curiosity purposes can you download android terminal emulator and type getprop ro.bootloader and press enter post what version it says?
Since odin is failing, Id try Heimdall.
Click to expand...
Click to collapse
I bought it from a guy brand new. The phone was working perfectly fine when I purchased and there was no issues at all. I tried to flash a custom rom with 4.4.2 on the phone after rooting and everything just got messed up. Didn't check the baseband version then so I am not 100 percent sure about that as well. When I downloaded terminal emulator and did as you suggested, I got
M919UVUAMBF
I tried heimdall but don't know where to get the firmware package for the m919. Please any assistance will be very much appreciated at this point. Thank you very much

Samsung s3 odin problem

hey guys
im trying to update my s3 firmware from 4.1 to 4.3 using odin
i followed this guys tutorial
https://www.youtube.com/watch?v=eJkHx0zb-Bc
i literally have the exact same tech except i didnt start with 4.3, i started with 4.1
i used the odin to flash on the 4.3 thing, and when my phone restarted it showed an andoid robot with its chest open with blue circles and a blue progress bar
then after that just nothing. its completely black and no matter what i do it doesnt turn on or do anything
the only activity i can sense is that when i plug in the USB into the phone, the computer detects it
please help!!
heres the odin log thing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img.ext4
<ID:0/005> NON-HLOS.bin
<ID:0/005> recovery.img
<ID:0/005> rpm.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> system.img.ext4
<ID:0/005> tz.mbn
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

You have the i747m or i747? Where did you get the 4.3 ROM?

audit13 said:
You have the i747m or i747? Where did you get the 4.3 ROM?
Click to expand...
Click to collapse
Im not sure how to determine that
i got the 4.3 ROM from the youtube guide
I747UCUEMJB_2024954_REV04_user_low_ship
this is the file

Does your computer detect the phone in device manager as "qusbload" or something similar? If it does, you will need to try and debrick your phone using a debrick image and an sd card (http://forum.xda-developers.com/showthread.php?t=2549068).
Were you running stock 4.1.1 before you flashed?
Under the battery is a label attached to the phone. What is the model #? Is your s3 from AT&T?

audit13 said:
Does your computer detect the phone in device manager as "qusbload" or something similar? If it does, you will need to try and debrick your phone using a debrick image and an sd card (http://forum.xda-developers.com/showthread.php?t=2549068).
Were you running stock 4.1.1 before you flashed?
Under the battery is a label attached to the phone. What is the model #? Is your s3 from AT&T?
Click to expand...
Click to collapse
SGH I474
it IS from At&t
i dont remeber specifically which version
but it WAS 4.1
yes it says
qusbload

The phone is bricked because something seems to have gone wrong during the flash process. Most likely, something to do with the bootloader.
I read the comments on YouTube and it looks like a few people hard bricked their phone using this method.
Your phone is probably hard bricked since it does not boot at all. I assume you tried pulling and re-inserting the battery and charging the battery.
A USB jig, Odin, or Kies will probably not help. You will have to try the debrick method I linked or have it repaired via jtag.

audit13 said:
The phone is bricked because something seems to have gone wrong during the flash process. Most likely, something to do with the bootloader.
I read the comments on YouTube and it looks like a few people hard bricked their phone using this method.
How is your phone detected in Windows device manager?
Click to expand...
Click to collapse
it says qusbload
which guide do you recommend following to update my firmware correctly?

You can try this: http://forum.xda-developers.com/showthread.php?t=2549068 or this: http://forum.xda-developers.com/showthread.php?t=2660566
I have never used a de-brick method because I have never had to de-brick an s3.
I found this on youtube: https://www.youtube.com/watch?v=-RTAbLBVfMI

audit13 said:
You can try this: http://forum.xda-developers.com/showthread.php?t=2549068
I have never used a de-brick method because I have never had to de-brick an s3.
Click to expand...
Click to collapse
Can you explain to me what you think happened?
i mean i thought you werent supposed to go from 4.3 to 4.1 i thought i was going up
also im asking how you UPgrade fro 4.1 to 4.3 correctly
Thanks

Did you confirm the bootloader on your phone before upgrading? Maybe the phone needed to have a particular bootloader before applying the update.
Some people did brick their phones according to the youtube comments. Also, it looks like the 4.3 file that was on xda has been pulled because of possible bricking.
Try the debrick method as it is the only choice available unless you want to pay and have it repaired via jtag.

audit13 said:
Did you confirm the bootloader on your phone before upgrading? Maybe the phone needed to have a particular bootloader before applying the update.
Some people did brick their phones according to the youtube comments. Also, it looks like the 4.3 file that was on xda has been pulled because of possible bricking.
Click to expand...
Click to collapse
i dont know what "confirming bootloader on phone before upgrading" means
ahhh im so lost, someone save me T_T
im reading the link you sent me but the its not organized well in a way i know what is i474m or i474

The i747 is the AT&T version of the s3. The i747m is the Canadian version of the s3.
You need debrick images for the AT&T i747.
Before flashing anything to the s3, it is important to know the bootloader version of your phone. If the bootloader on your phone before the flash was newer than the 4.3 mjb version you flashed, this will brick the phone.
The debrick threads can be confusing which is why it is important to read and understand how your phone works with its software components.
Follow the instructions for the AT&T i747.

audit13 said:
The i747 is the AT&T version of the s3. The i747m is the Canadian version of the s3.
You need debrick images for the AT&T i747.
Before flashing anything to the s3, it is important to know the bootloader version of your phone. If the bootloader on your phone before the flash was newer than the 4.3 mjb version you flashed, this will brick the phone.
The debrick threads can be confusing which is why it is important to read and understand how your phone works with its software components.
Follow the instructions for the AT&T i747.
Click to expand...
Click to collapse
so the debrick brought my phone back to download mode! yay!
next i have to put the 4.3 bootloaders, a 4.3 rom, a 4.3 kernel and a 4.3 modem
im not sure how i should do this

Find the tar version of mjb bootloader and mjb modem in the general section of this forum and flash them using Odin.
Bootloader: http://forum.xda-developers.com/showthread.php?t=2321310
Then flash the latest TWRP custom recovery for the d2lte. Then flash the latest cm11 for your phone via TWRP.
This will hopefully get your phone up and running with a custom ROM.

audit13 said:
Find the tar version of mjb bootloader and mjb modem in the general section of this forum and flash them using Odin.
Bootloader: http://forum.xda-developers.com/showthread.php?t=2321310
Then flash the latest TWRP custom recovery for the d2lte. Then flash the latest cm11 for your phone via TWRP.
This will hopefully get your phone up and running with a custom ROM.
Click to expand...
Click to collapse
im following the instructions for the link you gave me
im stuck on this step:
When I first got mine booting again it would only boot with the micro SD card that has the .IMG file on it in the phone and only after a battery pull. What I did was boot back to recovery, remove my SD card and I had a spare SD card I used to flash the files with, I inserted it told TWRP to mount the new SD card, flashed the bootloader again and it seems to have cured my phones malfunctions. It now boots on its own like nothing ever happened. It may not happen like this for you???
my phone wont boot without the debrick SD card.
im not sure what this is trying to tell me to do
whats your take on it?
also in recovery mode, there is a option for factory reset.
is factory reset going to help at all with this?

I would not think that a factory reset would help since it only wipes the data and cache partitions.
So everything works again? Sounds like it was a bootloader issue.

audit13 said:
I would not think that a factory reset would help since it only wipes the data and cache partitions.
So everything works again? Sounds like it was a bootloader issue.
Click to expand...
Click to collapse
hey so i did the phones software update in about devices and it put me up to 4.4.1 kitkat
so im where i want to be.
if i want to install cyanogen mod, do you think following this link is good?
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
Thanks for the help

The latest is 4.4.2.
The easiest way would be to install a custom recovery usi Odin, backup the existing rom, wipe cache, data, system, install cm and gapps.
Use ROMs for the d2lte.

audit13 said:
The latest is 4.4.2.
The easiest way would be to install a custom recovery usi Odin, backup the existing rom, wipe cache, data, system, install cm and gapps.
Use ROMs for the d2lte.
Click to expand...
Click to collapse
can you give me a reputable URL that shows me how to do this?

Hopefully, the links still work: http://forum.xda-developers.com/showpost.php?p=60813687&postcount=3

HELP!!!! Galaxy S3 SGH-747. Cant restore firmware. Think its bricked!

I have a galaxy s3 and i rooted it. Then after a while when i booted the phone it the att logo pops up and the boot sound stops. The phone then stays like that with the LED pulsing blue. I tried odin to restore and it wont work. I tried flashing a new custom rom. Wont work. What do i do?
this is what i get in odin
<ID:0/003> 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/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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
warranty Bit: 1

After you use Odin to factory reset boot to stock recovery and do a factory reset and then let the phone boot the first time
Sent from my GT-N7105 using Tapatalk

rogersb11 said:
After you use Odin to factory reset boot to stock recovery and do a factory reset and then let the phone boot the first time
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
i tried odin and it failed. SW REV CHECK FAIL: Fused 3> Binary 0
i have cwrm installed. i think somethings wrong with the bootloader? Havent used android inyears so. i dont know whats going on...

donwload TWRP to your phone model, use odin to install and trie to do a reset factory, after that donwload firmware http://forum.xda-developers.com/showthread.php?t=1968625 copy to you phone and install use twrp

I would use Odin to flash TWRP recovery and then factory reset it, or use it to flash a rom, ur CWM may be too old to flash newer roms, try an updated version of TWRP
Sent from my XT1585 using Tapatalk

soupysoup said:
I would use Odin to flash TWRP recovery and then factory reset it, or use it to flash a rom, ur CWM may be too old to flash newer roms, try an updated version of TWRP
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
I ended up installing a rom but i still get the freezing. is thre anyway to flash every bit of the phone so that its as if it was brand new? because i dont know what modem version and other stuff my phone was at. had all the latest updates. what can i do. if i flashed the wrong bootloader or something would it even start?

BakedOnSomeSour said:
I ended up installing a rom but i still get the freezing. is thre anyway to flash every bit of the phone so that its as if it was brand new? because i dont know what modem version and other stuff my phone was at. had all the latest updates. what can i do. if i flashed the wrong bootloader or something would it even start?
Click to expand...
Click to collapse
No if u flashed the wrong bootloader or something it wouldn't even boot, there would be no coming back from a bad bootloader flash, I would try installing TWRP and then reset, then flash it stock with odin
Sent from my XT1585 using Tapatalk

Odin is failing because the ROM you are trying to flash has a bootloader that is older than the bootloader in the phone.
Before flashing anything else, I recommend finding the bootloader and modem version of the phone. Once you have this information, you will have a better idea of what you can and can't flash. An incompatible bootloader/modem combination could hard brick the phone too.

audit13 said:
Odin is failing because the ROM you are trying to flash has a bootloader that is older than the bootloader in the phone.
Before flashing anything else, I recommend finding the bootloader and modem version of the phone. Once you have this information, you will have a better idea of what you can and can't flash. An incompatible bootloader/modem combination could hard brick the phone too.
Click to expand...
Click to collapse
where can i find that info. i know it was updated to the latest software version. i cant remember all the info for it though. is there any way to get it? i cant get the phone to boot into OS so....

BakedOnSomeSour said:
where can i find that info. i know it was updated to the latest software version. i cant remember all the info for it though. is there any way to get it? i cant get the phone to boot into OS so....
Click to expand...
Click to collapse
i think i fixed it. will update

audit13 said:
Odin is failing because the ROM you are trying to flash has a bootloader that is older than the bootloader in the phone.
Before flashing anything else, I recommend finding the bootloader and modem version of the phone. Once you have this information, you will have a better idea of what you can and can't flash. An incompatible bootloader/modem combination could hard brick the phone too.
Click to expand...
Click to collapse
fixed it with this http://forum.xda-developers.com/gal...t/rom-d2att-ucufnj2-stock-rom-deodex-t3183267
without the help of all of you i woulda passed out lol

need to reprogram as the phone stuck at Samsung Galaxy S III

My phone got crashed which can't bootup. The phone always stayed with Official release, never rooted. I am not sure which version has been upgraded to, now it stuck with Galaxy S 3 screen, only thing I know it has the SecureLinux enabled, so it must be either 4.3 or 4.4. I wanted to reprogram to the official firmware, but not sure if I reprogram to the wrong version, would that causes any problem?
Please help.

additional infomation:
at download mode:
PRODUCT nAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE

Does this download menu look like 4.2?
Or it is 4.3 , I dont see warrenty flag.
Thanks.

No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.

audit13 said:
No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.
Click to expand...
Click to collapse
The phone is T999 for T-mobile, but seems there is one time only that it had official release of 4.2.1 or 4.2.2 available. I am not sure if I should flash the 4.1.2 or 4.2.1 back. But I seem can't find the 4.2.1 or 4.2.2 firmware on line anymore.
Question is that if I try to flash 4.1.2 to the phone, would it cause any problem if it was in 4.2.1?
Thanks all, I know this probably an old issue.

Flashing 4.1.1 or 4.1.2 should be fine.

audit13 said:
Flashing 4.1.1 or 4.1.2 should be fine.
Click to expand...
Click to collapse
###Right now I can't go to recovery mode, so I am trying to program the stock recovery, but failed. When I tried to odin the stock 4.1.2 it failed too. Here is the error during flashing stock recovery.
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Tried different USB cables? Different USB ports? The rom cam from sammobile.com?

audit13 said:
Tried different USB cables? Different USB ports? The rom cam from sammobile.com?
Click to expand...
Click to collapse
Here is the error msg:
<ID:0/008> 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/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)

It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.

audit13 said:
It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.
Click to expand...
Click to collapse
thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3?

You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.

thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3? All I want is just get the phone back. I tried to load 4.3 bootloader, but it failed.

audit13 said:
You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.
Click to expand...
Click to collapse
There is possibility that the pit is wrong, I tried to load the downloaded T999-16Gb pit from download site, maybe that file is not right? Since I can flash the stock boot.img by using Odin for version 4.1.2, the bootloader must be right???, Don't know what aboot.mbn would be affected by anything else.
I am wondering if someone can provide the T999 regular 16GB pit file, the early version of T999, Thanks.

A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.

audit13 said:
A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.
Click to expand...
Click to collapse
is it possible that the phone is upgrading from 4.1.2 to 4.3 and got crashed. but the bootloader is still showing 4.1.2?
what other possible reason that I can't flash aboot.mbn?

Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.

audit13 said:
Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.
Click to expand...
Click to collapse
Reboot to download mode, it is saying the same.
I am trying to flash stock recovery, modem, bootloader, all stock version 4.1.2 Only it can flash 4.1.2 bootloader, the recovery and modem always fails. Also the stock rom got failed.
With the same setting I can flash my other S3 recovery without problem, so the Odin, USB cable should not be an issue.
Thanks.

Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.

audit13 said:
Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.
Click to expand...
Click to collapse
the only problem is that my other working phone is running 4.3. I don't know what is the procedure to program it to 4.3 if my crashed one is in 4.1.2