Related
I want to flash a modem with mobile odin since I am not using a repack kernel. I didn't find a tar file but I found a zip file. Can I extract the modem.bin and then in mobile odin lite select modem and browse to where the modem.bin is and select it and then flash? Or does it have to be a tar file? I am new to mobile odin but I really like it.
Well normally you would pull the modem.bin file out of the ZIP and flash it, but it won't work on our phone. I haven't been able to get a single modem.bin file or any of Calk's modem TAR files to flash in Mobile Odin. It just goes through the motions. Supposedly it will flash the modem from a full TAR image though.
Sent from my SPH-D710 using Tapatalk
Thanks for the info. I guess I will Odin the repack with recovery and flash the modem and flash the stock kernel back then.
ElAguila said:
Thanks for the info. I guess I will Odin the repack with recovery and flash the modem and flash the stock kernel back then.
Click to expand...
Click to collapse
If for some reason you don't like the repacks, you can also install the stock FB27 zImage and it should flash the modems (they ignore signature failures in FB27 stock recovery) Same number of steps as installing a CWM repack except you will always be running pure stock software (I figure there must be a reason you haven't installed a CWM repack already)
How to ? Mobile Odin cannot recognize the modem.bin file, it's only recognize the .tar file
supercjlee said:
How to ? Mobile Odin cannot recognize the modem.bin file, it's only recognize the .tar file
Click to expand...
Click to collapse
Though I don't use it, I believe Mobile ODIN recognizes modem.bin and tar. It just doesn't flash modem.bin on CDMA systems.
Flashing the modem with the actual odin does not raise any flash counters or cause any yellow triangles. Why not just do it thru odin?
im0rtalz said:
Flashing the modem with the actual odin does not raise any flash counters or cause any yellow triangles. Why not just do it thru odin?
Click to expand...
Click to collapse
Convenience mainly.
Sent from my SPH-D710 using Tapatalk 2
Hi,
I own a galaxy note 2 lte version. I have a situation where i have to open, delete modem.bin and repack the stock tar.md5 file.
So here is the situation,
I recently flashed a MF2 stock rom from a different region (Portugal) onto my phone. If you guys are aware, the MF2 modem changes the efs partition and hence if I have to go back to an old stock rom the imei will not be recognized. So I have to re flash the mf2 modem to get the imei working else with old modem imei will not be correct.
What I plan to do,
Flash an old stock firmware without modem so that the current modem is retained and I have a valid imei.
I would like to ask you guys if you think it would work and in that case can I, using 7zip, extract the tar.md5 file and delete the modem.bin file and repack it to tar.md5 again to be flashed via odin PDA?
Thanks in advance for the heads up.
ysrini said:
Hi,
I own a galaxy note 2 lte version. I have a situation where i have to open, delete modem.bin and repack the stock tar.md5 file.
So here is the situation,
I recently flashed a MF2 stock rom from a different region (Portugal) onto my phone. If you guys are aware, the MF2 modem changes the efs partition and hence if I have to go back to an old stock rom the imei will not be recognized. So I have to re flash the mf2 modem to get the imei working else with old modem imei will not be correct.
What I plan to do,
Flash an old stock firmware without modem so that the current modem is retained and I have a valid imei.
I would like to ask you guys if you think it would work and in that case can I, using 7zip, extract the tar.md5 file and delete the modem.bin file and repack it to tar.md5 again to be flashed via odin PDA?
Thanks in advance for the heads up.
Click to expand...
Click to collapse
I don;t quite understand why would you delete modem, don't you need to flash previous modem version? Isn't it then easier to just flash old modem?
dalanik said:
I don;t quite understand why would you delete modem, don't you need to flash previous modem version? Isn't it then easier to just flash old modem?
Click to expand...
Click to collapse
I plan to delete the modem from TAR just because in that case the old modem would be retained.
If you are not much familiar with linux, it will be more difficult for you to unpack, repack and adding tar + md5
Here solution which can be followed by newbie too
-Flash old ROM, (you will lose baseband and IMEI, don't worry)
-Extract new ROM (e.g. mf2) and find modem.bin
-Flash modem.bin with PC odin for 'phone' tab (unstead of PDA we are using for flashing ROM)
-Now you will have baseban and IMEI back
Done.
dr.ketan said:
If you are not much familiar with linux, it will be more difficult for you to unpack, repack and adding tar + md5
Here solution which can be followed by newbie too
-Flash old ROM, (you will lose baseband and IMEI, don't worry)
-Extract new ROM (e.g. mf2) and find modem.bin
-Flash modem.bin with PC odin for 'phone' tab (unstead of PDA we are using for flashing ROM)
-Now you will have baseban and IMEI back
Done.
Click to expand...
Click to collapse
Thanks a lot for your timely help and concern.
I downloaded the Singapore Starhub MC1 firmware from the sammobile website and flashed it using Odin.
Luckily after flashing and setting up the phone -> the Modem was able to read mt EFS and my IMEI is intact.
Everything is okay. Happy :victory:
Finally, one more question,
If the MF2 Kernel makes changes in the EFS partition, in my case now -> how do you guys think the old MB3's modem was able to read the EFS partition and IMEI without any EFS backup / modem change.
Wht you getting by dialing *#1234#
Sent from my GT-N7100 using xda premium
dr.ketan said:
wht you getting by dialing *#1234#
sent from my gt-n7100 using xda premium
Click to expand...
Click to collapse
ap: N7105xxdmb3
cp: N7105dxdll1
csc: N7105olbdmc1
May be this scenario limited to N7100
Or mf2 you have flashed still doesn't have kernel that causing efs modification.
Sent from my GT-N7100 using xda premium
dr.ketan said:
May be this scenario limited to N7100
Or mf2 you have flashed still doesn't have kernel that causing efs modification.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yes, I too hope the same.
To make a long story short I was in CM11 and when trying to restore to stock I tripped the Knox Counter. I no longer have voice or audio. I tried to restore to other custom roms with same issue. I tried downloading stock tmobiles images and am unable to restore with odin. Question after triggering the Knox does that not allow me to even restore a stock rom or is my issue some place else? Any help?
It's my understanding you can not Odin back to MDL but you should be able to Odin the MK2 firmware.
☞ Sent from here☜???
re: knox
ahoslc said:
To make a long story short I was in CM11 and when trying to restore to stock I tripped the Knox Counter. I no longer have voice or audio. I tried to restore to other custom roms with same issue. I tried downloading stock tmobiles images and am unable to restore with odin. Question after triggering the Knox does that not allow me to even restore a stock rom or is my issue some place else? Any help?
Click to expand...
Click to collapse
If you are sure that you tripped the knox counter this is how to fix the audio issue.
Download the official M919 STOCK 4.3 MK2 firmware/rom from http://SamMobile.com .
(filename: M919UVUEMK2_M919TMBEMK2_TMB.zip inside zip is the tar file)
Then Odin flash the tar in Odin's PDA slot.
After you odin flashed the 4.3 MK2 successfully see if the audio/sound/voice is good.
If it's not then download the latest KToonsez 12-12-2013 kernel and flash it using
cwm/twrp recovery. (after the phone is rooted)
Here is the direct download link for KToonsez kernel:
https://copy.com/kEWuwwaGj8j2/TW%20JB%204.3%20Versions/KT-SGS4-JB4.3- TW-TMO-12.12.2013.zip?download=1
Before you can cwm/twrp flash the kernel or any cwm/twrp flashable zip file you need to
be rooted.
Here is the direct download link for the odin flash CF-AUTOROOT:
http://download.chainfire.eu/328/CF...jfltetmo-jfltetmo-sghm919.zip?retrieve_file=1
It's always best in any case to flash the KToonsez kernel after flashing new roms.
Good luck!
It's always best in any case to flash the KToonsez kernel after flashing new roms.
WHy is this kernel so famous and need to install after installing new ROMs? -
Good luck![/QUOTE]
Misterjunky said:
If you are sure that you tripped the knox counter this is how to fix the audio issue.
Download the official M919 STOCK 4.3 MK2 firmware/rom from http://SamMobile.com .
(filename: M919UVUEMK2_M919TMBEMK2_TMB.zip inside zip is the tar file)
Then Odin flash the tar in Odin's PDA slot.
After you odin flashed the 4.3 MK2 successfully see if the audio/sound/voice is good.
If it's not then download the latest KToonsez 12-12-2013 kernel and flash it using
cwm/twrp recovery. (after the phone is rooted)
Here is the direct download link for KToonsez kernel:
https://copy.com/kEWuwwaGj8j2/TW%20JB%204.3%20Versions/KT-SGS4-JB4.3- TW-TMO-12.12.2013.zip?download=1
Before you can cwm/twrp flash the kernel or any cwm/twrp flashable zip file you need to
be rooted.
Here is the direct download link for the odin flash CF-AUTOROOT:
http://download.chainfire.eu/328/CF...jfltetmo-jfltetmo-sghm919.zip?retrieve_file=1
It's always best in any case to flash the KToonsez kernel after flashing new roms.
Good luck!
Click to expand...
Click to collapse
I am having the same issue as the OP. But my understanding is, with Knox (which I unfortunately seem to have acquired, my fault) I cannot use Odin to flash a tar file.
You can still flash. You may trip the counter and you can't flash back to 4.2, but Odin still works.
Sent from my SGH-M919 using XDA Premium 4 mobile app
At this point knox is already tripped, and that's okay. But to resolve my loss of sound and voice I would have to use Odin to flash a T-Mo 4.3 tar, such as the one above? This will flash everything, including modem, right?
Could i also Odin flash the full TMo 4.3 modem with the same results?
re: knox
alouden said:
I am having the same issue as the OP. But my understanding is, with Knox (which I unfortunately seem to have acquired, my fault) I cannot use Odin to flash a tar file.
Click to expand...
Click to collapse
Not being able to flash tar files with odin due to having knox
must be some kind of rumor, but that's all it is a rumor.
It's not true at all.
Good luck!
Misterjunky said:
Not being able to flash tar files with odin due to having knox
must be some kind of rumor, but that's all it is a rumor.
It's not true at all.
Good luck!
Click to expand...
Click to collapse
Thanks. Will be doing this later at home. Fingers crossed :good:
Misterjunky said:
Not being able to flash tar files with odin due to having knox
must be some kind of rumor, but that's all it is a rumor.
It's not true at all.
Good luck!
Click to expand...
Click to collapse
Intersting...I Odin flashed the latest update. During the flash, I did see modem being flashed in the progress window. Still Have the same issue. I am confused. Not sure why this did not work.
re: modem/baseband/mdl/mk2
alouden said:
At this point knox is already tripped, and that's okay. But to resolve my loss of sound and voice I would have to use Odin to flash a T-Mo 4.3 tar, such as the one above? This will flash everything, including modem, right?
Could i also Odin flash the full TMo 4.3 modem with the same results?
Click to expand...
Click to collapse
Here are the step by step instruction on how to get the MK2 modem.bin
baseband flashed successfully.
Here is the way to fix the audio issue you are having.
This will ONLY fix your audio issue if your baseband is MDL
so check your baseband by going to Settings>More>About device
and scroll down after clicking About device til you see baseband.
It will either have MK2 or MDL in it. If it's MDL then your
audio issue can be fixed by following the instructions below.
You can Odin flash MK2 while on an Wicked v9.1 4.2.2 rom or ODIN
flash it after flashing the Wicked v9.1 4.3 or other M919 based 4.3 roms.
Either way it makes no difference.
What does make a difference is to follow this step by step exactly to a "T".
#1: Manually power down the phone using the power button only
#2: Start ODIN and put the MODEM.BIN file into ODIN'S PHONE slot/tab.
#3: Put the phone into download mode by using the volume down and power button only.
#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 using the power button.
#9: Wait 20 or so seconds before you power on the phone.
After doing this the MK2 baseband should show up in About Device.
Here is the direct download link for the Tmobile 4.3 M919 MK2 modem.bin:
http://www.mediafire.com/download/1g...l89x/modem.bin
After your baseband displays MK2 you don't need to do anything,
the phone will then be ready to use with all it's bells and whistles.
I would highly suggest that you make a nandroid backup in TWRP recovery before you
change any settings, installing or flashing any apps, mods, themes or anything else.
Good luck!
Misterjunky said:
Here are the step by step instruction on how to get the MK2 modem.bin
baseband flashed successfully.
Here is the way to fix the audio issue you are having.
This will ONLY fix your audio issue if your baseband is MDL
so check your baseband by going to Settings>More>About device
and scroll down after clicking About device til you see baseband.
It will either have MK2 or MDL in it. If it's MDL then your
audio issue can be fixed by following the instructions below.
You can Odin flash MK2 while on an Wicked v9.1 4.2.2 rom or ODIN
flash it after flashing the Wicked v9.1 4.3 or other M919 based 4.3 roms.
Either way it makes no difference.
What does make a difference is to follow this step by step exactly to a "T".
#1: Manually power down the phone using the power button only
#2: Start ODIN and put the MODEM.BIN file into ODIN'S PHONE slot/tab.
#3: Put the phone into download mode by using the volume down and power button only.
#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 using the power button.
#9: Wait 20 or so seconds before you power on the phone.
After doing this the MK2 baseband should show up in About Device.
Here is the direct download link for the Tmobile 4.3 M919 MK2 modem.bin:
http://www.mediafire.com/download/1g...l89x/modem.bin
After your baseband displays MK2 you don't need to do anything,
the phone will then be ready to use with all it's bells and whistles.
I would highly suggest that you make a nandroid backup in TWRP recovery before you
change any settings, installing or flashing any apps, mods, themes or anything else.
Good luck!
Click to expand...
Click to collapse
Thanks for the detailed steps. So when I check baseband, I see that I have the MK2 baseband.
re: no more issues
alouden said:
Thanks for the detailed steps. So when I check baseband, I see that I have the MK2 baseband.
Click to expand...
Click to collapse
If you have MK2 baseband then you should have proper audio, no audio issues at all
and the rest of your phone should be working fine since it's already rooted and the
phone has the best custom recovery already flashed in it.
Be sure to make a nandroid backup using Twrp recovery before downloading,
installing, adding or flashing any mods, apps, themes or anything else.
Good luck!
Misterjunky said:
If you have MK2 baseband then you should have proper audio, no audio issues at all
and the rest of your phone should be working fine since it's already rooted and the
phone has the best custom recovery already flashed in it.
Good luck!
Click to expand...
Click to collapse
In a perfect world, yes. Not this time....I still have no sounds. And no audio on phonecalls. On the threat of divorce, my wife has made me promise to resolve this one way or another. All my efforts have failed. i am now stock 4.3, rooted, with twrp recovery. no sound.
Ah well...Happy New Year. And thanks to everyone for their help. I haven't given up. But my wife has a good lawyer.
Misterjunky said:
If you have MK2 baseband then you should have proper audio, no audio issues at all
and the rest of your phone should be working fine since it's already rooted and the
phone has the best custom recovery already flashed in it.
Be sure to make a nandroid backup using Twrp recovery before downloading,
installing, adding or flashing any mods, apps, themes or anything else.
Good luck!
Click to expand...
Click to collapse
Figured out the problem. So the MK2 Tar file I had was the culprit. I redownloaded the file from a different source, re-extracted the Tar and used Odin to reflash the tar file. Funny, the first file did not have a MD5 mismatch and did flash a modem. Well, whatever the issue was, I am glad it was resolved. Thanks for all your help guys.
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
How to install new stock .tar file? ODIN 3.12 says "Download BL + AP + CP + HOME_CSC
I did download G935PVPS4APK1_SPT4APK1_SPR_Sprint_USA_6.0.1 which does contain files that start with AP_, BL_, CP_, CSC_SPT, HOME_CSC_SPT.
These match with the ODIN sections which I was previously advised never to flash.
What are each of these? Should I actually flash them? Should I flash them in a certain order? I always get fail when I try to install (may need to run as admin).
hammerchucker said:
I did download G935PVPS4APK1_SPT4APK1_SPR_Sprint_USA_6.0.1 which does contain files that start with AP_, BL_, CP_, CSC_SPT, HOME_CSC_SPT.
These match with the ODIN sections which I was previously advised never to flash.
What are each of these? Should I actually flash them? Should I flash them in a certain order? I always get fail when I try to install (may need to run as admin).
Click to expand...
Click to collapse
If your download is zipped, extract the tar.md5 file and load in AP slot.
You've downloaded a S7 Edge file but posted in Note 4 forum. Check your model number and make sure you're flashing the right stock tar. Note 4 has stock tar thread in general forum for Note 4.
Even the Sprint S7E uses a full stock tar.md5 file to flash in AP slot per Sammobile. The dialogue you're seeing in the newer Odin is used for other purposes like recovering phone. Maybe other models use that or it's another option for flashing native csc on international phone but Sprint phones would normally use the full tar.md5 in AP slot.
Sent from my SM-N920P using Tapatalk
samep said:
If your download is zipped, extract the tar.md5 file and load in AP slot.
You've downloaded a S7 Edge file but posted in Note 4 forum. Check your model number and make sure you're flashing the right stock tar. Note 4 has stock tar thread in general forum for Note 4.
Even the Sprint S7E uses a full stock tar.md5 file to flash in AP slot per Sammobile. The dialogue you're seeing in the newer Odin is used for other purposes like recovering phone. Maybe other models use that or it's another option for flashing native csc on international phone but Sprint phones would normally use the full tar.md5 in AP slot.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thanks for the response and catch that this is S7 ROM. It never flashed (failed in ODIN) and I ended up d/l the Sprint N4 PK1 which led to a successful Note 7 install.