So back in 2020 I purchased a Z Flip 5G (SM-F707U) from T-Mobile. I paid it off, and then I had it unlocked, and I swtiched over to Cricket (which runs on AT&T network) and did not have any issues for about a year. Then all of a sudden earlier this year (2022), I stopped being able to make any phone calls. Text and data worked fine, but incoming voice calls would go straight to voicemail and outgoing calls would disconnect as soon as I hit the call button. After several frustrating days, and a few calls to tech support, I was advised that AT&T had removed 3G access from their network and that I need to turn on some feature called VoLTE calling or HD calling. Well it turns out that my Z Flip 5G from T-Mobile does not have those features availble, and was basically told that it will never work on the AT&T and Cricket networks and that I needed to get a new phone
Now that was the case until today!!!
I replaced the SM-F707U TMB firmware with SM-F707U1 XAA firmware (XAA is the firmware that ships if you order unlocked phone direct from Samsung) and now voice calls are working again on the Cricket network. Note that with the old TMB firmware voice calls still worked only on the T-Mobile network. The new XAA firmware has replaced the T-Mobile startup logo with the Samsung logo, and voice calls just work on Cricket without having to change any settings.
Special thanks to the following threads, as I would not have been able to complete this process without them:
This was the key post that helped realize I could use the U1 XAA firmware on my zflip:
F707U AT&T Odin Firmware Links
For those who don't know, F707U is the model number of all of the US carrier versions of the Galaxy Z Flip 5G. The F707U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100%...
forum.xda-developers.com
How to download patched version of Odin:
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
Step by step instructions on everything I needed to do:
How to update to the latest Software via Odin - also for flashing/unbricking any firmware
Hello everyone! I made a tutorial regarding flashing the latest updates, flashing custom ROMs or unbricking your device: Video guide: Steps: 1. Download and extract both Frija and Odin. 2. Launch Frija. 3. Check the "Auto" button. Write your...
forum.xda-developers.com
How to download Frija so you can then download the firmware file you need ... the BL and AP and CP and CSC/HOME_CSC files:
[Tool] Frija - Samsung firmware downloader/checker
* * * PLEASE UNDERSTAND WHAT YOU ARE INSTALLING TO YOUR DEVICES AT ALL TIMES AND ME AND THE DEVELOPER ARE NOT RESPONSIBLE FOR ANY SORT OF DAMAGE TO YOUR DEVICE * * * Hey Guys :) Frija is a new tool (successor of now depreciated tool SamFirm)...
forum.xda-developers.com
Note that I did NOT need a USERDATA file.
Note that I used the HOME_CSC file not the CSC file.
Related
The reason i want to do this is i own an ATT s6 edge (SM-G925A) but im in the uk and im on the H3G (3) network. It is network unlocked. It would be nice if the phone acted as if i had bought it here (able to update OTA, boot with 3 logo etc). I found the firmware on sammobile (SM-G920F), it was only a single file though, using Odin3 i loaded it into the AP tab, but i just got a fail and a soft brick which i fixed with the original ATT firmware that has 4 files. AP,BL,CP and CSC. I'll admit i'm not sure what they do individually.
I really want to know, is what i'm trying to do even possible and if so, where if i needed, can i get a more complete firmware file? I'd be really grateful of any help or advice, thanks.
Hi all!
I bought an S6 Edge second hand and after flashing a stock ROM, I had the "emergency only" calls issue, I tried everything I could find in the forums to no avail and I ended up taking it to a repair service. I did not think they could fix it but they did and I would like to know what they did to it in order to prevent it from happening again and to know if I can leave it as default (not custom OS) so that it can upgrade.
State of phone when bought:
So, the phone was working well with all carriers (from Colombia). The only thing I was able to notice after I bought it was that it was still on Marshmallow (6.0.1) with carrier branded stuff. It was in perfect shape otherwise.
So I downloaded a stock ROM and installed it using Odin. After this the phone would not let me make calls as it was not registering on the network. It did not even let me make emergency calls despite getting full bars of signal and being able to recognise the list of carriers when attempting to manually connect to them.
Important: The ROM downloaded was for the right version of the phone which was the G925i and the IMEI, serial number and baseband were not altered from the original. Also, I checked the phone to see if it was reported as lost/stolen and it was not (of this I'm sure because in Colombia you can consult a centralised database on any carrier's webpage). Also.. Here in Colombia it is illegal for carriers to lock phones.
Steps I took to fix it:
Downloaded ROMs for all carriers, branded and unbranded, I even installed one from Trinidad and Tobago and a LATAM one.
I performed all the tricks to disable and enable flight mode, location services, try con connect manually to the networks, changing to GSM only, GMS/CDMA, international roaming, etc.
I also extracted modem.bin from an earlier version and flashed the modem.bin with Odin (6.0.1 moden on 7.0, 5.1.1 moden on 6.0.1 and 5.1.1 moden on 7.0). All modems flashed correctly and the issue remained exactly the same.
So I finally gave up.. I installed the latest stock ROM which was an unbranded Nougat (7.0) version and took it to a repair service and they fixed it in a couple hours.
What I noticed after the phone was "repaired":
- The phone was rooted, SuperSu was installed, no other root app was installed.
- On SuperSu, there are entries for ADB shell (they all say Superuser command contents have not been logged for this entry) in a two minute timespan.
- The android version was downgraded to 6.0.1, I was told not to try to update it.
- Developer options was enabled with USB debugging turned on.
- The boot option (the one where you can wipe data and cache partition) was left as original (not the TWRP one).
- The ROM used to downgrade was the same I had before but only downgraded the version.
I suspect this same procedure was performed before on the phone but it had the original ROM carrier branded so it seems as if they installed a custom ROM, rooted it, connected with pc and performed some command line stuff to fix it, then cleaned the bootloader to a stock one.
The questions:
Any ideas what did the repairman do to fix the phone? Also, would it be safe to make a full backup with TWRP and flash again a stock ROM upgraded to 7.0 and then flash the backed up modem to get it working? Or would that possibly screw up the repair?
Thank you all in advance for any help. I'm sure there are lots of people out there experiencing the same "emergency only" issue I had but there does not seem to be a fix around, but clearly there is one! So I hope this sheds some light into what could possibly happen.
I’m trying to flash the firmware on a S6 edge (Android 7.0) in the hope I might get wifi calling calling on Three in the UK as there’s no mobile signal where I live and the 3inTouch app I’ve been using is discontinued. I’m on PAYG which is perfect because I’m a light user and Three’s credit doesn’t expire.
I used Odin successfully to install BTU firmware from Sammobile but that doesn’t give me wifi calling. But when I try to install H3G firmware for Three I get a failed error in Odin and a “SECURE CHECK FAIL (BOOTLOADER)” error on the phone. I’ve tried various versions of Odin and firmware from another site but all failed. USB debugging is enabled in developer options.
I found a thread where it appeared someone managed to get wifi calling working on an S6 using Kies to enter the model number and serial number of the phone and then was then offered a menu to select the firmware he wanted to install. I tried this on a separate pc (in order not to interfere with Odin) with the newest version of Kies I could find that gave me the option to enter the model & serial number. But this gave me the error “SM-G925F does not support initialising”.
So is the only solution now to root the phone, which I’m reluctant to do because of security? If I do root it and manage to update the firmware is there anything I can do to make it secure? And if I give up and buy a new unlocked sim-free phone (S7 or above) from Amazon or elsewhere will wifi calling work or would I need to be flashing firmware again which I don’t really want to do on a new phone.? Three's website says it has to be bought from them.
I should also have said that OEM unlock doesn't appear in the developer options
Just bought a samsung SM-N690F/DS. Newbie with rooting. I tried root but got stuck on SAMSUNG screen logo. I playing with TWRP and end clean whole the phone. I can only booty TWRP and get to DOWNLOAD MODE. I'M looking for the stock rom but i need csc code not sure which region my phone is? is way to find out...I find download mode...but not seeing anything look like csc code. Thanks for any help
Your phone can have any of the supported CSC codes, you just have to flash it.
For start just flash the latest and everything should go back to stock, use this link (https://www.sammobile.com/samsung/galaxy-note9/firmware/SM-N960F/DBT/download/N960FXXS8FUC4/1511407/) or use frija for faster download speeds. It will show as Germany but it is universal(for exynos - N960F - make sure the F is exactly your letter, there are more linke N or U).
After that you should find your country csc code, you can go to this link and select your country(https://www.sammobile.com/samsung/galaxy-note9/firmware/#SM-N960F).
CSC codes are dependent of region(like country) and carrier(SIM network provider). You can choose a specific carrier or use your country(this should have all your country carriers included and no carrier bloat apps included)
Converting your Unlocked device over to FirstNet firmware requires Patched Odin you need the v3.14.1 Patched version. You will also need the newest TMB (universal) carrier firmware, links below. Extract the zip when the download completes. You will not lose any data or factory reset during this process. You will need an ATT sim card.
S22
S22 Plus
S22 Ultra
Take your current S22 running the unlocked U1 firmware (don't skip this step, only U1 firmware can make the change to the ATT - CSC) and insert an ATT sim it has to be ATT not your FN Sim. If you don't have one you can try your local ATT store with a FirstNet rep and explain that you just need an unactivated ATT sim. If they give you any trouble, WalMart sells prepaid ones for $10.
Insert the ATT sim, you will get a pop-up explaining that the phone needs to restart to apply ATT settings. Let it restart. Once your phone is up and running, power it down.
Open Patched Odin and load up all the respective files from the folder you downloaded. Use BL, AP, CP and HOME_CSC (using the other CSC will factory reset and revert to XAA firmware.) now put your phone in download mode (boot up while holding power + vol up + vol down.) Once in download mode connect the phone via USB to your computer. Once Patched Odin recognizes the phone go ahead and flash. Your phone will reboot with an ATT logo. You can now swap back to the FN Sim.
Now you have a FirstNet S22.
What are the benefits of this? Just allows you to use a firstnet sim?
I assume since it's FirstNet, this works for the USA Snapdragon variant? Also, does this still trip Knox since you are just changing firmware and not rooting?
*** Took the chance. Works great and super easy. Thanks for the guide!
Does flashing to ATT firmware like this preclude the auto switch function of the unlocked model redownloading the appropriate firmware OTA when a different SIM (i.e. Verizon or T-Mobile) is inserted?
Will this void my warranty?
brajonrondo said:
Converting your Unlocked device over to FirstNet firmware requires Patched Odin you need the v3.14.1 Patched version. You will also need the newest TMB (universal) carrier firmware, links below. Extract the zip when the download completes. You will not lose any data or factory reset during this process. You will need an ATT sim card.
S22
S22 Plus
S22 Ultra
Take your current S22 running the unlocked U1 firmware (don't skip this step, only U1 firmware can make the change to the ATT - CSC) and insert an ATT sim it has to be ATT not your FN Sim. If you don't have one you can try your local ATT store with a FirstNet rep and explain that you just need an unactivated ATT sim. If they give you any trouble, WalMart sells prepaid ones for $10.
Insert the ATT sim, you will get a pop-up explaining that the phone needs to restart to apply ATT settings. Let it restart. Once your phone is up and running, power it down.
Open Patched Odin and load up all the respective files from the folder you downloaded. Use BL, AP, CP and HOME_CSC (using the other CSC will factory reset and revert to XAA firmware.) now put your phone in download mode (boot up while holding power + vol up + vol down.) Once in download mode connect the phone via USB to your computer. Once Patched Odin recognizes the phone go ahead and flash. Your phone will reboot with an ATT logo. You can now swap back to the FN Sim.
Now you have a FirstNet S22.
Click to expand...
Click to collapse
Hello, not trying to say anything is wrong just want to try and understand a little better. Why use the TMB carrier firmware instead of getting the CSC ATT from the website?
"https://samfw.com/firmware/SM-S908U/ATT"
GlJ0E said:
Hello, not trying to say anything is wrong just want to try and understand a little better. Why use the TMB carrier firmware instead of getting the CSC ATT from the website?
"https://samfw.com/firmware/SM-S908U/ATT"
Click to expand...
Click to collapse
ATT was not available at the time of writing. As you can see they rarely leak out. At this point in the game, you just want to download either the equivalent or newer build than you have on your phone, in order to avoid any data loss.
Flashing TMB (which historically has been near the front of the update pack) contains ATT in the firmware. Back at launch, the hotspot was somewhat finicky until you downloaded at least one ATT OTA update directly. I no longer have an S22 to test if this is still the case, but it was working last I checked.
brajonrondo said:
ATT was not available at the time of writing. As you can see they rarely leak out. At this point in the game, you just want to download either the equivalent or newer build than you have on your phone, in order to avoid any data loss.
Flashing TMB (which historically has been near the front of the update pack) contains ATT in the firmware. Back at launch, the hotspot was somewhat finicky until you downloaded at least one ATT OTA update directly. I no longer have an S22 to test if this is still the case, but it was working last I checked.
Click to expand...
Click to collapse
Alrighty thank you for the quick response honestly wasn't expecting that. I m going to try it I believe I understand the steps correctly and if not then gonna ask to exchange it for the ATT model. Thank you for all your info!