OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Yeah, just don't flash any odin files.
aooga said:
Yeah, just don't flash any odin files.
Click to expand...
Click to collapse
can you clarify please?
seattleboi1982 said:
can you clarify please?
Click to expand...
Click to collapse
Not sure what you mean. You can flash any rom from any variant of the S5 (obviously not the exynos variant, but there's hardly anything for it anyway). When I say rom, I mean a zip that's flashable in cwm or twrp. NOT the files that you flash in ODIN (tar, md5). DON'T flash those files from any other phone except the G900T.
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Well yes, but the way it works may not be quite the way you picture it. If you flash your phone to TMobile it isn't a 100% change over to TMobile as you probably assume it would be. Picture your phone as having two parts.. a baseband + ROM. The baseband is basically just the bootloader and modem. It's very hard to change the baseband and it's hardly ever done. So your baseband will more than likely remain ATT forever no matter what you do.
But that isn't likely to be a problem either. The baseband is compatible between ATT and TMobile and pretty much any other GSM system too. Otherwise you wouldn't be able to roam on other systems. You can change the ROM part to TMobile and your phone will act, smell and behave like a TMobile phone in pretty much every way that is likely to matter to you. The only obvious snag is that automatic OTA updates may or may not work, if that matters to you.
The customary way to change your phone to TMobile would be to root it, install a custom recovery e.g. TWRP. Then flash a TMobile ROM (or custom ROM if you want to) from TWRP. Note that installing a custom recovery like TWRP will change your Knox warranty bit. That might have warranty implications if your phone is still under warranty. Some carriers don't care about Knox - you can check the ATT forum to see how ATT handles warranty claims.
Alternately, if Knox matters to you, you may be able to flash a full stock TMobile image to your phone with the Odin program. This works for some carriers and not others. I don't know how ATT's locked bootloader would react to that. It's just a possibility that you could investigate if Knox and warranty are an issue to you. It would probably mean using a newer root method that doesn't trip Knox, then flashing a full TMobile firmware image, along with the correct TMobile PIT file. Hopefully Odin would just ignore the baseband and just write the ROM, while preserving the Knox bit. But you'd have to confirm that the ATT bootloader won't go bananas over the attempt i.e. search the forum to find out what happened when other people tried it.
.
fffft said:
Well yes, but the way it works may not be quite the way you picture it. If you flash your phone to TMobile it isn't a 100% change over to TMobile as you probably assume it would be. Picture your phone as having two parts.. a baseband + ROM. The baseband is basically just the bootloader and modem. It's very hard to change the baseband and it's hardly ever done. So your baseband will more than likely remain ATT forever no matter what you do.
But that isn't likely to be a problem either. The baseband is compatible between ATT and TMobile and pretty much any other GSM system too. Otherwise you wouldn't be able to roam on other systems. You can change the ROM part to TMobile and your phone will act, smell and behave like a TMobile phone in pretty much every way that is likely to matter to you. The only obvious snag is that automatic OTA updates may or may not work, if that matters to you.
The customary way to change your phone to TMobile would be to root it, install a custom recovery e.g. TWRP. Then flash a TMobile ROM (or custom ROM if you want to) from TWRP. Note that installing a custom recovery like TWRP will change your Knox warranty bit. That might have warranty implications if your phone is still under warranty. Some carriers don't care about Knox - you can check the ATT forum to see how ATT handles warranty claims.
Alternately, if Knox matters to you, you may be able to flash a full stock TMobile image to your phone with the Odin program. This works for some carriers and not others. I don't know how ATT's locked bootloader would react to that. It's just a possibility that you could investigate if Knox and warranty are an issue to you. It would probably mean using a newer root method that doesn't trip Knox, then flashing a full TMobile firmware image, along with the correct TMobile PIT file. Hopefully Odin would just ignore the baseband and just write the ROM, while preserving the Knox bit. But you'd have to confirm that the ATT bootloader won't go bananas over the attempt i.e. search the forum to find out what happened when other people tried it.
.
Click to expand...
Click to collapse
actually its T-mobile S5 flash to to make it like ATT S5. Samsung is a differant beast for me as i am usually a HTC or Moto user.
seattleboi1982 said:
actually its T-mobile S5 flash to to make it like ATT S5.
Click to expand...
Click to collapse
Your original post stated the opposite. Unintentionally I'm sure, but it goes to show that clarity counts.
It's much easier to go in that direction because the 900T uses an unlocked bootloader and TMB is generally less restrictive.
So yes, you can install an ATT (or other custom ROM) onto a 900T.
Keep in mind that it is not necessary to do so. The 900T will work fine on ATT with it's original firmware. But you can change the ROM to ATT if you want to for some reason. The proper way to do so is to find an ATT PIT file, then flash a full stock ATT firmware + PIT to your 900T. Most people don't bother with the PIT file and occasionally that leads to bootloops and soft bricking.
Anyway, go ahead and flash it if you want. Odin won't change the baseband, but everything else (ROM) will transition to ATT. FWIW, I think that a custom (debloated) ROM e.g. Phoenix ROM (which is not branded for ATT or TMB) is a nicer experience and better performance than using the ATT ROM. But up to you of course.
There is a XDA thread on S5 PIT files that has the 16 GB version of the ATT PIT if you need it.
.
fffft said:
Your original post stated the opposite. Unintentionally I'm sure, but it goes to show that clarity counts.
It's much easier to go in that direction because the 900T uses an unlocked bootloader and TMB is generally less restrictive.
So yes, you can install an ATT (or other custom ROM) onto a 900T.
Keep in mind that it is not necessary to do so. The 900T will work fine on ATT with it's original firmware. But you can change the ROM to ATT if you want to for some reason. The proper way to do so is to find an ATT PIT file, then flash a full stock ATT firmware + PIT to your 900T. Most people don't bother with the PIT file and occasionally that leads to bootloops and soft bricking.
Anyway, go ahead and flash it if you want. Odin won't change the baseband, but everything else (ROM) will transition to ATT. FWIW, I think that a custom (debloated) ROM e.g. Phoenix ROM (which is not branded for ATT or TMB) is a nicer experience and better performance than using the ATT ROM. But up to you of course.
There is a XDA thread on S5 PIT files that has the 16 GB version of the ATT PIT if you need it.
.
Click to expand...
Click to collapse
Odin will change the baseband. There's no need at all do do anything with ODIN. All it does is cause more problems if he does something wrong. I would just use TWRP and flash a stock ATT rom.
aooga said:
Odin will change the baseband. There's no need at all do do anything with ODIN. All it does is cause more problems if he does something wrong. I would just use TWRP and flash a stock ATT rom.
Click to expand...
Click to collapse
Installing a custom recovery like TWRP will trip Knox. That probably isn't an issue as TMobile doesn't care about Knox and virtually everyone says that it does not affect how TMobile handles warranty claims. But the OP should still know about Knox in advance in case it is an issue for him somehow.
I agree that a flashable zip is easier than Odin if the ROM that he wants exists in that form. Specifically, I don't know if anyone has repackaged an ATT ROM into a zip format. If someone has, then i agree with your approach. If not, he would have to use Odin.
IMO, the OP would do best to install something like the unbranded Phoenix ROM via TWRP.
Odin will not usually a foreign baseband to be flashed. Not that he necessarily has to try. You can use Odin to flash AP, CP, and CSC, but not the BL. Only when the constituent components are unavailable do you need to use the full OEM Odin image.
.
OP: Why do you need an ATT rom anyway? If you tell us what part you actually need, it might be easier than flashing an entire rom, either with odin or twrp.
fffft said:
Installing a custom recovery like TWRP will trip Knox. That probably isn't an issue as TMobile doesn't care about Knox and virtually everyone says that it does not affect how TMobile handles warranty claims. But the OP should still know about Knox in advance in case it is an issue for him somehow.
I agree that a flashable zip is easier than Odin if the ROM that he wants exists in that form. Specifically, I don't know if anyone has repackaged an ATT ROM into a zip format. If someone has, then i agree with your approach. If not, he would have to use Odin.
IMO, the OP would do best to install something like the unbranded Phoenix ROM via TWRP.
Odin will not usually a foreign baseband to be flashed. Not that he necessarily has to try. You can use Odin to flash AP, CP, and CSC, but not the BL. Only when the constituent components are unavailable do you need to use the full OEM Odin image.
.
Click to expand...
Click to collapse
How would someone deal with tmobile warranty without a tmobile account?
Is that possible at all?
Like via prepaid or something? Just wondering..
I would trip knox if I knew I had something to fall back on.
Lostatsea23 said:
How would someone deal with tmobile warranty without a tmobile account?
Is that possible at all?
Like via prepaid or something? Just wondering..
I would trip knox if I knew I had something to fall back on.
Click to expand...
Click to collapse
No, you need to be a tmobile customer with a postpaid account.
aooga said:
No, you need to be a tmobile customer with a postpaid account.
Click to expand...
Click to collapse
Well. Theres my options lol
aooga said:
No, you need to be a tmobile customer with a postpaid account.
Click to expand...
Click to collapse
Do you have a source or even solid rationale for that? I don't disagree that TMB, like pretty much any carrier treats current, postpaid customers better. But I have not seen any written policy or even credible assertions that TMB disavows their warranty for prepaid or ex-customers. AFAIK, if you bought the phone from TMB, postpaid or prepaid, you have a warranty through TMB. The obvious impediments being a stolen phone or account in serious arrears.
Discretionary powers exist, so it's sometimes difficult to distinguish between common practice or what they can be persuaded to do versus actual policy. Policy is a definite advantage in negotiations, so if there is anything written that says prepaid or ex-customers must deal with Samsung directly, I'd like to see that.
Everything in my direct experience is to the contrary. TMB honours warranty and doesn't care about Knox. They do have less respect for prepaid customers. But the few prepaid TMB customers that I know still had TMB handle their warranty claims.
.
fffft said:
Do you have a source or even solid rationale for that? I don't disagree that TMB, like pretty much any carrier treats current, postpaid customers better. But I have not seen any written policy or even credible assertions that TMB disavows their warranty for prepaid or ex-customers. AFAIK, if you bought the phone from TMB, postpaid or prepaid, you have a warranty through TMB. The obvious impediments being a stolen phone or account in serious arrears.
Discretionary powers exist, so it's sometimes difficult to distinguish between common practice or what they can be persuaded to do versus actual policy. Policy is a definite advantage in negotiations, so if there is anything written that says prepaid or ex-customers must deal with Samsung directly, I'd like to see that.
Everything in my direct experience is to the contrary. TMB honours warranty and doesn't care about Knox. They do have less respect for prepaid customers. But the few prepaid TMB customers that I know still had TMB handle their warranty claims.
.
Click to expand...
Click to collapse
Source would be experience. When you call, you cannot speak to a warranty rep unless you have a tmobile account. They ask for the phone number and last 4 of your ssn. Maybe you can convince them to make an exception, but when I tried with ATT, they told me since you're not a ATT customer, we can't help you.
aooga said:
Source would be experience. When you call, you cannot speak to a warranty rep unless you have a tmobile account.
Click to expand...
Click to collapse
All right. Your experience is completely contrary to mine. With no evidence of that being policy, I can only assume that you've encountered less helpful CSRs. Anyone finding themselves in a similar position may well prevail if they try talking to different CSRs.
.
fffft said:
All right. Your experience is completely contrary to mine. With no evidence of that being policy, I can only assume that you've encountered less helpful CSRs. Anyone finding themselves in a similar position may well prevail if they try talking to different CSRs.
.
Click to expand...
Click to collapse
Have you actually done an exchange with a carrier that you don't have service with? Just think about it...they don't have any of your info. CC, ssn, email, even your full name. If for some reason the customer doesn't ship the defective phone back, they can't charge you. If tmobile has a way of doing this for non-customers, I'll gladly shut up
aooga said:
...
Click to expand...
Click to collapse
I already expressed my opinion on this. If you disagree, so be it. And it's tangential and off topic in this thread.
Getting back on topic, the OP asked if he can flash an ATT "ROM" onto his TMB 900T phone.
Yes he can. We agreed that the easiest way to do so is to use TWRP, provided that he does not mind Knox being tripped. And of course, assuming that someone has repackaged an ATT ROM into a flashable zip format.
The alternative is a traditional Odin flash. He can flash ATT firmware onto his TMB 900T phone. It should be done in conjunction with the appropriate ATT PIT file. But those who are impatient or don't know about PIT files, usually don't run into problems eschewing the PIT. I won't advise that approach though.
Two last considerations. There isn't necessarily a good reason to do any of this in the first place. A TMobile S5 can roam on or use an ATT SIM directly. And without missing out on anything that the average user would notice. But it is possible to so for sundry reasons. As one way of changing the CSC and opt into an automatic OTA update scenario. To gain carrier specific ATT apps and so forth.
There is a lot of confusion regarding the mechanics of transitioning a phone from TMB to ATT for these sundry goals. A phone has a ROM, which is the apps and most of the system files. That can certainly be changed.
And then there is the low level baseband. The baseband can be updated with something newer from the same carrier that the phone originated from. But it is difficult and hard to find a good reason to change the baseband to a different carrier. To be more specific the baseband represents the bootloader and modem. A modem from one carrier works just fine on another carrier 99% of the time. So pragmatically, the best approach is to simply update the modem to a newer version from the original carrier, regardless of what carrier you actually use the phone on. There is rarely something carrier specific in a modem module.
If you enjoy fighting with Odin, you can flash some modems from foreign carriers. It will also sometimes brick your phone. And Odin often refuses to proceed with the flash for various reasons. So again, not recommended. Nor necessary in most cases.
The bootloader is exponentially harder to change to another carrier. Not to mention almost pointless except for cosmetic reasons and involves having Odin jump through a lot of hoops. Difficult enough to do that it isn't inaccurate to say it can't be done. It can't be done by most people. And it would be rare to hear a reason with merit for doing so.
.
.
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Why would you want to run an att rom, no wifi calling? lol, anyways, what rom are you trying to run?
i would like to run as close as possible to an AT&T ROM as im an ATT subsciber with a T-mobile phone. especially now with VoLTE.
Related
hello people out there, does anyone have the radio files for bell network?
You can use any of the files in this thread:
http://forum.xda-developers.com/showthread.php?t=531134
Bell hasn't released a software upgrade (and most likely never will) for the Touch Pro. That means there is no stock Bell radio to flash to.
so i assume you would use the telus radio file because they use the same towers?
yellowz24 said:
so i assume you would use the telus radio file because they use the same towers?
Click to expand...
Click to collapse
It doesn't matter which radio you use, they are carrier inspecific. The carrier name on the radio just refers to the carrier whose ROM update the radio shipped with.
That said, if you flash one of these radios and need to return your phone to bell for whatever reason you will never be able to flash back to a stock bell radio. If the tech who checks it out knows/cares what s/he is doing they will notice that you have a different radio version than what bell typically offers and your warranty will be voided.
Finding out which radio is right for you is trial and error. The good thing is that flashing a new radio does not hard reset your device...so you can flash and reflash to different radios quite easily. I suggest trying a bunch out for a week or two at a time. I know it's time consuming but there is no other real way around it.
I am also on Bell, and have tried the Telus and Sprint (latest v.) radios. I haven't yet found much of a difference, but I'm taking my time.
Read the FAQ in that link I posted for more info.
the radio file i am looking for is for is 1.04.02v
yellowz24 said:
the radio file i am looking for is for is 1.04.02v
Click to expand...
Click to collapse
sorry mate, like he said above. if youve flashed to a different radio you cant flash back to the one that came on your bell touch pro. id like to try the different radios but dont wanna pooch my chances of returning it if ever needed so i never did it. from what i understand it needs to be dumped out of the stock one but for some reason it cant/hasnt been done
i need to send mine in for service but the warranty would proball be voided if they see a different radio version, i have the stock rom back in it. i guess i am going to have to try to send it and see what happens
yellowz24 said:
i need to send mine in for service but the warranty would proball be voided if they see a different radio version, i have the stock rom back in it. i guess i am going to have to try to send it and see what happens
Click to expand...
Click to collapse
That's the risk you take flashing a phone with no carrier rom available.
yellowz24 said:
i need to send mine in for service but the warranty would proball be voided if they see a different radio version, i have the stock rom back in it. i guess i am going to have to try to send it and see what happens
Click to expand...
Click to collapse
Your best chance is to flash to the Telus radio (as the version numbers are similar), send it in and hope that you get a not-very-observant tech who doesn't check the radio versions (or the boot-loader for that matter).
If they notice, play dumb; but nothing is guaranteed.
Hello everyone
I am making this post because from reading discussions, there seems to be a large degree of confusion circulating regarding the differences between Verizon branded HTC 10 and the unlocked edition HTC 10, and what software can be used on either and what works on the Verizon network and doesn't. None of the information below is officially endorsed or supported, and I make no guarantees that it will work on your device-- can only vouch what works on mine.
Firstly...if you own an HTC 10 and are a Verizon customer, and your device is S-OFF, this applies to you. Whether it was purchased as an unlocked edition or a Verizon branded edition, the hardware is identical (as far as I understand), and if your device is S-OFF then you can put any software on the device as you so desire. This means when you travel, you can flash GSM firmware, then buy a cheap local prepaid SIM card in your destination country. Or if you get tired of Verizon, you can switch to ATT or TMobile-- or, vice versa, you can switch to Verizon from AT&T or TMobile.
When we get to the subject of firmware, the waters start to get muddy. Generally you are told that if you are on Verizon's network, you must flash only Verizon firmware or your device will not work on their network. This kinda sucks for us Verizon customers, because Verizon is known to be painfully slow at rolling out updates, and there could be serious security holes that are left unpatched while waiting for them to come through.
*However*, I have found that this device runs perfectly fine on Verizon's network with the unlocked-edition firmware (which is significantly more up-to-date as the Verizon firmware), as long as your RADIO partition is flashed with Verizon-specific radio firmware. But aside from the radio partition, none of the software on the other partitions need be Verizon-specific software. This is the method I use for updating to the latest unlocked firmware and Verizon radio (S-OFF requred):
--to update to the latest Verizon radio, flash the latest Verizon firmware-- just search for Verizon htc 10 firmware updates downloads, and you should be able to find it.. I will update this post later with a direct link to that thread..
--next step-- copy your radio partition to a disk image file. boot into recovery, then from adb shell run :
dd if=/dev/block/mmcblk0p30 of=radio.img
exit the shell, use adb pull to pull the radio.img file onto your PC
--step 3. flash the newest firmware for the unlocked-edition...
--step 4. flash the radio.img that you extracted earlier. Fastboot flash from bootloader mode (not RUU mode, not download mode-- just regular bootloader mode with the white screen and the tiny menu). 'fastboot flash radio radio.img'
And that's it.. you're good to go.. again, these instructions assume you are S-OFF and are familiar with the basic procedures for flashing firmware. If you wish to do this, it is done at your own risk.
Happy to answer any questions...hopefully some folks here will find this useful .
Well written, appreciate the info. [emoji106]
Sent from my HTC 10 using Tapatalk
Excellent guide, especially for those of us on Verizon who might want to test the waters with other 10-based ROMs. Since Verizon disables certain functions on its own devices (e.g. "Powersaver," SystemUI Tuner), one might want to look at the unlocked ROMs for full features. Thanks.:good:
I'm googling like crazy how to do the ADB Pull part up. lol I'm in bootloader with CMD promt open and i dont know what to type to ADB pull (never attempted this before).
EDIT: So apparently you need supercid to do this and when i try to modify the cid through "htc_fastboot oem writecid 11111111" it fails and I cannot continue. Anyone have luck doing this?
EDIT2: After a reboot, it allowed me to changed the CID. I tried to flash the firmware first (which crashed and I wasn't able to) so that must have caused the inability to change CID.
Answer to my Question by user @sbong
To Backup your Radio:
1. adb shell
2. su (if needed to get a #)
3. dd if=dev/block/mmcblk0p30 of=/sdcard/radio.img
4. exit
5. You'll find the radio image on the internal sd card
Flashing Latest unlocked firmware WIPED my ROM so just a heads up to anyone trying this.
I ran through these steps and flashed the international firmware version 1.95.401.4 and then flashed the radio I had while still on my VZW firmware. I did have to change my MID and CID before the firmware would flash but after I did it flashed successfully. Then I went back to bootloader (white screen with options) and flashed the radio.img file. After doing that and rebooting I am now sitting at the HTC splash screen with the white background and the red text saying this build is for dev purposes only. Any idea what to do at this point? Thanks!
EDIT: I am trying in TWRP to wipe system, data, and boot and then restore my ROM from a TWRP backup. Will post if it boots after doing this.
EDIT 2: Wiping my partitions in TWRP and the doing a restore allowed me to boot...interesting to note I got my firmware from here: https://docs.google.com/spreadsheets/d/1EdAHLDDxqf9jH65me_8bY9oXdaYusI0eedpwO6yUY2s/pubhtml under the NoWipe section so it shouldn't have messed with my ROM.
I'm hoping this helps with battery life as previously I was on old VZW firmware but my ROM was running a newer FW base. I heard that could cause battery drain. Now my phone FW matches the FW my ROM was based off of.
Unlocked software doesn't support Verizon advanced calling features. Which is a pretty big no for perfect. Just saying...
Sent from my HTC6545LVW using Tapatalk
dottat said:
Unlocked software doesn't support Verizon advanced calling features. Which is a pretty big no for perfect. Just saying...
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I'm running unlocked US firmware version 1.95.401.4, but what I did do was extract the radio.img from my VZW firmware first, flashed the US unlocked, then flashed the VZW radio.img and booted up. My HD and WiFi calling is activated and working.
pettigrew95 said:
I'm running unlocked US firmware version 1.95.401.4, but what I did do was extract the radio.img from my VZW firmware first, flashed the US unlocked, then flashed the VZW radio.img and booted up. My HD and WiFi calling is activated and working.
Click to expand...
Click to collapse
You still didn't say what rom/software you are running. You can run the firmware from unlocked minus radio while on a Verizon rom and still have these features (why one would do this I have no clue). The unlocked os itself does no have advanced calling built in for Verizon unless it's a custom ROM like what @santod040 built where he added those features back in.
Sent from my HTC6545LVW using Tapatalk
dottat said:
You still didn't say what rom/software you are running. You can run the firmware from unlocked minus radio while on a Verizon rom and still have these features (why one would do this I have no clue). The unlocked os itself does no have advanced calling built in for Verizon unless it's a custom ROM like what @santod040 built where he added those features back in.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
The reason I flashed the US unlocked 1.95.401.4 is because I am running LeeDroid 2.7.0 which is based off of that firmware. I wanted the FW my ROM was based off of to match the firmware my phone was running. Also, VZW is way behind on FW updates for the 10 and I like to be somewhat up to date on the latest security patches from Google.
pettigrew95 said:
The reason I flashed the US unlocked 1.95.401.4 is because I am running LeeDroid 2.7.0 which is based off of that firmware. I wanted the FW my ROM was based off of to match the firmware my phone was running. Also, VZW is way behind on FW updates for the 10 and I like to be somewhat up to date on the latest security patches from Google.
Click to expand...
Click to collapse
Those security updates will be covered on the os side. While leedroid may be based off a 401 build make no mistake that most ril functions required for it to work on Verizon have been carved in from an actual Verizon rom. So in a sense, the parts that actually matter for connectivity are still going to interface best with Verizon firmware.
Sent from my HTC6545LVW using Tapatalk
dottat said:
Those security updates will be covered on the os side. While leedroid may be based off a 401 build make no mistake that most ril functions required for it to work on Verizon have been carved in from an actual Verizon rom. So in a sense, the parts that actually matter for connectivity are still going to interface best with Verizon firmware.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Thank you for that info. So is there any benefit then to what I did? Is anything broken in my phone that I don't know about? I have heard that if the FW a ROM was based off didn't match the FW your phone was running it could be a rogue battery drainer, is this true?
pettigrew95 said:
Thank you for that info. So is there any benefit then to what I did? Is anything broken in my phone that I don't know about? I have heard that if the FW a ROM was based off didn't match the FW your phone was running it could be a rogue battery drainer, is this true?
Click to expand...
Click to collapse
I would say likely not. As to whether anything is broken... if it's working it hasn't broken anything yet. You have to be careful though when running bits and pieces of mixed firmware because partition structure of the phone can change on htc phones based on aboot/hboot. So you can run into a scenario where a phone might not be partitioned to allow certain size images to flash successfully. Me personally, I would run one or the either. In this case, while on verizon, I would use the verizon firmware even if on a custom based rom. The one exception to this would be a built from the ground up rom like CM or AOSP. Some of these were developed to work solely on specific firmware.. One such variant of this in the htc m8 days was super popular. It was also the number one killer of m8's due to the specific/custom firmware flashing that was recommended in the OP. I can't tell you how many users i attempted to help fix their phones that either would not boot at all or that the phone itself was in a full write protected state.
When we get to the subject of firmware, the waters start to get muddy. Generally you are told that if you are on Verizon's network, you must flash only Verizon firmware or your device will not work on their network. This kinda sucks for us Verizon customers, because Verizon is known to be painfully slow at rolling out updates, and there could be serious security holes that are left unpatched while waiting for them to come through.
Click to expand...
Click to collapse
I find this statement sort of funny. Since we are talking firmware and not OS here it's not muddy at all. Verizon is behind on OS updates. Yes they toss in the HTC provided firmware updates as HTC requires.. but make not mistake the OS itself carries the security patches. So thinking you've somehow patched yourself by flashing firmware only is false re-assurement.
If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users.
dottat said:
I would say likely not. As to whether anything is broken... if it's working it hasn't broken anything yet. You have to be careful though when running bits and pieces of mixed firmware because partition structure of the phone can change on htc phones based on aboot/hboot. So you can run into a scenario where a phone might not be partitioned to allow certain size images to flash successfully. Me personally, I would run one or the either. In this case, while on verizon, I would use the verizon firmware even if on a custom based rom. The one exception to this would be a built from the ground up rom like CM or AOSP. Some of these were developed to work solely on specific firmware.. One such variant of this in the htc m8 days was super popular. It was also the number one killer of m8's due to the specific/custom firmware flashing that was recommended in the OP. I can't tell you how many users i attempted to help fix their phones that either would not boot at all or that the phone itself was in a full write protected state.
I find this statement sort of funny. Since we are talking firmware and not OS here it's not muddy at all. Verizon is behind on OS updates. Yes they toss in the HTC provided firmware updates as HTC requires.. but make not mistake the OS itself carries the security patches. So thinking you've somehow patched yourself by flashing firmware only is false re-assurement.
If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users.
Click to expand...
Click to collapse
When you say:
"If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users."
Is this correct? I thought flashing the VZW radio.img would enable advanced calling features to work? I am on a US unlocked FW with VZW radio.img flashed and my advanced calling features are functional on LeeDroid 2.7.0.
pettigrew95 said:
When you say:
"If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users."
Is this correct? I thought flashing the VZW radio.img would enable advanced calling features to work? I am on a US unlocked FW with VZW radio.img flashed and my advanced calling features are functional on LeeDroid 2.7.0.
Click to expand...
Click to collapse
Again,, I will restate it. You are NOT on unlocked. You have pieces of the firmware and a custom rom. That custom rom was based off international rom ( Not even the unlocked version as 401 is international and 617 is the actual unlocked variant).
Don't believe me this is a result of custom rom work and not firmware? Flash the unlocked RUU and then the verizon radio to get service. You will notice that advanced calling doesn't exist in the menu for you.
dottat said:
Again,, I will restate it. You are NOT on unlocked. You have pieces of the firmware and a custom rom. That custom rom was based off international rom ( Not even the unlocked version as 401 is international and 617 is the actual unlocked variant).
Don't believe me this is a result of custom rom work and not firmware? Flash the unlocked RUU and then the verizon radio to get service. You will notice that advanced calling doesn't exist in the menu for you.
Click to expand...
Click to collapse
Ok, sorry if my confusion is frustrating ...So basically my advanced calling features are operable due to my ROM and not the fact that I flashed a VZW radio.img on top of the non VZW firmware I flashed? In a nutshell...Is what I have done beneficial in any way or should I just flash back to the VZW 1.85 FW? Thank you for the help here, it is much appreciated!
pettigrew95 said:
Ok, sorry if my confusion is frustrating ...So basically my advanced calling features are operable due to my ROM and not the fact that I flashed a VZW radio.img on top of the non VZW firmware I flashed? In a nutshell...Is what I have done beneficial in any way or should I just flash back to the VZW 1.85 FW? Thank you for the help here, it is much appreciated!
Click to expand...
Click to collapse
Not frustrating at all. Don't take my responses as that way and certainly don't stop asking questions because of it. I'm still waking up here today so it's probably how i'm writing my responses lol. Personally I would just run the stock verizon firmware and enjoy your custom rom.
Your advanced call features are working due to leedroid splicing in the functional pieces of the advanced call features from the current verizon rom. I remember using an earlier version of his rom that lacked this feature set. I bailed on his rom pretty quickly when that was the only offering available as i needed advanced calling. A month or so later he added it to the rom later. @santod040 is one verizon dev who can comment here further when he sees this to attest to the fact the only way advanced calling works on verizon while on a non-verizon rom is that the DEV must enable it.
On the CM side of the house i have been involved in tracking down pieces of volte/advanced calling even back on the m9 in order to get it functional and I can tell you there it's not easy. So if you're on a non-vzw based rom and have advanced calling... make sure you thank the guys who baked your rom.
dottat said:
Not frustrating at all. Don't take my responses as that way and certainly don't stop asking questions because of it. I'm still waking up here today so it's probably how i'm writing my responses lol. Personally I would just run the stock verizon firmware and enjoy your custom rom.
Your advanced call features are working due to leedroid splicing in the functional pieces of the advanced call features from the current verizon rom. I remember using an earlier version of his rom that lacked this feature set. I bailed on his rom pretty quickly when that was the only offering available as i needed advanced calling. A month or so later he added it to the rom later. @santod040 is one verizon dev who can comment here further when he sees this to attest to the fact the only way advanced calling works on verizon while on a non-verizon rom is that the DEV must enable it.
On the CM side of the house i have been involved in tracking down pieces of volte/advanced calling even back on the m9 in order to get it functional and I can tell you there it's not easy. So if you're on a non-vzw based rom and have advanced calling... make sure you thank the guys who baked your rom.
Click to expand...
Click to collapse
Ok awesome, that pretty much sums up what I needed to hear! My last question, I have heard in the past that if the phone FW does not match the ROMs FW base it could be a rogue battery drainer, is this true? Part of the reason of me flashing the matching FW that LeeDroid 2.7.0 runs is in case mismatched ROM FW and phone FW does cause some kind of battery drain. I have to say, my phones battery is pretty pathetic even with Amplify, Greenify, Power Nap, etc. Thanks again!
Wow. I don't think I could be more confused. I'm humbly asking for clarity
I've got a Verizon 10 that is s-off, rooted, unlocked and running LeeDroid. The download screen shows 1.19 for the OS and @60504 for the radio. If I don't care about preserving the contents of the internal card, what's the simple path to get the fw/radio updated (looks like 1.85.605.8) and back to LeeDroid? If extracting the radio.img is a requirement, usually that kind of file is linked inline with the threads to root or update the fw. It's not, so alarms are going off in my head that there is a reason a flashable radio isn't right next to the RUU which would be next to the instructions for going from a custom rom like LeeDroid or Viper -> update fw/radio -> back to custom rom.
It took me an hour of reading, and not working, just to figure out I have an old fw/radio and one wrong move would commit myself to a day of reading and trying random things.
I can't stress the humble position I'm in and I did search and try to find the clear path, but I can't see it. Help?
jimbob_sf said:
Wow. I don't think I could be more confused. I'm humbly asking for clarity
I've got a Verizon 10 that is s-off, rooted, unlocked and running LeeDroid. The download screen shows 1.19 for the OS and @60504 for the radio. If I don't care about preserving the contents of the internal card, what's the simple path to get the fw/radio updated (looks like 1.85.605.8) and back to LeeDroid? If extracting the radio.img is a requirement, usually that kind of file is linked inline with the threads to root or update the fw. It's not, so alarms are going off in my head that there is a reason a flashable radio isn't right next to the RUU which would be next to the instructions for going from a custom rom like LeeDroid or Viper -> update fw/radio -> back to custom rom.
It took me an hour of reading, and not working, just to figure out I have an old fw/radio and one wrong move would commit myself to a day of reading and trying random things.
I can't stress the humble position I'm in and I did search and try to find the clear path, but I can't see it. Help?
Click to expand...
Click to collapse
For you just flash the custom firmware zip for Verizon that's been posted. You want the one without stock recovery and bootloader.
Going that route updates your phones firmware and saves you from wiping and flashing.
Sent from my HTC6545LVW using Tapatalk
Thank you! Now to figure out which thread has the file you're referring to. I've looked at them all and I can't tell which one does what you're saying.
Question for those of you with experience on the V10. I just upgraded to the V20 (love it btw). My V10 is probably the first phone I never rooted, or loaded a ROM on. I've had many devices with custom roms in the past, however they were always carried branded (not unlocked) phones. Here is my question:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Thanks in advance..
X
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
xarius76 said:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Click to expand...
Click to collapse
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
beavis5706 said:
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
Click to expand...
Click to collapse
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
emdroidle said:
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
Click to expand...
Click to collapse
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
X
xarius76 said:
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
Click to expand...
Click to collapse
This is a substantial annoyance to many people, though there are some hopes of working around this...
xarius76 said:
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
Click to expand...
Click to collapse
I won't swear to it, but I was under the impression the updates come from LG, at which point it should still nominally update if brought to the EU. Failing that, LG Bridge should be able to get updates.
xarius76 said:
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
Click to expand...
Click to collapse
Remember, this is risky though hopeful.
Hi XDA haven't been on here for a while.
So I have a question I was given a S9+ from Sprint it's unlocked I'm currently using it on TMO but I don't have wifi calling nor video calling. I wanted to see if it was possible to flash a TMO firmware. Since it's still on July's patch here's a screen shoot of current firmware.
I moved from Sprint to Tmo, and just put in the sim and then updated the firmware through the system update interface. All works as expected.
The difference may (or may not) be, if the phone was unlocked by Sprint or by another method. My wife's phone was unlocked via "another method" and cannot get it to update system software. I haven't bothered looking into it further though, as we don't expect to keep the S9+ too much longer.
berzerkus said:
I moved from Sprint to Tmo, and just put in the sim and then updated the firmware through the system update interface. All works as expected.
The difference may (or may not) be, if the phone was unlocked by Sprint or by another method. My wife's phone was unlocked via "another method" and cannot get it to update system software. I haven't bothered looking into it further though, as we don't expect to keep the S9+ too much longer.
Click to expand...
Click to collapse
Yes mine was unlocked different method so it won't update normally.
That's why I asked if I could cross flash to TMO
Colombia81er said:
Yes mine was unlocked different method so it won't update normally.
That's why I asked if I could cross flash to TMO
Click to expand...
Click to collapse
If you figure it out, let us know. I'd be interested in giving it a go.
berzerkus said:
I moved from Sprint to Tmo, and just put in the sim and then updated the firmware through the system update interface. All works as expected.
The difference may (or may not) be, if the phone was unlocked by Sprint or by another method. My wife's phone was unlocked via "another method" and cannot get it to update system software. I haven't bothered looking into it further though, as we don't expect to keep the S9+ too much longer.
Click to expand...
Click to collapse
Colombia81er said:
Yes mine was unlocked different method so it won't update normally.
That's why I asked if I could cross flash to TMO
Click to expand...
Click to collapse
berzerkus said:
If you figure it out, let us know. I'd be interested in giving it a go.
Click to expand...
Click to collapse
if your phone is unlocked via whatever method, it wont interfere with system updates. OTAs will happen at regular intervals based on the firmware flashed on the phone and the recovery status. Stock recovery means that youll get OTAs, if youre not, its likely a glitch and has nothing to do with the unlock status.
If youre looking to get your phone working on tmob and its a spr phone, all you really need to do is unlock it, put the new sim in it and configure the APN. If you want full features like voLTE and wifi calling, then youll need to flash a tmob firmware version on your phone which requires the patched version of Odin. I have a Cricket branded (originally, at least) S9 and i flashed the U1 firmware on it via patched Odin and the phone now thinks its a factory unlocked S9, as i also unlocked it via "alternative methods". Perfectly seamless transition and i get OTAs all the time
berzerkus said:
If you figure it out, let us know. I'd be interested in giving it a go.
Click to expand...
Click to collapse
Sorry to revive the post, so i finally did the update it worked flawless i did the update to the latest firmware G965USQS7DTB1_G965UOYN7DTB1_TMB now i got Wifi Calling and VoLTE.
I used Odin3-v3.13.1-Patched
Unrar the firmware and then just load the files in Odin
Heres a great tut https://www.youtube.com/watch?v=bnPkwICq_Bw&t=
hi i have a verizon tab s6 sm-t867v(lte version) the stock rom does not let you use phone app to do calls and messages app dont work. all the calls or messages should go throug the verizon propritory messages+ app ,where you need to add verizon number. . and the tablet is unlocked to any career. . I DONT WANT TO ROOT THE DEVICE. i did a career switch for my note 8 from att to tmobile without rooting so i thought i can do the same to tab s6. i have few questions
1. is there a way i can swap for another career rom
2. can i flash international rom just throug odin so that i dont deal with verizon bloatware.
can any one point me to the files and the thread.
is there a way i can use calling and texting on without going throug messages+ app. thanks for the help in advance. i am sorry if anythin i ask is silly. peace
shiva49 said:
hi i have a verizon tab s6 sm-t867v(lte version) the stock rom does not let you use phone app to do calls and messages app dont work. all the calls or messages should go throug the verizon propritory messages+ app ,where you need to add verizon number. . and the tablet is unlocked to any career. . I DONT WANT TO ROOT THE DEVICE. i did a career switch for my note 8 from att to tmobile without rooting so i thought i can do the same to tab s6. i have few questions
1. is there a way i can swap for another career rom
2. can i flash international rom just throug odin so that i dont deal with verizon bloatware.
can any one point me to the files and the thread.
is there a way i can use calling and texting on without going throug messages+ app. thanks for the help in advance. i am sorry if anythin i ask is silly. peace
Click to expand...
Click to collapse
Yes you can switch the firmware on the sm-t867v from Verizon to TMobile or Sprint. It keeps the bootloader locked down so root is still impossible but since you are not looking to root it just switching the firmware version should work just fine. I personally have metro pcs and their $15 unlimited tablet data plan on mine and I switched my firmware to TMobile so I could pick up the LTE bands it would not connect to with the Verizon firmware. All you need to do is download the modified Odin 3.14 and the firmware of the carrier you wish to switch to. It HAS to have the same base model. For example I went from the SM-T867V firmware and flashed the SM-T867U firmware to the device. So your firmware choice absolutely MUST have the SM-T867 in the beginning of it. Any other firmware will most likely brick your device if Odin even allows it to flash. The thing that makes the difference between Verizon and TMobile is the user userdata file. You must flash it with the rest of the firmware files, So BL, AP, CP, CSC, and Userdata. Don't worry, the stock firmware will come with the userdata file. Also its best that you don't flash the CSC-Home file but flash the regular CSC file as the home one will not delete your data and its probably best to do a full wipe when switching firmwares, so make sure you back up anything you don't wish to lose. When the flashing is finished it will boot and instead of the white screen with big red circle for Verizon you will get a pink TMobile screen and it will be model SM-T867U now. All OTA updates will still work without problem and you will get a functional dial pad which works for all the secret menus and all that fun stuff. BTW, I take absolutely no responsibility if for some reason it messes up or bricks your tab s6 lte. Goodluck and enjoy your non Verizon tablet.
Tofor said:
Yes you can switch the firmware on the sm-t867v from Verizon to TMobile or Sprint. It keeps the bootloader locked down so root is still impossible but since you are not looking to root it just switching the firmware version should work just fine. I personally have metro pcs and their $15 unlimited tablet data plan on mine and I switched my firmware to TMobile so I could pick up the LTE bands it would not connect to with the Verizon firmware. All you need to do is download the modified Odin 3.14 and the firmware of the carrier you wish to switch to. It HAS to have the same base model. For example I went from the SM-T867V firmware and flashed the SM-T867U firmware to the device. So your firmware choice absolutely MUST have the SM-T867 in the beginning of it. Any other firmware will most likely brick your device if Odin even allows it to flash. The thing that makes the difference between Verizon and TMobile is the user userdata file. You must flash it with the rest of the firmware files, So BL, AP, CP, CSC, and Userdata. Don't worry, the stock firmware will come with the userdata file. Also its best that you don't flash the CSC-Home file but flash the regular CSC file as the home one will not delete your data and its probably best to do a full wipe when switching firmwares, so make sure you back up anything you don't wish to lose. When the flashing is finished it will boot and instead of the white screen with big red circle for Verizon you will get a pink TMobile screen and it will be model SM-T867U now. All OTA updates will still work without problem and you will get a functional dial pad which works for all the secret menus and all that fun stuff. BTW, I take absolutely no responsibility if for some reason it messes up or bricks your tab s6 lte. Goodluck and enjoy your non Verizon tablet.
Click to expand...
Click to collapse
Followed instruction and successfully changed from V to T-mobile. Thankyou!
geoffwdixon said:
Followed instruction and successfully changed from V to T-mobile. Thankyou!
Click to expand...
Click to collapse
I'm glad it worked for you without any major issues. This was the first thread I've given any real instruction on. Hope your tab continues to work perfectly. I broke the screen on mine so the only thing it's really used for is an android PC. Thank God for the Tab S6`s ability to output video so easily and the Samsung DEX software.