[Q] Changing from carrier specific to international. What to expect? - Samsung Galaxy Alpha

I'm considering flashing the international firmware. I have three reasons for doing so:
Carrier bloatware
Carrier firmware update latency (not always the case but not wanting to take the risk)
Some users have confirmed that "international" improved the battery life & speed.
I have several questions before flashing:
My phone was carrier locked but I got the unlock code; will the code still work?
Will I get notified for updates for the international version instead of the current version (thinking the answer is "yes" but need to be sure)?
Do I need to take into consideration something in particular for flashing?
Other?

Related

[Q] Firmware crossgrade

Hi all.
I have one of the AT&T Atrix phones, and was wondering whether, when my local carrier (Telstra) bring out their own branded version, it will be possible to install the Telstra firmware over the AT&T one. Perhaps when they bring out the update to 2.3?
I know the bootloader will only allow signed firmware, but I'm wondering whether they also check whether you're trying to install firmware from a different carrier or not. If not, it could be a way to get both localised features as well as remove some of the AT&T restrictions.
Any thoughts?
For anyone interested, it turns out that this is possible to do (but may cause reception issues because their firmware will be for the international version of the Atrix, which has different radio capabilities).
Thanks for the info. I was wondering the same thing. Could you keep us informed if you hear anything else?

HTC, HTC Desire X ROMs, CID ... questions

Hello,
I'm quite new with android devices and have read several topics here, but still have some questions. So I do apologize if it's answered or explained already somewhere, but I haven't found it.
Let me first explain what my assumption was and what are now.
1. HTC kernel/update - So HTC is getting generic android from google and make and add their modifications.
- Maybe there are some difference in the ROMs and/or devises for different regions like Europe, Asia, America ... , but not sure if it's correct and why it is needed at all, unless it is something specific with network carriers
- I do not understand the reason to have a different ROM or OAU per network carrier unless that the update should be approved by the carrier /why needed/. If so, what about the countries and carriers not available on htcdev site, that means such operators and countries use generic regional like WWE Eastern Europe or EU, but who is approving them in that case
- currently there are quite big difference to updates and versions available for different regions and carrier operators
2. Is there any way to get stock/original ROMs
So till recently I believed there is a generic ROM and depending on your home network/operator/carrier you got OAU or not, but it turned out that is completely wrong. It seems the phone is preloaded with a specific ROM made for specific operator or more generic one like EU, and depending on those ROM you have particular update or not.
- still not sure what the reason for this is
3. What is the meaning of CID on particular ROM, isn't it just a simple configuration in a configuration file into ROM.
I thought if you have stock ROM with different CID inside than current one, you should be able to flash the phone with it and it should work. Possible issues should be only with network carrier , but all the rest should work, isn't that correct.
4. If you flash you phone would your IMEI and/or CID change or the CID is hw locked and not into ROM
5. Is there any way to change the CID
6. I've read a lot in the forum in regards to ROMs, but still not clear
- is there any really original stock ROMs
- why people having issues with stock ROM depending on their current CID, and the ROM is working with some and doesn't with others
- what is the problem with OAU after change of the ROM with stock one
7. Is it possible to make a image of my phones without rooting them
8. What's the problem to get the ROM from one phone and put it in another as both are original coming from HTC with devices
I do not want to root the device or put custom ROM for now, but interested in having original HTC ROM with different CID than the current one, and trying to understand the setup and how it is working and how can it be done.
I own two Desire X which happened to be with different ROMs and CIDs, one Orange CH, the other T-Mobile PL, so there are some difference, so I would prefer to have them both identical may be EU or Eastern Europe ROMs inside and have the corresponding OAU working .
appreciate you help.

Hardware agnostic?

i'm not sure if this is possible, but was wondering if there was a way to flash a certain firmware on our edge phones to make it carrier agnostic? I came from a Nexus 5 so we could flash different versions of the OS to either the international version or the US version, etc. Can we do that with these locked phones? Is it possible to say flash a Sprint phone with the ATT firmware? or is the hardware actually different in the phones?
There may be partition and bootloader variations especially with the ATT and Sprint versions so I wouldn't risk it. Roms however are a different story as long as you have a compatible kernel.

[Q] Help with updating to 5.0

I just got a new unlocked AT&T M8, switched over from iPhone. I'm going to be using it with T-Mobile, and I'm still struggling to learn how all this stuff works. So the phone is running on Android 4.4.4 currently, and I want to install a custom ROM on it, but I need Android 5.0. Since I have a T-Mobile sim card, I don't have any OTA updates. From what I understand, if I wanted to switch to a T-Mobile ROM, I'd have to pay $25 for Sunshine, which I'd rather not do. Would I also need to do so to get an international ROM? Also, from what I'm reading, my other option is to use the AT&T RUU from HTC's website to update to 5.0, and then install a custom ROM from there. Is this correct, would that remove my unlock, and are there instructions/recommended readings before I try anything? Thanks for any help.
grant523 said:
I just got a new unlocked AT&T M8, switched over from iPhone. I'm going to be using it with T-Mobile, and I'm still struggling to learn how all this stuff works. So the phone is running on Android 4.4.4 currently, and I want to install a custom ROM on it, but I need Android 5.0. Since I have a T-Mobile sim card, I don't have any OTA updates. From what I understand, if I wanted to switch to a T-Mobile ROM, I'd have to pay $25 for Sunshine, which I'd rather not do. Would I also need to do so to get an international ROM? Also, from what I'm reading, my other option is to use the AT&T RUU from HTC's website to update to 5.0, and then install a custom ROM from there. Is this correct, would that remove my unlock, and are there instructions/recommended readings before I try anything? Thanks for any help.
Click to expand...
Click to collapse
You probably want the T-Mob radio software, so you can enable the 3G and LTE bands used by T-Mob. Otherwise, you will find that the AT&T radio does not give you 3G and LTE in many locations.
In order to flash another carrier's radio, you need s-off, and there is no way around that. Then you need to change the carrier ID (CID) and model ID (MID) to that of T-Mob.
At that point, you may as well RUU to a stock factory T-Mobile software image (not just the radio) and that would be recommended, is it will get you a complete T-Mobile "baseline" phone as opposed to an AT&T ROM with T-Mob radio, etc.
After running the T-Mob RUU, your phone will be "fully converted" to the T-Mob version in terms of software. Others here have converted the AT&T version for use on T-Mob. So I'll try to find one of those threads instead of trying to explain it all again.
None of these mods will change your SIM unlock. That will remain unlocked.
---------- Post added at 11:06 AM ---------- Previous post was at 10:58 AM ----------
Here you go: http://forum.xda-developers.com/att-htc-one-m8/help/installing-tmobile-rom-att-branded-phone-t3069388
Another point: You can update to the latest AT&T Lollipop software by RUU. And you can flash custom Lollipop ROMs after that. But neither of these will enable the 3G and LTE bands used by T-Mob. So that is why I suggest "converting" the phone to T-Mob stock software instead.
Thanks for the response! Appreciate it. A few more questions, since I'm not sure I fully grasp the concept of radios.
If I first flash a T-Mobile ROM, and then install a custom ROM, is that any different from updating with a AT&T RUU and then installing a custom ROM? Will I still be missing the bands?
If yes, then should I just stay away from Custom ROMs all together? Is this a problem because I bought an AT&T phone?
Thanks again!
grant523 said:
Thanks for the response! Appreciate it. A few more questions, since I'm not sure I fully grasp the concept of radios.
If I first flash a T-Mobile ROM, and then install a custom ROM, is that any different from updating with a AT&T RUU and then installing a custom ROM? Will I still be missing the bands?
If yes, then should I just stay away from Custom ROMs all together? Is this a problem because I bought an AT&T phone?
Thanks again!
Click to expand...
Click to collapse
Yes it's different the AT&T ruu won't give you the T-Mobile bands. And you can install custom roms if you want but I would reccomend paying the $25 to s-off and fully converting to t-mobile and either stay on stock or flash a custom t-mobile rom
grant523 said:
A few more questions, since I'm not sure I fully grasp the concept of radios.
If I first flash a T-Mobile ROM, and then install a custom ROM, is that any different from updating with a AT&T RUU and then installing a custom ROM? Will I still be missing the bands?
Click to expand...
Click to collapse
I think your first phrase was intended to read "flash the T-Mob RUU, then install a custom ROM".
The radio is not contained in the ROM, and flashing a ROM doesn't affect the radio in any way.
The radio is contained in what many folks here called the "firmware package" or firmware.zip; and it can be installed by flashing the RUU.
Another thing that will help you understand, is that the phone has something like 36 (or more) partitions. The ROM is just one of those. The radio is a separate partition (as bootloader, recovery, and others have their own separate partitions as well). Flashing one partition, does not effect the others. The RUU is a complete software image that flashes all the partitions to factory stock for a certain carrier version.
You can also flash the radio or firmware.zip manually (without flashing the whole RUU). But my personal recommendation would be to baseline to a fully stock T-Mobile software profile, since you are on the T-Mob network, to make sure every partition plays well together (as opposed to mixing T-Mob and AT&T software components).
grant523 said:
If yes, then should I just stay away from Custom ROMs all together?
Click to expand...
Click to collapse
I wouldn't say that. Custom ROMs have their place. But a custom ROM will not open up the T-Mob bands. As mentioned, you can only do that by flashing the radio, which isn't affected by flashing the ROM.
After baselining to a T-Mob stock config as I've suggested, you can feel free to flash a custom recovery and flash custom ROMs if you like. But if would be for other reasons than the radio bands; such as performance, customization, debloating, etc..
grant523 said:
Is this a problem because I bought an AT&T phone?
Click to expand...
Click to collapse
Basically yes. If you want to be sure a phone works fully on a certain network "out of the box", you should buy the phone that is branded for that network. Otherwise, you should always thoroughly research a phone (not branded for your carrier) before trying to use it on your network.
Luckily for you, on this device the radio bands can be changed in software using the mods I've noted above. On past devices, the band support was set in hardware, meaning where was no way to change it in software. In that case, you would really have some buyer's remorse to deal with.
Ah OK thanks for the responses! I think I'm starting to understand. I did research how an At&t m8 would work with T-MOBILE but I didn't realize i would have to go throw this whole software process to make it work! Anyhow I appreciate the help and I'll buy a Sunshine license when I get a chance. Thanks again!
You are quite welcome.
Here is a thread with more info on changing from AT&T to T-Mob software: http://forum.xda-developers.com/att-htc-one-m8/help/installing-tmobile-rom-att-branded-phone-t3069388#post60606278
Good luck!

Flashing an unbranded firmware on a carrier-locked phone

So I was wondering if this is possible. My phone (running lollipop 5.1.1) is locked to a carrier but I was planing on flashing an unbranded 6.0.1 (from Italy). Marshmallow will eventually come to my country but I just can`t wait anymore. Will flashing this firmware brick anything ?? I am well aware that the phone will remain locked to my carrier, but is anything else going to be affected ? Anyone had a similar experience ? Your answers are really appreciated.:highfive:
Depends on the phone. Generally, if it is locked to a carrier then other firmwares will fail when trying to flash due to other differences such as the modem/baseband. There are exceptions, but pretty sure they are few and far between.
es0tericcha0s said:
Depends on the phone. Generally, if it is locked to a carrier then other firmwares will fail when trying to flash due to other differences such as the modem/baseband. There are exceptions, but pretty sure they are few and far between.
Click to expand...
Click to collapse
Thanks for your answer. It's galaxy a5 2016. Better not to touch anything. Don't want to mess is up within just 2 months after the purchase.

Categories

Resources