Related
I have a Canadian variant with a different model number but I want to install firmware from tmobile which basically has the same specs, but when I do Odin flash I get fail messages. The only firmware that works is for my specific model N910W8.
How can I flash other country firmware? Anyone know how? I did it with my S5 so I'm confused. Thanks
re: firmware
Brava27 said:
I have a Canadian variant with a different model number but I want to install firmware from tmobile which basically has the same specs, but when I do Odin flash I get fail messages. The only firmware that works is for my specific model N910W8.
How can I flash other country firmware? Anyone know how? I did it with my S5 so I'm confused. Thanks
Click to expand...
Click to collapse
It's not a question of another country's firmware but instead it's just a fact that
you should not and cannot odin flash a different model's firmware into your
phone no matter how similar the two models might be.
I cannot odin flash firmware from sammobile designed
for N910W8 into my N910T model either.
You are lucky that your odin flashing of N910T firmware simply failed,
it could have been a disaster since it could have easily bricked your phone.
Remember there is a BIG difference between firmware and roms...
They are NOT the same thing...
You will be able to flash some zip file roms which are designed for the N910T
successfully using twrp recovery but before you do I would strongly suggest to
do a lot of research before flashing anything so you don't wind up with a shiny
brick.
Good luck!
Misterjunky said:
It's not a question of another country's firmware but instead it's just a fact that
you should not and cannot odin flash a different model's firmware into your
phone no matter how similar the two models might be.
I cannot odin flash firmware from sammobile designed
for N910W8 into my N910T model either.
You are lucky that your odin flashing of N910T firmware simply failed,
it could have been a disaster since it could have easily bricked your phone.
Remember there is a BIG difference between firmware and roms...
They are NOT the same thing...
You will be able to flash some zip file roms which are designed for the N910T
successfully using twrp recovery but before you do I would strongly suggest to
do a lot of research before flashing anything so you don't wind up with a shiny
brick.
Good luck!
Click to expand...
Click to collapse
Appreciate your time for the answer! Thanks
Probably against my better judgement, I've bought a 'new' S4 active off of Ebay here in the UK...it turns out its an unlocked AT&T device. While the phone works, it has AT&T branding all over it, and has an AT&T firmware updater rather than the stock android one, which is stuck on 4.3
Is it possible to flash this device with standard UK 4.4.2 firmware? I've attached a screenshot from the device showing what it's running. CSC information is:
Original CSC: XSG
Firmware CSC: ATT
Active CSC: XSG/ATT
CSC Country UAE
CSC Country ISO : AE
Using Phone info it shows:
Baseband I537UCUBML2...but in standard phone settings Baseband I9295XXDMK1??
PDA: I9295UCUBML2 / I537UCUBML2
I think stock UK firmware is BTU CSC, so I've downloaded that from SAMMOBILE.COM, but when I try to flash that with Odin, it just give me a fail with "Complete(Write) operation failed". I've tried different ports, cables and making sure no Kies processes are running (as I've read these can affect it), but still fail.....So my question is, is what I'm trying to do even possible....it is possible to turn an unlocked AT&T device into a stock UK device? If it is maybe I just have to keep trying different PC's and ports and cables till I strike lucky!
Many thanks for any help
Vince
vincexda said:
Probably against my better judgement, I've bought a 'new' S4 active off of Ebay here in the UK...it turns out its an unlocked AT&T device. While the phone works, it has AT&T branding all over it, and has an AT&T firmware updater rather than the stock android one, which is stuck on 4.3
Is it possible to flash this device with standard UK 4.4.2 firmware? I've attached a screenshot from the device showing what it's running. CSC information is:
Original CSC: XSG
Firmware CSC: ATT
Active CSC: XSG/ATT
CSC Country UAE
CSC Country ISO : AE
Using Phone info it shows:
Baseband I537UCUBML2...but in standard phone settings Baseband I9295XXDMK1??
PDA: I9295UCUBML2 / I537UCUBML2
I think stock UK firmware is BTU CSC, so I've downloaded that from SAMMOBILE.COM, but when I try to flash that with Odin, it just give me a fail with "Complete(Write) operation failed". I've tried different ports, cables and making sure no Kies processes are running (as I've read these can affect it), but still fail.....So my question is, is what I'm trying to do even possible....it is possible to turn an unlocked AT&T device into a stock UK device? If it is maybe I just have to keep trying different PC's and ports and cables till I strike lucky!
Many thanks for any help
Vince
Click to expand...
Click to collapse
I have bad news for you, currently it is impossible. About the only thing you can do is flash i537 firmware and then use UK modems, since it seems like that is what was already done. Sorry, you bought a phone with a locked bootloader and there's nothing that can be done until somebody figures out how to unlock the bootloader on Samsung phones.
Thanks for the reply....I had a bad feeling this was going to be the response, at least now I don't have to waste any more evenings trying to do this, that's the risk of ebay I guess!! Not sure if I'm brave or experienced enough to know how to get hold of the latest 4.4.2 AT&T firmware, flash that, and THEN install UK modems without risking a bricked device!
vincexda said:
Thanks for the reply....I had a bad feeling this was going to be the response, at least now I don't have to waste any more evenings trying to do this, that's the risk of ebay I guess!! Not sure if I'm brave or experienced enough to know how to get hold of the latest 4.4.2 AT&T firmware, flash that, and THEN install UK modems without risking a bricked device!
Click to expand...
Click to collapse
I try to make people's lives easy, check out the i537 Firmware Guide. At some point in the future I'm going to put together a post on how to flash modems so you can wait for that if you want, but it is really easy to flash modems with Odin and there is pretty much no risk to bricking, the only risk you'll run in to is that your radios won't work until you properly flash the modem. Good luck.
That looks like a great source of information thanks....so it should be possible to install the latest 4.4.2 AT&T firmware, then re-install the UK modems ....I wasn't what the risk of flashing modems was, but it seems like you just use Odin again with the correct file. So as long as I can get hold of those I should be OK.
Many thanks again for the assist.
I have an i9295 that I'm using on T-Mobile's network here in the US. I've been doing a little research to figure out if it's possible to get LTE on the i9295. From what I've been able to gather I need the 1700 band in order to get an LTE connection from T-Mobile, but apparently the i9295 lacks that capability while the i537 has that capability. From what I understand the i9295 and i537 are identical with regards to the hardware, so it seems like it should be possible with the right software.
My question is: is it possibly to flash an i537 modem to the i9295? If so are there any caveats, will I end up bricking my phone? Has anybody attempted this? Is this not possible due to the different bootloaders?
Do not flash a modem on a i9295 for a i537, you might brick your phone
MrMikeTyson said:
Do not flash a modem on a i9295 for a i537, you might brick your phone
Click to expand...
Click to collapse
This is why I'm asking, I need to know for sure whether or not I'm going to brick it before I try.
We learned that jflte modem didn't work on jactivelte here http://forum.xda-developers.com/showthread.php?p=55753476
Didn't hear anything about bricking after spegelius tested that.
But that is only modem.bin handling GSM traffic.
Then you have the relationship between bootloader to the LTE modem/network certificate non-hlos.bin that need to match up. I9295 (jactivelte) can accept flashing of different versions of bootloader and non-hlos.bin. Unmatched versions have bad impact on audio and WiFi.
http://forum.xda-developers.com/showthread.php?p=57332718
It is more difficult to do that on i537 as I understand because of the locked bootloader.
Perhaps there is some common factors in the kernel or RIL.
ThumbsUp button under every post is free to use in case you're in the mood to show appreciation.
O-T said:
We learned that jflte modem didn't work on jactivelte here http://forum.xda-developers.com/showthread.php?p=55753476
Didn't hear anything about bricking after spegelius tested that.
But that is only modem.bin handling GSM traffic.
Then you have the relationship between bootloader to the LTE modem/network certificate non-hlos.bin that need to match up. I9295 (jactivelte) can accept flashing of different versions of bootloader and non-hlos.bin. Unmatched versions have bad impact on audio and WiFi.
http://forum.xda-developers.com/showthread.php?p=57332718
It is more difficult to do that on i537 as I understand because of the locked bootloader.
Perhaps there is some common factors in the kernel or RIL.
ThumbsUp button under every post is free to use in case you're in the mood to show appreciation.
Click to expand...
Click to collapse
I understand that it would be difficult to flash a modem, but I'm guessing I should be able to extract modems from the i537 and flash them to the i9295. I understand that I need to make sure the non-hlos matches my bootloader, but I shouldn't brick my phone when I try if I understand everything you've written. I don't care if it's a soft brick, I just want to make sure I don't hard brick.
Hi I'm trying to flash the T-Mobile firmware from sammobile.com, but whenever I try, I get an error at 32% when it says Installing System Update. I attempted to flash CSC,AP,BL, and CP with it saying PASS in Odin. I really need the T-Mobile firmware and am wondering if it is possible to do? I determined that I cant install CSC files and get the error when I try. Any Solutions?
SM-G950U
Odin 3.12.3
T-Mobile Firmware:
PDA: G950USQU1AQD9
CSC: G950UOYN1AQD9
I'm having the same problem with an ATT phone flash with the US "U" unlocked version firmware. When I don't flash the csc it will start up only with the USB plug in but shut down after the beginning startup
Search for a "modified Odin". It was what I used to be able to flash unlocked firmware on a 7 and 7 edge a few months ago. The "normal" Odin wouldn't let me do it, but the modified one did. Though you may need to wait until it's been updated....I haven't checked it in awhile.
Still no solution to avoid the error to 32%?
Try this Odin. This is the one I used to flash the Canadian firmware on mine.
I managed with odin version 3.12.5! But only with BL AP and CP!
When I add CSC I get the error at 32%!
So a priori everything works, I no longer have the Verizon overlay (nor the logo at startup) more by cons I have duplicates in the settings menu ...
What is the CSC file?
bsharp8 said:
Try this Odin. This is the one I used to flash the Canadian firmware on mine.
Click to expand...
Click to collapse
The Canadian firmware you got it or? On sammobile I find it not:
https://www.sammobile.com/firmwares/galaxy-s8/SM-G950U/
The Canadian firmware is stock or operator?
I would have access to all the bands?
Its the firmware with the "w" at the end. Please read this thread for all the information on doing this and make sure you want to do it.
https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473
bsharp8 said:
Its the firmware with the "w" at the end. Please read this thread for all the information on doing this and make sure you want to do it.
https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473
Click to expand...
Click to collapse
so to do this we actually have to go to the canadian firmware first, do the csc change then flash the Tmo firmware? You can't just flash the Tmo Firmware via the modded Odin? Just to save confusion.
I would imagine it's worth it just to get the proper network options, VOLTE, WiFi calling and such.
How To Flash To T-Mobile
dbpaddler said:
so to do this we actually have to go to the canadian firmware first, do the csc change then flash the Tmo firmware? You can't just flash the Tmo Firmware via the modded Odin? Just to save confusion.
I would imagine it's worth it just to get the proper network options, VOLTE, WiFi calling and such.
Click to expand...
Click to collapse
This is the exact thread that I used. Follow the steps and you can skip engboot. If you flash the full Canadian firmware, its impossible to reverse. So, only flash whatever is in the steps. I successfully went from Verizon To T-Mobile and then back to Verizon. https://forum.xda-developers.com/galaxy-s8/how-to/switch-to-carrier-firmware-100-t3609487
This tread also helps, who wants to flash their phones: https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
For those who aren't already aware, G991U is the model number of all of the US carrier versions of the S21. The G991U1 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=322084
U1 firmware: https://www.androidfilehost.com/?w=files&flid=322085
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)
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
Thanks for the firmware links!
Odin blocks flashing from U to U1 or U1 to U. To successfully flash: Use the patched/modded odin found here.
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
realbbb
Sinker Slime
Anyone from T-Mobile move to u1? If so better or worse. Not sure if I should make the move. Thanks
Is the Verizon userdata available? I have an ATT version and I want to switch to Verizon.
Thanks.
N0v1c3 said:
Is the Verizon userdata available? I have an ATT version and I want to switch to Verizon.
Thanks.
Click to expand...
Click to collapse
U firmware is available via the various firmware download tools like SamFirm and Frija
Hey guys, I'm curious if anybody could help me fix an issue I'm having with flashing. I'm trying to flash from the U variant to the U1 but it seems to be csc locked to TMB. I've tried multiple firmwares, pulling the sim out before flashing and even flashing back and forth from U to U1 I can't seem to get the carrier update pop-up at all. I'm kinda at a loss and would appreciate any help you guys could give me
braxf said:
Hey guys, I'm curious if anybody could help me fix an issue I'm having with flashing. I'm trying to flash from the U variant to the U1 but it seems to be csc locked to TMB. I've tried multiple firmwares, pulling the sim out before flashing and even flashing back and forth from U to U1 I can't seem to get the carrier update pop-up at all. I'm kinda at a loss and would appreciate any help you guys could give me
Click to expand...
Click to collapse
Are you saying the service provider codes stay as TMB/TMB/TMB, even after you flash U1?
Yes the csc is locked to TMB for some reason. I did the full csc non home flash several times with no luck
braxf said:
Yes the csc is locked to TMB for some reason. I did the full csc non home flash several times with no luck
Click to expand...
Click to collapse
S21 Ultra users are reporting the same thing. Not sure what's going on with T-Mo this time
Yes I saw the thread. Do you think a repartition could possibly work? It's much more in depth but it would be a completely clean install
braxf said:
Yes I saw the thread. Do you think a repartition could possibly work? It's much more in depth but it would be a completely clean install
Click to expand...
Click to collapse
If you know how to repartition it, go for it
I don't, I read that you need a pit code. How would you go about getting that?
braxf said:
I don't, I read that you need a pit code. How would you go about getting that?
Click to expand...
Click to collapse
If you mean a PIT file, that's already included in the CSC file. So that is flashed, if you flash that file
So it's relatively the same concept but you use the csc file in the pit section?
braxf said:
So it's relatively the same concept but you use the csc file in the pit section?
Click to expand...
Click to collapse
Huh? No. The only thing that can go in the pit section is the pit file
Oh I misunderstood, you're saying when you flash the csc it automatically flashes that pit file?
braxf said:
Oh I misunderstood, you're saying when you flash the csc it automatically flashes that pit file?
Click to expand...
Click to collapse
Yep
Update: I'm completely lost. I downloaded the Canadian firmware which gave me the xac csc then I flashed back to U1 which also updated to Xaa. But I still showed only t-mobile n41 and 71 bands so I flashed back to U with Verizon bloatware and now I have a Verizon U firmware with xaa csc and still only showing t-mobile bands
braxf said:
Update: I'm completely lost. I downloaded the Canadian firmware which gave me the xac csc then I flashed back to U1 which also updated to Xaa. But I still showed only t-mobile n41 and 71 bands so I flashed back to U with Verizon bloatware and now I have a Verizon U firmware with xaa csc and still only showing t-mobile bands
Click to expand...
Click to collapse
I don't guarantee that any particular bands will work on any particular firmware. Also, carriers don't use every single band in every single area