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
Related
I am looking for any CSC packages that can be flashed by CWM.
I have three identical SGSII phones, and have brought them all on holiday to Thailand. Two of them are working fine, but one cannot connect to the network. After some investigation, I have found that the one that does not work is actually not able to even see the network that the SIM card is issued by. It can see several others, but even when I put a SIM card from one of those, it still doesn't work (I took it to a shop and they had a few cards to test).
I have a few theories:
1) The CSC package is either incorrectly installed, or is not compatible with the networks here.
2) This is a variant of the i9100 that is not compatible with the networks here. However, it is using the same ROM file (Galnet MIUI 2.6.15) as the other two, and About Phone reports i9100 as the model and I can find no indication otherwise.
3) The phone (which was purchased from a second hand dealer in Australia) was reported as stolen in Thailand, and the local networks have blocked the phone's IMEI for connecting.
1 can be easily tested. Are there any CSC packages which can be flashed via CWM? If so, I can try those to see if that fixes it. I am reasonably sure that 2 is not the case, but I cannot rule it out. 3 I can only find out by lengthy investigation here, and I have no intention of going that far.
So, where could I find CWM flashable CSC packages?
Here. I'm sure searching Google or XDA will throw up other sources.
CWM versions?
The problem is that I am overseas and do not have access to a machine with Odin that I can trust to do a proper flash. I have used Odin before from a PC with improperly installed USB drivers. I got the yellow COM box, but the process did not complete and the phone was soft-bricked, causing me a lot of inconvenience.
So if I can flash the CSC via CWM that would be far easier for me. Are there CWM versions of these packages?
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 have been at this issue since Saturday and gone through a lot of possible solutions but to no avail. So first of all i am in Ghana. A friend came to me with his s6 edge that he had some issues with his phone going off when he unplugs the charger and getting stuck in a bootloop when turning it on unless he plugs a charger in before it boots up fully(even with full charge)
So first of all he wanted to do a factory reset(phone was not rooted). Factory reset completed successfully but issue still persisted.
Specs of the phone was:
android 5.0.2
model number = SM-G925F
original csc (i wasnt able to note that down because downloading stock firmware was going to be the last ultimate weapon. first i was going to try some custom roms to see if it fixed the issue. Besides it was working fine here in Ghana.)
So that's when i flashed a twrp and i dont exactly remember but i think i might have tried to flash a lineage OS or something. But long story short, when u try booting up, the samsung galaxy edge screen with powered by android came on and stayed there. and it did not go on to boot up.
After trying through the night i then decided to use the ultimate tool and flash a stock firmware. Try as i might none of them got past the "Repartition Operation Failed" portion of flashing it. The Pit File was becoming an issue. Tried firmwares for my country, countries nearer to us, contries in africa and finally even european firmwares. And since from reading from here and other forums that the F variant was an international version the international pit files should work but they werent.
All this while whenever i go to Odin Download mode on the phone, the product name there was SM-G925D. This started the confusion because at that point i had looked through alot of firmware and that was not an option. When i searched google for that, the search results mostly correlated it to SC-04G, which looking at it was a Japanese firmware. I didnt want to use a japanese Firmware for obvious reasons. At least i wanted a firmware that was by default in English. But after about 2 days and seeing a lot of answers saying stuff about going to settings and checking stuff there plus me wanting to see an interface and work my way from there i succumbed.
And lo and behold, it flashed on the first try(i used the 4-part files firmware. It was android 7.0). But when it came to booting up, the splash screen had changed from samsung bla bla bla powered by android to NTT DOCOMO powered by android. But it booted up and i skipped through the setup. i had to change the language to english but there were a lot of japanese bloatware that came with it. But as i expected when i popped a sim card into it, and restarted the phone, there was the not available symbol(circle with a bar across) where the network bars were supposed to be.
Seeing that this was not going to do, i went to the settings this time to check on any important details and this were the new details
android version 7.0(January, 2018)
model number=SC-04G
build number was now SC0.....(cant write the full code as im currently in odin mode)
But obviously it was the japanese network. After this i have downloaded more firmwares and they all fail at "Setting PIT...Re-Partition failed". Somtimes i try to mix the 4 files up using maybe the CSC portion of the Japanese firmware but BL, CP, and AP of firmware from my region. This time the error is "sboot.bin failed".
And that has been my grind till now. Downloading likely firmwares and all failing to doing extremes like the mix and match. When the mix and match with BL, CP, and CSC of Japanese with AP of my region works and eventually boots up, there is no touch input. The touch does not work. When that happens i just have to start all over with the SC-04G, which never fails to work.
I have even seen some things about changing csc files in the file explorer with root so i flashed the Japanese FW and rooted it. Went through the processes but to no avail.
PS:
The first part of the Odin screen where you choose to continue or reboot is now completely in Japanese whiles it was formerly in English.
And there is no indication on the phone itself that it was from Japan. The back says Samsung and below it says Galaxy s6 edge. Friend bought it from a shop in Ghana here brand new.(not from a carrier)
****So here lies my confusion. How come a phone with an original model number of SM-G925F have a Product name of SM-G925D in Odin and hence only Flash Japanese Firmware SC-04G(CSC code = DCM) but would not flash any of the international variants. Even if i can eventually get the Japanese firmware to read the sim card we can manage it that way. But thats for when there are no options left.
So please i would like to know your ideas as to how this is happening and any possible solutions that might be different from what my batallion of open tabs are telling me. You can also let me know if you want any more details i might not have included. Looking forward to hearing from you guys.
Update On Issue
I ended up using the japanese firmware in the end because it wasnt picking anything else.
This time after the setup process, it picked up the sim card and the imei is available. So since network is now available i just rooted it with cf autoroot and removed the japanese bloatware and everything looks normal now.
Except the original issue of going off randomly whn power cable is pulled out even when having full charge.
:good:
So I have a rooted Galaxy J7 pro with me (SM-J730f/DS)
This phone was rooted and it was blocked at boot showing "Custom Binary Blocked by OEM Lock"
I went into Odin mode and there wasn't anything that showed a country code. So I downloaded a stock rom according to my country and it's carrier was open (which I thought meant any carrier, I mean there ain't any career named "open" in my country) So I flashed it using odin, everything went smooth. The phone is performing well but after inserting sim cards, it detects the sim but doesn't work. Shows "unable to connect" and "error while connecting" when I tried to set network manually.
I probably should now flash the correct firmware but I don't know in which country this phone belongs. I dialed *#1234#* but I obviously got the information about the rom I installed.
In the back of the phone "UK" is written after the model number (SM-J730F/DD, Samsung, Yateley, GU46 6GG, UK) but I couldn't find a UK rom. I looked into Imei.info but couldn't find any info about region.
Is there anyway to fix the issue other than trying every J7 firmware there is
Hey guys, while I am not new to this, it has been several years.
I recently got a used unlocked Comcast/Xifinity S21. I have a T-mobile SIM card.
I tried flashing the rom to stock U1 which worked great but my signal is poor. While connected to Wi-Fi, the mobile networks/Network Operators in settings shows "T-mobile Wi-Fi Calling". But while I am not connected to Wi-Fi, the Network Operators shows Xfinity Mobile.
Under software information, it shows: CCT/CCT/CCT
How I can fix this? I made sure to not click the HOME_CSC when using ODIN, and I even did this twice. Should I just try the U firmware instead? Or was this because I left the USERDATA section blank in ODIN? (I used XAA, and then TMB a second time under Frija to download the files though).
Thank you for your help
Facing the same issue with my unlocked S21 from Xfinity Mobile - now using it on VZW but I can't get Wi-Fi calling to work at all... the toggle for it isn't even there! Haven't found a way to change the CSC.
It doesn't matter the SIM, even an AT&T SIM card displays as "Xfinity Mobile" on this phone!
Update: I was able to use SamKEY to change the CSC to VZW!
Instructions:
You need to buy one credit from a reseller on eBay and download the program on samkey.org
Then turn on Developer Options in Android, and from there, turn on USB Debugging.
Connect your phone to your PC, then run the SamKEY program.
Login with the credentials you obtained from the eBay reseller, put TMB into the "Change CSC (buyer)" box, and click "CHANGE CSC"!
During the process, the phone will ask you to grant permission to your PC, don't forget to allow it (promptly), or else the program will exit, without changing your CSC.
As to which firmware to use, I'm tempted to say the TMB firmware might be the most reliable in your situation?
I'm using the latest VZW "991U" firmware and all the carrier features are working properly now.
quadrun1 said:
Update: I was able to use SamKEY to change the CSC to VZW!
Instructions:
You need to buy one credit from a reseller on eBay and download the program on samkey.org
Then turn on Developer Options in Android, and from there, turn on USB Debugging.
Connect your phone to your PC, then run the SamKEY program.
Login with the credentials you obtained from the eBay reseller, put TMB into the "Change CSC (buyer)" box, and click "CHANGE CSC"!
During the process, the phone will ask you to grant permission to your PC, don't forget to allow it (promptly), or else the program will exit, without changing your CSC.
As to which firmware to use, I'm tempted to say the TMB firmware might be the most reliable in your situation?
I'm using the latest VZW "991U" firmware and all the carrier features are working properly now.
Click to expand...
Click to collapse
Hey thanks for this!
I'm ready to change it but I get a warning using SamKey. Just wanted to see if you got the same warning or not:
"You phone has Special Carrier settings!
ITS NOT RECCOMENDED TO CHANGE CSC ON THIS MODEL.
Because Security area (SEC) may get "Relocked" and NO WAY TO UNLOCK IT again!!!
Are you sure YOU WANT TO CONTINUE CHANGE CSC?"
As you would imagine, just wanted to double check with you and see if you got this same warning or not.
Thanks! If not, I'll try doing a freshwipe and firmware and seeing if I get the same warning.
quadrun1 said:
Update: I was able to use SamKEY to change the CSC to VZW!
Instructions:
You need to buy one credit from a reseller on eBay and download the program on samkey.org
Then turn on Developer Options in Android, and from there, turn on USB Debugging.
Connect your phone to your PC, then run the SamKEY program.
Login with the credentials you obtained from the eBay reseller, put TMB into the "Change CSC (buyer)" box, and click "CHANGE CSC"!
During the process, the phone will ask you to grant permission to your PC, don't forget to allow it (promptly), or else the program will exit, without changing your CSC.
As to which firmware to use, I'm tempted to say the TMB firmware might be the most reliable in your situation?
I'm using the latest VZW "991U" firmware and all the carrier features are working properly now.
Click to expand...
Click to collapse
ignore my last post. I did a fresh wipe and tried again and didn't get that error. The CSC has now changed to TMB and already my signal has shot up. Thank you again so much!
shadowwisp1 said:
ignore my last post. I did a fresh wipe and tried again and didn't get that error. The CSC has now changed to TMB and already my signal has shot up. Thank you again so much!
Click to expand...
Click to collapse
What if I didn't fresh install and continue changing the CSC with this warning? What would happen?