Database Users

I9505 - No 3G or 4G and hideously intermittent connection on 2G (UK)

Hi all,
I've bought an I9505 from a Hong Kong ebay seller with the intention to use in the UK on BT Mobile.
It came supplied, supposedly brand new, and with KitKat. However, the connection to 2G and the phone network was highly unreliable, and drops out around 50% of the entire time. it would also never connect to 3G or 4G at all. While I set it up from scratch, and am convinced I chose the United Kingdom at setup (with a witness!), it did afterwards initially seem to be setup for the UAE, which I thought was strange. Just in case, I did a factory reset and set it up for the UK. The exact same network problems persisted.
I've tried the SIM in another phone and it is perfectly fine. I've tried upgrading the S4 to both 5.0 and then 5.1 (BTU UK firmware). I've tried rebuilding the nvm. Yes, the APNs are setup correctly. I've (of course) made sure that all network options are selected in Mobile Networks. None of these things work.
I'm tearing my hair out trying to get this working with a reliable connection and on 3G/4G data. I'm thinking the phone is just faulty (battery drain is pretty bad too), but I'm wondering if the seller tested it with a Hong Kong SIM and it's region locked it in some way before UK use.
If this helps to know:
AP: I9505XXUHOJ2
CP: I9505XXUHOJ2
CSC: I9505BTUHOJ1
Anyone? Any ideas at all?
Happy new year,
schnidex

schnidex said:
Hi all,
I've bought an I9505 from a Hong Kong ebay seller with the intention to use in the UK on BT Mobile.
It came supplied, supposedly brand new, and with KitKat. However, the connection to 2G and the phone network was highly unreliable, and drops out around 50% of the entire time. it would also never connect to 3G or 4G at all. While I set it up from scratch, and am convinced I chose the United Kingdom at setup (with a witness!), it did afterwards initially seem to be setup for the UAE, which I thought was strange. Just in case, I did a factory reset and set it up for the UK. The exact same network problems persisted.
I've tried the SIM in another phone and it is perfectly fine. I've tried upgrading the S4 to both 5.0 and then 5.1 (BTU UK firmware). I've tried rebuilding the nvm. Yes, the APNs are setup correctly. I've (of course) made sure that all network options are selected in Mobile Networks. None of these things work.
I'm tearing my hair out trying to get this working with a reliable connection and on 3G/4G data. I'm thinking the phone is just faulty (battery drain is pretty bad too), but I'm wondering if the seller tested it with a Hong Kong SIM and it's region locked it in some way before UK use.
If this helps to know:
AP: I9505XXUHOJ2
CP: I9505XXUHOJ2
CSC: I9505BTUHOJ1
Anyone? Any ideas at all?
Happy new year,
schnidex
Click to expand...
Click to collapse
What does it say your model is when booted into download mode?
Here is also a thread descriping a similair problem. Maybe it can help you.
http://forum.xda-developers.com/galaxy-s4/help/i9505-doesnt-3g-t2998527

schnidex said:
Hi all,
I've bought an I9505 from a Hong Kong ebay seller with the intention to use in the UK on BT Mobile.
It came supplied, supposedly brand new, and with KitKat. However, the connection to 2G and the phone network was highly unreliable, and drops out around 50% of the entire time. it would also never connect to 3G or 4G at all. While I set it up from scratch, and am convinced I chose the United Kingdom at setup (with a witness!), it did afterwards initially seem to be setup for the UAE, which I thought was strange. Just in case, I did a factory reset and set it up for the UK. The exact same network problems persisted.
I've tried the SIM in another phone and it is perfectly fine. I've tried upgrading the S4 to both 5.0 and then 5.1 (BTU UK firmware). I've tried rebuilding the nvm. Yes, the APNs are setup correctly. I've (of course) made sure that all network options are selected in Mobile Networks. None of these things work.
I'm tearing my hair out trying to get this working with a reliable connection and on 3G/4G data. I'm thinking the phone is just faulty (battery drain is pretty bad too), but I'm wondering if the seller tested it with a Hong Kong SIM and it's region locked it in some way before UK use.
If this helps to know:
AP: I9505XXUHOJ2
CP: I9505XXUHOJ2
CSC: I9505BTUHOJ1
Anyone? Any ideas at all?
Happy new year,
schnidex
Click to expand...
Click to collapse
Install this APP and add screenshots coz it will give you/us more info about your device.

Lennyz1988 said:
What does it say your model is when booted into download mode?
Click to expand...
Click to collapse
Thanks for the reply. On the download screen (Vol down + Home + Power on), assuming this is what you wanted to know, it says:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION : Enable
eMMC BURST MODE enabled
I imagine that most of this isn't relevant, but I'm posting it in case it's useful later.
Also, thanks for the thread linked, but that's actually one I quoted in terms of rebuilding the NVM! Everything appeared to go through, but the problem persisted. The only difference was that the final reboot took less than the three minutes predicted, and was closer to instantaneous. I didn't get any error messages, and assume I followed each step correctly.

Joku1981 said:
Install this APP and add screenshots coz it will give you/us more info about your device.
Click to expand...
Click to collapse
I had that installed to try and figure out the problem, including whether the handset had been previously used or not! Amongst other things, it says that a headset has used once, although I don't believe it has been. This is what made me think the HK seller had previously tested the handset, and initiated a region lock.
Are there any specific screens you'd like me to take shots of?
I've since tested another SIM from a different network in the same S4, just to be 100% sure it wasn't the current SIM, and the problem persisted.
(All help appreciated, and thank you).

schnidex said:
I had that installed to try and figure out the problem, including whether the handset had been previously used or not! Amongst other things, it says that a headset has used once, although I don't believe it has been. This is what made me think the HK seller had previously tested the handset, and initiated a region lock.
Are there any specific screens you'd like me to take shots of?
I've since tested another SIM from a different network in the same S4, just to be 100% sure it wasn't the current SIM, and the problem persisted.
(All help appreciated, and thank you).
Click to expand...
Click to collapse
All screenshots if possible (IMEI Screen not necessary if agree with the one under the battery).

Joku1981 said:
All screenshots if possible (IMEI Screen not necessary if agree with the one under the battery).
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So there's all the main screens - the IMEI does match up, but I posted that screen anyway.
One thing I thought was strange is that when I performed the serial check in the menu options, the software said it wasn't a valid serial number. That's despite what's double-checking behind the battery.
And thanks for taking the time to look at this.

schnidex said:
And thanks for taking the time to look at this.
Click to expand...
Click to collapse
The product code being inactive and causing no network is somewhat related to EFS being corrupted even if the IMEI is still intact. Restore a EFS backup if you have it or get your device to repair.

Joku1981 said:
The product code being inactive and causing no network is somewhat related to EFS being corrupted even if the IMEI is still intact. Restore a EFS backup if you have it or get your device to repair.
Click to expand...
Click to collapse
An EFS backup? I've not heard of that before, and am fairly sure I don't have one. I can't repair this myself then, I assume?
I think, instead, I'll just have to return the device. The seller has already said they'll accept a return, and we've taken videos as proof the phone appears to be faulty. So starting from scratch with a new device is the way I'll probably go.
Any idea how this could have happened?
Thanks again for the continued support.

Joku1981 said:
The product code being inactive and causing no network is somewhat related to EFS being corrupted even if the IMEI is still intact. Restore a EFS backup if you have it or get your device to repair.
Click to expand...
Click to collapse
Sorry to bump this, but here's what's happened - the seller in Hong Kong wouldn't take the phone back, so we got a refund, which is of course great. However, we still have a phone that we'd like to use.
I called up Samsung UK and they took the IMEI, but said that it was a Hong Kong phone (despite being an I9505, which I thought was the European model). Because of that, they won't repair it - something about not having the parts or software, although I highly doubt that's true.
Is there anything we can do with it? If nothing else, it seems like such a waste of expensive equipment otherwise.

schnidex said:
Sorry to bump this, but here's what's happened - the seller in Hong Kong wouldn't take the phone back, so we got a refund, which is of course great. However, we still have a phone that we'd like to use.
I called up Samsung UK and they took the IMEI, but said that it was a Hong Kong phone (despite being an I9505, which I thought was the European model). Because of that, they won't repair it - something about not having the parts or software, although I highly doubt that's true.
Is there anything we can do with it? If nothing else, it seems like such a waste of expensive equipment otherwise.
Click to expand...
Click to collapse
They are lying to you. An I9505 is an I9505 and it doesn't matter where it's from.
1. Flash the latest stock rom trough Odin. If it succeeds go to step two.
2. Load up the stock rom files again (make sure you also have the bootloader selected) but this time use the i9505 .pit file, check re-partition and select nand erase all.
Try it.

Lennyz1988 said:
They are lying to you. An I9505 is an I9505 and it doesn't matter where it's from.
1. Flash the latest stock rom trough Odin. If it succeeds go to step two.
2. Load up the stock rom files again (make sure you also have the bootloader selected) but this time use the i9505 .pit file, check re-partition and select nand erase all.
Try it.
Click to expand...
Click to collapse
Thanks very much for this! The latest stock has already been flashed with Odin, so I should be good on step 1.
I don't have the phone (or Odin) in front of me right now but I was planning on using the file from this thread. I'm assuming they're all the same and that this one will be fine.
So in step 2 when you flash the .pit, do you also flash the latest stock again at the same time?
I'm looking forward to trying this, even if I'm a little scared too! Hopefully this will fix it.

schnidex said:
Thanks very much for this! The latest stock has already been flashed with Odin, so I should be good on step 1.
I don't have the phone (or Odin) in front of me right now but I was planning on using the file from this thread. I'm assuming they're all the same and that this one will be fine.
So in step 2 when you flash the .pit, do you also flash the latest stock again at the same time?
I'm looking forward to trying this, even if I'm a little scared too! Hopefully this will fix it.
Click to expand...
Click to collapse
Step 1 is only a test run to make sure Odin works as intended. So don't skip it
Yes you flash the files at the same time.

Lennyz1988 said:
Step 1 is only a test run to make sure Odin works as intended. So don't skip it
Yes you flash the files at the same time.
Click to expand...
Click to collapse
Got it! Thank you. And when I load up Odin for step #2, I assume I'll leave both the default check marks on, but also add Repartition and NAND Erase All.
:good:

Lennyz1988 said:
They are lying to you. An I9505 is an I9505 and it doesn't matter where it's from.
1. Flash the latest stock rom trough Odin. If it succeeds go to step two.
2. Load up the stock rom files again (make sure you also have the bootloader selected) but this time use the i9505 .pit file, check re-partition and select nand erase all.
Try it.
Click to expand...
Click to collapse
I've just started step 2 and it's flashing now - but I may have made a big mistake! When you've said:
make sure you also have the bootloader selected
Click to expand...
Click to collapse
..I've ticked "Phone Bootloader Update" but I'm now wondering if you actually meant choose a file under BL on the right side. I don't know what file that would have been. Which was the right thing to do?
(And thanks again for your help, btw)

Lennyz1988 said:
Step 1 is only a test run to make sure Odin works as intended. So don't skip it
Yes you flash the files at the same time.
Click to expand...
Click to collapse
Okay, it completed although it doesn't seem to have made any difference whatsoever. Everything is literally the same as it was before - Android didn't install from scratch, the device name is the same, it looks like nothing changed. Yet Odin said the processes completed.
I'm confused. At this point, I guess I'll have to take it into a Samsung store and have an unpleasant conversation hoping that it, somehow, results in them taking it in.

schnidex said:
Okay, it completed although it doesn't seem to have made any difference whatsoever. Everything is literally the same as it was before - Android didn't install from scratch, the device name is the same, it looks like nothing changed. Yet Odin said the processes completed.
I'm confused. At this point, I guess I'll have to take it into a Samsung store and have an unpleasant conversation hoping that it, somehow, results in them taking it in.
Click to expand...
Click to collapse
I'm not sure I did it right with the bootloader part, maybe that was it

I'm posting this for the benefit of anyone who experiences the same problem and finds this thread.
My phone was sent for repair to Fone Fun Shop in Sheffield, UK and has now supposedly been fixed. There were two reported problems.
Firstly, one of the partitions had become corrupt and the product code/IMEI information was damaged. A Riff Jtag box repair was performed.
Secondly, however, the antenna was damaged inside the phone and out of aligned. Worringly, the phone was sold to us as new but appears to somehow be a refurb. The screen had previously been replaced and the antenna was not put back properly.
Videos on how to check for this second problem are available on YouTube, although I didn't want to try it myself and wasn't sure this was the problem anyway, so sent it for repair. I hope that helps someone.
EDIT: Unfortunately, I've now had the phone returned - and it still isn't working.

Unlock Assistance [SOLVED]

Greetings, I have used your services a lot (different ROMS and tutorials) and appreciate all the effort the XDA community has provided to users of all levels. However now, I am unable to find the solution that I have been working on for quite some time.
For the last week or so, I have been trying my best to SIM unlock my S4. I know I could just ask my provider and save the headache of all this but I do find there is a great sense of accomplishment and learning when things are done yourself. I will list the phone's info below and the methods I have tried. I have ran multiple roms on this device: Stock --(wanted to be different)--> Slim ROM --(wanted to try something new)--> Resurrection --(had too many mic issues) --> CyanogenMod (now GPS doesn't work so I might try a new ROM)
S4 - SGH-i337M (jfltecan/jflte)... verified root
CyanogenMod version 11-20160815-NIGHTLY-jflte
Baseband version: I337MVLUGOH1
Build number: cm_jftle-userdebug 4.4.4 KTU84Q e2d38f60cf
Android 4.4.4
Kernal: 3.4.104-cyanogenmod-g8b03f0c
Recovery is via CWM
Locked Network info (via Phone INFO and SIM Card Information app):
Original CSC Code: FMC (Fido Canada)
Active CSC Code: FMC (Fido Canada)
The phone was bought from Fido a couple years back.
Network Operator Code: 302720 (Rogers Wireless - I think this what my Network atm is for emergency calls)
This is all the information I could get, please let me know if you need more info
I tried the popular method of doing this via ServiceMode by dialing #*0011# but nothing shows up on screen when I do that, the numbers don't even disappear (they just sit there taunting me); the same goes for *#197328640#. The only code that I have seen work is *#06# (IMEI). I looked up multiple android codes and either the numbers would stay and nothing would happen but sometimes the numbers would just disappear when i completed the code with no changes on the screen. I have downloaded and ran Service Mode Shortcut and Service Mode app and when I click ServiceMode on them, it says "Not Supported." in a little caption bubble at the bottom of the screen.
I then ran GalaxySim Unlock App and it states "Your device should be unlockable if you downgrade your baseband to MDJ or before. When I click on How to do it?, it pretty much asks me to download a stock version of my phone and try the app again.
I would like some advice on what steps I should take next.
Thank you for your time,
roms4eva
THE SOLUTION FOR ME:
Hi, I am going to leave a summary of what I did to fix my sim! Thanks to @audit13!
All the download links can either be found via google or on some on this thread. The link in post#2 has useful download links within it!
PLEASE MAKE SURE YOU BACK UP ALL YOUR IMPORTANT SELFIES, FILES, VIDEOS, ETC... My steps will require a clean installation, if you do not want a clean installation, just skip step 10 where you have to do a factory restart and just continue as is.
Short instructions - if you are already familiar with the content:
Flash 4.4.2 stock(.tar.md5), flash modem 4.2.2 (.bin) (if you can't, try another odin), flash TWRP (.zip), install SuperUS (.zip), install and run RegionLock Away 1.3 (.apk), reflash 4.4.2 or 5.0.1 if you wanna newer ROMs on.
Long instructions:
Download Stock firmware of 4.4.2 for your provider (via Google)... extract it out until you get the .md5 file out (ie. I337MVLUFNE1_I337MOYAFNE2_I337MVLUFNE1_HOME.tar.md5)
Download modem 4.2.2 for your provider (via post #2) (ie.modem.bin)
Download TWRP (via post #2) (ie. twrp-3.0.2-0-jfltecan.img.tar)
Download SuperUS.zip (via post #2) (ie. SuperSU-v2.79-201612051815.zip) and put it onto your s4 storage (via MTP setting and USB debugging on)
Download Regionlock Away 1.3.apk (via post #2) (ie. RegionLockAway-v1.3.apk) and put it onto your s4 storage (via MTP setting and USB debugging on)
Download Odin v3.12.3 and/or v3.07 (via post#2 or Google) (if one does not work, ie. stays stuck in "file analysis...", try the other odin)
Verify that Odin can recognize your device (plug s4 in via download mode status [Turn off, then hold Down + Power] and see if oden says "Added!!")
Run Odin 3.12.3 w/ administrator powers, make sure your device is "Added!!", click AP and select the .md5 file you downloaded(its the 4.4.2 in step 1).
Give Odin some time as it verifies the md5, then click start once that button is available. Then click start again once it says "Leave CS..." [this one took me an embarrassing two hours to figure out... LOL)
Let the s4 boot up and then restart into recovery (turn off phone, then hold UP Volume + Power), and do a factory reset (select on factory reset/data wip and choose Yes)
Restart the phone and go to download mode again (Down Volume + Power).
Go back to Odin 3.12.3 with admin power and under CP select the modem file for your carrier (modem.bin) and click start. If you are stuck on file analysis... after doing this and it has been over one minute, close Odin 3.12.3 and try it with odin 3.07 with admin power... the modem.bin file goes into Phone section.
While in download mode still, you could restart odin and flash the TWRP with any of the odin programs (odin 3.12 via AP section, or 3.07 via PDA)
start the phone up in recovery mode (UP vol + power), click on install, then find the SuperUS.zip file and install it.
Start the phone up normally with the SIM inside if you haven't put it in yet. (internet connection not required and it doesn't matter if SIM was in or not in the previous steps)
Go to File Manager or File Explorer, find the RegionLockAway-v1.3.apk you put in and run it... make sure you enable the ability for apks to be manually installed.
Go to apps and open the RegionLock Away app.... Click on Region Unlock button and grant it the superUS permissions it requires... then reboot!
The SIM Network Unlock Pin should disappear and your phone is now SIM Unlocked! If it asks again, wait a minute and restart the phone. If that doesn't work, retry the steps or make a thread and someone might be able to help you out.
Repeat step 8 again! You need to reflash! [note that this will remove your TWRP recovery, so reinstall that again like you did in step 13 if you want that. You will also lose root due to reflashing (so install superUS again)
Good luck!

I think ServiceMode is available only on TouchWiz ROMs.

Do you recommend I go back to stock via samsung-updates id=SGH-I337M (selecting Galaxy S 4 (Canada) SGH-I337M FMC I337MVLUGOH1 Android 5.0.1 24.08.2015 4508315)

Flash back to stock 4.4.2, flash 4.2.2 modem, root, run regionlockaway, reflash stock 4.4.2, enjoy your sim unlocked phone. This may help: http://forum.xda-developers.com/showpost.php?p=68889708&postcount=120
Btw, remove the imei from your post.

audit13 said:
Flash back to stock 4.4.2, flash 4.2.2 modem, root, run regionlockaway, reflash stock 4.4.2, enjoy your sim unlocked phone. This may help: http://forum.xda-developers.com/showpost.php?p=68889708&postcount=120
Btw, remove the imei from your post.
Click to expand...
Click to collapse
Thanks, I am currently doing as you have stated.
You also mentioned that I should install the regional unlock app. Will your method as well allow me to have my SIM unlocked? I am trying to use another carrier in another country (Saint Martin) and I am asked for my SIM unlock code.
Will I be able to use other Roms after this or am I stuck with 4.4.2 when I reflash?

roms4eva said:
Thanks, I am currently doing as you have stated.
You also mentioned that I should install the regional unlock app. Will your method as well allow me to have my SIM unlocked? I am trying to use another carrier in another country (Saint Martin) and I am asked for my SIM unlock code.
Will I be able to use other Roms after this or am I stuck with 4.4.2 when I reflash?
Click to expand...
Click to collapse
Yes it's a sim unlock method and you can use other roms as well
Sent from my GT-I9505 using XDA-Developers mobile app

I used the method @audit13 described and unlocked my device without trouble. My device is an I9505 and ran on Straight Talk in the US, so you should have no problem with using the device as you wish. Once you get the device unlocked, you can run any ROM you want. In my case I run AOSP 7.1.1 without trouble.

audit13 said:
Flash back to stock 4.4.2, flash 4.2.2 modem, root, run regionlockaway, reflash stock 4.4.2, enjoy your sim unlocked phone. This may help: http://forum.xda-developers.com/showpost.php?p=68889708&postcount=120
Btw, remove the imei from your post.
Click to expand...
Click to collapse
Hi,
So I did everything you mentioned above. Should I consider my device Stock and unrooted but with SIM unlock? Am I free to install ROMS now?
When I boot up, it asks for my SIM network unlock PIN, as well it says I have an "Invalid SIM card (network locked SIM card inserted)". - should I try the *#0011# method? I have access to ServiceMode now it seems!
I have followed through w/ your instructions... is everything set now? The SIM card is from the Caribbeans and I will not know if it actually works until I arrive there on Jan 2 for schooling.
Android version: 4.4.2
Baseband version: i337MLUFNE1
Kernel Version: 3.4.0-1529758
Build number: KOT49H.I337MVLUFNE1

If you followed the instructions, you should not be prompted for a network unlock code. Are you prompted to enter a SIM pin or network pin?

audit13 said:
If you followed the instructions, you should not be prompted for a network unlock code. Are you prompted to enter a SIM pin or network pin?
Click to expand...
Click to collapse
I am asked for the SIM network unlock PIN.

Did you add a security pin to the SIM card? Did you try different SIM cards?

audit13 said:
Did you add a security pin to the SIM card? Did you try different SIM cards?
Click to expand...
Click to collapse
Hi, when I go to the sim card app, there is a thing called "Secure Pass" on it. The carrier is CHIPPIE. I will try a newer sim card today.

if it helps:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

should i try your steps again?

Something has gone wrong because you should not be b seeing that screen if the steps were followed. I have used this method to unlock about 7 sgh-i337m phones.

audit13 said:
Something has gone wrong because you should not be b seeing that screen if the steps were followed. I have used this method to unlock about 7 sgh-i337m phones.
Click to expand...
Click to collapse
I have faith in xda users, I shall try it again!
Is the modem and firmware accurate?

Yes, it should be. After flashing the modem, wi-fi and cell service won't work.

audit13 said:
Yes, it should be. After flashing the modem, wi-fi and cell service won't work.
Click to expand...
Click to collapse
Hi, could you link me the 4.2.2 modem?
I am using this zip file found here (and flashed it via CWM on the 1st time i tried it) http://forum.xda-developers.com/showthread.php?t=2318233 and when i try to flash just the modem.bin via odin CP (1st time and now), it stays on the file analysis step and nothing happens. (I also restarted my phone and laptop). I know Odin works b/c i flashed the rom and twrp with it.
I think that may be the wrong one because upon cross checking with this link: http://forum.xda-developers.com/showthread.php?t=2324667 , it seems like the 1st link is for puerto rico, not canada as it claimed.
Also, the download links on the 2nd link are not working...

You need to use the modem I linked. Puerto Rico and Canada have the same s4.
I checked the links and they work for me.

audit13 said:
You need to use the modem I linked. Puerto Rico and Canada have the same s4.
I checked the links and they work for me.
Click to expand...
Click to collapse
i meant the dropbox links here: http://forum.xda-developers.com/showthread.php?t=2324667

Nougat w/ working Samsung Pay STEP BY STEP Guide

UPDATE: There is another set of instructions from user derektm. below which make a lot of sense. I didn't have a good understanding of how multi-csc roms functioned before.
This is a step by step guide on how to properly upgrade to Nougat while retaining Samsung Pay functionality. Thanks to user jhunkab for basically pointing everything out in another thread.
NOTES:
***YOU WILL BE WIPING THE PHONE*** UNLESS YOU ALREADY HAVE 6.0.1 DBT INSTALLED W/ SAMSUNG PAY ACTIVATED YOU CAN SKIP TO STEP 17.
STEPS
1. Download SAMFIRM 0.3.5
2. Download Odin 3.12.3
3. Open Samfirm
4. In "region" field enter DBT, press Check Update. You should now get a response for Android 6.0.1. Click Download (decrypt automatically checked)
5. Unzip file once downloaded
6. Backup anything you need on your phone (you will be completely wiping it)
7. Power down phone
8. Boot into flash (while holding down volume down+home button press and hold power button until blue screen appears. press volume up to continue) You should now be at a blue screen that says Downloading
9. Connect phone via micro USB to your computer and open Odin 3.12.3
10. You will now be selecting all files that you previously unzipped from the 6.0.1 DBT firmware. BL+AP+CP+CSC (**NOT HOME_CSC**)
11. Click Options tab in Odin, check Re-Partition
12. Once BL+AP+CP+CSC is loaded into Odin, press Start. Your phone will now begin flashing. Once Odin says it's finished, you can exit out of the program.
13. Wait until phone finishes flashing and boots up (this can take up to 5-10 minutes. be patient you are not in a bootloop)
14. Add WIFI, Google account, setup a fingerprint. don't bother with cloud recovery at this point (google/samsung)
15. Go to apkmirror.com and download Samsung Pay/Samsung Pay Framework from August 4th 2016 release. Install Framework first, then Samsung Pay (you will be prompted by security because they are side loaded)
16. Open Samsung Pay, go through the registration process, and add all your debit/credit cards. UPDATE application through settings>about. Verify that fingerprint authentication is initiating properly by pretending you are purchasing something. If you see the countdown, it's working.
17. Open Samfirm AGAIN
18. in Region enter BTU and press Check Update. It should populate with Android 7 firmware. Click download.
19. Unzip the file and open Odin
20. Repeat the same process for the BTU firmware EXCEPT instead of using CSC file you will now use HOME_CSC. (this is the HOME_CSC from the BTU firmware NOT the DBT one) **MAKE SURE RE-PARTITION IS NOT CHECKED IN OPTIONS TAB**
21. Press Start to flash Nougat BTU firmware.
22. Once it's finished, you are all set. You should now be on Nougat while still retaining your newly setup Samsung Pay from 6.0.1. Open the app to make sure everything is fine. If it goes back to registration or you do not see the Samsung Pay app, you did not flash correctly.
23. Restore your apps/cloud data and go about your life.
Enjoy.

How about directly downloading 7 (BTU) and installing Samsung pay? Will that work?
Edit: Never mind, I am already on DBT for 6.0.1 with everything setup, I will just follow steps from 17 onwards.
Can you elaborate step 23 a little (How-to)?

Step 23 just means restore from whatever backup you had... or don't. However you want to set it up

Thanks for posting these steps. I successfully updated after being on the beta with the DBT CSC code. Not sure if other people have this problem, but I am still unable to load an American Express card. This problem has existed for some time though. Otherwise the steps above seemed to work fine.

Ruturaj001 said:
How about directly downloading 7 (BTU) and installing Samsung pay? Will that work?
Edit: Never mind, I am already on DBT for 6.0.1 with everything setup, I will just follow steps from 17 onwards.
Can you elaborate step 23 a little (How-to)?
Click to expand...
Click to collapse
Were you successful in starting from step 17? I'm in the same boat (DBT and already updated/setup) and will probably try this tonight.

This worked for me as well. I was already on DBT so I started at step 17.

Guys you are perfectly fine skipping to step 17 if you have DBT with samsung pay set up. Just flash BUT with HOME_CSC

oplix said:
Step 23 just means restore from whatever backup you had... or don't. However you want to set it up
Click to expand...
Click to collapse
Thank you for making this thread.
Backup of google account, apps, local data (pictures and all)?
Will this update will work as an OTA update or flashing new ROM?
As Samsung pay app will retain data, I thought it works like OTA update.
Edit: Never mind. I am too dumb. You are flashing DBT first which is resetting everything.
One more question, will I receive OTA updates in future? (for UK or Germany Version)?
HalVllVler said:
Were you successful in starting from step 17? I'm in the same boat (DBT and already updated/setup) and will probably try this tonight.
Click to expand...
Click to collapse
I haven't tried yet but others did. And it seems to works. I just had mac yesterday. Bringing my work laptop to home today to flash update.
sstrunks84 said:
This worked for me as well. I was already on DBT so I started at step 17.
Click to expand...
Click to collapse
oplix said:
Guys you are perfectly fine skipping to step 17 if you have DBT with samsung pay set up. Judy flash BUT with HOME_CSC
Click to expand...
Click to collapse
Thank you sstrunks84 and oplix for letting me know.
Did it reset your phone? Data, accounts, applications?

@Ruturaj001 all data stayed intact, and didn't have to restore or setup anything over again.

sstrunks84 said:
@Ruturaj001 all data stayed intact, and didn't have to restore or setup anything over again.
Click to expand...
Click to collapse
That is great news, thanks. I am planning to flash it tomorrow.
Edit: Flashed it, everything works like a charm.

you saved my day bro...
i did everything right by my own... but the real trick from you is Samsung Pay/Framework apk dated August 4th. I was using most latest version and it didnt help.
Thank you very much.

Hey, everyone, I am having problem with installing theme, is anyone else is having one too?
Edit: I think I had that problem since I went from olympic edition to normal one. Flashed original Germany firmware. Everything works.

Thanks for the great research and directions. Started at Step 17 after already being updated on DBT. All went smoothly and SPay seems intact.

for me, all went well until i flashed nougat and it asked me that samsung pay be updated before it can be used. I gave "Later" to that and that was it, neither does the app open nor can it be updated from any of the stores. So I went ahead and flashed BTU with CSC and Re.Partition checked and decided to give up on Samsung Pay or until they announce it officially.

RamanRJN said:
for me, all went well until i flashed nougat and it asked me that samsung pay be updated before it can be used. I gave "Later" to that and that was it, neither does the app open nor can it be updated from any of the stores. So I went ahead and flashed BTU with CSC and Re.Partition checked and decided to give up on Samsung Pay or until they announce it officially.
Click to expand...
Click to collapse
You need to update it before flashing nougat. Look through the steps again.

Edit 2/23: Updated and reduced steps. Easier now.
BTU firmware is Multi CSC and has DBT CSC.... You guys are all doing it wrong if your setting up Samsung pay on MM and then flashing the HOME_CSC to prevent full wipe....
Proper way:
1) Flash MM DBT first using AP, BL, CP, and CSC. (The only reason for this is to set the phone to DBT CSC.) Allow phone to boot, go back to download mode (dont have to set anything up)
2) Flash BTU Nougat using AP, BL, CP, and CSC. (NOT Home_CSC).
Now you have clean, factory and OTA friendly Nougat BTU with DBT set as CSC (since BTU is multi csc, it doesnt change your csc from DBT, even using the normal CSC file for full wipe.) Set phone up and proceed....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Install this SPay APK: https://drive.google.com/file/d/0B0Z0JzkNunQ5Z0pkOFhFbUNaLVk/view?usp=sharing It is untouched and was put on my phone by the SPay app itsself when it updated. The versions on APK mirror for some reason are different and do not work correctly. They are from an incorrect region or something.
5) Now go into Samsung Pay, add all your cards, and update to latest version, if there is one. Note: Samsung pay may fail the first startup and complain about a server connection issue. Force close the app and start over. Its normal.
6) Done.
I have received additional updates through the Samsung pay app since I set this up several weeks ago. So updates are not an issue and you will always have latest version.

Your instructions are all good. Didn't know about the multi-csc

oplix said:
Hi working instructions have been posted please do not hijack
Click to expand...
Click to collapse
Its not hijacking its better information. This is a community to help each other and if the method can be improved then I am sure it is welcomed by the other members. :good:

derektm. said:
Its not hijacking its better information. This is a community to help each other and if the method can be improved then I am sure it is welcomed by the other members. :good:
Click to expand...
Click to collapse
This is not "better" information. The correct procedure is posted already. Do not confuse people. Someone was confused and you decided to add additional conflicting information.

oplix said:
This is not "better" information. The correct procedure is posted already. Do not confuse people. Someone was confused and you decided to add additional conflicting information.
Click to expand...
Click to collapse
Don´t be like that, there's no correct procedure in phone hacking world, his instructions seems clearer and also make more sense since you get a just wiped Nougat build in the phone and not an updated one.
Welcome to the internet, if you don't like listening to others you shouldn't be here.

G981U and G981U1 Firmware Links and Flashing Discussion Here

For those who aren't already aware, G981U is the model number of all of the US carrier versions of the S20. The G981U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I pay for a subscription to a site that gets the official releases (usually) before they hit SamFirm/Frija, so that's where my files come from. However, I don't have unlimited bandwidth on the site, and it's also quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x model - so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit SamFirm/Frija.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=305577
U1 firmware: https://www.androidfilehost.com/?w=files&flid=305578
(Quebec tends to be the fastest download mirror, if it gives you that option)
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading to an S20, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in SamFirm/Frija:
AIO = Cricket (not available via SamFirm/Frija)
ATT = AT&T (not available via SamFirm/Frija)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via SamFirm/Frija, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
- the correct procedure for switching from one carrier's firmware to another is:
1. Flash full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want

Pre-release notes:
1. I do not have one of these and do not plan to acquire one, so I have no idea if anything can actually be flashed at this moment - I'm just providing the firmware. Like all other models, I'm assuming patched Odin is needed for this, but it wouldn't surprise me if a new version is needed for this specific device. There's only one way to know though, so as soon as someone gets their hands on one and can try this, please let us know.
2. I don't know if using the HOME CSC will actually save data. I don't get access to that file straight from the source - I have to decompile the regular CSC, remove the parts that initiate the factory reset, and then re-compile it. Based on the S10 and Note 10, I've done what I think will avoid a factory reset. But the S20 has some new partitions, so we won't know for sure until someone tests it. So if you're willing to be that guinea pig, you're responsible for taking proper steps to avoid an FRP lock, make sure your data is backed up, etc

So I flashed with Odin with my unlocked from Samsung U1 firmware to the T-Mobile U firmware because I wanted the advanced messaging. Only issue in the beginning was not using the patched Odin, but once I did, no problems.
Tools:
Downloaded from this previous thread, post #2, with Modified Odin and Samsung Drivers https://forum.xda-developers.com/s10-plus/how-to/sm-g975u-firmware-downloads-tmo-spr-att-t3908657
Since it's been awhile since I've done flashing or Odin, I followed this basic guide:
https://forum.xda-developers.com/s10-plus/how-to/guide-g975f-flashing-megathread-faqs-t3936704
Of note, only needed the files from the TAW folder only, did not need the T-Mobile specific U firmware as resetting the phone with a T-mobile sim automatically loaded it.
My quick rundown:
1)Extract the G981U_TAW firmware file you just downloaded. You should get 5 files:
AP (System & Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_OXM (OXM CSC file, will wipe your phone)
HOME_CSC_OXM (OXM CSC file, will NOT wipe your phone)
2.)In Modified Odin I added each file to it's respective slot EXCEPT for HOME_CSC as I wanted to do a clean factory reset
3) Put the S20 in Download/ Odin mode. 2 different ways as outlined here https://www.youtube.com/watch?v=ZPSWEL6-gWg&t=8s
4) Once the phone was detected in the COM port number in Odin, I clicked the start button and waited til Odin said "PASS". One thing I noticed was the phone didn't reboot all the way automatically, it actually went into recovery mode and I ended up having to do a factory reset through there because at first it would bootloop and take me back into recovery mode, but after doing a factory reset in recovery mode it restarted just fine with the T-mobile firmware along with the t-mobile apps and advanced messaging working as it should be.

I want to flash my unlocked samsung s20 so I can use the ATT Volte and wifi calling but will rom eventually get released

jameslee2 said:
I want to flash my unlocked samsung s20 so I can use the ATT Volte and wifi calling but will rom eventually get released
Click to expand...
Click to collapse
If you're saying that you want AT&T apps and bloatware and features, then all the files that you need are already linked in the OP

I'm worried that I already know the answer, but i'm asking it anyways. I'm currently on a SM-G981N (South Korean version), which is a Snapdragon865 phone. I'm wondering if I can change my firmware to the SM-G981U version to get rid of the bloatware on my phone. For what I read for other phone's this wouldn't work. Perhaps I should start looking for an unbloated SM-G981N rom? Thanks!

tijsva said:
I'm worried that I already know the answer, but i'm asking it anyways. I'm currently on a SM-G981N (South Korean version), which is a Snapdragon865 phone. I'm wondering if I can change my firmware to the SM-G981U version to get rid of the bloatware on my phone. For what I read for other phone's this wouldn't work. Perhaps I should start looking for an unbloated SM-G981N rom? Thanks!
Click to expand...
Click to collapse
I'm assuming the flash would fail. But there's only one way to know for sure

I'll first try an unbloated korean firmware, until I'll find out if crossflashing between different region phones is safe and working...

tijsva said:
I'll first try an unbloated korean firmware, until I'll find out if crossflashing between different region phones is safe and working...
Click to expand...
Click to collapse
Is the a recovery for sm-g981u?
Sent from my SM-G981U using Tapatalk

Bee101 said:
Is the a recovery for sm-g981u?
Sent from my SM-G981U using Tapatalk
Click to expand...
Click to collapse
I don't understand what you're asking

Tried to flash the unbloated (my assumption at least) of the Korean rom: KOO. Followed the correct steps, flashed without problems but bloatware was not removed, also bootlogo of the original carrier doesn't disappear.
@iBowToAndroid, have you tested this method yourself with the S20 series? Flashing from unlocked to carrier firmware should always work I would say, but the other way around, have you got confirmed results for the S20 series?

SM-G981U Carrier Aggregation for Europe
I have S20 SM-G981U1 that i flashed with SM-G981U with no problems but is there any way to make CA to work in Europe?
Any help will be greatly appreciated because i have way lower mobile data speed in EU with my US unlocked phone...

tijsva said:
Tried to flash the unbloated (my assumption at least) of the Korean rom: KOO. Followed the correct steps, flashed without problems but bloatware was not removed, also bootlogo of the original carrier doesn't disappear.
@iBowToAndroid, have you tested this method yourself with the S20 series? Flashing from unlocked to carrier firmware should always work I would say, but the other way around, have you got confirmed results for the S20 series?
Click to expand...
Click to collapse
For U and U1 firmware, yes. You'll have to look elsewhere for discussions on Korean firmware

So you have tested flashing from (US) carrier firmware to unlocked carrier on the S20 succesfully? All bloatware and carrier bootscreens removed?

Any firmware (compatible with U1) that has CSC feature enabled for native call recording?

tijsva said:
So you have tested flashing from (US) carrier firmware to unlocked carrier on the S20 succesfully? All bloatware and carrier bootscreens removed?
Click to expand...
Click to collapse
@iBowToAndroid. Have you got confirmed results that bloatware is indeed removed including boot animations when changing from a US carrier branded phone to the international firmware on the Galaxy S20? I'm starting to wonder if there have been new restrictions in the S20 series that won't allow the CSC to be modified and therefor bloatware/carrier logo's won't be removed.

tijsva said:
@iBowToAndroid. Have you got confirmed results that bloatware is indeed removed including boot animations when changing from a US carrier branded phone to the international firmware on the Galaxy S20? I'm starting to wonder if there have been new restrictions in the S20 series that won't allow the CSC to be modified and therefor bloatware/carrier logo's won't be removed.
Click to expand...
Click to collapse
International firmware can't be flashed to a US model - never have been able to, never will be able to. Just because it's bloatware free doesn't make it "international". But yes, flashing the U1 firmware package removes all of the bloatware - it's been that way ever since the S7

iBowToAndroid said:
International firmware can't be flashed to a US model - never have been able to, never will be able to. Just because it's bloatware free doesn't make it "international". But yes, flashing the U1 firmware package removes all of the bloatware - it's been that way ever since the S7
Click to expand...
Click to collapse
Sorry, typo, should have been "unlocked" firmware.
You still haven't answered my question though Have you got confirmed results? Proof? I see you had good results for the S10 series, but so far I can't seem to find similar results for the S20 series.

dtothesquare said:
So I flashed with Odin with my unlocked from Samsung U1 firmware to the T-Mobile U firmware because I wanted the advanced messaging. Only issue in the beginning was not using the patched Odin, but once I did, no problems.
Tools:
Downloaded from this previous thread, post #2, with Modified Odin and Samsung Drivers https://forum.xda-developers.com/s10-plus/how-to/sm-g975u-firmware-downloads-tmo-spr-att-t3908657
Since it's been awhile since I've done flashing or Odin, I followed this basic guide:
https://forum.xda-developers.com/s10-plus/how-to/guide-g975f-flashing-megathread-faqs-t3936704
Of note, only needed the files from the TAW folder only, did not need the T-Mobile specific U firmware as resetting the phone with a T-mobile sim automatically loaded it.
My quick rundown:
1)Extract the G981U_TAW firmware file you just downloaded. You should get 5 files:
AP (System & Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_OXM (OXM CSC file, will wipe your phone)
HOME_CSC_OXM (OXM CSC file, will NOT wipe your phone)
2.)In Modified Odin I added each file to it's respective slot EXCEPT for HOME_CSC as I wanted to do a clean factory reset
3) Put the S20 in Download/ Odin mode. 2 different ways as outlined here
&t=8s
4) Once the phone was detected in the COM port number in Odin, I clicked the start button and waited til Odin said "PASS". One thing I noticed was the phone didn't reboot all the way automatically, it actually went into recovery mode and I ended up having to do a factory reset through there because at first it would bootloop and take me back into recovery mode, but after doing a factory reset in recovery mode it restarted just fine with the T-mobile firmware along with the t-mobile apps and advanced messaging working as it should be.
Click to expand...
Click to collapse
i got advanced messaging by just inserting a T-Mobile SIM into my unlocked s20, it restarted the phone and i even have the wifi calling too

tijsva said:
Sorry, typo, should have been "unlocked" firmware.
You still haven't answered my question though Have you got confirmed results? Proof? I see you had good results for the S10 series, but so far I can't seem to find similar results for the S20 series.
Click to expand...
Click to collapse
The proof is already here in the thread. Many users have already done it

Advice on S7e Firmware from UAE to BTU

Hopefully you guys might take a mo whilst we are in lockdown to just give me a few pointers please
Original S7e screen bust 6 months ago so i purchased a rekon S7e from Amazon Uk, all seemed well and i re applied my backups from my old phone to the replacement phone, after a few days of getting the phone the same as the original i realised the phone had a UAE csc, annoying at best but as i needed a working phone i kind of let it slide and carried on using the phone, apart from Samsung Health showing UAE adverts and pay showing UAE info the phone seemed ok.... actually add to that it has recieved no updates since Oct 2019 either, i have tried all ways to get security updates and phone os updates but to no avail, it just says it is up to date which i know is wrong as security updates have been released since last year
Now in lockdown and its raining its time to hopefully get the thing back on track, could you guys advise on what exact files i need so i dont brick or trip knox please
dev mode no issues
usb config no isuues
i have grabbed the latest UAE files
i have grabbed the latest UK BTU files
odin installed
do i need to mix and match files from both downloads ? just use the BTU files ?? if you guys could please give me some info on which set of files i need to load into odin it would be much appreciated
if you need csc pda numbers no probs just shout, i have never messed with android firmware before, all i want to do is get a Uk updating phone again
Thanks if you can help and stay safe

norsane said:
Hopefully you guys might take a mo whilst we are in lockdown to just give me a few pointers please
Original S7e screen bust 6 months ago so i purchased a rekon S7e from Amazon Uk, all seemed well and i re applied my backups from my old phone to the replacement phone, after a few days of getting the phone the same as the original i realised the phone had a UAE csc, annoying at best but as i needed a working phone i kind of let it slide and carried on using the phone, apart from Samsung Health showing UAE adverts and pay showing UAE info the phone seemed ok.... actually add to that it has recieved no updates since Oct 2019 either, i have tried all ways to get security updates and phone os updates but to no avail, it just says it is up to date which i know is wrong as security updates have been released since last year
Now in lockdown and its raining its time to hopefully get the thing back on track, could you guys advise on what exact files i need so i dont brick or trip knox please
dev mode no issues
usb config no isuues
i have grabbed the latest UAE files
i have grabbed the latest UK BTU files
odin installed
do i need to mix and match files from both downloads ? just use the BTU files ?? if you guys could please give me some info on which set of files i need to load into odin it would be much appreciated
if you need csc pda numbers no probs just shout, i have never messed with android firmware before, all i want to do is get a Uk updating phone again
Thanks if you can help and stay safe
Click to expand...
Click to collapse
Well, there is a saying which goes like this ;
"Don't try to fix which isn't broken"
You can make calls.. your phone works in all aspects.
Except that you dislike some uae built-in apps
Just disable those apps..
But if you have decided you want to jump in the "pseudo effect of update feels good" ship .. then i can't stop you.. its ur phone
But trust me you WON'T WANT TO HAVE LATEST UPDATES because i did what you want to do and now suffer
Okay but if you want to flash latest rom for your current country follow these steps.
1. See which rom/firmware is currently installed in your phone .. i.e : build numbers , and copy paste them here and also note them down so you can remember..
2. Since you want to get in this ship you need to ENABLE OEM UNLOCK AND USB DEBUGGING IN DEVELOPER OPTIONS, just to stay safe ** i will tell you why later **
3. Download latest odin from here i.e 3.14.4 https://technastic.com/odin-download-samsung-latest-all-versions/
4. Download latest firmware for your current country from here :
https://www.sammobile.com/samsung/galaxy-s7-edge/firmware/SM-G935F/BTU/
(if it is uk then there are 2 csc for uk .. btu and xeu)
5. *Important* make a backup of everything in your phone, then turn it off and go in recovery mode (by holding vol up + home + power buttons while its off)
Factory data reset and wipe cache.. then turn off phone..
6. Then put your phone in download mode while its off (by holding vol down + home + power buttons)
7. Run odin as admin on your pc, extract the firmware file you downloaded earlier.. it will give 4 files .. BL , AP , CP , CSC..
Select correct files corresponding to the boxes in odin..
*In odin options don't select any option other then F.reset time*
*USE CSC (NOT HOME CSC) IN CSC BOX..
8. Connect your phone to pc while in download mode (odin should detect the port.. if not install samsung drivers or smart switch for pc)
9. Press on start button to begin flashing.. once odin says success unplug your phone .. it will still be in download mode .. so hold vol down + home + power button to force reboot (once phone screen goes black immediately change from holding vol down to vol up + home + power .. this will put you in recovery mode.. do a factory data wipe + clear cache, then reboot phone)
**WARNING : DON'T UNPLUG YOUR PHONE WHILE ODIN IS FLASHING OR BEFORE IT SAYS SUCCESS ! **
10. Configure your settings and restore your data .. you should have btu csc now
*IMPORTANT*
*FLASHING A SECOND HAND BOUGHT PHONE (WHICH COULD BE PATCHED/MODIFIED BY A HARDWARE BOX) THROUGH ODIN CAN MAKE IT A HARD BRICK BUT IF OEM UNLOCK IS ENABLED YOU CAN FIX IT EASILY BUT IF SOME CERTIFICATES/IMEI WAS PATCHED THEN YOU WILL LOSE NETWORK !!*
*FLASHING TO LATEST FIRMWARE WILL CAUSE BOOTLOADER VERSION UPDATE AND YOU WILL BE STUCK WITH THAT BOOTLOADER (SINCE YOU CANNOT DOWNGRADE/FLASH ANY OTHER ROM WITH LOWER BOOTLOADER NUMBER OR EVEN TROUBLESHOOT USING A COMBINATION ROM*
*LATEST FIRMWARES HAVE SERIOUS PERFORMANCE/BATTERY ISSUES FROM MY EXPERIENCE AND YOU CAN DOWNGRADE ONCE YOU UPDATE TO A HIGHER BOOTLOADER NUMBER ! TRY EVERYTHING ON YOUR OWN RISK ! *
Sent from my S7 Edge using XDA Labs

shah22 said:
)
*IMPORTANT*
*FLASHING A SECOND HAND BOUGHT PHONE (WHICH COULD BE PATCHED/MODIFIED BY A HARDWARE BOX) THROUGH ODIN CAN MAKE IT A HARD BRICK BUT IF OEM UNLOCK IS ENABLED YOU CAN FIX IT EASILY BUT IF SOME CERTIFICATES/IMEI WAS PATCHED THEN YOU WILL LOSE NETWORK !!*
*FLASHING TO LATEST FIRMWARE WILL CAUSE BOOTLOADER VERSION UPDATE AND YOU WILL BE STUCK WITH THAT BOOTLOADER (SINCE YOU CANNOT DOWNGRADE/FLASH ANY OTHER ROM WITH LOWER BOOTLOADER NUMBER OR EVEN TROUBLESHOOT USING A COMBINATION ROM*
*LATEST FIRMWARE HAVE SERIOUS PERFORMANCE/BATTERY ISSUES FROM MY EXPERIENCE, TRY EVERYTHING ON YOUR OWN RISK! *
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Thanks Shah
Yup it definately is a second hand phone, the rear o2 blood sensor has a very dim red light on all the time, i read a software update cured that ?? which is another reason i wanted to try and get the phone to update
what does concern me, how can i tell if the phone has patched certs or IMEI ?? is there a way of finding this out ?? that does appear to be the only thing that at present i cannot find out
If any of this helps i would appreciate you taking a look
product name hero2ltexx
manufacture date 20160506
knox warranty bit 0x0
product code SM-G935FZSLXSG
PDA G935FXXS6ESH5
CSC G935FOJV6ESH5
BASEBAND G935FXXU6ASG1
BOOTLOADER G935FXXS6ESH5

norsane said:
Thanks Shah
Yup it definately is a second hand phone, the rear o2 blood sensor has a very dim red light on all the time, i read a software update cured that ?? which is another reason i wanted to try and get the phone to update
what does concern me, how can i tell if the phone has patched certs or IMEI ?? is there a way of finding this out ?? that does appear to be the only thing that at present i cannot find out
If any of this helps i would appreciate you taking a look
product name hero2ltexx
manufacture date 20160506
knox warranty bit 0x0
product code SM-G935FZSLXSG
PDA G935FXXS6ESH5
CSC G935FOJV6ESH5
BASEBAND G935FXXU6ASG1
BOOTLOADER G935FXXS6ESH5
Click to expand...
Click to collapse
Install phone info app.. send the csc and firmware tab screenshot..
Then go in download mode and send a pic of it too..
Edit : i am on XSG too.. but i never had any sensor light bug ever !
Sent from my S7 Edge using XDA Labs

shah22 said:
Install phone info app.. send the csc and firmware tab screenshot..
Then go in download mode and send a pic of it too..
Edit : i am on XSG too.. but i never had any sensor light bug ever !
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
How do i send a pic of Download mode, if the phones in download mode does it still capture ??

Product Code: SM-G935FZSLXSG
PDA: G935FXXS6ESH5
CSC: G935FOJV6ESH5
Baseband: G935FXXU6ASG1
Bootloader: G935FXXS6ESH5
Download option
Current Binary : Samsung official
System status : Official
FRP Lock : Off
Secure Download : Enabled
Warranty void : 0 (0x0000)
RP SWREV : B:6 K:4 S:5

Hey I need some help too, surprisingly I'm also in UAE I'm on the black diamond ROM running Moro kernel, my only problem is the sim card isn't working how do i make this work

norsane said:
Product Code: SM-G935FZSLXSG
PDA: G935FXXS6ESH5
CSC: G935FOJV6ESH5
Baseband: G935FXXU6ASG1
Bootloader: G935FXXS6ESH5
Download option
Current Binary : Samsung official
System status : Official
FRP Lock : Off
Secure Download : Enabled
Warranty void : 0 (0x0000)
RP SWREV : B:6 K:4 S:5
Click to expand...
Click to collapse
Ok it looks un-tempered.. you can try flashing btu
Alandc said:
Hey I need some help too, surprisingly I'm also in UAE I'm on the black diamond ROM running Moro kernel, my only problem is the sim card isn't working how do i make this work
Click to expand...
Click to collapse
Do other sim cards work ? Is phone's imei displaying correctly ?
Sent from my S7 Edge using XDA Labs

shah22 said:
Well, there is a saying which goes like this ;
"Don't try to fix which isn't broken"
You can make calls.. your phone works in all aspects.
Except that you dislike some uae built-in apps
Just disable those apps..
But if you have decided you want to jump in the "pseudo effect of update feels good" ship .. then i can't stop you.. its ur phone
But trust me you WON'T WANT TO HAVE LATEST UPDATES because i did what you want to do and now suffer
Okay but if you want to flash latest rom for your current country follow these steps.
1. See which rom/firmware is currently installed in your phone .. i.e : build numbers , and copy paste them here and also note them down so you can remember..
2. Since you want to get in this ship you need to ENABLE OEM UNLOCK AND USB DEBUGGING IN DEVELOPER OPTIONS, just to stay safe ** i will tell you why later **
3. Download latest odin from here i.e 3.14.4 https://technastic.com/odin-download-samsung-latest-all-versions/
4. Download latest firmware for your current country from here :
https://www.sammobile.com/samsung/galaxy-s7-edge/firmware/SM-G935F/BTU/
(if it is uk then there are 2 csc for uk .. btu and xeu)
5. *Important* make a backup of everything in your phone, then turn it off and go in recovery mode (by holding vol up + home + power buttons while its off)
Factory data reset and wipe cache.. then turn off phone..
6. Then put your phone in download mode while its off (by holding vol down + home + power buttons)
7. Run odin as admin on your pc, extract the firmware file you downloaded earlier.. it will give 4 files .. BL , AP , CP , CSC..
Select correct files corresponding to the boxes in odin..
*In odin options don't select any option other then F.reset time*
*USE CSC (NOT HOME CSC) IN CSC BOX..
8. Connect your phone to pc while in download mode (odin should detect the port.. if not install samsung drivers or smart switch for pc)
9. Press on start button to begin flashing.. once odin says success unplug your phone .. it will still be in download mode .. so hold vol down + home + power button to force reboot (once phone screen goes black immediately change from holding vol down to vol up + home + power .. this will put you in recovery mode.. do a factory data wipe + clear cache, then reboot phone)
**WARNING : DON'T UNPLUG YOUR PHONE WHILE ODIN IS FLASHING OR BEFORE IT SAYS SUCCESS ! **
10. Configure your settings and restore your data .. you should have btu csc now
*IMPORTANT*
*FLASHING A SECOND HAND BOUGHT PHONE (WHICH COULD BE PATCHED/MODIFIED BY A HARDWARE BOX) THROUGH ODIN CAN MAKE IT A HARD BRICK BUT IF OEM UNLOCK IS ENABLED YOU CAN FIX IT EASILY BUT IF SOME CERTIFICATES/IMEI WAS PATCHED THEN YOU WILL LOSE NETWORK !!*
*FLASHING TO LATEST FIRMWARE WILL CAUSE BOOTLOADER VERSION UPDATE AND YOU WILL BE STUCK WITH THAT BOOTLOADER (SINCE YOU CANNOT DOWNGRADE/FLASH ANY OTHER ROM WITH LOWER BOOTLOADER NUMBER OR EVEN TROUBLESHOOT USING A COMBINATION ROM*
*LATEST FIRMWARES HAVE SERIOUS PERFORMANCE/BATTERY ISSUES FROM MY EXPERIENCE AND YOU CAN DOWNGRADE ONCE YOU UPDATE TO A HIGHER BOOTLOADER NUMBER ! TRY EVERYTHING ON YOUR OWN RISK ! *
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Can you explain that a little further?
"BUT IF SOME CERTIFICATES/IMEI WAS PATCHED THEN YOU WILL LOSE NETWORK !!"
I have an SM-G935FD Galaxy S7 edge phone from Malaysia. I have it in Greece and as soon as I got it in my hands I let it go all the updates until Android 8. And then installed a custom rom. Since then I can't make or receive any calls and sometimes it recognize my sim card (Cosmote) and sometimes it doesn't. Even the times that recognize my network operator I still can't make or receive calls. And of course I don't have any data.
What I have done:
1. Flashed original Malaysian and Indonesian firmware with no luck
2. Activated and deactivated volte
3. Tried different sim card
4. Flashed original Greek firmware (which I thought it would solve my problem but nothing). At root files it has all the network operators enebled as normal.
5. Tried several custom ROMs from Android 7 to 10. The only one that had some result was Floyd 10. The result was that for a minute I had data and couple of sms came from missed calls. But then again nothing. And since the first time I installed it, when I reinstalled Floyd not even for a minute.
6. Tampered customer.xml file for csc folder as a friend from Floyd rom thread suggested but still nothing
7. With a different sim from different provider I have data almost all the time but no calls at all
do all that has something to do with what you stated above? because it pretty much looks like i ve lost network
Thanks

achkap said:
Can you explain that a little further?
"BUT IF SOME CERTIFICATES/IMEI WAS PATCHED THEN YOU WILL LOSE NETWORK !!"
I have an SM-G935FD Galaxy S7 edge phone from Malaysia. I have it in Greece and as soon as I got it in my hands I let it go all the updates until Android 8. And then installed a custom rom. Since then I can't make or receive any calls and sometimes it recognize my sim card (Cosmote) and sometimes it doesn't. Even the times that recognize my network operator I still can't make or receive calls. And of course I don't have any data.
What I have done:
1. Flashed original Malaysian and Indonesian firmware with no luck
2. Activated and deactivated volte
3. Tried different sim card
4. Flashed original Greek firmware (which I thought it would solve my problem but nothing). At root files it has all the network operators enebled as normal.
5. Tried several custom ROMs from Android 7 to 10. The only one that had some result was Floyd 10. The result was that for a minute I had data and couple of sms came from missed calls. But then again nothing. And since the first time I installed it, when I reinstalled Floyd not even for a minute.
6. Tampered customer.xml file for csc folder as a friend from Floyd rom thread suggested but still nothing
7. With a different sim from different provider I have data almost all the time but no calls at all
do all that has something to do with what you stated above? because it pretty much looks like i ve lost network
Thanks
Click to expand...
Click to collapse
If you bought it second hand then yes, it certificates/imei may have been patched using a hardware box and reflashing or even factory formatting results in network loss.. it may only be fixed by a box (or a local repair shop having box)
The other reason can be that your efs partition got corrupted and if you don't have a backup of efs before you rooted/customized your phone then ur out of luck mate..
Even if you had efs backup you would have been still out of luck because you made the mistake of "updating" to latest binary firmware and we need combination rom to fully repair network issues (and combination roms are not being available/leaked online for latest binaries)
Also a box can fix this too (or a local repair shop having box)
Can you tell if your imei is displayed correctly and if its different from the one printed on the phone's back or phone's packaging ? (If you got any)
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
If you bought it second hand then yes, it certificates/imei may have been patched using a hardware box and reflashing or even factory formatting results in network loss.. it may only be fixed by a box (or a local repair shop having box)
The other reason can be that your efs partition got corrupted and if you don't have a backup of efs before you rooted/customized your phone then ur out of luck mate..
Even if you had efs backup you would have been still out of luck because you made the mistake of "updating" to latest binary firmware and we need combination rom to fully repair network issues (and combination roms are not being available/leaked online for latest binaries)
Also a box can fix this too (or a local repair shop having box)
Can you tell if your imei is displayed correctly and if its different from the one printed on the phone's back or phone's packaging ? (If you got any)
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
Both my IMEI and efs are alright. I'm trying all this time to find a way to patch the certificates because on the one hand I don't have 120euros top but z3x and in the other I live on an island in Greece where there aren't any Samsung repair shops. I found halabtech tool and I patched certificates with that but I'm not sure that it is ok for my phone. Anyway network didn't came back after that.
Anyway after I saw your post I searched a lot and in found done threads that say that only at Android 6 the certificates can be patched. Any help would be appreciated...

achkap said:
Both my IMEI and efs are alright. I'm trying all this time to find a way to patch the certificates because on the one hand I don't have 120euros top but z3x and in the other I live on an island in Greece where there aren't any Samsung repair shops. I found halabtech tool and I patched certificates with that but I'm not sure that it is ok for my phone. Anyway network didn't came back after that.
Anyway after I saw your post I searched a lot and in found done threads that say that only at Android 6 the certificates can be patched. Any help would be appreciated...
Click to expand...
Click to collapse
If you need to patch certs then your imei's aren't alright lol, your imei's are either changed or blacklisted which is causing the issues, and yes downgrading to android 6 is necessary for patching certs.. but i think you need a hardware box for that..
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
If you need to patch certs then your imei's aren't alright lol, your imei's are either changed or blacklisted which is causing the issues, and yes downgrading to android 6 is necessary for patching certs.. but i think you need a hardware box for that..
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
So if the IMEI is the same and not blacklisted then there is no need for the patch? I bought the phone from a friend of mine, who he didn't do anything to the phone. Not even the updates. When I took it I let it update to Android 8, flashed twrp and then an Android 10 rom. A process I have done a million times until now, just not on this phone. At no point I lost the IMEI. So although I don't have the packaging I'm pretty sure that it is the same. I checked and it is not blacklisted either.
Any idea what could be then?
And again thank you for your time

achkap said:
So if the IMEI is the same and not blacklisted then there is no need for the patch? I bought the phone from a friend of mine, who he didn't do anything to the phone. Not even the updates. When I took it I let it update to Android 8, flashed twrp and then an Android 10 rom. A process I have done a million times until now. At any point I lost the IMEI. So although I don't have the box I'm pretty sure that it is the same. I checked and it is not blacklisted either.
Any idea what could be then?
And again thank you for your time
Click to expand...
Click to collapse
Yes, you can't verify that imei's are the same since you don't have original phone packaging, ask your friend to confirm..
And if imei's are okay then its efs bug/corruption, which i told in above post, you should have done backup before modifying phone.. but even if you got backup you cannot restore efs because you are on latest binaries and you need latest combination roms for successfully repairing efs, which sadly aren't available, so yeah sorry but hate to say can't guide further
Thats why i ask peeps to NOT get on latest firmware train lol and ALWAYS make efs backup before doing anything to your phone !
Btw, can you tell me which is the current firmware's build number ?
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
Yes, you can't verify that imei's are the same since you don't have original phone packaging, ask your friend to confirm..
And if imei's are okay then its efs bug/corruption, which i told in above post, you should have done backup before modifying phone.. but even if you got backup you cannot restore efs because you are on latest binaries and you need latest combination roms for successfully repairing efs, which sadly aren't available, so yeah sorry but hate to say can't guide further
Thats why i ask peeps to NOT get on latest firmware train lol and ALWAYS make efs backup before doing anything to your phone !
Btw, can you tell me which is the current firmware's build number ?
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
So i dialed *#06# and it shows both my imei and sn. This isn't a sign that everything is ok? Is there a way to test if my efs is corrupted?
I'm sending you screenshots of about phone to see my build and android version.
View attachment 5025621
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Στάλθηκε από το SM-G935F μου χρησιμοποιώντας Tapatalk

achkap said:
So i dialed *#06# and it shows both my imei and sn. This isn't a sign that everything is ok? Is there a way to test if my efs is corrupted?
I'm sending you screenshots of about phone to see my build and android version.
View attachment 5025621View attachment 5025625
Στάλθηκε από το SM-G935F μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
And the thing that troubles me most is that with a SIM card from a different provider I have data connection but no calls. Would that happen with corrupted efs?
Στάλθηκε από το SM-G935F μου χρησιμοποιώντας Tapatalk

achkap said:
And the thing that troubles me most is that with a SIM card from a different provider I have data connection but no calls. Would that happen with corrupted efs?
Στάλθηκε από το SM-G935F μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
So yeah imei may still be okay but you can't verify that this wasn't changed or such, by the looks of it its either a changed imei which lost its certs when reflashing..
Or a bugged/corrupted efs which isn't letting you connect to the networks.. and it can only be resolved as i said by combination rom and efs backup..
Since your binary is the latest 8th, there is no combination rom available for it
Btw you could try this guide here .. who knows it may work lol..
https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
So yeah imei may still be okay but you can't verify that this wasn't changed or such, by the looks of it its either a changed imei which lost its certs when reflashing..
Or a bugged/corrupted efs which isn't letting you connect to the networks.. and it can only be resolved as i said by combination rom and efs backup..
Since your binary is the latest 8th, there is no combination rom available for it
Btw you could try this guide here .. who knows it may work lol..
https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
Is there a way to downgrade to Android 7?

achkap said:
Is there a way to downgrade to Android 7?
Click to expand...
Click to collapse
Nope, not by conventional means.. a hardware box .. possibly but still no guarantee..
Thats why one should always research before immediately hopping in the "latest is best" train.. because often then not, it isn't the best if not the worst
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
Nope, not by conventional means.. a hardware box .. possibly but still no guarantee..
Thats why one should always research before immediately hopping in the "latest is best" train.. because often then not, it isn't the best if not the worst
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
I'm flashing my phones since 2012. Never I had a problem like that. That's why I hurried to change rom. Anyway. Thank you for your help. You clarified several things for me. I think I'm going to try the above method you told me. The phone isn't usable anyway....
Thanks again