Develop Bugs

[Q] MK2 Modem FAIL'S on Odin

I am having trouble updating my modem to the new MK2. I have tried several times following the instructions
found in various places here on XDA, but nothing works.
_________________________________________________
Phone: SGH-M919 ( Galaxy 4 )
Carrier: T-Mobile LTE
Location: Phoenix
Custom ROM: DARTHSTALKER S4 v.X1 (MK2 & MDL Compliant)
Android version: 4.3 <<<<---- Is this a problem Im on 4.3 ?
Baseband: M919UVUAMDL
Kernel: 3.4.0-g4fe9989-dirty.joy23 #1
SELinux status: Permissive
This is what I am doing to try to update modem.....
1. Open Odin on PC (Mobile Odin doesn't run on G4 T-Mobile.LTE USA)
2. Uncheck Auto-Reboot / Load Modem.bin in the phone tab
3. Boot the phone into Download Mode via power & vol down
4. Plug USB into PC and PHONE
5. I see the BIG GREEN DROID
In the upper left corner of the phone, in tiny font it says:
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Back on Odin now.....
The ID:COM tab in Odin turns blue and looks good to go. I click on "START".
The bar above ID:COM slowly fills with green. BUT when it is finished, the box above the ID:COM
turns RED and says FAILED !!.
### SEE PICTURE BELLOW ###
Back on the phone the tiny print in the upper left corner now says:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
START [224,1440]
SECURE CHECK FAIL : NDN
Why is it failing ??? Is it because I am on a 4.3 ROM ?
Please help me ....
Thanks
.

Follow this thread:
http://forum.xda-developers.com/showthread.php?t=2544612
There might be something wrong with the file. The bootloader is not accepting it due to failed authentication. Be aware that when updating, you won't see the baseband version as UVUEMK2. You'll just see the old MDL one. This is because you can only update to one of the modem files without any issues.

I have absolutely the same problem - Nothing helps - I have followed the link that was pasted in the second comment and it simply does not work. Once it fails on my phone I have to try to flash stock 4.2.2 to unbrick my device. I am following all of the posts hopefully some new way to update the modems comes out so that I do not have to lock my bootloader down.

Are you trying to just flash the bin file not tarred?
Sent from my SGH-M919 using Tapatalk

Thibor69 said:
I am having trouble updating my modem to the new MK2. I have tried several times following the instructions
found in various places here on XDA, but nothing works.
_________________________________________________
Phone: SGH-M919 ( Galaxy 4 )
Carrier: T-Mobile LTE
Location: Phoenix
Custom ROM: DARTHSTALKER S4 v.X1 (MK2 & MDL Compliant)
Android version: 4.3 <<<<---- Is this a problem Im on 4.3 ?
Baseband: M919UVUAMDL
Kernel: 3.4.0-g4fe9989-dirty.joy23 #1
SELinux status: Permissive
This is what I am doing to try to update modem.....
1. Open Odin on PC (Mobile Odin doesn't run on G4 T-Mobile.LTE USA)
2. Uncheck Auto-Reboot / Load Modem.bin in the phone tab
3. Boot the phone into Download Mode via power & vol down
4. Plug USB into PC and PHONE
5. I see the BIG GREEN DROID
In the upper left corner of the phone, in tiny font it says:
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Back on Odin now.....
The ID:COM tab in Odin turns blue and looks good to go. I click on "START".
The bar above ID:COM slowly fills with green. BUT when it is finished, the box above the ID:COM
turns RED and says FAILED !!.
### SEE PICTURE BELLOW ###
Back on the phone the tiny print in the upper left corner now says:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
START [224,1440]
SECURE CHECK FAIL : NDN
Why is it failing ??? Is it because I am on a 4.3 ROM ?
Please help me ....
Thanks
.
Click to expand...
Click to collapse
Please NOTE: the following procedure is NOT valid for AOSP/AOKP/KitKat/CM roms.
The following instructions are exclusively for those people who are using the
Tmobile M919 stock based Jellybean 4.2.2 or 4.3 Touchwiz custom roms.
Follow the easy step by step instructions to a "T".
You can Odin flash the MK2 modem.bin while on any Jellybean Touchwiz 4.2.2 based rom
or ODIN flash it after flashing the Infamous v9, Wicked v9.1, or any M919 MK2 JB based
Touchwiz 4.3 roms. Either way it makes no difference.
What does make a difference is to follow this step by step exactly.
First download the MK2 modem.bin from the link below:
http://www.mediafire.com/download/1gsjokadys4l89x/modem.bin
#1: Manually power down the phone by using the power button only.
#2: Start ODIN and put the MODEM.BIN file into ODIN'S PHONE slot.
#3: Put the phone into download mode using the volume down and power button.
#4: Plug the USB cable into the phone and into the computer.
#5: Make sure that ODIN'S [COM:xx] lights up.
#6: Un-Check the Auto-Reboot in ODIN and click START.
#7: After its done flashing unplug the usb cable.
#8: Manually power off the phone by using the power button only.
#9: Wait 30 or so seconds before you power on the phone.
After doing this the MK2 baseband should show up in About Device.
Once it displays MK2 you can flash any MK2 JB TW 4.3 custom cwm/twrp
zip file roms unless you have already flashed it before flashing the modem.bin
in which case you are done and ready to use the phone.
Good luck!

Misterjunky said:
Please NOTE: the following procedure is NOT valid for AOSP/AOKP/KitKat/CM roms.
The following instructions are exclusively for those people who are using the
Tmobile M919 stock based Jellybean 4.2.2 or 4.3 Touchwiz custom roms.
Follow the easy step by step instructions to a "T".
You can Odin flash the MK2 modem.bin while on any Jellybean Touchwiz 4.2.2 based rom
or ODIN flash it after flashing the Infamous v9, Wicked v9.1, or any M919 MK2 JB based
Touchwiz 4.3 roms. Either way it makes no difference.
What does make a difference is to follow this step by step exactly.
First download the MK2 modem.bin from the link below:
http://www.mediafire.com/download/1gsjokadys4l89x/modem.bin
#1: Manually power down the phone by using the power button only.
#2: Start ODIN and put the MODEM.BIN file into ODIN'S PHONE slot.
#3: Put the phone into download mode using the volume down and power button.
#4: Plug the USB cable into the phone and into the computer.
#5: Make sure that ODIN'S [COM:xx] lights up.
#6: Un-Check the Auto-Reboot in ODIN and click START.
#7: After its done flashing unplug the usb cable.
#8: Manually power off the phone by using the power button only.
#9: Wait 30 or so seconds before you power on the phone.
After doing this the MK2 baseband should show up in About Device.
Once it displays MK2 you can flash any MK2 JB TW 4.3 custom cwm/twrp
zip file roms unless you have already flashed it before flashing the modem.bin
in which case you are done and ready to use the phone.
Good luck!
Click to expand...
Click to collapse
.
.
Hi Misterjunky
I do thank you for the walk through .... but unless I am really blind, I am pretty sure as per my
OP that I did follow your steps to a "T" :angel:. If I missed something, PLEASE point it out for me ??
Everything goes just fine until Odin finishes the flash of the modem.bin and says FAILED.
I think the only difference is that I am running a different ROM than you mention, but you do say:
1) You can Odin flash the MK2 modem.bin while on any Jellybean Touchwiz 4.2.2 based rom
2) Or ODIN flash it after flashing the Infamous v9, Wicked v9.1, or any M919 MK2 JB based
Touchwiz 4.3 roms. Either way it makes no difference.
Now since I am running DARTHSTALKER S4 ☆ | VERSION X1 | Aroma | Multi-Carrier | 12.29.2013
( This ROM Is Based On The T-Mobile UVUEMK2 4.3 Base )
Option #1) does not apply to me ... BUT ... option #2) DOES apply to me and this ROM since DarthStalker is 4.3 based.
So I should be able to just Odin flash Modem.bin via your steps correct ?? Or am I wrong ?
Please help me ... my OCD is in overdrive atm
Thanks guys !!
.
PS: Shinyside - Yes I am only flashing Modem.bin since I am already on a MDL there is no need to flash the *MDL.tar.MD5
PSS: Vigs - you wrote "There might be something wrong with the file. The bootloader is not accepting it due to failed
authentication. Be aware that when updating, you won't see the baseband version as UVUEMK2. You'll see the old MDL one.
Yes I have tried the Modem.bin file from 3 sources and the file
is fine. I know I wont see baseband as MK2, but that's not my issue mate. The flash FAILS.
.

Thibor69 said:
.
.
Hi Misterjunky
I do thank you for the walk through .... but unless I am really blind, I am pretty sure as per my
OP that I did follow your steps to a "T" :angel:. If I missed something, PLEASE point it out for me ??
Everything goes just fine until Odin finishes the flash of the modem.bin and says FAILED.
I think the only difference is that I am running a different ROM than you mention, but you do say:
1) You can Odin flash the MK2 modem.bin while on any Jellybean Touchwiz 4.2.2 based rom
2) Or ODIN flash it after flashing the Infamous v9, Wicked v9.1, or any M919 MK2 JB based
Touchwiz 4.3 roms. Either way it makes no difference.
Now since I am running DARTHSTALKER S4 ☆ | VERSION X1 | Aroma | Multi-Carrier | 12.29.2013
( This ROM Is Based On The T-Mobile UVUEMK2 4.3 Base )
Option #1) does not apply to me ... BUT ... option #2) DOES apply to me and this ROM since DarthStalker is 4.3 based.
So I should be able to just Odin flash Modem.bin via your steps correct ?? Or am I wrong ?
Please help me ... my OCD is in overdrive atm
Thanks guys !!
.
PS: Shinyside - Yes I am only flashing Modem.bin since I am already on a MDL there is no need to flash the *MDL.tar.MD5
PSS: Vigs - you wrote "There might be something wrong with the file. The bootloader is not accepting it due to failed
authentication. Be aware that when updating, you won't see the baseband version as UVUEMK2. You'll see the old MDL one.
Yes I have tried the Modem.bin file from 3 sources and the file
is fine. I know I wont see baseband as MK2, but that's not my issue mate. The flash FAILS.
.
Click to expand...
Click to collapse
I know you're only flashing the modem. But is it just in is raw form or is it tarred? The modem bin needs to be tarred. And from your screen shot, because I can't remember off the top of my head if Odin shows the tar ext when loaded, it looks like you are just loading the actual bin file and not tarred

Since I have the exact problem I thought I'd chime in too. The problem seems to be in the response from the bootloader. That is the step which my flashing stops as well. I have followed all steps and in all the posts very carefully and it is simply not the problem.
I am just wondering what the response from the bootloader have to be for that step to be completed successfully!
I am on stock 4.2.2 I only have it rooted so still looking for some solution for the modem to be able to update 4.3 as the op!
Sent from my Nexus 7 using Tapatalk

alextop30 said:
Since I have the exact problem I thought I'd chime in too. The problem seems to be in the response from the bootloader. That is the step which my flashing stops as well. I have followed all steps and in all the posts very carefully and it is simply not the problem.
I am just wondering what the response from the bootloader have to be for that step to be completed successfully!
I am on stock 4.2.2 I only have it rooted so still looking for some solution for the modem to be able to update 4.3 as the op!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Try mobile Odin. I was able to bypass the checks and flash i9505 modems a while back.
Sent from my SGH-M919 using Tapatalk

re: TAR files.
ShinySide said:
I know you're only flashing the modem. But is it just in is raw form or is it tarred? The modem bin needs to be tarred. And from your screen shot, because I can't remember off the top of my head if Odin shows the tar ext when loaded, it looks like you are just loading the actual bin file and not tarred
Click to expand...
Click to collapse
The actual MODEM.BIN file is what needs to be loaded into Odin's "PHONE" tab/slot.
It should also work if it's a TAR file but it's best to flash it as modem.bin, that way there
is less of a chance of having a TAR file which might be or become corrupt.
The nice part about TAR or ZIP files is that we can flash multiple files in one flashing.
But if there is only one file which needs to be flashed (modem.bin) it's always best just
to flash the one file without adding compression or other changes to it.
TAR files are similar to ZIP files, they compress whatever files are inside of them
to a smaller size, but in doing so there is more of a chance that the file inside the TAR
or ZIP getting corrupted.
That's why I simply posted the modem.bin to be used by Odin, less chance of problems.

.
Hey MisterJunky,
Yes I was pretty certain that modem.bin does NOT need to be tar'd or zipped, so you also confirmed this.
Well that then leads us to a DEAD END. Since I am doing it EXACTLY the way you discribe it (with Modem.bin)
I don't know what else could be wrong. You quoted / replied to Shinyside's theory which is fine, but didn't
really reply to my thoughts .... I was wondering if it could be a issue with my ROM which is a 4.3 ROM. Although I think it doesn't matter .. ?
Thibor69 said:
I think the only difference is that I am running a different ROM than you mention, but you do say:
1) You can Odin flash the MK2 modem.bin while on any Jellybean Touchwiz 4.2.2 based rom
2) Or ODIN flash it after flashing the Infamous v9, Wicked v9.1, or any M919 MK2 JB based
Touchwiz 4.3 roms. Either way it makes no difference.
Now since I am running DARTHSTALKER S4 ☆ | VERSION X1 | Aroma | Multi-Carrier | 12.29.2013
( This ROM Is Based On The T-Mobile UVUEMK2 4.3 Base )
Option #1) does not apply to me ... BUT ... option #2) DOES apply to me and this ROM since DarthStalker is 4.3 based.
So I should be able to just Odin flash Modem.bin via your steps correct ?? Or am I wrong ?
Click to expand...
Click to collapse
ALSO ... just so you all know. Mobile Odin DOES NOT RUN on a USA T-Mobile Galaxy 4 phone. Mobile Odin has documented this fact.
Any other suggestions guys ????
Thank you
Misterjunky said:
The actual MODEM.BIN file is what needs to be loaded into Odin's "PHONE" tab/slot.
It should also work if it's a TAR file but it's best to flash it as modem.bin, that way there
is less of a chance of having a TAR file which might be or become corrupt.
The nice part about TAR or ZIP files is that we can flash multiple files in one flashing.
But if there is only one file which needs to be flashed (modem.bin) it's always best just
to flash the one file without adding compression or other changes to it.
TAR files are similar to ZIP files, they compress whatever files are inside of them
to a smaller size, but in doing so there is more of a chance that the file inside the TAR
or ZIP getting corrupted.
That's why I simply posted the modem.bin to be used by Odin, less chance of problems.
Click to expand...
Click to collapse

Yeah I've never heard of anyone not taring items for Odin. Weird but if it works it works.
Sent from my SGH-M919 using Tapatalk
---------- Post added at 04:09 AM ---------- Previous post was at 04:07 AM ----------
Thibor69 said:
.
Hey MisterJunky,
Yes I was pretty certain that modem.bin does NOT need to be tar'd or zipped, so you also confirmed this.
Well that then leads us to a DEAD END. Since I am doing it EXACTLY the way you discribe it (with Modem.bin)
I don't know what else could be wrong. You quoted / replied to Shinyside's theory which is fine, but didn't
really reply to my thoughts .... I was wondering if it could be a issue with my ROM which is a 4.3 ROM. Although I think it doesn't matter .. ?
ALSO ... just so you all know. Mobile Odin DOES NOT RUN on a USA T-Mobile Galaxy 4 phone. Mobile Odin has documented this fact.
Any other suggestions guys ????
Thank you
Click to expand...
Click to collapse
It's your bootloader rejecting it.
Do you have mobile Odin? It actually skips or over rides or doesn't get stopped by the bootloader verification.
Sent from my SGH-M919 using Tapatalk

Thibor69 said:
I am having trouble updating my modem to the new MK2. I have tried several times following the instructions
found in various places here on XDA, but nothing works.
_________________________________________________
Phone: SGH-M919 ( Galaxy 4 )
Carrier: T-Mobile LTE
Location: Phoenix
Custom ROM: DARTHSTALKER S4 v.X1 (MK2 & MDL Compliant)
Android version: 4.3 <<<<---- Is this a problem Im on 4.3 ?
Baseband: M919UVUAMDL
Kernel: 3.4.0-g4fe9989-dirty.joy23 #1
SELinux status: Permissive
This is what I am doing to try to update modem.....
1. Open Odin on PC (Mobile Odin doesn't run on G4 T-Mobile.LTE USA)
2. Uncheck Auto-Reboot / Load Modem.bin in the phone tab
3. Boot the phone into Download Mode via power & vol down
4. Plug USB into PC and PHONE
5. I see the BIG GREEN DROID
In the upper left corner of the phone, in tiny font it says:
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Back on Odin now.....
The ID:COM tab in Odin turns blue and looks good to go. I click on "START".
The bar above ID:COM slowly fills with green. BUT when it is finished, the box above the ID:COM
turns RED and says FAILED !!.
### SEE PICTURE BELLOW ###
Back on the phone the tiny print in the upper left corner now says:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
START [224,1440]
SECURE CHECK FAIL : NDN
Why is it failing ??? Is it because I am on a 4.3 ROM ?
Please help me ....
Thanks
.
Click to expand...
Click to collapse
I've already posted a possible solution on my thread, but just in case, I'll repost it here: "Hm...I'm going to guess that it's maybe the Odin version that's affecting it? Here, try flashing using this version of Odin here: http://www.mediafire.com/download/1ap3sg0e2215ga6/Odin3.rar."

Thibor69 said:
.
Hey MisterJunky,
Yes I was pretty certain that modem.bin does NOT need to be tar'd or zipped, so you also confirmed this.
Well that then leads us to a DEAD END. Since I am doing it EXACTLY the way you discribe it (with Modem.bin)
I don't know what else could be wrong. You quoted / replied to Shinyside's theory which is fine, but didn't
really reply to my thoughts .... I was wondering if it could be a issue with my ROM which is a 4.3 ROM. Although I think it doesn't matter .. ?
ALSO ... just so you all know. Mobile Odin DOES NOT RUN on a USA T-Mobile Galaxy 4 phone. Mobile Odin has documented this fact.
Any other suggestions guys ????
Thank you
Click to expand...
Click to collapse
I just checked the supported devices of Mobile Odin in the thread by Chainfire and it seems that the SGH - M919 - which is the T-Mobile variant of the galaxy s4 is supported http://forum.xda-developers.com/showthread.php?t=1347899
Can you please link the documentation that you cannot flash the modem using that tool - I just want to read it before I go flash something again and end up softbricking my device.
As for my comment that pertains to the rest of the post - I just cannot understand how it worked for so many people using Odin from your computer and now it seems like it just does not flash for anyone that has recently attempted to update the modems!

re: try this.
alextop30 said:
I just checked the supported devices of Mobile Odin in the thread by Chainfire and it seems that the SGH - M919 - which is the T-Mobile variant of the galaxy s4 is supported http://forum.xda-developers.com/showthread.php?t=1347899
Can you please link the documentation that you cannot flash the modem using that tool - I just want to read it before I go flash something again and end up softbricking my device.
As for my comment that pertains to the rest of the post - I just cannot understand how it worked for so many people using Odin from your computer and now it seems like it just does not flash for anyone that has recently attempted to update the modems!
Click to expand...
Click to collapse
Why not try this, but before you do if you have a working rom in your phone right now
be sure to make a nandroid backup in recovery before trying the following:
Go into recovery and do a "Factory Reset" and wipe data/cache/system/dalvik cache.
Then shut down the phone, wait 20 seconds or so after shutting it down and boot back
up into Download mode and try Odin again...............
There is a 50/50 chance it will work.
Good luck!

alextop30 said:
I just checked the supported devices of Mobile Odin in the thread by Chainfire and it seems that the SGH - M919 - which is the T-Mobile variant of the galaxy s4 is supported http://forum.xda-developers.com/showthread.php?t=1347899
Can you please link the documentation that you cannot flash the modem using that tool - I just want to read it before I go flash something again and end up softbricking my device.
Click to expand...
Click to collapse
Huh .... I bought the app last night and returned for a refund, BUT this looks like a newer version then the one I had... allthough the update of Mobile Odin is from Nov. it looks like a different version ... how can that be. ANyway I will try this version tomorrow and let you know if it fails .... Thank you !!
Hi Shiamatsu -
Thank you for the link to that version of PC Odin. I will try that in the morning also.
I follow your post ... sorry I missed that !! Thanks
Hi MisterJunky -
Thanks for the idea. I will try that as my final attempt if the above 2 things dont work out for me.
Thanks all !!!!

alextop30 said:
I just checked the supported devices of Mobile Odin in the thread by Chainfire and it seems that the SGH - M919 - which is the T-Mobile variant of the galaxy s4 is supported http://forum.xda-developers.com/showthread.php?t=1347899
Can you please link the documentation that you cannot flash the modem using that tool - I just want to read it before I go flash something again and end up softbricking my device.
Click to expand...
Click to collapse
Well I guess it is not the phone that wont run Odin, but seems that Odin Mobile Pro does not like Android 4.3
### SEE PICTURE ####
I am now searching for a FlashKernel for this phone.
Need FlashKernel for T-Mobile SGH-M919 running on Android 4.3 ROM. If you happen to find one, please share !!!! )
ThaNKS

shiamatsu said:
I've already posted a possible solution on my thread, but just in case, I'll repost it here: "Hm...I'm going to guess that it's maybe the Odin version that's affecting it? Here, try flashing using this version of Odin here: http://www.mediafire.com/download/1ap3sg0e2215ga6/Odin3.rar."
Click to expand...
Click to collapse
Thanks but sorry it is still a NO GO with that version of ODIN.

Alright before flashing the MK2 modem via Download Mode, try resetting the binary counter using an app called Triangle Away (its located here on xda developers). Once you install the app, please follow the instructions given. You need to be on a TouchWiz rom with a stock Samsung kernel (best way is to Odin to stock 4.2.2 MDL). This is something that I read from Chainfire's Google+ page which may be the solution:
"Still, the binary status needs to be official and the counter 0 on recent bootloaders if you want to do fun things like flash modems with for example Mobile ODIN (update coming as well). Otherwise the bootloader will mark those regions of the flash storage as protected, and they cannot be written to (causing freezes and whatnot)."
Give it a try and see what happens. The 4.2.2 bootloader isn't recent. But, who knows?

Thibor69 did resetting the counter work to flash the modem successfully?
Sent from my Nexus 7 using Tapatalk

Unrooting from CM 11 after a previous stock 4.3 OTA update - NAND Write Fail!!

Hi Guys,
I have an unlock code from AT&T and I want to use it from the Stock ROM. I am currently running CM 11 nightlies.
I tried the standard method of using ODIN from PC to flash stock ROM. It doesnt seem to work. I am always stuck in ;NAND write Fail'.
Before installing CM a while ago I updated OTA to 4.3, and based on what I read everywhere this seems to have something to do with the issue.
Any help on how to proceed will be great.
I am using ODIN 3.07
Downloaded Stock ROM from sammobile.
This is what my download screen reads.
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (2 Counts)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 2
SW REV CHECK FAIL: Fused 2 > Binary 0
Thanks!

Once you have the 4.3 bootloader, you cannot use Odin to install a stock AT&T ROM. You can try this: http://forum.xda-developers.com/showthread.php?t=2658486

audit13 said:
Once you have the 4.3 bootloader, you cannot use Odin to install a stock AT&T ROM. You can try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
Thanks! I will take a look. Hopefully I can unlock my device at some point.

Was able to unlock based on the lead from post #2

[Q] Soft Bricked? i747 help

hello, I bought this i747 in its current condition. I know nothing about its history.
when I power it on it goes to the phone, !, comp screen saying firmware upgrade encounter an issue, select recovery mode in kies.
in the top corner it says:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BITS: 0
BOOTLOADER RP SWREV: 2
Now when I connect to kies and run emergency firmware everything loads on kies, then gives an error, and
underneath BOOTLOADER RP SWREV: 2 it says: SW REV CHECK FAIL: Fused 2 > Binary 0 in red.
If this phone fixable? Any help would be appreciated.

mtsosie said:
hello, I bought this i747 in its current condition. I know nothing about its history.
when I power it on it goes to the phone, !, comp screen saying firmware upgrade encounter an issue, select recovery mode in kies.
in the top corner it says:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BITS: 0
BOOTLOADER RP SWREV: 2
Now when I connect to kies and run emergency firmware everything loads on kies, then gives an error, and
underneath BOOTLOADER RP SWREV: 2 it says: SW REV CHECK FAIL: Fused 2 > Binary 0 in red.
If this phone fixable? Any help would be appreciated.
Click to expand...
Click to collapse
Did you say it was recognized in Kies but firmware recovery failed? If so, and you were using Kies (not Kies 3), we may assume the last system update was not older than Android 4.1.1. I'll suggest you try these steps (in that order),i.e. if one doesn't work, try the next step ..
1. Try booting into recovery mode and doing a hard wipe/reset
2. Download the correct stock image from the thread below and flash via Odin. If you need help with flashing via Odin, please let me know
http://forum.xda-developers.com/showthread.php?t=1739426 or visit Sammobile.com to download the correct stock image.
3. Open Kies. Do not connect the phone yet. Go to Tools => Firmware Upgrade and Initialization. Enter your phone model name (SGH-I747)=>OK and serial number. Check device information inside the battery compartment. Wait for firmware download to complete and you are prompted to connect the phone and follow the rest of the on-screen instructions.
4. Contact the vendor to find out what they did wrong and see what refund options you have

Ok, so I also wasn't able to get into recovery.
I decided to flash cwm via odin. After it flashed the phone rebooted and turned on normally. I have turned it on and off like 5 times and everytime it boots normal.....But, there is still a problem... baseband version is Unknown and there is no IMEI Number.

Larry2999 said:
Did you say it was recognized in Kies but firmware recovery failed? If so, and you were using Kies (not Kies 3), we may assume the last system update was not older than Android 4.1.1. I'll suggest you try these steps (in that order),i.e. if one doesn't work, try the next step ..
1. Try booting into recovery mode and doing a hard wipe/reset
2. Download the correct stock image from the thread below and flash via Odin. If you need help with flashing via Odin, please let me know
http://forum.xda-developers.com/showthread.php?t=1739426 or visit Sammobile.com to download the correct stock image.
3. Open Kies. Do not connect the phone yet. Go to Tools => Firmware Upgrade and Initialization. Enter your phone model name (SGH-I747)=>OK and serial number. Check device information inside the battery compartment. Wait for firmware download to complete and you are prompted to connect the phone and follow the rest of the on-screen instructions.
4. Contact the vendor to find out what they did wrong and see what refund options you have
Click to expand...
Click to collapse
hi, yes those were the steps I tried and the result was fail. Now that I can boot it, it shows its 4.3 but no baseband and no imei.

mtsosie said:
hi, yes those were the steps I tried and the result was fail. Now that I can boot it, it shows its 4.3 but no baseband and no imei.
Click to expand...
Click to collapse
Oh, it's 4.3. Perhaps even better because you may be able to flash the 4.3 restore image. Your baseband/modem is corrupt or missing which is why it's showing the no baseband message.
Please see the thread below for the complete 4.3 stock restore image. Download the stock restore image and flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=2658486
Or you may just flash the 4.3 JB modem via custom recovery since you have custom recovery working. The modem zip can be found here ...
http://www.androidfilehost.com/?fid=23212708291681456

Larry2999 said:
Oh, it's 4.3. Perhaps even better because you may be able to flash the 4.3 restore image. Your baseband/modem is corrupt or missing which is why it's showing the no baseband message.
Please see the thread below for the complete 4.3 stock restore image. Download the stock restore image and flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=2658486
Or you may just flash the 4.3 JB modem via custom recovery since you have custom recovery working. The modem zip can be found here ...
http://www.androidfilehost.com/?fid=23212708291681456
Click to expand...
Click to collapse
:good: right on. you rock man. I flashed the modem and it works great now. thanks again.

mtsosie said:
:good: right on. you rock man. I flashed the modem and it works great now. thanks again.
Click to expand...
Click to collapse
You are most welcome. Glad to know it's now working.

hey guys am in trouble
Odin Refuse to flash
I747 warranty bit :1
bootloader rp swrev 2
SW rev check fail fused 2
Phone stuck on kies firmware upgrade encounterd
I Cant get 4.3 back again or downgrade to any older version
plz help me :'(
here is two screen shot in download mode while odin error
and in normal mode when i try 2 open

dark_darkness said:
hey guys am in trouble
Odin Refuse to flash
I747 warranty bit :1
bootloader rp swrev 2
SW rev check fail fused 2
Phone stuck on kies firmware upgrade encounterd
I Cant get 4.3 back again or downgrade to any older version
plz help me :'(
here is two screen shot in download mode while odin error
and in normal mode when i try 2 open
Click to expand...
Click to collapse
Can you try flashing custom recovery via Odin and then using custom recovery to do a stock restore to 4.3 following the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486

can u share a link?
Larry2999 said:
Can you try flashing custom recovery via Odin and then using custom recovery to do a stock restore to 4.3 following the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
i've tried many custom roms
start flashing will and end with bug error at the end coz of warranty
can u share me a link for firmware tested ?

dark_darkness said:
i've tried many custom roms
start flashing will and end with bug error at the end coz of warranty
can u share me a link for firmware tested ?
Click to expand...
Click to collapse
I suggested custom recovery and not custom ROM. The idea is to get your phone back in working order first. Flashing a complete stock restore image should do it. Please refer to the thread I forwarded earlier. You should be able to flash custom recovery (like CWM or TWRP) to your phone via Odin and then use the custom recovery to flash the stock restore image.

Sgh-747 bricked

I was trying to change the firmware of my S3 but in the middle of the process the computer went off. Now is bricked showing the KIES message, when a try to go back to stock using the only official firmware that is in Sammobile it says AUTH error.
The screen of the S3 in download mode says:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD:NO
CURRENT BINARY:SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV: 2
It was running the 4.2.2 that I got via OTA but I can not use the same because I do not have access to the recovery mode. I think that if I could find a .tar 4.2.2 I could solve the problem. Please guys I need your help on this. Any suggestion o way to solve?

wmobility00 said:
I was trying to change the firmware of my S3 but in the middle of the process the computer went off. Now is bricked showing the KIES message, when a try to go back to stock using the only official firmware that is in Sammobile it says AUTH error.
The screen of the S3 in download mode says:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD:NO
CURRENT BINARY:SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV: 2
It was running the 4.2.2 that I got via OTA but I can not use the same because I do not have access to the recovery mode. I think that if I could find a .tar 4.2.2 I could solve the problem. Please guys I need your help on this. Any suggestion o way to solve?
Click to expand...
Click to collapse
Were you running 4.2.2 or 4.4.2? I thought the AT&T SGS3 (i747) went from 4.1.1 to 4.1.2 to 4.3 to 4.4.2 for official ROMs. The 4.1.1 stock ROM on sammobile was the last full release, all since have been updates. The WARRANTY BIT: 1 output would indicate it was on at least the 4.3 release if not one of the 4.4.2 releases; NE4, NJ1, or NJ2.
While I am waiting for a reply I will search to see if any of the devs created a 4.4.2 stock tar, I have seen in done with an older version, but it is a rare occurrence.

Simplest way to get the phone up and running would be to flash TWRP and then cm11. By booting CM11, you could determine the bootloader and modem. Once these two things are know, you may be able to flash an updated bootloader, modem, and ROM from TWRP.

dawgdoc said:
Were you running 4.2.2 or 4.4.2? I thought the AT&T SGS3 (i747) went from 4.1.1 to 4.1.2 to 4.3 to 4.4.2 for official ROMs. The 4.1.1 stock ROM on sammobile was the last full release, all since have been updates. The WARRANTY BIT: 1 output would indicate it was on at least the 4.3 release if not one of the 4.4.2 releases; NE4, NJ1, or NJ2.
While I am waiting for a reply I will search to see if any of the devs created a 4.4.2 stock tar, I have seen in done with an older version, but it is a rare occurrence.
Click to expand...
Click to collapse
To be sincere I am not pretty sure, I think it was 4.4.2. I can not enter to recovery so installing the last one through it is not an option.

wmobility00 said:
To be sincere I am not pretty sure, I think it was 4.4.2. I can not enter to recovery so installing the last one through it is not an option.
Click to expand...
Click to collapse
If you can get to download mode you could do as audit13 suggested and flash the TWRP.tar.md5 (custom recovery) with Odin or Heimdall and then flash either CM11 as he suggested, or one if enewman17's stock 4.4.2 roms.

thank you all guys. I installed TWRP then CM11 and now is back! I appreciate your help. Have the best wishes and Merry Christmas! Greetings

wmobility00 said:
thank you all guys. I installed TWRP then CM11 and now is back! I appreciate your help. Have the best wishes and Merry Christmas! Greetings
Click to expand...
Click to collapse
Yeah, I was about to suggest flashing twrp but glad to find that you have fixed it. I used this same method to recover a galaxy tab GT-P6210 a while ago

soft-bricked i747m

i had my s3 i747m on cm13. i was having a lot of problems with bluetooth. so i tried going back to stock firmware and i bricked my phone. i can still access download mode.
with odin running as admin or not, this is what it says when i try to install stock rom in download mode:
ODIN MODE
PRODUCT NAME: SGH-I747M
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
SW REV CHECK FAIL : Fused 2 > Binary 0
i've tried looking for solutions, but all say the same thing...which is to use odin and install the stock rom file.
i had twrp recovery installed if that helps.

sal82 said:
i had my s3 i747m on cm13. i was having a lot of problems with bluetooth. so i tried going back to stock firmware and i bricked my phone. i can still access download mode.
with odin running as admin or not, this is what it says when i try to install stock rom in download mode:
ODIN MODE
PRODUCT NAME: SGH-I747M
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
SW REV CHECK FAIL : Fused 2 > Binary 0
i've tried looking for solutions, but all say the same thing...which is to use odin and install the stock rom file.
i had twrp recovery installed if that helps.
Click to expand...
Click to collapse
can you re-flash twrp recovery?

ethanchow said:
can you re-flash twrp recovery?
Click to expand...
Click to collapse
OMFG!! thank you!! it's working again with cm13! i was pulling my hair out lol.
i just reflashed twrp with odin and it started to work. i guess it was just the recovery files damaged?

sal82 said:
OMFG!! thank you!! it's working again with cm13! i was pulling my hair out lol.
i just reflashed twrp with odin and it started to work. i guess it was just the recovery files damaged?
Click to expand...
Click to collapse
Yes, sometimes stock images won't flash because the bootloader version is lower than the one you have.