Bad Modem.bin was pushed to phone - Verizon Samsung Galaxy S7 Questions & Answers

Hello!
So because I was having issues connecting to Verizons 4G network (i could still call and text but no data) I had attempted to flash the latest CP and CSC I had from SamMobile. I am on Bootloader 10 with this GS7, however in ODIN, it took the file but on boot, it told me that Secure Check had failed on MODEM.BIN. No clue why it accepted the file so I had tried to find Verizons Repair Assistant. After an hour, it looked like it tried to push it but the phone had rejected it through ODIN saying "Unsupported dev_type" and since that CP and CSC was the latest on the site, I have no clue what to do now. Also just to note, dont know if its normal or not but DVIF!! comes up on the top left of ODIN when using Verizons tool.

sounds like you're trying to flash a lower version modem.bin
please provide here the name of the CP file

Related

Unflashable S7Edge?

I have an S7 Edge from Verizon that I had previously flashed U on. I was going to try flashing the AT&T FW so I could flash the unreleased final Nougat.
I found the AT&T stock FW (G935AUCS4APK1) but Odin would not flash it. It stalls at
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
and the phone displays "Odin protocol version error!". So I canceled the flash and rebooted, and got a screen that said "An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC software".
Now, I can't flash anything. Every FW I try to flash with Odin results in the "Odin protocol version error!". Smart Switch does not recognize the phone either.
A little help please?
Maybe try a diff USB port/cable? Did you have more than one of each file like ap others?
Sent from my SM-G935U using Tapatalk
I had two CSC files. Hone_csc and CSC.
I had several different FW that I tried, the AT&T one I mentioned, PI3 Vzw and pl4 U. None will flash. I noticed that download mode shows the model number as g935a now. I tracked down a newer version of Odin that's supposed to work with the att model, but I haven't had a a chance to try it yet.
Edit: The 3.12 version of Odin worked and I got the AT&T APK1 to flash. Time to go flash Nougat!
raduque said:
I had two CSC files. Hone_csc and CSC.
I had several different FW that I tried, the AT&T one I mentioned, PI3 Vzw and pl4 U. None will flash. I noticed that download mode shows the model number as g935a now. I tracked down a newer version of Odin that's supposed to work with the att model, but I haven't had a a chance to try it yet.
Edit: The 3.12 version of Odin worked and I got the AT&T APK1 to flash. Time to go flash Nougat!
Click to expand...
Click to collapse
Don't you have a. Verizon sim though I flashed the update before nougat and could not make calls and data was also flakey.
Sent from my SM-G935V using XDA-Developers Legacy app
Crsdr37 said:
Don't you have a. Verizon sim though I flashed the update before nougat and could not make calls and data was also flakey.
Click to expand...
Click to collapse
I don't have a SIM card in it, though. Just using it to play around with the OS. SO far, it reminds me of my Note 7. I put the phone away in a drawer, just too depressing to use. I wish I never got rid of my Note 7.

Samsung Galaxy Note 4 System software not authorized by ATT has been found

Got a huge problem with a AT&T phone Samsung Galaxy Note 4. Got it from an ebay handler. It was supposed to be rooted. However, after installing Magisk software (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I got the message "System software not authorized by ATT has been found on your phone". Whenever I turn it on, I see it and the phone doesn't start. Since more than 6 months have passed, the ebay handler declined to help. I called AT&T, but since the phone is rooted, they declined to repair it even after I offered to pay. There are some solutions I found online for other samsung galaxy models, but none which works for note 4.
Tried to restore the system to the factory version, it said that restoration has been successful, but I still see the AT&T message.
I followed the instructions to unbrick the phone by reinstalling the firmware - the method that should work for all phones (not just note 3) https://www.youtube.com/watch?v=bv_NCfYemEs with the firmware for SM-N910A , however no matter how long I waited, the download process never completed.
Any suggestions?
Thanks!
vmmessage said:
Got a huge problem with a AT&T phone Samsung Galaxy Note 4. Got it from an ebay handler. It was supposed to be rooted. However, after installing Magisk software (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I got the message "System software not authorized by ATT has been found on your phone". Whenever I turn it on, I see it and the phone doesn't start. Since more than 6 months have passed, the ebay handler declined to help. I called AT&T, but since the phone is rooted, they declined to repair it even after I offered to pay. There are some solutions I found online for other samsung galaxy models, but none which works for note 4.
Tried to restore the system to the factory version, it said that restoration has been successful, but I still see the AT&T message.
I followed the instructions to unbrick the phone by reinstalling the firmware - the method that should work for all phones (not just note 3) https://www.youtube.com/watch?v=bv_NCfYemEs with the firmware for SM-N910A , however no matter how long I waited, the download process never completed.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
Grab latest firmware for N910A from here
https://androidfilehost.com/?fid=745425885120746376
Make sure samsung usb drivers are properly installed on your pc before you begin.
STEPS
1 Download odin and Firmware and Extract it.
2 open odin tool and upload firmware in AP slot.
Odin can take up to 5 minutes to upload firmware so be patient
3 put phone into download mode
4 connect phone via usb cable and hit start.
5 After FLASH once odin shows pass boot into stock recovery by pressing 3 button combo volume up+ home+ power.
6 in recovery do wipe cache+ wipe data factory reset.
7 reboot system and wait 10 to 5 minutes.
DONE
Trex888 method should be good, however you may need to find the pit file and flash it before odin back to stock. I bought my note 4 already rooted, but the person that did it used the wrong files to flash. Mine was good but buggy. The rom flashed was not verizon, and it locked out some partitions including the one where the imei was held. I had to fix the partitions with the pit file then reflash to a different rom and i was good to go after that.
Thanks
Thanks for the reply! Great! I will try that - very hopeful
tattmann said:
Trex888 method should be good, however you may need to find the pit file and flash it before odin back to stock. I bought my note 4 already rooted, but the person that did it used the wrong files to flash. Mine was good but buggy. The rom flashed was not verizon, and it locked out some partitions including the one where the imei was held. I had to fix the partitions with the pit file then reflash to a different rom and i was good to go after that.
Click to expand...
Click to collapse
You dont need dedicated pit file unless your device has errors such as "dm verity verification failed" or failed to mount cache/efs etc etc.
If stock rom flashing by odin went smoothly no require for repartition or pit file.
Playing with pit file and repartition is extremely dangerous and can cause device to hard brick so i would not recommend unless some serious issues with device.
Fyi every samsung stock firmware has pit file in the system image by default and odin take advantage of it by it self during flashing.
Have a nice day.
Trex888 said:
You dont need dedicated pit file unless your device has errors such as "dm verity verification failed" or failed to mount cache/efs etc etc.
If stock rom flashing by odin went smoothly no require for repartition or pit file.
Playing with pit file and repartition is extremely dangerous and can cause device to hard brick so i would not recommend unless some serious issues with device.
Fyi every samsung stock firmware has pit file in the system image by default and odin take advantage of it by it self during flashing.
Have a nice day.
Click to expand...
Click to collapse
in my case, whoever flashed my phone flashed an f file instead of the v file. It lost the imei and would not recognize a sim card. I tried flashing original firmware but the imei was still gone. The ONLY thing that saved mine was to find the correct pit file and flash it before firmware. It fixed my issue and got me back up and running. every original fw flash for me failed until I flashed just the pit. I cannot explain why the original fw included in the odin package would NOT work. Hence the statement of "you may need to" instead of "you will have to".

Galaxy s10+ SM-G975FDS samsung firmwares need help

When searching for a firmware for the phone I just bought on ebay none of the sites i have checked, including sammobile and updato.com, have the baseband version I have which is G975FXXAU1ASE5. I specifically bought this phone so that i could root it and when I checked all the bands that it has there are all except 1 for the tmobile network and I read that it should still work. I currently use metropcs so my question is which firmware can i use that is going to work with tmobile or metropcs and if i use one with a different baseband or csc will it affect if my phone works or not on the tmobile network. I am also in California in the US and all the firmwares are international so what should I use? My CSC is G975FOXM1ASE5 and I haven't seen any with the same CSC either
AlwaysPhresh said:
When searching for a firmware for the phone I just bought on ebay none of the sites i have checked, including sammobile and updato.com, have the baseband version I have which is G975FXXAU1ASE5. I specifically bought this phone so that i could root it and when I checked all the bands that it has there are all except 1 for the tmobile network and I read that it should still work. I currently use metropcs so my question is which firmware can i use that is going to work with tmobile or metropcs and if i use one with a different baseband or csc will it affect if my phone works or not on the tmobile network. I am also in California in the US and all the firmwares are international so what should I use? My CSC is G975FOXM1ASE5 and I haven't seen any with the same CSC either
Click to expand...
Click to collapse
You will be able to use on Tmobile. All of the carrier features are available excepted RCS messaging. You will also be missing some of the LTE bands, like 71. You can flash any of the 975F firmwares. OXM denotes multi csc firmware regions. Use Frida download tool instead of Sammobile or updato. It much faster - 4/5 minutes vs hours with those websites. AUT gets updates first, but you can choose the same one that is currently on your phone.
Cindysmith0994 said:
You will be able to use on Tmobile. All of the carrier features are available excepted RCS messaging. You will also be missing some of the LTE bands, like 71. You can flash any of the 975F firmwares. OXM denotes multi csc firmware regions. Use Frida download tool instead of Sammobile or updato. It much faster - 4/5 minutes vs hours with those websites. AUT gets updates first, but you can choose the same one that is currently on your phone.
Click to expand...
Click to collapse
I have Frija already and tried it last night with the auto setting and it didn't let me put OXM for a CSC. I tried to run it with MODEL- SM-975F and for the CSC I chose AUT with auto selected and it gives me an error that it cannot find a firmware. I read a comment from somebody with the same phone as I have on yt and somebody replied with a firmware from Nepal and it said OXM in the CSC would that have been compatible too?
AlwaysPhresh said:
I have Frija already and tried it last night with the auto setting and it didn't let me put OXM for a CSC. I tried to run it with MODEL- SM-975F and for the CSC I chose AUT with auto selected and it gives me an error that it cannot find a firmware. I read a comment from somebody with the same phone as I have on yt and somebody replied with a firmware from Nepal and it said OXM in the CSC would that have been compatible too?
Click to expand...
Click to collapse
You can't choose OXM. I just tried it with AUT, it works. The model needs to be SM-G975F.
Cindysmith0994 said:
You can't choose OXM. I just tried it with AUT, it works. The model needs to be SM-G975F.
Click to expand...
Click to collapse
I had SM-975F without the G before the 9 so it wasn't working thank you very much for replying and the help. The firmware that I am getting will work with Odin and rooting the phone with Magisk correct?
AlwaysPhresh said:
I had SM-975F without the G before the 9 so it wasn't working thank you very much for replying and the help. The firmware that I am getting will work with Odin and rooting the phone with Magisk correct?
Click to expand...
Click to collapse
Yes. Just follow the root instructions on the S10 forum.
Cindysmith0994 said:
Yes. Just follow the root instructions on the S10 forum.
Click to expand...
Click to collapse
I followed the instructions and now my phone won't boot and gives me a message saying the phone does not have samsung's official firmware and I used the firmware from Frija. It is not booting in any way.
AlwaysPhresh said:
I followed the instructions and now my phone won't boot and gives me a message saying the phone does not have samsung's official firmware and I used the firmware from Frija. It is not booting in any way.
Click to expand...
Click to collapse
Your bootloader is still locked. Reflash entire stock firmware [BL, AP, CP, CSC (not home_csc). It's much easier to follow the videos showing the process instead of following written posts if you're having issues.
Cindysmith0994 said:
Your bootloader is still locked. Reflash entire stock firmware [BL, AP, CP, CSC (not home_csc). It's much easier to follow the videos showing the process instead of following written posts if you're having issues.
Click to expand...
Click to collapse
My bootloader was unlocked fine already. I followed both of these videos https://www.youtube.com/watch?v=o3a8YnWT3yk&t=179s / https://www.youtube.com/watch?v=s2Xp-lQg1xs&t=612s
Both are pretty much the exact same all the way through. I flashed the patched tar from Magisk restarted the phone and held the vol up bixby power combo when it went black and then I went to wipe data factory reset then rebooted. After it booted i set up the phone the same and checked if magisk was there and it was not so i turned off the phone and when booting i did the vol up bixby and power and the screen stayed on the boot logo saying the this phone is not running samsung's official software and on the top a red line that said i can flash any official software and it stayed like that and after trying to just boot it with the power it gave the exact same message. Only difference from the video and what I did was the firmware I got was from frija while they got theirs from different methods like sammobile and samfirm
EDIT- I flashed the ap cp and csc not the bl file from the firmware i got off of frija and the phone booted up now. The phones bootloader is still unlocked and it boots up but there is no root.
AlwaysPhresh said:
My bootloader was unlocked fine already. I followed both of these videos https://www.youtube.com/watch?v=o3a8YnWT3yk&t=179s / https://www.youtube.com/watch?v=s2Xp-lQg1xs&t=612s
Both are pretty much the exact same all the way through. I flashed the patched tar from Magisk restarted the phone and held the vol up bixby power combo when it went black and then I went to wipe data factory reset then rebooted. After it booted i set up the phone the same and checked if magisk was there and it was not so i turned off the phone and when booting i did the vol up bixby and power and the screen stayed on the boot logo saying the this phone is not running samsung's official software and on the top a red line that said i can flash any official software and it stayed like that and after trying to just boot it with the power it gave the exact same message. Only difference from the video and what I did was the firmware I got was from frija while they got theirs from different methods like sammobile and samfirm
EDIT- I flashed the ap cp and csc not the bl file from the firmware i got off of frija and the phone booted up now. The phones bootloader is still unlocked and it boots up but there is no root.
Click to expand...
Click to collapse
If you flashed those files you should be back to stock. Start the process again. Try this video: https://m.youtube.com/watch?v=Mn4dTjxY89I
Also make sure your patched magisk file is not corrupted when transferred back to your PC.
If not, I'm out of suggestions...sorry.

Update fails at 27%

Hi folks, just got my hands on a S8+ and after PUK issue now solved (my own fault I think, my sim had a code on it) I am finding it will not update.
It came sat on android 9 with One UI 1.0 - 1/sept 2019 security patch. Downloads 1/march 2020 304.72MB security patch and runs through install, ERROR at 27%, reboots and tells me it failed.
Everything seems fine on the phone except headphones don't get callers audio. That I have noticed so far.
Would appreciate some help. Happy to run flash (not root) and go for a genuine rom. Got it for a good price with a bit of screen burn so hope it can be updated.
Thanks
codQuore said:
Hi folks, just got my hands on a S8+ and after PUK issue now solved (my own fault I think, my sim had a code on it) I am finding it will not update.
It came sat on android 9 with One UI 1.0 - 1/sept 2019 security patch. Downloads 1/march 2020 304.72MB security patch and runs through install, ERROR at 27%, reboots and tells me it failed.
Everything seems fine on the phone except headphones don't get callers audio. That I have noticed so far.
Would appreciate some help. Happy to run flash (not root) and go for a genuine rom. Got it for a good price with a bit of screen burn so hope it can be updated.
Thanks
Click to expand...
Click to collapse
Easier method but you lose all data: Find older version of Samsung Kies (official Samsung software) which has Firmware Upgrade and Initialization feature. Install that version of Samsung Kies, install device driver (also under Kies), then go for Firmware Upgrade and Initialization (here you enter device model number and serial number and it will automagically install the correct version of software).
Harder method but you don't lose your user data: Download correct firmware using SamFirm, then install that firmware on your phone using Odin. The firmware includes 5 files whose names start with following letters: AP, BL, CP, CSC and HOME_CSC. Then you need to place AP file in the AP input box, BL into BL, CP into CP and HOME_CSC into CSC field! This means you use all files from the firmware except CSC (if you use CSC instead of HOME_CSC it will wipe all your user data).
roberta-xda said:
Easier method but you lose all data: Find older version of Samsung Kies (official Samsung software) which has Firmware Upgrade and Initialization feature. Install that version of Samsung Kies, install device driver (also under Kies), then go for Firmware Upgrade and Initialization (here you enter device model number and serial number and it will automagically install the correct version of software).
Harder method but you don't lose your user data: Download correct firmware using SamFirm, then install that firmware on your phone using Odin. The firmware includes 5 files whose names start with following letters: AP, BL, CP, CSC and HOME_CSC. Then you need to place AP file in the AP input box, BL into BL, CP into CP and HOME_CSC into CSC field! This means you use all files from the firmware except CSC (if you use CSC instead of HOME_CSC it will wipe all your user data).
Click to expand...
Click to collapse
After a faff, downloading prince version of Odin, then finding out to get 3.1.3+ and all done. Fully uptodate. Thank you for the help ! :good::highfive:
Now if I can work out why voice calls dont come thru headphones when ringtone does.

re-flashing stock OS onto Samsung Galaxy S8

Model: SM-G950F
Build Number: PPR1.180610.011.G850FXXUCDUD1
So I recently flashed /e/ OS (a fork of Lineage if anyone is unfamiliar). Unfortunately, /e/ was giving my phone problems, and also Verizon doesn't work with it, so I decided to flash Android 9 Pie back onto it. After hunting down the version of my phone's firmware (I live in the US but my phone is a refurbished phone from the UK), I downloaded it, plugged the BL, AP, CP, and HOME_CSC into PrinceComsy Odin. In TWRP I formatted the storage and all that, and then I flashed it using Odin. I got the green "Pass!" and the <OSM> All threads completed. (succeed 1 / failed 0) messages, but when I went to TWRP's reboot screen, it said there was no OS.
Are there settings I am missing or something? I have the G850FXXUCDUD1 firmware, I tried combinations of just flashing the AP and CSC, just AP, AP BL and CSC, so on and so forth, but no dice.
I've scoured the internet for help but nothing I have tried has solved the issue, so I figured I'd try here. Any help literally at all would be appreciated. If you need more information on the device or what I did in specific I would be happy to oblige. Thank you in advance!
EDIT: I've only gotten into software hacking relatively recently, and XDA-Developers even more so. As you can tell by the age of my account, this is the first time I've ever posted or anything haha. I tend to lurk on tech forums. Anyhoo that is all
EDIT 2: I downloaded Odin 3.13.3 and am trying that. Thus far it either fails or gets stuck on SetupConnection
EDIT 3: I downloaded a different zip from a different source for my phone. It succeeded in Odin, put the default recovery back on my phone, but now it is stuck on the samsung logo when trying to boot.

Categories

Resources