So you all know Samsung has been busy for a couple of years now region locking their phones -correction: our phones!- for their sales and marketing strategy or whatever and has been hurting us, the individual users, along the way. This is considered ridiculous by those of us who love buying the phone from wherever they want, using it wherever they want, and using whichever firmware they want. Buying a Galaxy S7 phone on a trip to Europe and failing to make the 5 minutes local activation call (as per the hidden fine print under the box seal) should never force you to send the phone back to where you bought it (that's Samsung's official response!!) And so, the challenge was accepted.. we fight back!
Latest information on the region lock:
The region lock is not as simple as it first seamed and will not be affected by sales code changes, product code changes, stock firmware flashing, rooting, hard resets, or upgrades.
The lock information is stored in an encrypted lock info vector stored in an encrypted block in the nv_data.bin file.
It's not clear how similar the region lock is to the SIM locks, or carrier network locks. But from the feedback of other owners, most services that offer network unlock codes mention that they don't support unlocking the new region lock by Samsung.
More recently a few independent service providers explicitly announced they support removing Samsung regional lock for anywhere from $20 to $45 depending on the region and the service provider. But unfortunately the service could be go down for some regions at any time for an extended duration. Again Samsung is responsible here because these services seem to rely on accessing a database if IMEIs and unlock codes managed by Samsung itself.
On a different front, a couple of the service providers seem to use a direct cable unlock method to remove all sorts of locks of various phones through communication with the phone's modem through AT commands. This method does not depend on any databases and so has leveled the play field, returning the control back to us.
Taking it from there, we had a look at the android RILJ, the native RILD, and even gave the firmware of modem a shot. The Ril.java class in the com.android.internal.telephony package showed a very solid hope: nvReadItem and nvWriteItem methods. However, working around the security measures involved in protecting the interprocess communication with the service stub implementation earned us nothing but disappointment when the 2 methods returned "not supported" error when executed through the RILD. The RILD analysis gave some similar false positives.
Finally, we found what we wanted after inspecting the modem.bin. The following 2 strings were found surrounded by AT commands and looked exceptionally interesting: +NVVALUEREAD and +NVVALUEWRITE. From there, we followed through and managed to use those to create the Galaxy Region Unlock app which allowed us to instantly remove the Samsung region lock on a Galaxy S7 G930F that had been locked to the European region (and who knows what other phones of the Galaxy family and what other sorts of locks it could be removing along the way!! any adventurers? ). In addition, the app allowed changing the product code without resetting or even restarting the phone!!
One catch though. The region unlock method hooks seems to have been killed from the modem in builds BPH1 and above (meaning new firmware released starting August 2016). It was working on APEQ modem build. But still, not a big deal, we have the old working modem firmware lying around and can flash it temporarily if needed.
Compatible Phones:
Samsung Galaxy S7 G930F (Exynos)
Compatible Modem Firmware:
G930FXXU1APEQ
G930FXXU1APB6
Enjoy the victory!
P.S. I'm trying to attach the apk here but I can't figure out how! Will make an edit afterwards once I figure out.
Update: Still can't figure out how to add an attachment. Can't add a link to the app on Google Play either for now, but you can easily find it on Google Play by searching using "com.ZigBrick.GalaxyRegionUnlock".
It's just for rooted phone?
Sent from my SM-G930F using XDA-Developers mobile app
Hi,
But I got that error: Operation failed: Failed to get lock level
Have you a solution?
Thank you in advance
ZigBrick said:
So you all know Samsung has been busy for a couple of years now region locking their phones -correction: our phones!- for their sales and marketing strategy or whatever and has been hurting us, the individual users, along the way. This is considered ridiculous by those of us who love buying the phone from wherever they want, using it wherever they want, and using whichever firmware they want. Buying a Galaxy S7 phone on a trip to Europe and failing to make the 5 minutes local activation call (as per the hidden fine print under the box seal) should never force you to send the phone back to where you bought it (that's Samsung's official response!!) And so, the challenge was accepted.. we fight back!
Latest information on the region lock:
The region lock is not as simple as it first seamed and will not be affected by sales code changes, product code changes, stock firmware flashing, rooting, hard resets, or upgrades.
The lock information is stored in an encrypted lock info vector stored in an encrypted block in the nv_data.bin file.
It's not clear how similar the region lock is to the SIM locks, or carrier network locks. But from the feedback of other owners, most services that offer network unlock codes mention that they don't support unlocking the new region lock by Samsung.
More recently a few independent service providers explicitly announced they support removing Samsung regional lock for anywhere from $20 to $45 depending on the region and the service provider. But unfortunately the service could be go down for some regions at any time for an extended duration. Again Samsung is responsible here because these services seem to rely on accessing a database if IMEIs and unlock codes managed by Samsung itself.
On a different front, a couple of the service providers seem to use a direct cable unlock method to remove all sorts of locks of various phones through communication with the phone's modem through AT commands. This method does not depend on any databases and so has leveled the play field, returning the control back to us.
Taking it from there, we had a look at the android RILJ, the native RILD, and even gave the firmware of modem a shot. The Ril.java class in the com.android.internal.telephony package showed a very solid hope: nvReadItem and nvWriteItem methods. However, working around the security measures involved in protecting the interprocess communication with the service stub implementation earned us nothing but disappointment when the 2 methods returned "not supported" error when executed through the RILD. The RILD analysis gave some similar false positives.
Finally, we found what we wanted after inspecting the modem.bin. The following 2 strings were found surrounded by AT commands and looked exceptionally interesting: +NVVALUEREAD and +NVVALUEWRITE. From there, we followed through and managed to use those to create the Galaxy Region Unlock app which allowed us to instantly remove the Samsung region lock on a Galaxy S7 G930F that had been locked to the European region (and who knows what other phones of the Galaxy family and what other sorts of locks it could be removing along the way!! any adventurers? ). In addition, the app allowed changing the product code without resetting or even restarting the phone!!
One catch though. The region unlock method hooks seems to have been killed from the modem in builds BPH1 and above (meaning new firmware released starting August 2016). It was working on APEQ modem build. But still, not a big deal, we have the old working modem firmware lying around and can flash it temporarily if needed.
Compatible Phones:
Samsung Galaxy S7 G930F (Exynos)
Compatible Modem Firmware:
G930FXXU1APEQ
G930FXXU1APB6
Enjoy the victory!
P.S. I'm trying to attach the apk here but I can't figure out how! Will make an edit afterwards once I figure out.
Update: Still can't figure out how to add an attachment. Can't add a link to the app on Google Play either for now, but you can easily find it on Google Play by searching using "com.ZigBrick.GalaxyRegionUnlock".
Click to expand...
Click to collapse
Are you with the correct (old) modem version?
Sent from my SM-G930F using Tapatalk
ZigBrick said:
So you all know Samsung has been busy for a couple of years now region locking their phones -correction: our phones!- for their sales and marketing strategy or whatever and has been hurting us, the individual users, along the way. This is considered ridiculous by those of us who love buying the phone from wherever they want, using it wherever they want, and using whichever firmware they want. Buying a Galaxy S7 phone on a trip to Europe and failing to make the 5 minutes local activation call (as per the hidden fine print under the box seal) should never force you to send the phone back to where you bought it (that's Samsung's official response!!) And so, the challenge was accepted.. we fight back!
Latest information on the region lock:
The region lock is not as simple as it first seamed and will not be affected by sales code changes, product code changes, stock firmware flashing, rooting, hard resets, or upgrades.
The lock information is stored in an encrypted lock info vector stored in an encrypted block in the nv_data.bin file.
It's not clear how similar the region lock is to the SIM locks, or carrier network locks. But from the feedback of other owners, most services that offer network unlock codes mention that they don't support unlocking the new region lock by Samsung.
More recently a few independent service providers explicitly announced they support removing Samsung regional lock for anywhere from $20 to $45 depending on the region and the service provider. But unfortunately the service could be go down for some regions at any time for an extended duration. Again Samsung is responsible here because these services seem to rely on accessing a database if IMEIs and unlock codes managed by Samsung itself.
On a different front, a couple of the service providers seem to use a direct cable unlock method to remove all sorts of locks of various phones through communication with the phone's modem through AT commands. This method does not depend on any databases and so has leveled the play field, returning the control back to us.
Taking it from there, we had a look at the android RILJ, the native RILD, and even gave the firmware of modem a shot. The Ril.java class in the com.android.internal.telephony package showed a very solid hope: nvReadItem and nvWriteItem methods. However, working around the security measures involved in protecting the interprocess communication with the service stub implementation earned us nothing but disappointment when the 2 methods returned "not supported" error when executed through the RILD. The RILD analysis gave some similar false positives.
Finally, we found what we wanted after inspecting the modem.bin. The following 2 strings were found surrounded by AT commands and looked exceptionally interesting: +NVVALUEREAD and +NVVALUEWRITE. From there, we followed through and managed to use those to create the Galaxy Region Unlock app which allowed us to instantly remove the Samsung region lock on a Galaxy S7 G930F that had been locked to the European region (and who knows what other phones of the Galaxy family and what other sorts of locks it could be removing along the way!! any adventurers? ). In addition, the app allowed changing the product code without resetting or even restarting the phone!!
One catch though. The region unlock method hooks seems to have been killed from the modem in builds BPH1 and above (meaning new firmware released starting August 2016). It was working on APEQ modem build. But still, not a big deal, we have the old working modem firmware lying around and can flash it temporarily if needed.
Compatible Phones:
Samsung Galaxy S7 G930F (Exynos)
Compatible Modem Firmware:
G930FXXU1APEQ
G930FXXU1APB6
Enjoy the victory!
P.S. I'm trying to attach the apk here but I can't figure out how! Will make an edit afterwards once I figure out.
Update: Still can't figure out how to add an attachment. Can't add a link to the app on Google Play either for now, but you can easily find it on Google Play by searching using "com.ZigBrick.GalaxyRegionUnlock".
Click to expand...
Click to collapse
Thank you for the beautiful explantion but unfortunally my modem version is BPH1 so the app is not working. what other options i have got? just finished rooting my phone.
---------- Post added at 04:16 AM ---------- Previous post was at 04:05 AM ----------
omrij said:
Are you with the correct (old) modem version?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
no. my modem version is G930FXXU1BPH1
So flash old modem
https://drive.google.com/open?id=0B_KNNXfgovrMNXcxNlZuMmtwaGs
After that, you can return to the new one
https://drive.google.com/open?id=0B_KNNXfgovrMUVhPTHdQSV81Z2M
Sent from my SM-G930F using Tapatalk
Thanks Brother for this great apps!!
Hi good day, I want to try this but i don't want to Trip my Knox yet, i'm not ready for that.
I hope the Non-Rooted support come soon
thanks for this great development.
Thumbs up for you Bro.
if the non-rooted is released i want to donate for a coffee for your nice work.
thanks a lot
waiting
cyke0213 said:
Hi good day, I want to try this but i don't want to Trip my Knox yet, i'm not ready for that.
I hope the Non-Rooted support come soon
thanks for this great development.
Thumbs up for you Bro.
if the non-rooted is released i want to donate for a coffee for your nice work.
thanks a lot
waiting
Click to expand...
Click to collapse
misulik79 said:
It's just for rooted phone?
Click to expand...
Click to collapse
Sorry I was away for the past few days. Actually we have tested a version that doesn't require rooting the phone. The only thing you'd miss with the non-root version would be the ability to backup your EFS info. We only have to do the final testing and release it, but we decided to postpone that for a while since we didn't find huge demand for such feature to justify the effort to put towards that.
I've created a poll to see if more people would like to have a non-root version of this app. If we find high demand for the non-rooted version, then we would bring releasing it back to the top of our priorities.
Changing csc without root would be great!
Thanks for the effort.
Sent from my SM-G930F using Tapatalk
Samsung S6 Region lock
So I bought my Samsung S6 from the UK in June, now I live in South Africa and it seems the region lock has kicked in after about a month in the country. I have tried just about everything to try and unlock the phone (except flying back to the UK to make my 5 minute call and paying for unlock codes over the internet). I've tried your app on my model SM-G920F (Software Version G920FXXS4DPH7, Modem Version G920FXXS4DPG3) but it says "Operation failed: Failed to get lock info". How do I get around this? Is there an older modem version for my S6 that will allow this?
Just to explain why I've never paid for an unlock code over the internet, I have never gotten an unlock screen request on the device so that's why I'm unsure if that will work. My device simply says "No SIM | Emergency Calls only", but Samsung UK has confirmed that the device contains a regional SIM lock.
Thanks in advance!
Pieter
vmostransistor said:
So I bought my Samsung S6 from the UK in June, now I live in South Africa and it seems the region lock has kicked in after about a month in the country. I have tried just about everything to try and unlock the phone (except flying back to the UK to make my 5 minute call and paying for unlock codes over the internet). I've tried your app on my model SM-G920F (Software Version G920FXXS4DPH7, Modem Version G920FXXS4DPG3) but it says "Operation failed: Failed to get lock info". How do I get around this? Is there an older modem version for my S6 that will allow this?
Just to explain why I've never paid for an unlock code over the internet, I have never gotten an unlock screen request on the device so that's why I'm unsure if that will work. My device simply says "No SIM | Emergency Calls only", but Samsung UK has confirmed that the device contains a regional SIM lock.
Thanks in advance!
Pieter
Click to expand...
Click to collapse
It's very annoying and inconvenient indeed.
You can find old stock firmware images for your device at sammobile. You can try the following steps:
Download the desired firmware from here: http://www.sammobile.com/firmwares/database/SM-G920F/
Extract the zip file.
Put the phone in download mode and flash the extracted file "CP_..." only. Make sure to use the latest version of Odin (3.12 or later) as they've changed the way you provide the files. Fill the CP field only in Odin.
@ZigBrick Sir
First up, Thank you very much for resurrecting this kind of app really! It's a life saver for unfortunate souls like me who have been robbed by Samsung by region locking our phones.
As a noob I have a few questions though
I have a region-locked (European, unlocked Single SIM, SM-G935F) Galaxy S7 Edge, should I try this app in my phone?
Is removal of Region lock is a one-time phenomenon? I mean will updating the phone bring the lock again or not?
Thanks in advance
---------- Post added at 09:32 PM ---------- Previous post was at 09:29 PM ----------
omrij said:
So flash old modem
https://drive.google.com/open?id=0B_KNNXfgovrMNXcxNlZuMmtwaGs
After that, you can return to the new one
https://drive.google.com/open?id=0B_KNNXfgovrMUVhPTHdQSV81Z2M
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
Please can you share old modem download link for Galaxy S7 Edge (SM-G935F Exynos variant)?
technomedico said:
@ZigBrick Sir
First up, Thank you very much for resurrecting this kind of app really! It's a life saver for unfortunate souls like me who have been robbed by Samsung by region locking our phones.
As a noob I have a few questions though
I have a region-locked (European, unlocked Single SIM, SM-G935F) Galaxy S7 Edge, should I try this app in my phone?
Is removal of Region lock is a one-time phenomenon? I mean will updating the phone bring the lock again or not?
Thanks in advance
---------- Post added at 09:32 PM ---------- Previous post was at 09:29 PM ----------
Please can you share old modem download link for Galaxy S7 Edge (SM-G935F Exynos variant)?
Click to expand...
Click to collapse
Thank you for the encouragement.
The app has already been successfully used to unlock SM-G935F.
The app modifies the nv-data.bin file, which contains specific settings for your phone (including IMEI, serial number, etc.) This file is not included with any firmware and doesn't get changed as part of updating/flashing. Therefore, updating "should" normally not cause your device to get locked again. This had been verified with several firmware updates.
I'm saying "should" because we don't know the future and whether samsung could be able to implement something specific in future firmwares that would detect this unlock method and undo it.
You can find old stock firmware images for your device at sammobile. You can try the following steps:
Download the desired firmware from here:
1- http://www.sammobile.com/firmwares/database/SM-G935F/
2- Extract the zip file.
3- Put the phone in download mode and flash the extracted file "CP_..." only. Make sure to use the latest version of Odin (3.12 or later) as they've changed the way you provide the files. Fill the CP field only in Odin.
ZigBrick said:
Thank you for the encouragement.
The app has already been successfully used to unlock SM-G935F.
The app modifies the nv-data.bin file, which contains specific settings for your phone (including IMEI, serial number, etc.) This file is not included with any firmware and doesn't get changed as part of updating/flashing. Therefore, updating "should" normally not cause your device to get locked again. This had been verified with several firmware updates.
I'm saying "should" because we don't know the future and whether samsung could be able to implement something specific in future firmwares that would detect this unlock method and undo it.
You can find old stock firmware images for your device at sammobile. You can try the following steps:
Download the desired firmware from here:
1- http://www.sammobile.com/firmwares/database/SM-G935F/
2- Extract the zip file.
3- Put the phone in download mode and flash the extracted file "CP_..." only. Make sure to use the latest version of Odin (3.12 or later) as they've changed the way you provide the files. Fill the CP field only in Odin.
Click to expand...
Click to collapse
Thanks for the quick reply!
I will update here whatever happens to my S7 Edge (hopefully the lock is removed).
This is very helpful, I had been looking for such an app to remove the region lock on my device. RegionLock Away wasn't working, and now I know why (thanks to the OP), however, even though this app worked and removed the region lock (in theory), I still have no access to my network. I can't make calls, and have no mobile data.
My device is an SIM-unlocked Galaxy S7 edge (SM-G935F), bought from the UK. It was set up for use in Tanzania, and worked fine there. However, it's now with me in the US, with a Verizon sim card, and seems to still be region-locked despite me using this app to remove that lock.
This is probably a long shot, but does anybody know what more I can do? Thanks for your help!
KaiserCola said:
This is very helpful, I had been looking for such an app to remove the region lock on my device. RegionLock Away wasn't working, and now I know why (thanks to the OP), however, even though this app worked and removed the region lock (in theory), I still have no access to my network. I can't make calls, and have no mobile data.
My device is an SIM-unlocked Galaxy S7 edge (SM-G935F), bought from the UK. It was set up for use in Tanzania, and worked fine there. However, it's now with me in the US, with a Verizon sim card, and seems to still be region-locked despite me using this app to remove that lock.
This is probably a long shot, but does anybody know what more I can do? Thanks for your help!
Click to expand...
Click to collapse
I'm not an expert in the CDMA networks phone compatibility, but according to this (http://forum.xda-developers.com/s7-edge/help/sm-g935f-verizon-t3346926), SM-G935F seems to have frequency compatibility problems with Verizon.
I suggest you investigate more along the CDMA compatibility route and possibly pop in a SIM from another US compatible network to verify.
flashing with older modem.bin crashes app
ZigBrick said:
It's very annoying and inconvenient indeed.
You can find old stock firmware images for your device at sammobile. You can try the following steps:
...
Put the phone in download mode and flash the extracted file "CP_..." only. Make sure to use the latest version of Odin (3.12 or later) as they've changed the way you provide the files. Fill the CP field only in Odin.
Click to expand...
Click to collapse
[Galaxy S6 SM-G920F]
I do not know how to generate a CP_ file like you ask above or where to find it. SamMobile only has tar.md5 files from which I can extract the bin file. I assume a CP_ only contains the modem.bin?
So I used Odin3 v3.10 to flash the modem.bin file from G920FXXU3DPER_G920FOJV3DPE3_G920FXXU3DPF2_HOME.tar.md5 which is dated 2016/06/10. Anyways the flashing was successful but when I execute your app it crashes. I have sent a feedback report via the phone which I think includes logs. I also tried flashing the whole ROM but that doesn't work, it fails at boot.bin so I suspect the bootloader version is different.
It could also be that there is some difference with the S7 modem and the S6 modem comms and that may be why your app crashes. Anyways I hope you can investigate and revert back. Let me know if there is any info I can supply! It would be great if your app can also be used to remove the region lock from S6 devices!
vmostransistor said:
[Galaxy S6 SM-G920F]
I do not know how to generate a CP_ file like you ask above or where to find it. SamMobile only has tar.md5 files from which I can extract the bin file. I assume a CP_ only contains the modem.bin?
So I used Odin3 v3.10 to flash the modem.bin file from G920FXXU3DPER_G920FOJV3DPE3_G920FXXU3DPF2_HOME.tar.md5 which is dated 2016/06/10. Anyways the flashing was successful but when I execute your app it crashes. I have sent a feedback report via the phone which I think includes logs. I also tried flashing the whole ROM but that doesn't work, it fails at boot.bin so I suspect the bootloader version is different.
It could also be that there is some difference with the S7 modem and the S6 modem comms and that may be why your app crashes. Anyways I hope you can investigate and revert back. Let me know if there is any info I can supply! It would be great if your app can also be used to remove the region lock from S6 devices!
Click to expand...
Click to collapse
The S7 firmware on SamMobile is packaged differently (a single ZIP file containing several tar.md5 files, with one tar containing the modem only.) The S6 seems to be using the old packaging structure. Anyway, flashing the old modem.bin is the goal and should work.
As for the crash, we can see the source of the problem (reading the RIL product code). But we need you to run the following and send back the results to see why the app is unable to read the RIL product code.
Code:
getprop | grep -i ril
getprop | grep -i product
ZigBrick said:
The S7 firmware on SamMobile is packaged differently (a single ZIP file containing several tar.md5 files, with one tar containing the modem only.) The S6 seems to be using the old packaging structure. Anyway, flashing the old modem.bin is the goal and should work.
As for the crash, we can see the source of the problem (reading the RIL product code). But we need you to run the following and send back the results to see why the app is unable to read the RIL product code.
Code:
getprop | grep -i ril
getprop | grep -i product
Click to expand...
Click to collapse
I did a getprop and I assume the product info you want is the ro.product because I don't see any other product info. seems there are some missing ril info on the old modem.
But I also see now that the G920FXXS4DPG3 modem date is before 1 August so shouldn't that have worked then? Maybe that's why the app said that it possibly supports region unlocking but when I ran it it said failed to get lock info.
Baseband G920FXXS4DPG3 2016-07-05
This works but cannot unlock
[ril.CompleteMsg]: [OK]
[ril.ICC_TYPE]: [0]
[ril.RildInit]: [1]
[ril.approved_codever]: [none]
[ril.approved_cscver]: [none]
[ril.approved_modemver]: [none]
[ril.atd_status]: [1_1_0]
[ril.backoffstate]: [33792]
[ril.cbd.boot_done]: [1]
[ril.cbd.rfs_check_done]: [1]
[ril.cs_svc]: [1]
[ril.ecclist00]: [112,911,999,000,08,110,118,119]
[ril.hasisim]: [0]
[ril.hw_ver]: [MP 1.000]
[ril.ims.ecsupport]: [2]
[ril.ims.ltevoicesupport]: [2]
[ril.model_id]: [UNKNOWN]
[ril.modem.board]: [SHANNON333]
[ril.official_cscver]: [G920FOJV3DPF3]
[ril.product_code]: [SM-G920FZKAXSG]
[ril.radiostate]: [10]
[ril.rfcal_date]: [20160414]
[ril.serialnumber]: [RF8H41GPKRJ]
[ril.servicestate]: [2]
[ril.ss.routing]: [0]
[ril.subinfo]: [0:2147483643]
[ril.sw_ver]: [G920FXXS4DPG3]
[ril.timezoneID]: [Africa/Johannesburg]
[ril.voice.rat]: [3]
Baseband G920FXXU3DPF2 2016-06-09
This crashes
[ril.ICC_TYPE]: [0]
[ril.approved_codever]: [none]
[ril.approved_cscver]: [none]
[ril.approved_modemver]: [none]
[ril.cbd.rfs_check_done]: [1]
[ril.ecclist00]: [112,911,999,000,08,110,118,119]
[ril.hasisim]: [0]
[ril.official_cscver]: [G920FOJV3DPF3]
[ril.serialnumber]: [RF8H41GPKRJ]
[ril.servicestate]: [1]
[ril.ss.routing]: [0]
[ril.subinfo]: [0:2147483643]
[ro.product.board]: [universal7420]
[ro.product.brand]: [samsung]
[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: [arm64-v8a]
[ro.product.device]: [zeroflte]
[ro.product.locale]: [en-GB]
[ro.product.manufacturer]: [samsung]
[ro.product.model]: [SM-G920F]
[ro.product.name]: [zerofltexx]
[ro.product_ship]: [true]
vmostransistor said:
I did a getprop and I assume the product info you want is the ro.product because I don't see any other product info. seems there are some missing ril info on the old modem.
But I also see now that the G920FXXS4DPG3 modem date is before 1 August so shouldn't that have worked then? Maybe that's why the app said that it possibly supports region unlocking but when I ran it it said failed to get lock info.
Baseband G920FXXS4DPG3 2016-07-05
This works but cannot unlock
[ril.CompleteMsg]: [OK]
[ril.ICC_TYPE]: [0]
[ril.RildInit]: [1]
[ril.approved_codever]: [none]
[ril.approved_cscver]: [none]
[ril.approved_modemver]: [none]
[ril.atd_status]: [1_1_0]
[ril.backoffstate]: [33792]
[ril.cbd.boot_done]: [1]
[ril.cbd.rfs_check_done]: [1]
[ril.cs_svc]: [1]
[ril.ecclist00]: [112,911,999,000,08,110,118,119]
[ril.hasisim]: [0]
[ril.hw_ver]: [MP 1.000]
[ril.ims.ecsupport]: [2]
[ril.ims.ltevoicesupport]: [2]
[ril.model_id]: [UNKNOWN]
[ril.modem.board]: [SHANNON333]
[ril.official_cscver]: [G920FOJV3DPF3]
[ril.product_code]: [SM-G920FZKAXSG]
[ril.radiostate]: [10]
[ril.rfcal_date]: [20160414]
[ril.serialnumber]: [RF8H41GPKRJ]
[ril.servicestate]: [2]
[ril.ss.routing]: [0]
[ril.subinfo]: [0:2147483643]
[ril.sw_ver]: [G920FXXS4DPG3]
[ril.timezoneID]: [Africa/Johannesburg]
[ril.voice.rat]: [3]
Baseband G920FXXU3DPF2 2016-06-09
This crashes
[ril.ICC_TYPE]: [0]
[ril.approved_codever]: [none]
[ril.approved_cscver]: [none]
[ril.approved_modemver]: [none]
[ril.cbd.rfs_check_done]: [1]
[ril.ecclist00]: [112,911,999,000,08,110,118,119]
[ril.hasisim]: [0]
[ril.official_cscver]: [G920FOJV3DPF3]
[ril.serialnumber]: [RF8H41GPKRJ]
[ril.servicestate]: [1]
[ril.ss.routing]: [0]
[ril.subinfo]: [0:2147483643]
[ro.product.board]: [universal7420]
[ro.product.brand]: [samsung]
[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: [arm64-v8a]
[ro.product.device]: [zeroflte]
[ro.product.locale]: [en-GB]
[ro.product.manufacturer]: [samsung]
[ro.product.model]: [SM-G920F]
[ro.product.name]: [zerofltexx]
[ro.product_ship]: [true]
Click to expand...
Click to collapse
The app was looking for "ril.product_code" setting value and crashed when it couldn't find it. This entry is not critical and we could easily bypass it. However, there are many other missing RIL properties from your device after flashing the old modem. This suggests that the RILD probably failed to initialize, either due to some incompatibility introduced by Samsung between the old and new firmwares you are mixing or due to incorrect modem bin flashing.
The date 1 August is used as a quick inaccurate check for now; i.e. just a best guess based on a few tested ROMs for S7. The exact modem version where Samsung killed the unlock backdoor used by this app is still not identified exactly. Also, whether the same change was rollout to modem firmwares releases of other devices in the Galaxy family around the same time is just a wild guess and is yet to be verified.
Perhaps you could flash the full old firmware to avoid any incompatibility the RILD might be having? (You mentioned that flashing the old ROM fails at boot.bin. I guess that is probably due to downgrade protection. I'm not very familiar with this area but I believe you might find better directions towards downgrading S6 images in this forum.)
Related
My wife works in a hospital and we used wifi calling because reception was poor.
It's still poor with Tmobile but no wifi calling. When we moved from At&t the wifi
option was greyed out. Tmobile states that it works fine on their network.
Is there any way to get a samsung s7 g930a and a samsung j7-j727a to use wifi calling
on the Tmobile network?
I'm sure it will probably involve something over my pay grade but I am willing to try
anything needed to get this feature to work
JohnAtlas said:
My wife works in a hospital and we used wifi calling because reception was poor.
It's still poor with Tmobile but no wifi calling. When we moved from At&t the wifi
option was greyed out. Tmobile states that it works fine on their network.
Is there any way to get a samsung s7 g930a and a samsung j7-j727a to use wifi calling
on the Tmobile network?
I'm sure it will probably involve something over my pay grade but I am willing to try
anything needed to get this feature to work
Click to expand...
Click to collapse
If your current firmware has WiFi calling (Volte) You can only use Volte if the network supports it. There are however many apps you can use for WiFi calling look on the play store.
Not sure what volte is, I have had some other issues with the
service that I thought might be resolved by installing a
different rom
Tell me if i'm wrong
Thanks
JohnAtlas said:
Not sure what volte is, I have had some other issues with the
service that I thought might be resolved by installing a
different rom
Tell me if i'm wrong
Thanks
Click to expand...
Click to collapse
Volte is wi fi calling over a network which the network operator supports without the need for a specific app.
Please tell me exactly what you are trying to do
What network are both phones using?
Which networks were the phones on initially?
Have you modified the phones in any way? Root? or TWRP?
What firmware are both phones currently using? Go to Settings>about phone>software information>baseband version G930A????
Sorry for not getting back sooner
Both phones are currently on Tmobile network
Both phones were originally on At&t network
No modification
Samsung s7 g930a baseband version G930AUCS8CRL1
Samsung j7-j727a baseband version J727AUCS4BRL1
Note: Wifi calling was available on original at&t network but is now greyed out on tmobile network
JohnAtlas said:
Sorry for not getting back sooner
Both phones are currently on Tmobile network
Both phones were originally on At&t network
No modification
Samsung s7 g930a baseband version G930AUCS8CRL1
Samsung j7-j727a baseband version J727AUCS4BRL1
Note: Wifi calling was available on original at&t network but is now greyed out on tmobile network
Click to expand...
Click to collapse
Ok since wi fi calling is network specific (some have it some don't) you either need to have unbranded firmware on your phone so it works no matter which network is providing it, or you need to now flash T Mobile firmware for it to work again on your phone.
US networks are a nightmare when it comes to this sort of thing and it's a right pain in the a** to solve it. So what you need to search for now on here is how to flash different firmware on AT&T S7. You should always try to flash unbranded firmware so everything works easily, if not it will have to be T Mobile Oreo.
cooltt said:
Ok since wi fi calling is network specific (some have it some don't) you either need to have unbranded firmware on your phone so it works no matter which network is providing it, or you need to now flash T Mobile firmware for it to work again on your phone.
US networks are a nightmare when it comes to this sort of thing and it's a right pain in the a** to solve it. So what you need to search for now on here is how to flash different firmware on AT&T S7. You should always try to flash unbranded firmware so everything works easily, if not it will have to be T Mobile Oreo.
Click to expand...
Click to collapse
Ok, If you think unbranded is the best way to go can you point me in the right direction
updato.com and sammobile.com both host firmware and have flash guides. SamFirmTool also is good for downloading firmware, but only lets you download the latest version and isn't as user friendly.
For unbranded you'll want to look for G930U firmware.
For best compatibility you flash all 4 files using (AP,BL,CP,CSC) this will wipe the phone clean. Otherwise you can try Home_CSC instead of CSC (So AP, BL, CP, Home_CSC) , which keeps your data but may not fully resolve your issues.
Beanvee7 said:
updato.com and sammobile.com both host firmware and have flash guides. SamFirmTool also is good for downloading firmware, but only lets you download the latest version and isn't as user friendly.
For unbranded you'll want to look for G930U firmware.
For best compatibility you flash all 4 files using (AP,BL,CP,CSC) this will wipe the phone clean. Otherwise you can try Home_CSC instead of CSC (So AP, BL, CP, Home_CSC) , which keeps your data but may not fully resolve your issues.
Click to expand...
Click to collapse
What beanvee has said but I think it's worth mentioning I find Sam Firm tool pretty straight forward to use and you'll always get the firmware in separate parts which can be useful.
I found a link for the G930A here
I'm not really understanding the differences in firmware. How is flashing with this firmware
any different than what's on the phone right now?
I am just trying to get the wifi calling to work, How is flashing it with at&t version firmware going
to help me on the tmobile network.
I guess I don't know what I need, stock, unbranded, official or custom rom.
I checked all sites listed and there is no firmware for the J727a, alternative?
I would rather someone more knowledgeable guess what I need to do, if that is what is
necessary because the phones are no good to me without that feature. Any suggestions
would be appreciated.
Each carrier deploys their own CSC file, which contains carrier specific configurations, and its this file that determines if VoLTE or VoWIFI is enabled and how it connects.
AT&T may have different VoWIFI settings to TMobile, which is why using AT&T firmware it doesn't work. Some carriers outright disable it since they don't offer it.
Your best bet would be G930T firmware https://updato.com/firmware-archive-select-model?q=SM-G930T&rpp=15&order=date&dir=desc&exact=1
However unbranded G930U should also work because the unbranded firmware is meant to work on all cariers. G930A would likely get you no where since it'll be AT&T specific
The phones in the USA are all identical hardware under the hood, the only difference is the carrier branding and firmware.
But that's only for the S7, I'm not familiar with the J7.
And it's not through lack of knowledge @JohnAtlas, US phones are a nightmare to do anything with. There are several options available but it's difficult to explain what to do and how to do if you are not familiar with how the software works.
There are many guides on how to unlock the software on all US networks, and depending on the network can include multiple steps to complete, you just have to search and read.
Ok, I was able to find the latest firmware for the G930 phone
I installed odin and have the files, BL, AP, CP, and CSC or Home CSC
My question is, Do I load all files and then start or do one file at a time in odin
I tried all files the first time and got failed error and dismatch
Thanks
JohnAtlas said:
Ok, I was able to find the latest firmware for the G930 phone
I installed odin and have the files, BL, AP, CP, and CSC or Home CSC
My question is, Do I load all files and then start or do one file at a time in odin
I tried all files the first time and got failed error and dismatch
Thanks
Click to expand...
Click to collapse
All files in correct slots and use this Odin https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Put all files in and used patched odin via link
Received fail and screen that said, "An error has occurred while updating the device software"
After reading more, tried to install twrp and received secure check fail : recovery
Rebooted phone and this is the screen right now, not sure what to do next
Thanks
https://drive.google.com/file/d/1QRvaTNb067u49lW1s4UZdRZivK936C2Y/view?usp=sharing
JohnAtlas said:
Put all files in and used patched odin via link
Received fail and screen that said, "An error has occurred while updating the device software"
After reading more, tried to install twrp and received secure check fail : recovery
Rebooted phone and this is the screen right now, not sure what to do next
Thanks
https://drive.google.com/file/d/1QRvaTNb067u49lW1s4UZdRZivK936C2Y/view?usp=sharing
Click to expand...
Click to collapse
That is the system recovery and when you flash with Odin you need to put your phone in download mode first press volume down+home+power. The phone should not go to that screen you have posted either before or after Odin, its a completely different recovery mode.
Get your firmware from updato. Com or sammobile
G930U, filter by USA and choose the latest XAA or USC and use the modified version of Odin. We know this works because thousands of people have used it to do what you are trying to do.
Thanks for info, I used G930U TMK version since we are on Tmobile carrier
It seems to be working fine and wifi calling is available
There is no TMK version for the J727U but will try the XAA for the other phone
The way I understand it is that the U means unlocked and the XAA is generic and not carrier specific
Please advise if I'm not on the right track
Thanks for your help
JohnAtlas said:
Thanks for info, I used G930U TMK version since we are on Tmobile carrier
It seems to be working fine and wifi calling is available
There is no TMK version for the J727U but will try the XAA for the other phone
The way I understand it is that the U means unlocked and the XAA is generic and not carrier specific
Please advise if I'm not on the right track
Thanks for your help
Click to expand...
Click to collapse
That's brilliant , glad your up and running.
So the letter "U"after the "G930" denotes the region of the world the device is build to operate in, the Americas just happens to be U. The unbranded firmware is the one that has a region but no network assigned to it, so a 3 letter code is used instead, in your case its USC, or XAA.
Europe is G930"F" or "FD" and the 3 letter code for unbranded is BTU & XEA.
Anyway if your phone is running great on T Mobile then don't update it anymore, turn auto update off. The advantage of keeping it T Mobile is you have the wifi calling, the unbranded firmware needs more fiddling around with the get the wifi calling working on the network your using, so best to stick with what works.
I will have a look for firmware for the J7 you have to see if i can recommend doing something with it to get the wifi calling working.
*update*
So it seems the J727 is the same as the J7 in terms of the internal components, everything is the same in both models so that's great news. I think the "27" bit is just a marketing thing.
In theory you should be able to flash the latest T Mobile Oreo to your device from this link https://www.sammobile.com/firmwares/galaxy-j7-pop/SM-J727T/TMB/download/J727TUVS4BRK1/249137/
Now before we start please check / do the following to avoid further problems.
1. Save everything you need from the phone to your pc.
2. Check that you have OEM unlocked in "developer settings" and "USB debug" enabled.
3. developer setting menu is, settings>about phone>software and information>build number>tap 7 or 8 times, developer menu should now appear. (Sometimes it's somewhere else but build number is what you want to find and tap on 7-8 times).
4. To avoid any issues with device FRP lock, delete your google account off the phone., settings>accounts>google. delete it. When successfully flashed you just add the account again when the phone starts for the first time by signing in.
5. Use the same version of Odin you used to flash your S7.
you can also use updato.com (i think it's slightly faster than sammobile.)
Let me know how you get on.
Remember J727T (TMB) is the firmware you want.
Phone: Samsung Note 10+ (USA Unlocked, purchased directly from Samsung)
Model: SM-N975U1
Baseband/PDA: N975U1UES3BTB3
CSC: N975U1OYM3BTB3 (from *#1234#)
The other day I received a notification on my phone saying that a root certificate has been added. It did not tell me any identifying information about the certificate. I did not add or approve this myself. I do not want to do a Factory Reset in case an attacker used the certificate in their attack to maliciously modify my phone to bypass deletion through a Factory Reset.
I did some research and found a reputable website (SamMobile) to download the firmware from. When I search for my phone's Baseband/PDA and CSC the first 10-15 entries are highlighted. Everything but the Country/Carrier column appears to be the same. I was thinking the USA version would be correct, but there are 2 of them.
Does anyone know how to pick the correct one? Does anyone have advice on my situation?
You can use the (USC) or (XAA), I did use the (USC) few times without flashing the userdata with no issues,
fred_yo said:
You can use the (USC) or (XAA), I did use the (USC) few times without flashing the userdata with no issues,
Click to expand...
Click to collapse
Thanks for the help! I'm not sure what USC or XAA is. I did some internet searches and nothing came back.
I'm alright with losing userdata if that means knowing my phone is secure.
Jets162 said:
Thanks for the help! I'm not sure what USC or XAA is. I did some internet searches and nothing came back.
I'm alright with losing userdata if that means knowing my phone is secure.
Click to expand...
Click to collapse
It means the type of carrier (tmo), means t-mobile, xaa means no carrier branding, like me i have ATT and i did flash a firmware with (USC) code .. to remove all the att branding...
https://updato.com/firmware-archive-select-model/?q=Sm-n975u1&exact=1
Uptado is another good site (slow) but good to get firmware files..
For those who aren't already aware, G996U is the model number of all of the US carrier versions of the S21+. The G996U1 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 the various firmware download tools posted here on XDA like 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 the firmware download tools, so that's where my files come from.
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=322091
U1 firmware: https://www.androidfilehost.com/?w=files&flid=322092
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 S21, 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
- it's 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 the firmware download tools.
- 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 the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, 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
Initial U firmware and AT&T USERDATA are posted, along with U1 firmware. U firmware is not yet accessible in the firmware download tools like SamFirm and Frija, but if anyone wants a different carrier's USERDATA (for flashing bloatware to a U1 device or for converting a U device from one carrier's bloatware to a different one), let me know and I'll get it for you
Are the firmware in OP compatible for the S21 (Non-plus)?
craznazn said:
Are the firmware in OP compatible for the S21 (Non-plus)?
Click to expand...
Click to collapse
This thread is in the S21+ forum, not the S21 forum.
This thread is for model numbers G996U and G996U1, not G991U or G991U1.
If you're looking for S21 firmware, that will be found in the S21 forum
I agree with you
Does the firmware control the SIM lock? So, can you flash the U1-XAA firmware and use say a phone purchased from AT&T on another carrier? Or do you need to do the SIM unlock before flashing?
3BeersKen said:
Does the firmware control the SIM lock? So, can you flash the U1-XAA firmware and use say a phone purchased from AT&T on another carrier? Or do you need to do the SIM unlock before flashing?
Click to expand...
Click to collapse
SIM unlock always goes much deeper than firmware. Flashing U1 will never automatically unlock any model - the unlock has to be done separately. If desired, I can provide a recommendation for a professional 3rd party business to do the unlocking, for any interested users who may not meet the carrier's unlock requirement(s).
Thanks. That's what I figured, but wanted to make sure. I like to get off of the AT&T firmware as quickly as possible as you can't get their updates unless you have an active SIM in the phone.
3BeersKen said:
You can't get their updates unless you have an active SIM in the phone.
Click to expand...
Click to collapse
Correct. They're A-holes like that haha
iBowToAndroid said:
Correct. They're A-holes like that haha
Click to expand...
Click to collapse
I got TMobile s21+ and want flash to u1,do you know which odin should I use, thanks
yijinsa said:
I got TMobile s21+ and want flash to u1,do you know which odin should I use, thanks
Click to expand...
Click to collapse
3.14.1 patched
I don't have my S21+ yet but it will be here soon. I ordered from Samsung and selected the Verizon version as unlocked was considerably more expensive.
Does anyone know what Verizon specific bloatware the S21+ has?
Are there certain apps which can be uninstalled with the U1 version but not the Verizon U version?
Are there any potential speed benefits on the 5G network that would be lost using the U1 version, or features like tethering that won't work?
For updates in the future, would they arrive faster on the U1 version, slower, or the same?
My main purpose in flashing from U to U1 is to free up the maximum amount of space of the 128 GB while still retaining 100% of the speed and features I would have with the Verizon version.
Thank you for educating me! It's been a couple years since I flashed my Note 8.
I order a unlocked S21+ U1 version straight from Samsung and didn't have to put in any VZW info.
There is a buttload of Samsung bloatware but no VZW except fot MyVZX
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
x1tymez said:
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
Click to expand...
Click to collapse
Yes, that seems to be a common issue with T-Mobile S21s - all 3 models
iBowToAndroid said:
Yes, that seems to be a common issue with T-Mobile S21s - all 3 models
Click to expand...
Click to collapse
You think there will be a fix for this? It's weird that dialer codes also don't work.
x1tymez said:
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
Click to expand...
Click to collapse
I've got a T-Mobile locked that I was able to get flashed over to U1 without much trouble. Shows mode number SM-G996U1 now, build number shows same.
edit: Nevermind, I see the TMB/TMB/TMB
krisology said:
You think there will be a fix for this? It's weird that dialer codes also don't work.
Click to expand...
Click to collapse
Dialer codes don't work? On which firmware?
iBowToAndroid said:
Dialer codes don't work? On which firmware?
Click to expand...
Click to collapse
XAA U1, VZW U1, stock TMB U, and I've tried the TLI U1 above and couldn't get it to work. Using google dialer, I input the codes like *#*#27262826#*#* and as soon as I type the last star it just disappears and nothing pops up. I tried with T-Mobile and Verizon sim.
krisology said:
XAA U1, VZW U1, stock TMB U, and I've tried the TLI U1 above and couldn't get it to work. Using google dialer, I input the codes like *#*#27262826#*#* and as soon as I type the last star it just disappears and nothing pops up. I tried with T-Mobile and Verizon sim.
Click to expand...
Click to collapse
Dialer codes usually don't work on VZW firmware, whether U or U1. But they almost always work on TMB and all others.
Have you tried *#06# ?
(WIP, files are currently processing and uploading)
For those who aren't already aware, F711U is the model number of all of the US carrier versions of the Z Flip3. The F711U1 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 the various firmware download tools posted here on XDA like 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 have access to an internal Samsung firmware download tool that usually gets new versions before they hit the public firmware download tools, so that's where my files come from.
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=327752
U1 firmware: https://www.androidfilehost.com/?w=files&flid=327753
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, 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
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single flagship 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 the firmware download tools.
- 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 the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
nwb_sam said:
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
Click to expand...
Click to collapse
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
iBowToAndroid said:
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
Click to expand...
Click to collapse
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
nwb_sam said:
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
Click to expand...
Click to collapse
Which F711U1 version did you flash?
iBowToAndroid said:
Which F711U1 version did you flash?
Click to expand...
Click to collapse
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
nwb_sam said:
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
Click to expand...
Click to collapse
Well UG7 is the latest that's available. So yes, I would expect you to get an error.
Once an update is available, if the phone is still giving the same error, then you can worry about it
Hello, well from my understanding Xfinity is bootloader unlockable after 60days and fully played for. I am wondering if anyone is planning on making a thread for Xfinity specifically. Or want too work with me on One. Sorry too spam or thread. But if u are familiar with how rom building, and flashing was with any other recent samsung model/Xfinity/bootloader unlock. It would be highly appreciated too know your experience.
jokono421 said:
Hello, well from my understanding Xfinity is bootloader unlockable
Click to expand...
Click to collapse
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
iBowToAndroid said:
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
Click to expand...
Click to collapse
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
twistedumbrella said:
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
Click to expand...
Click to collapse
Probably so
Can someone locate the thom browne fimware please?
blkghost22 said:
Can someone locate the thom browne fimware please?
Click to expand...
Click to collapse
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
iBowToAndroid said:
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
Click to expand...
Click to collapse
Thank you and always the best.
blkghost22 said:
Thank you and always the best.
Click to expand...
Click to collapse
Added, UGC build
iBowToAndroid said:
Added, UGC build
Click to expand...
Click to collapse
Guess its taking time to upload? Dont see the files just yet..
Edit:
Nvm i see the files now... again thank you so much
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
blkghost22 said:
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
Click to expand...
Click to collapse
1. Thom Browne *is* U1 firmware
2. USERDATA belongs to U firmware, not U1. So I have absolutely no idea. You'll have to try it and see what happens
Have successfully flashed F711U1 to F711W. Everything working fine. Used Odin 3.14, CSC_OMC_OYV, and working on Telus with all available features working.
Please note that AFTER the flash, you will be prompted to reset the device to stock. Reason being is that it needs to install the appropriate CSC linked to the inserted SIM card.
Can anyone confirm if cross flashing different build firmwares that it will unlock the unlock bootloader option?
Currently on carrier firmware for TMobile and I'm wondering if this is possible or if the u1 firmware has the unlock bootloader option available
A question from a noob here. I have a T-Mobile S22 Ultra phone which is network unlocked. As I recently I switched from T-Mobile to Verizon, I'm missing some of the features that are Verizon specific, while not needing anything that is T-Mobile specific anymore. From what I understand, Samsung installs multi SCS firmware on most of the phones these days, which can be changed by a dialer code. That however did not work at all.
Another option I've come across is by flashing provider specific (in my case Verizon) firmware as long as firmware version is the same (S908USQU2AVDC). There are a number of articles on how to do it by using Odin. The issues is no matter what I do and what files I select (like by using CSC file instead of HOME_CSC with or without flashing USERDATA file as well) the result is the same. It shows success and reboots and then reports an error and does the full factory reset which ends up back on T-Mobile version.
The question I have if it's even possible? And if so what I'm doing wrong here. Unlocking a bootloader is not really an option for me...
samirski said:
A question from a noob here. I have a T-Mobile S22 Ultra phone which is network unlocked. As I recently I switched from T-Mobile to Verizon, I'm missing some of the features that are Verizon specific, while not needing anything that is T-Mobile specific anymore. From what I understand, Samsung installs multi SCS firmware on most of the phones these days, which can be changed by a dialer code. That however did not work at all.
Another option I've come across is by flashing provider specific (in my case Verizon) firmware as long as firmware version is the same (S908USQU2AVDC). There are a number of articles on how to do it by using Odin. The issues is no matter what I do and what files I select (like by using CSC file instead of HOME_CSC with or without flashing USERDATA file as well) the result is the same. It shows success and reboots and then reports an error and does the full factory reset which ends up back on T-Mobile version.
The question I have if it's even possible? And if so what I'm doing wrong here. Unlocking a bootloader is not really an option for me...
Click to expand...
Click to collapse
In theory, flashing the correct firmware (VERIZON) should work. I would honestly first wipe the device, then flash (clean, not dirty) the Verizon firmware and setup accordingly. I had a similar case with a TMBILE unit (I had changed carriers) and I had managed to use XAA CSC and then when I reverted to TMOBILE SIM it would not "restart and install carrier updates". I had to basically switch the unit to U1 and then revert to U and it finally pulled all the TMO crap.
I may be mistaken since I haven't done this type stuff since S10, but I think you need to first reset the device and flash the unlocked version then when you put the verizon sim in it should provision it. Then you can flash the verizon package if you want the bloat apps. The features may be hit or miss. You may need to activate the features on the verizon website. Some features may never work as the carrier wont push them to IMEI not in their database of branded phones. There may be things you can do in hidden settings with "Activity Launcher" or other methods.
I'm here trying to figure out the same things for Tmobile and a factory Unlocked phone, before I buy.
Thanks a lot for your suggestions guys! I managed to do what I wanted. This is what I ended up doing, first flashed the unbranded U1 version on my phone and on the first boot Verizon sim was provisioned. Then I flashed Verizon firmware and it worked!