I found a HK 4.3 ROM that I would like to use in my i317. However I am not sure how to start. Here are what I have tried:
Flash it directly in ODIN would result in a fail right at tz.
I am also not able to fully cook the rom, as Linux Reader cannot open the csc_cache file converted (red with a big question mark), so my rom is left without CSC.
Without CSC, I am able to create the custom rom, flash it, update modem to MH3. Using bootloader without KNOX (4.1.2), with a custom wifi fix kernel (for all other phones except i317) I found in this forum. Technically the rom works, but I don't feel very comfortable on using it.
I am looking for some input here. Thank you.
82801BA said:
I found a HK 4.3 ROM that I would like to use in my i317. However I am not sure how to start. Here are what I have tried:
Flash it directly in ODIN would result in a fail right at tz.
I am also not able to fully cook the rom, as Linux Reader cannot open the csc_cache file converted (red with a big question mark), so my rom is left without CSC.
Without CSC, I am able to create the custom rom, flash it, update modem to MH3. Using bootloader without KNOX (4.1.2), with a custom wifi fix kernel (for all other phones except i317) I found in this forum. Technically the rom works, but I don't feel very comfortable on using it.
I am looking for some input here. Thank you.
Click to expand...
Click to collapse
This will not work. You will need to go to the porting thread in the dev section for this. Don't try to flash a rom from the 7105
Sent from my phone
210euser said:
This will not work. You will need to go to the porting thread in the dev section for this. Don't try to flash a rom from the 7105
Sent from my phone
Click to expand...
Click to collapse
I have successfully cooked N7105 rom for use with i317 before, with 4.1.2.
My main concern at this moment is how I can deal with CSC, since Linux Reader is unable to mount any of the csc_cache.img.ext4 (the 1.4GB file from the 20MB cache.img) converted from 4.3 ROM. Have tried 7100 and 7105 and it cannot be mounted.
Update:
I am now able to grab CSC from both ROM and cook in Kitchen. However:
Using stock N7105 MK3 CSC, no matter what modem I use, baseband is always unknown. And the device is not so smooth.
If I extract AT&T MJ4 CSC, I can get everything working EXCEPT mobile data. The Mobile Network State always says "Disconnected" even "Mobile network type" shows LTE and I have the correct APN (from AT&T's CSC).
Scratching my head on this.
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.
Hello,
I recently sideloaded the new OneUI beta ( https://www.xda-developers.com/install-one-ui-beta-samsung-galaxy-s9-galaxy-s9-plus/ ) and would like to know how I could reverse this process.
MehNameIsFrog said:
Hello,
I recently sideloaded the new OneUI beta ( https://www.xda-developers.com/install-one-ui-beta-samsung-galaxy-s9-galaxy-s9-plus/ ) and would like to know how I could reverse this process.
Click to expand...
Click to collapse
Flash back to the Oreo firmware with ODIN... guides are all over XDA and sammobile
Since it's sideloaded I'm not sure if it will work but the latest version of Smart Switch for Windows has an option to roll back the OTA's to Oreo.
I am in the same position as the op. I have the rom I need to flash. Should I flash all components including bl, csc, ap etc or just ap? Smart Switch doesn't allow me to roll back. Cheers.
pjam said:
I am in the same position as the op. I have the rom I need to flash. Should I flash all components including bl, csc, ap etc or just ap? Smart Switch doesn't allow me to roll back. Cheers.
Click to expand...
Click to collapse
All, flash the same way you would any time, and use CSC not HOME_CSC
Hi all. Is it possible to roll back using smart switch for Mac? I don't have access to a Windows PC, so if it's not possible to roll back using the Mac version, is there any other way apart from Odin?
I have successfully gone back to Oreo. UK rom from updato. Odin 3.13.1 Flashed bl, ap, cp and csc (not csc home). I had the latest smart switch installed but no option to go back to Oreo in it. Thanks for advice on here.
pjam said:
I have successfully gone back to Oreo. UK rom from updato. Odin 3.12. Flashed ap, cs and csc (not csc home). I had the latest smart switch installed but no option to go back to Oreo in it. Thanks for advice on here.
Click to expand...
Click to collapse
ODIN 3.12?
ODIN 3.13.1 was needed for Oreo
Oops my bad. 3.13.1
You can with odin. Tested by me and many others.
Hello, I am using Odin v3.13.3
My phone was running with latest Ukraine firmware which is:
A705FNXXU3ASJ3 ap
A705FNXXU3ASJ3 bl
A705FNXXU3ASH1 cp
A705FNOXM3ASJ3 csc
Today I wanted to format it and decided to do it via Odin. But it stuck at system.img. So I tried to flash the firmware which was just before the newest one. And Odin flashed it with success.
I also had the same problem when I tried to install that older firmware a few months ago till I found Odin with version 3.13.3
So, What do I need to do, I couldn't find a newer Odin. Is there any other problem. How can I flash the latest firmware via Odin?
Thanks ^^
where is home csc,there is only 4 but must have 5 to flash...
imenko79 said:
where is home csc,there is only 4 but must have 5 to flash...
Click to expand...
Click to collapse
It's same as csc, if you flash home csc it doesn't wipe. If you flash only CSC, it wipes your phone. You select one of them, you can't flash both.
And as you see, I succesfully flashed an older firmware. The problem is that odin can't flash the newest firmware.
y.erenbektas said:
Hello, I am using Odin v3.13.3
My phone was running with latest Ukraine firmware which is:
A705FNXXU3ASJ3 ap
A705FNXXU3ASJ3 bl
A705FNXXU3ASH1 cp
A705FNOXM3ASJ3 csc
Today I wanted to format it and decided to do it via Odin. But it stuck at system.img. So I tried to flash the firmware which was just before the newest one. And Odin flashed it with success.
I also had the same problem when I tried to install that older firmware a few months ago till I found Odin with version 3.13.3
So, What do I need to do, I couldn't find a newer Odin. Is there any other problem. How can I flash the latest firmware via Odin?
Thanks ^^
Click to expand...
Click to collapse
Try going into developer options and enabling OEM Unlock then flashyour desired CSC FW with Odin
dezborders said:
Try going into developer options and enabling OEM Unlock then flashyour desired CSC FW with Odin
Click to expand...
Click to collapse
I'll give this next weekend. Thanks ^^