[Q] Quick question about flashing. - Galaxy S III Q&A, Help & Troubleshooting

Hello,
I recently bought a GS3 and since it's "carrier blocked" as its not recieving any further updates since my carrier is not willing to pay for new firmwares, I was wondering if, when I flash a new official firmware with ODIN, such as in my case DBT (Germany's one)...do I have to do anything special after or before flashing, or is it just safe to go and fash the firmware?
Thanks

No, it will just become an unbranded phone if you flash the latest stock rom for your country, or branded with another carrier if you choose their firmware.
What it won't do is unlock the old carrier SIM lock, so you'll still have to use their network.
Follow the sticky guides on using odin, backup your efs and you'll be fine.
Edit: you might need to factory reset before you flash, depending on how old your current firmware is.

Carrier blocked ??? Do you mean the phone and its IMEI has been blocked by the carrier ??

Related

[Q] Official JB XWLSD flash has caused carrier re-lock

I have an I9100 (international version) that I got from O2 in the UK. It was previously locked to O2 until I used the "Galaxy_S Unlock" app by Helroz. This seemed to unlock fine and could use it on Canadian networks with no problem.
I have flashed loads of other custom roms since with no problem, however I tried flashing the official sammy JB firmware (Nordic version, XWLSD) via Odin and found that my phone now asks for the carrier unlock code again. It seems to have re-locked itself to a carrier.
Any ideas? Is this a CSC issue? I thought firmware updates didn't affect the /efs files.
liabilityman said:
I have an I9100 (international version) that I got from O2 in the UK. It was previously locked to O2 until I used the "Galaxy_S Unlock" app by Helroz. This seemed to unlock fine and could use it on Canadian networks with no problem.
I have flashed loads of other custom roms since with no problem, however I tried flashing the official sammy JB firmware (Nordic version, XWLSD) via Odin and found that my phone now asks for the carrier unlock code again. It seems to have re-locked itself to a carrier.
Any ideas? Is this a CSC issue? I thought firmware updates didn't affect the /efs files.
Click to expand...
Click to collapse
Always back up EFS folder, ALWAYS.
Search was down earlier today but you still have google.
You could type something like "official jb carrier lock" and you get these results.
You could open a new tab for this and what do you know? problem solved.
gastonw said:
Always back up EFS folder, ALWAYS.
Search was down earlier today but you still have google.
You could type something like "official jb carrier lock" and you get these results.
You could open a new tab for this and what do you know? problem solved.
Click to expand...
Click to collapse
Yeah I did search, though nothing really relevant would come up as most results talked about the "leaked" firmware rather than the official releases, or would talk about "SIM" locks rather than a "carrier/network" locks.
I have backed up my EFS using ktool and have now used the GalaxSim Unlock apk linked above to remove the carrier lock. I had previously tried Helroz's app on the official JB firmware but it ended up corrupting my efs somehow and i lost my IMEI, managed to restore it though.
I was just suprised that flashing a new firmware would affect the carrier lock of a phone at all, it was my understanding that flashing firmware doesn't affect the efs directory. Anyway, problem solved and my phone is now usable abroad. Thanks!
Glad you solved it.
Now, read spocky's galaxysim thread, you'll see why your device relocked.
Sent from the little guy

[Q]Which stock firmware to use?

After buying my phone from a person (not an authorized seller) I factory reset the phone and it showed up in Arabic language, however since I accidentally bricked it I wasn't able to take a good look at what it's stock firmware was, Is there anyway at all to find what stock firmware I should be using? since I can't access the Lockscreen or the shutdown/screenshot features of the phone, I'm using a Turkey country 4.1.2 firmware
Go to Samfirmware. You can use the pulldown boxes to choose OS/phone model/country/carrier & it will give you a list of stock roms released by that carrier. At the end of the day it doesn't matter what (or even if) stock firmware you run, though obviously it might be difficult to get OTA updates if you're not running one for your country.
Well that's easy but they said on the newbie thread that in practice it's okay but it's not since the modems are different, and I already searched for a stock firmware but the problem is that the lockscreen isn't responding or not functioning (regardless of what screen lock you would like be it pattern or pin). They also said that I should use my IMEI to match the stock firmware I'm supposed to use? but I don't know that method yet.
If you flash a stock rom for your carrier, you will get a modem that's presumed they tested thorougly enough so it works for most people most of the time with their network before they released the rom.
If you've got that lockscreen issue, that's a different problem, but try flashing a stock rom for your carrier (and do a wipe after) before you do anything else.
An IMEI search won't give you the info you're after. And as I said in my PP, it's not important, but to make sure of things you flash a rom for your carrier.

Need clafication on what I can do on my SM-G925W8 S6 Edge Model

OK, this is gonna be long, but please bear with me......
TL;DR version first......
The Samsung S6 Edge SM-G925W8 bootloader is locked. Is this correct?
Somehow my changing of ROM caused the phone to be closed line again (Only accepts Rogers SIM) is this possible? Or perhaps the seller did some trick to accepy my local SIM card (Globe Mobile Philippines.)
And is there a free way to make the phone open line again?
Long Story below :
I'm from the Philippines and someone just sold me a Galaxy S6 Edge.
Looking at it's info it seems to be authentic, and is branded by Rogers.
SM-G925W8 is the model number and has Rogers built in apps. Android version is 6.0.1
What I did first is check if there is a way to downgrade, tried to do so by downloading a stock firmware (5.1.1 Rogers) from sammobile and tried to flash it thru ODIN. Failed. Upon research it seems that the bootloader of this model is locked and current you can flash with a firmware that's the same Android OS version (6.0.1), is this correct?
However, upon putting another stock, I noticed that it now rejects my local SIM card but before flashing it was fine. I wonder how did the seller did this? Perhaps they used a box device to openline it and me flashing anothe ROM caused it to lose open line status?
If anyone has something to add or correct me, please do so.
Hi, I'm not really active on here but I have this model and just installed a custom rom.
I used CF Autoroot through Odin to root the device, flashed custom kernel (Twisted-V11.5-EDGE) and TWRP and OZOP rom. My phone was originally 5.1.1 but I had to upgrade to 6.0.1 to install OZOP. I don't know if I would have been able had I updated before rooting and installing TWRP, but I flashed the kernel after I upgraded to 6.0.1 and that's what unlocks the bootloader, essentially.
As for unlocking from the carrier, I don't know if it's legit but there are a couple apps that claim to unlock for free at the push of a button. Might be worth a shot.

SM-T978U Odin Firmware Flash

Purchased a sim unlocked SM-T978U (Verizon Tab S7+ 5G) and am trying to flash the unlocked or Tmobile stock firmware to it. I've gotten "passed" flashes everything when flashing all of the files from the corresponding stock firmwares, but everything it boots back into the Verizon firmware. Any suggestions as to what I'm doing wrong that would cause this? I've probably flashed this thing 20 times at this point.
its a verizon tablet so thats normal.. u need to change csc is all
Thought that was part of flashing it with the patched version of Odin with a different CSC version of the firmware, but I've not done this before. Any suggestions or resources you can point to on how to do this? Thanks!
jmwfl2000 said:
Thought that was part of flashing it with the patched version of Odin with a different CSC version of the firmware, but I've not done this before. Any suggestions or resources you can point to on how to do this? Thanks!
Click to expand...
Click to collapse
patched odin only removes hash checks.. all the firmware has multi csc (all the usa csc) so simply flashing firmware doesnt change csc
Gotcha, so change the CSC first, then flash the matching firmware? What's the best method for changing the CSC on the S7+? This process? https://www.**********.com/how-to-change-csc-in-samsung-galaxy-phones/
Any suggestions on how to change the CSC? I've hit a wall and haven't been able to find a way to change it and then flash the desired firmware.
elliwigy said:
patched odin only removes hash checks.. all the firmware has multi csc (all the usa csc) so simply flashing firmware doesnt change csc
Click to expand...
Click to collapse
You need to flash with odin, wipe, then pop the other carrier sim in, on reboot it will boot with that carrier sw.
bs3pro said:
You need to flash with odin, wipe, then pop the other carrier sim in, on reboot it will boot with that carrier sw.
Click to expand...
Click to collapse
Ok, so SIM out, Odin flash with the TMB firmware. Then, what do you mean "wipe?" Is that just choosing the CSC file in Odin so that it resets all data, or some step after to wipe it?
So I tried again with these steps and had the same result, back into the Verizon firmware.
Removed Tmobile Sim
Odin flash TMB firmware
Tablet reboots automatically into VZW firmware
Then booted into recovery mode and performed a factory reset and cache wipe
Reinserted Sim and reboot
Tablet still boots into VZW firmware
I also tried this same process but with the unlocked "USC" firmware with the same results.
Am I supposed to somehow prevent the first boot after odin flash to perform the factory reset? I've tried that unsuccessfully but maybe I have the timing off or something.
jmwfl2000 said:
Ok, so SIM out, Odin flash with the TMB firmware. Then, what do you mean "wipe?" Is that just choosing the CSC file in Odin so that it resets all data, or some step after to wipe it?
Click to expand...
Click to collapse
jmwfl2000 said:
So I tried again with these steps and had the same result, back into the Verizon firmware.
Removed Tmobile Sim
Odin flash TMB firmware
Tablet reboots automatically into VZW firmware
Then booted into recovery mode and performed a factory reset and cache wipe
Reinserted Sim and reboot
Tablet still boots into VZW firmware
I also tried this same process but with the unlocked "USC" firmware with the same results.
Am I supposed to somehow prevent the first boot after odin flash to perform the factory reset? I've tried that unsuccessfully but maybe I have the timing off or something.
Click to expand...
Click to collapse
dunno wat ur flashing but all the firmware is the same.. theyre all multi csc.. so simply flashing different firmwares wont change csc lol
I don't know if this will help but on some samsung phones you can change the csc by opening the dailer and typing "*#272*IMEI number#"
edit: IMEI must me copied from the about tablet section in the settings. Press on the IMEI for a second and it will be copied to clipboard. Typing the IMEI will not likely not work.
After entering this in the dailer a menu pops up and you can select csc. Note this will usually factory reset the device.
Yes if you try this, please let me know if it works. I have the T878u 5g from Tmobile.
Any update on this? I purchased an SM-T978U (on Samsung website that is t-mobile S7+)
I expected it to not be carrier or network locked but it was locked to the t-mobile network.
Would love to flash an unlocked firmware but I can't find SM-T978U firmware, let alone U1 firmware...... I realize that flashing U1 firmware won't unlock the network but T-mobile support tells me the device can't possibly be truly carrier locked because the IMEI isn't even in their system. So I thought maybe the carrier lock is in their app tied to the system instead of the actual device??
Anyway has anyone found the firmware for these devices? Sammobile doesn't seem to list SM-T978 as a device
These devices don't have a dialer so entering the IMEI method mentioned above won't work unless there is a trick?
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
K3N422 said:
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
not sure y u tagged me lol.. i know hiw csc works.. in fact, in my last comment before this one you can see I clearly said just flashing firmware won't change the csc? seems like basically what you said but in a few words
K3N422 said:
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
Where is this U1 XAA firmware to download? Specifically for the SM-T978U?
RE: jmwfl2000 -I always untick the "Auto-Reboot" box when flashing new TWRP images to prevent stock recovery from being reapplied.After the first boot all should be well.
K3N422 said:
in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
I'm pretty stumped like OP. Where are you finding U1 XAA for Tab S7+? Doesn't seem to turn up anywhere. Would definitely appreciate it if you could provide a link. Thanks.
I tried resetting before flashing and unchecked the auto-reboot but mine still returns to Tmobile. I just want the call and text on other devices feature.
Edit: I go the feature to work without flashing a new firmware but I am still looking for U1 XAA for the tab if anyone found it.
jmwfl2000 said:
Purchased a sim unlocked SM-T978U (Verizon Tab S7+ 5G) and am trying to flash the unlocked or Tmobile stock firmware to it. I've gotten "passed" flashes everything when flashing all of the files from the corresponding stock firmwares, but everything it boots back into the Verizon firmware. Any suggestions as to what I'm doing wrong that would cause this? I've probably flashed this thing 20 times at this point.
Click to expand...
Click to collapse
I bought an unlocked Verizon Tab S7, probably same seller. Its brand new, stil has plastic on it. Are you wanting to unlock Tmobile 5G bands?

S6 Edge Baseband And Build number do not match

Hi Guys so i recently bought an s6 edge which turns out has had twrp installed onto it, im trying to get rid of this but i need the stock rom correct??
If so here's my issue, the phone is now unlocked, I believe it was locked to ee previously as a reset installs the my ee app bk on to the phone, and also lockout splash screen says in association with ee, So Do i need the btu version??, Even so when searching sammobile i get the following G925FXXS6ETI6 WHICH DOES MATCH THE BUILD NUMBER, However the baseband Code on my phone G925FXXU6ERF6, which of these numbers do i need for the correct rom?
The Below Is info from sammobile
United Kingdom (EE)
2020-12-17
7.0
G925FXXS6ETI6 (PDA, MATCHES PHONE)
G925FEVR6ETK1 (CSC, DOES NOT MATCH PHONE)
IM NOT EVEN SURE IF THE PHONE IS ROOTED, AN APP REPORTS IT IS NOT ROOTED CORRECTLY, THE PHONE HAS TWRP ON IT WHEN GOING TO RECOVERY OPTIONS
Correct me if I'm wrong, but since you've got twrp installed, you can create yourself a backup. I'm not sure if installing some random firmware from sammobile could be reverted using such a twrp backup but maybe it's worth a try?
It's been a while since the post has been posted, but any answer is better than no answers. You may let us know if you have already got rid of twrp
Andy259 said:
Hi Guys so i recently bought an s6 edge which turns out has had twrp installed onto it, im trying to get rid of this but i need the stock rom correct??
If so here's my issue, the phone is now unlocked, I believe it was locked to ee previously as a reset installs the my ee app bk on to the phone, and also lockout splash screen says in association with ee, So Do i need the btu version??, Even so when searching sammobile i get the following G925FXXS6ETI6 WHICH DOES MATCH THE BUILD NUMBER, However the baseband Code on my phone G925FXXU6ERF6, which of these numbers do i need for the correct rom?
The Below Is info from sammobile
United Kingdom (EE)
2020-12-17
7.0
G925FXXS6ETI6 (PDA, MATCHES PHONE)
G925FEVR6ETK1 (CSC, DOES NOT MATCH PHONE)
IM NOT EVEN SURE IF THE PHONE IS ROOTED, AN APP REPORTS IT IS NOT ROOTED CORRECTLY, THE PHONE HAS TWRP ON IT WHEN GOING TO RECOVERY OPTIONS
Click to expand...
Click to collapse
a UK 920 EE phone should be on
G920 FXXS 6ETI6 (PDA)
G920 FXEU 6ETJ1 (CSC)
G920 FXXU 6ERF6 (???)

Categories

Resources