hi guys. i have a note2 on sprint with the MA7 version of the OS. I'm trying to get 4.3, but i cant get any ota and when i try to connect to kies it says its unsupported. under system > about device, it shows "normal" (not modified). on KIES it shows PDA:MA7, PHONE:MA7, and CSC:LJC. from what ive researched, i need PDA and CSC to match. how do i do this.
quick history: i rooted it at one point then got tired of that and wanted the software updates so just this last week i reflashed some odin thing and got stock ma7. but i guess my csc didn't get changed. can anyone point me toward the right direction to get my csc changed?
I was trying to root my samsung galaxy a5 2017 with TWRP and I accidentally deleted system data. Then, I tried rebooting the phone and it got stuck in a bootloop. To fix this problem I tried flashing stock 8.0 firmware from sammobile via odin and I got this error:
Sw rev. Check fail. Device: 6, binary 5. I think that this means I have to flash the latest stock firmware but there isn't a newer one.
After that, I tried to use my phone by flashing a custom rom (Lineage 15.1) and I discovered that I have no imei,no baseband and no ip adress. I have installed many custom roms but the issue is still there. I am trying to get my phone to work with stock firmware and fix the IMEI issue but odin wont let me flash because of that error. I would appreciate if anyone could help. Thanks.
Flash a firmware version that contains S6 or U6 in the middle, it won't work with U5/S5! Not the Samsung phone S5 or S6, but rather, the firmware version.
For cellular, change the modem firmware, or backup and wipe /data/. /data/data/?.
Unless the efs was wiped (probably not if the baseband version isn't there, load a backup then, only if the efs was wiped don't restore it otherwise, and it must not be a backup created with an older twrp, view the recovery log in the backup folder)
julianmunozvaras said:
I was trying to root my samsung galaxy a5 2017 with TWRP and I accidentally deleted system data. Then, I tried rebooting the phone and it got stuck in a bootloop. To fix this problem I tried flashing stock 8.0 firmware from sammobile via odin and I got this error:
Sw rev. Check fail. Device: 6, binary 5. I think that this means I have to flash the latest stock firmware but there isn't a newer one.
After that, I tried to use my phone by flashing a custom rom (Lineage 15.1) and I discovered that I have no imei,no baseband and no ip adress. I have installed many custom roms but the issue is still there. I am trying to get my phone to work with stock firmware and fix the IMEI issue but odin wont let me flash because of that error. I would appreciate if anyone could help. Thanks.
Click to expand...
Click to collapse
You aren't flashing the current version of software.
Sent from my Samsung SM-A520W using XDA Labs
iloveoreos said:
You aren't flashing the current version of software.
Sent from my Samsung SM-A520W using XDA Labs
Click to expand...
Click to collapse
I tried installing the latest version available and I had the same error.
julianmunozvaras said:
I tried installing the latest version available and I had the same error.
Click to expand...
Click to collapse
Well, I don't know what else could be wrong.
Sent from my Samsung SM-A520W using XDA Labs
julianmunozvaras said:
I tried installing the latest version available and I had the same error.
Click to expand...
Click to collapse
Listen to me, it happened to me 2 days ago, and I came to the conclusion that I was not flash the latest firmware. You need to flash the same firmware with the same bootloader or more recent, the error you receive is because you are flashing an older version of bootloader. Do one thing, type the code *#1234# on the phone keypad
mark the code that gives you on 'AP and look it on Sammobile at https://www.sammobile.com/firmwares/galaxy-a5/SM-A520F/ITV/ select your language and look for the firmware with your own code . You will see that odin flash it.
Samsung A520F Custom Binary Error
Hello please I have been trying to reload my Samsung A520F firmware for a couple of weeks
It all started with the phone trying to update (over WIFI) and somewhere along the line files must have gotten corrupted
This led to the phone constantly restart and shutting down applications
I decided to just download the firmware and use Odin to reload. This, unfortunately, didn't go so well as now the phone isn't starting up anymore but can still get to download mode.
PDA firmware is A520FXXUACSE6
Region is EUR
Network is OPEN
every time I use this firmware I get the error
" Custom binary (BOOT) Blocked by FRP Lock
Please note currently at the moment phone refuses to boot up I read about removing OEM lock and don't know if this is the problem.
Please could you help out
koolblowkid said:
Hello please I have been trying to reload my Samsung A520F firmware for a couple of weeks
It all started with the phone trying to update (over WIFI) and somewhere along the line files must have gotten corrupted
This led to the phone constantly restart and shutting down applications
I decided to just download the firmware and use Odin to reload. This, unfortunately, didn't go so well as now the phone isn't starting up anymore but can still get to download mode.
PDA firmware is A520FXXUACSE6
Region is EUR
Network is OPEN
every time I use this firmware I get the error
" Custom binary (BOOT) Blocked by FRP Lock
Please note currently at the moment phone refuses to boot up I read about removing OEM lock and don't know if this is the problem.
Please could you help out
Click to expand...
Click to collapse
Obviously you are frp locked. But I didn't think that blocked from flashing official.
Hello fellas,
This morning I've tried to flash CSA1 from CLR1 with my A720F (2017) using the HOME_CSC in Odin 3.13.x and it failed. The first time, it wouldn't even pass from system.img, but after a reattempt it passed the file without issues.
However, it always fails after writing to HIDDEN partition. It has happened twice, so I kind of desisted for the moment and reflashed CLR1.
Do you think this could be related with the HOME_CSC? I have always been using it, if I recollect correctly, last full CSC flash was using region XXV (Vietnam). The CSA1 update failing comes from PCT (Puerto Rico).
Any help will be appreciated.
Nevermind, yesterday I've flashed latest firmware from region ZTO (Brazil unbranded) and it went like a charm.
You may close this thread.
Hello,
I just got a SM-N970U1 which I'm trying to convert to TMB FW. There are a couple of threads out there however haven't been updated with actual fixes since being posted in Aug 2019.
Issue I encountered, I used odin v3.14 to flash FW (bl/ap/cp/csc) that I got from Frija. It flashes fine, goes through the motions, however in the end, TMB settings aren't applied, meaning there is no splash screen, no RCS/Video etc. The android did update to V10, with UI of 2.0 (this was older version in stock phone), so that part did work.
I did follow the "put sim in, let do carrier initialization etc.", no changes.
I've attempted to flash a few times but haven't had any luck.
Any ideas for a fix? Hoping someone has come up with something for this as the phone has been out for sometime now.
So if anyone in the future needs this info, I ended up downloading the latest available TMO firmware for SM-970U (which is the carrier version of the phone), and just flashed using odin. Cleared the cache, and boom, works!
Not sure about OTA updates yet, as the FW i've installed has the 03/2020 patch.
Hi Guys,
About a month ago I got new Galaxy S9 with firmware G960FXXSBETH2,
As it turned out it has all kind of reception issues, so I tried to find alternate ROM for it to see if this issue can be improved.
While searching for ROM at Sammobile.com I noticed that the latest version for my region is different than the one I have on my device, and in fact I should have firmware G960FXXUAETG3.
I got ODIN (3.14.4) but when tried to flash the alternate firmware got this message:
"sw rev check fail bootloader device 11 binary 10"
So as it seems this device came with high boot-loader version 11 and I understand that I can not downgrade it either way - correct me if I'm wrong on this.
So what are my options on this?
Is there an alternate ROM that I could use? Maybe a customized one?
Or am I'm stuck with this firmware,
Many thanks