Can we flash other country firmware on my wave 1? - Bada Software Development

I have Wave 1, S8500. I wonder is it safe to flash other country to my phone? Mine is Malaysia, with Bada 1.0.
I want to upgrade to Bada 1.2 using this S8500DXKF1/S8500OLBKD1,Singapore(Singtel) which can get from here: http://www.sammobile.com/firmware/?page=3&t=1&o=2&m=GT-S8500&r=2
And flash it offline using this guide: http://www.tsar3000.com/Joomla/inde...s8500-wave-firmware&catid=57:how-to&Itemid=84
I hope it's a correct way.
The files from here: http://www.tsar3000.com/Joomla/inde...15:samsung-flashes&catid=55:samsung&Itemid=82
Seem very confusing. Too many to choose and don't know if it cross country compatible or not.

I'd say yes simply because I'm using non-Philippine firmware on my phone
Firmware's are usually varied by region. I believe this is mainly because of the languages included. For special releases such as those from carriers, it may cause your device to lock on to those carriers. I'm not sure, I've never tried.
Most importantly, since this device is quad-band, you should have no issues with the radio firmware.

If anyone could give me link to XME firmware?

Related

[Q] Why does samsung update their firmware based on regions?

There are many samsung firmware builds, just for i9505 and i9500 itself there are many different firmware variations.
From what I understand, different regions uses different modems am I right? If not, then why do Samsung update their firmware based on different regions?
When Android 4.3 was released, it was released as per region and to Russia first. Why cant they just send out one uniform update OTA to all devices of that model? If its because of the modems, then why dont other manufacturers like HTC do the same? They are able to push out one HTC update for all international HTC phones...
din89pm said:
There are many samsung firmware builds, just for i9505 and i9500 itself there are many different firmware variations.
From what I understand, different regions uses different modems am I right? If not, then why do Samsung update their firmware based on different regions?
When Android 4.3 was released, it was released as per region and to Russia first. Why cant they just send out one uniform update OTA to all devices of that model? If its because of the modems, then why dont other manufacturers like HTC do the same? They are able to push out one HTC update for all international HTC phones...
Click to expand...
Click to collapse
it s not always because of bandwidth traffics
sometimes they release firmware for test if someone find bug and then solve it for another region (and also with minor update for first regions)
htc released update for htc one world-wide But how u compare samsung with htc
S4 was one of the best sell in history of smartphone (always samsung device do this) so thr s more s4 users than htc one
also it happened for some device for sony xperia
SO be patient
However u can flash stocks roms
download flashable zip of ROM from another region and flash it via Odin
completely stock and without warranty void...
:good:
x102x96x said:
it s not always because of bandwidth traffics
sometimes they release firmware for test if someone find bug and then solve it for another region (and also with minor update for first regions)
htc released update for htc one world-wide But how u compare samsung with htc
S4 was one of the best sell in history of smartphone (always samsung device do this) so thr s more s4 users than htc one
also it happened for some device for sony xperia
SO be patient
However u can flash stocks roms
download flashable zip of ROM from another region and flash it via Odin
completely stock and without warranty void...
:good:
Click to expand...
Click to collapse
Actually the purpose of this post is to gain some knowledge on how Samsung update goes on... I am very patient I am not rushing to the point I need to flash a custom ROM. So you are saying that each region has their own Samsung tech guy that will work on the initial release to fix bugs before passing to another region?
There are not just more variants of firmware in s4, but also the same for any samsung phone. Does anyone else have their opinion on this matter as well? I would like to get feedback on what people think behind samsung's update procedure.
I'm also interested in having an answer on the subject. If I can flash a firmware from another region on my phone, what's the purpose of having several firmwares...Besides some tweaks apparently.
Wouldn't it be more interesting if all the developers from Samsung focused on the same firmware to eliminate the bugs more rapidly for example? I don't really see the link between several firmwares and the number of users. Ok, the S4 sold by millions, and?
Thanks.
What difference does it make.As long as your getting your updates, why would you care about any other region.
Are you doing a Samsung case study or preparing a lawsuit; otherwise email CEO of Samsung.
I can post his tag if needed..lol
Sent from my GT-I9505 using Tapatalk 2
The time discrepancy its coming from carriers. Most of them wants to integrate their own bloatwares in their phones. And some are doing faster than others. That's why there's so many region specific firmwares when its about Touchwiz. You won't see region specific firmwares for Google Play Edition.
Sent from my GT-I9505 using xda app-developers app
vladimir_carlan said:
The time discrepancy its coming from carriers. Most of them wants to integrate their own bloatwares in their phones. And some are doing faster than others. That's why there's so many region specific firmwares when its about Touchwiz. You won't see region specific firmwares for Google Play Edition.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Indeed, seems the most obvious reason... I just wanted to be sure that besides the bloatware, the Android version underneath was the same.
Thanks for your intel!
mr.death7 said:
Indeed, seems the most obvious reason... I just wanted to be sure that besides the bloatware, the Android version underneath was the same.
Thanks for your intel!
Click to expand...
Click to collapse
So just to be absolutely clear about this...
When I cant download the Dutch firmware version for my sm-t110, I ccould just download the australian one instead whitout bricking my device?
This is important thanks

[Q] Some versions dont get updates?

Hi all,
I've noticed something unacceptable and as a newbie I wanted your insight.
I hold a Samsung galaxy s4 I9500 that seems to come from Bangladesh or Vietnam, I;m not pretty sure. Anyway, I noticed that many many devices from these Asian regions do not get any updates since 2013 ! They were lasted updated to 4.3 Jelly bean and that is.
How do you explain the fact that the same devices take lollilop and others stay on Jelly bean?
How can I upgrade at least to Kitkat?
(I checked the Kies application and it says that I have the last updated firmware)
Thanks a lot!
Sammobile has 5.0.1 for Bangladesh and 4.4.2 for Vietnam. As to the discrepancy regarding firmware releases, carriers are the ones to decide whether to upgrade or not. So either you'll get it or not. Bangladesh chose to upgrade while Vietnam is holding back.
Yes, but there are other models which did not take any update.
For example this code: I9500XXUEMJ9 exists in 7 countries (Israel,Bangladesh,India etc.) and since 2013 hasn't done any updates. Still the firmware is 4.3.
Should the owners of these models wait for even more?
If their carriers choose not to provide an update, then yes, the owners of those devices will have to wait. Case in point: Straight Talk. Here in the US Straight Talk offers a S4 locked to Android 4.2.2 and refuses to provide updates for it. Worse for Straight Talk S4 owners, unlike the I9500 owners, they can't simply flash a ROM from a different region because their S4 is an exclusive model specifically made for Straight Talk. So they have to wait for an update that will never come. At least the tech-savvy I9500 owners have avenues available to them to get a more up-to-date stock ROM. Straight Talk S4 owners have to use custom ROMs, and risk losing their service doing so, as Straight Talk prohibits both rooting and custom ROMs in its terms and conditions.
First of all thanks for your info.
I've got two problems facing me right now.
First of all I can't figure out which specific country the phone comes from. This code appears in many countries.
Secondly I don't know which flash ROM I should use with this program called Odin. Should I choose randomly a version? Should I upgrade to lollilop or it is a must I pass from Kitkat first?
I value your help.
Please post the following information:
1. Model Number
2. Android Version, found by going to Settings > More > About device.
3. Firmware Version (AP, CP, CSC), found by dialing *#1234# in the dialer or by installing Phone Info from the Play Store and running it.
4. Service Provider
5. Country
6. Is the phone rooted? (Yes/No)
7. Is a custom ROM installed? (Yes/No, and the name of the ROM)
Some of this may seem redundant, but putting it all in one post makes it easier to help you.
1. GT-I9500
2. 4.3
3. Original csc code: TGY/TMB
Firmwares csc code: TMB
Csc country: Hong kong
country of origin: China
csc version: I9500XXUEMJ9
4. I dont get this
5. Country see above
6. No rooted
7. No
Number 4 is asking whom you use as a carrier. Also, your AP, CP, and CSC should have been posted as you had seen it on screen rather than "interpreting" it. Nevertheless, based upon the info you provided, the correct ROM for your device is here. Flash this ROM through Odin and you should be good to go.

[Q] Carrier Specific ROMs

Hey Guys!
I have a question regarding stock roms. I've been looking at SamMobile for an official release of Lollipop here in Philippines, the only download I can see is for a local carrier Globe. Will it cause problems if I flash this on my international N9005?
I also want to ask the same question for an S4 I9505, but it's the other way around; the phone is from Globe, network locked, and I am thinking of flashing an international version ROM. Will this cause problems? I know this isn't the right forum but just in case someone would like to answer.
Thank you!
hehsusss said:
Hey Guys!
I have a question regarding stock roms. I've been looking at SamMobile for an official release of Lollipop here in Philippines, the only download I can see is for a local carrier Globe. Will it cause problems if I flash this on my international N9005?
I also want to ask the same question for an S4 I9505, but it's the other way around; the phone is from Globe, network locked, and I am thinking of flashing an international version ROM. Will this cause problems? I know this isn't the right forum but just in case someone would like to answer.
Thank you!
Click to expand...
Click to collapse
1. Yes, you will have problems with the radios. It's not importat where you live that what CSC have your device. Install this APP and look for your CSC. Go to Sammobile.com, look for your csc, download and flash the latest stock rom for your device via ODIN. (Pic attached)
2. Regarding GT-i9505: Yes, it will cause lose of signal. The best you can do is unlock it by IMEI.
Joku1981 said:
1. Yes, you will have problems with the radios. It's not importat where you live that what CSC have your device. Install this APP and look for your CSC. Go to Sammobile.com, look for your csc, download and flash the latest stock rom for your device via ODIN. (Pic attached)
2. Regarding GT-i9505: Yes, it will cause lose of signal. The best you can do is unlock it by IMEI.
Click to expand...
Click to collapse
I flashed a rom from Brazil. Everything works great it's just that the bloatware included is annoying. I figured the best option to flasha ROM from my country but the only one with a Lollipop ROM is carrier specific.
Samsung allows users to use roms from their own region interchangeably. In most cases, even globally.
I've never encountered issues with radio or signal loss when flashing different providers and countries in my own region, and I've had thousands of people flash and use all sort of different EU firmwares. (you can find the region on the sticker on the box.)
(US users have different devices with real carrier locks, so those are excluded.)
Sent From My Samsung Galaxy Note 3 N9005 Using Tapatalk

G988U and G988U1 Firmware Links and Flashing Discussion Here

For those who aren't already aware, G988U is the model number of all of the US carrier versions of the S20 Ultra. The G988U1 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. 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 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 SamFirm/Frija, so that's where my files come from. However, I don't have unlimited bandwidth on the site, and it's also 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 SamFirm/Frija.
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, 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=305574
U1 firmware: https://www.androidfilehost.com/?w=files&flid=305575
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 S20, 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
- 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 SamFirm/Frija:
ATT = AT&T (not available via SamFirm/Frija)
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
USC = US Cellular
VZW = Verizon (available via SamFirm/Frija, 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
Pre-release notes:
1. I do not have one of these and do not plan to acquire one, so I have no idea if anything can actually be flashed at this moment - I'm just providing the firmware. Like all other models, I'm assuming patched Odin is needed for this, but it wouldn't surprise me if a new version is needed for this specific device. There's only one way to know though, so as soon as someone gets their hands on one and can try this, please let us know.
2. I don't know if using the HOME CSC will actually save data. I don't get access to that file straight from the source - I have to decompile the regular CSC, remove the parts that initiate the factory reset, and then re-compile it. Based on the S10 and Note 10, I've done what I think will avoid a factory reset. But the S20 has some new partitions, so we won't know for sure until someone tests it. So if you're willing to be that guinea pig, you're responsible for taking proper steps to avoid an FRP lock, make sure your data is backed up, etc
I will be the first to try. I ordered the unlocked. I will flash the TMO firmware. I have it downloaded already
Sent from my SM-G975U1 using Tapatalk
Thanks for posting these! I ordered the Verizon model but am planning on flashing the unlocked firmware once I get it in hand.
Sent from my SM-N975U using Tapatalk
at this point can we only flash the Userdata for the carrier without the actual firmware?
daraj said:
at this point can we only flash the Userdata for the carrier without the actual firmware?
Click to expand...
Click to collapse
I guess you could flash USERDATA by itself. There's really no point to doing that though
No the firmware is there. Its a separate file zipped up
Sent from my SM-G975U1 using Tapatalk
Is it possible to flash Canada firmware to the us variant or is that not advised ?
roadcabe14 said:
Is it possible to flash Canada firmware to the us variant or is that not advised ?
Click to expand...
Click to collapse
Canadian firmware has been able to be flashed to US Samsung flagship phones ever since the S7. So yes, I would assume that that trend will continue with the S20
Samfirm and Frija have TBN firmware available...I assume based on the naming that it's newer than the ones you have uploaded? I also saw on Sammobile that Verizon has already released a newer firmware which is odd considering they haven't even shipped them yet...lol
tlbland0426 said:
Samfirm and Frija have TBN firmware available...I assume based on the naming that it's newer than the ones you have uploaded? I also saw on Sammobile that Verizon has already released a newer firmware which is odd considering they haven't even shipped them yet...lol
Click to expand...
Click to collapse
1. SamFirm and Frija will always only give you whatever the newest/latest version is. So if it's not the same version that I have uploaded, then yes, it's a newer one.
2. Not odd at all. Most devices get an OTA before release to fix bugs, add features, etc. There was an OTA that came out shortly after I got access to the files, so TBN would be the 3rd release now for this model
3. Looks like firmware has now hit SamFirm and Frija for all S20 models, for anyone who wants to download it themselves
Tried flashing multiple times ATT FW with Odin 3.14.1. Odin reports no errors but it's definitely not taking. SW info still reports XAA and I have no "carrier bloat".
Its not as simple as that. There is a trick when going from unlocked to carrier fw. Look on s10 forums, the procedure is there I believe
Sent from my SM-G975U1 using Tapatalk
johnwayne27 said:
Its not as simple as that. There is a trick when going from unlocked to carrier fw. Look on s10 forums, the procedure is there I believe
Sent from my SM-G975U1 using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s10/help/samsung-s10-unlocked-phone-att-firmware-t3912973
this thread? pretty much the same process. if you don't mind linking me i'm working on trying to get this done proper and won't sleep until then lol
Ive been there done that. Timing is everything. Gotta reset dorectly after boot and flash and when i see carrier update prompt-you know its right. Trial and error.
Sent from my SM-G975U1 using Tapatalk
johnwayne27 said:
Ive been there done that. Timing is everything. Gotta reset dorectly after boot and flash and when i see carrier update prompt-you know its right. Trial and error.
Sent from my SM-G975U1 using Tapatalk
Click to expand...
Click to collapse
TY. Tried again this morning and got it. I assumed I did not need to flash U1 first since my phone was already unlocked. Doing that made all the difference. New to all of this but glad it's finally done!
johnwayne27 said:
Its not as simple as that. There is a trick when going from unlocked to carrier fw. Look on s10 forums, the procedure is there I believe
Sent from my SM-G975U1 using Tapatalk
Click to expand...
Click to collapse
Procedure is also given right here, in the OP
Will flashing the att firmware to an unlocked phone enable wifi calling?
Murph2k said:
Will flashing the att firmware to an unlocked phone enable wifi calling?
Click to expand...
Click to collapse
My other threads are chock full of discussions of this exact thing. Bottom line is, we don't know until someone tries it
I'm trying to download the Tmobile from the SamFirm tool for my S20 ultra SM-G988U1
I put in the model number above and TMB in the region.
But I also noticed that if I enter any other region, it's the same filename and size as well. Just want to make sure about downloading the right file.
I re-read the OP, and saw some youtube videos. It's my assumption now that I need to put SM-G988U in the MODEL and keep TMB as the region to download the correct firmware. Am I correct in assuming this is the correct way to go?
The reason I want to do this is because I want to have Tmobiles advance messaging feature back

G986U and G986U1 Firmware Links and Flashing Discussion Here

For those who aren't already aware, G986U is the model number of all of the US carrier versions of the S20+. The G986U1 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. 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 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 SamFirm/Frija, so that's where my files come from. However, I don't have unlimited bandwidth on the site, and it's also 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 SamFirm/Frija.
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=305579
U1 firmware: https://www.androidfilehost.com/?w=files&flid=305580
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 S20, 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
- 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 SamFirm/Frija:
AIO = Cricket (not available via SamFirm/Frija)
ATT = AT&T (not available via SamFirm/Frija)
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 SamFirm/Frija, 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
Notes:
1. I do not have one of these and do not plan to acquire one, so I have no idea if anything can actually be flashed at this moment - I'm just providing the firmware. Like all other models, I'm assuming patched Odin is needed for this, but it wouldn't surprise me if a new version is needed for this specific device. There's only one way to know though, so as soon as someone gets their hands on one and can try this, please let us know
It's been confirmed that Odin 3.14.1 Patched is needed for flashing S20s - https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
H/T @clabern
2. I don't know if using the HOME CSC will actually save data. I don't get access to that file straight from the source - I have to decompile the regular CSC, remove the parts that initiate the factory reset, and then re-compile it. Based on the S10 and Note 10, I've done what I think will avoid a factory reset. But the S20 has some new partitions, so we won't know for sure until someone tests it. So if you're willing to be that guinea pig, you're responsible for taking proper steps to avoid an FRP lock, make sure your data is backed up, etc
What are TAW and TAY
Vats12 said:
What are TAW and TAY
Click to expand...
Click to collapse
That's explained in the OP
Odin fail
Couldn't get odin to work, probably needs an update, tried 3.14.4 and custom. either freezes at setupconnection, or says write failed.
iBowToAndroid said:
That's explained in the OP
Click to expand...
Click to collapse
I want to know who is TAW/TAY? like SPR is Sprint, VZW is Verizon...
I didn't find this information on the internet or maybe I am not searching with the right keyword.
luminaire117 said:
Couldn't get odin to work, probably needs an update, tried 3.14.4 and custom. either freezes at setupconnection, or says write failed.
Click to expand...
Click to collapse
Freezing at SetupConnection can be a USB issue. Try again with a different port, different cable, or different PC
Vats12 said:
I want to know who is TAW/TAY? like SPR is Sprint, VZW is Verizon...
I didn't find this information on the internet or maybe I am not searching with the right keyword.
Click to expand...
Click to collapse
TAW/TAY are not carrier CSC codes. As I already stated, the explanation for what TAW/TAY is is given in the OP
Just wanted to let folks know I had to use this patched Odin (3.14.1_3B) in order to flash unlocked (U1) firmware on my Verizon S20+. Pulled the most recent firmware from Sammobile and flashed it successfully.
clabern said:
Just wanted to let folks know I had to use this patched Odin (3.14.1_3B) in order to flash unlocked (U1) firmware on my Verizon S20+. Pulled the most recent firmware from Sammobile and flashed it successfully.
Click to expand...
Click to collapse
Sweet, good to know - thanks!
maybe i am misreading the OP but can the stock firmware be used to go from t-mobile to stock?
danon.brown said:
maybe i am misreading the OP but can the stock firmware be used to go from t-mobile to stock?
Click to expand...
Click to collapse
Yes, if by "stock" you mean "factory unlocked" aka U1.
clabern said:
Just wanted to let folks know I had to use this patched Odin (3.14.1_3B) in order to flash unlocked (U1) firmware on my Verizon S20+. Pulled the most recent firmware from Sammobile and flashed it successfully.
Click to expand...
Click to collapse
It has been a while since i looked into flashing. I want to do the same (have an s20+ verizon) I want factory unlocked software . On sam mobile , everything looks like it has a carrier attached even looking up U1 model. Which did you pick?
iHTC said:
It has been a while since i looked into flashing. I want to do the same (have an s20+ verizon) I want factory unlocked software . On sam mobile , everything looks like it has a carrier attached even looking up U1 model. Which did you pick?
Click to expand...
Click to collapse
You want product code "XAA". So it should be this one.
clabern said:
You want product code "XAA". So it should be this one.
Click to expand...
Click to collapse
that's what I figured. Any difference going to sam mobile vs the one in the original post here, I assume both are current this early on in the game. Thanks for your help!
iHTC said:
that's what I figured. Any difference going to sam mobile vs the one in the original post here, I assume both are current this early on in the game. Thanks for your help!
Click to expand...
Click to collapse
The one from Sammobile is more current, there was an update soon after launch. You can compare the build number to that of the software on your phone.
Anybody else flash the VZW userdata and still end up with Tmo branding, bloat, and boot animation?
finshan said:
Anybody else flash the VZW userdata and still end up with Tmo branding, bloat, and boot animation?
Click to expand...
Click to collapse
If you didn't follow the steps in the OP correctly, then yes, you can very possibly end up with the same bloat as before
Ok. So I guess the one place I'm struggling, from a not implemented, but understanding standpoint is that the instructions show how to go to carrier branded versions, but if I just want the U1 firmware, do I need to follow through with the other portion, the second flashing that happens, or can I just run the unbranded one?
halcyon77 said:
Ok. So I guess the one place I'm struggling, from a not implemented, but understanding standpoint is that the instructions show how to go to carrier branded versions, but if I just want the U1 firmware, do I need to follow through with the other portion, the second flashing that happens, or can I just run the unbranded one?
Click to expand...
Click to collapse
Just flash U1 - nothing else
Thank you for this. I was able to flash from Tmobile to the U1 firmware with a virtual machine.

Categories

Resources