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.
Hi,
Here is an Odin .tar for AT&T stock radio, others coming soon:
AT&T UCLA1 Radio Odin tar
Here are instructions to pull radio using ADB (you can do this on a rooted running device)
Code:
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
adb pull /sdcard/amss.bin
adb pull /sdcard/mdm.bin
Post the resulting files up somewhere and link here.
Incidentally to flash a new radio dumped from this method vs. the odin tar:
Code:
adb push amss.bin /tmp/amss.bin
adb push mdm.bin /tmp/mdm.bin
adb shell dd if=/tmp/amss.bin of=/dev/block/mmcblk0p13
adb shell dd if=/tmp/mdm.bin of=/dev/block/mmcblk0p17
Do have a backup of your existing radio before flashing either way
Bell one incoming now....
Telus radio - http://www.mediafire.com/?nws1hn3wiof639e
Thank you very much, before the radio has never been a successful backup in DD
Well Da_G is Hot here
Here's the Rogers Radio imgs
http://www.mediafire.com/file/7x951mr8iz76nj1/i717Rogers_Radio.zip
May be a noob question
Is it possible to use Odin to flash the radio?
Should we use PDA or csc?
jqcc said:
May be a noob question
Is it possible to use Odin to flash the radio?
Should we use PDA or csc?
Click to expand...
Click to collapse
From my understanding from my vibrant days..
Actually you would use *phone* in Odin. Not PDA.
Sent from my sticky fingers because Ice cream sandwiches are tasty.
antiochasylum said:
Actually you would use *phone* in Odin. Not PDA.
Sent from my sticky fingers because Ice cream sandwiches are tasty.
Click to expand...
Click to collapse
Haha, correct! ****... sorry. I just turned on my comp to check and it is phone
Updated first post with AT&T stock radio Odin tar.
Will put together Rogers, TELUS, and Bell in two shakes!
Will you be making a radio that can be used with tmobile USA.
Sent from my SAMSUNG-SGH-I717 using xda premium
Duno, if the device has the hardware, if it can be enabled, etc. etc.
Flashing a radio from another device is the best way to find out
On that note, I can confirm the Rogers radio works fine on AT&T Note, and unlocks the RAT selection menu (*#2263# from dialer), allowing you to set band preferences etc.
So we flash it using Odin by placing it in the phone selection?
Da_G said:
Duno, if the device has the hardware, if it can be enabled, etc. etc.
Flashing a radio from another device is the best way to find out
On that note, I can confirm the Rogers radio works fine on AT&T Note, and unlocks the RAT selection menu (*#2263# from dialer), allowing you to set band preferences etc.
Click to expand...
Click to collapse
Nice find. Were you able to flash back to the AT&T radio after flashing to the Rogers?
Sent from my SAMSUNG-SGH-I717 using xda premium
Re: using odin,
No, Odin apparently validates the radio ROM and blocks it from applying. I should clarify and say that on AT&T Note Odin detects non-AT&T radio images and blocks them. I imagine you can flash the Rogers radio images to the Rogers phone through Odin without issues, as the signatures would match. Using dd/CWM bypasses the signature checks.
The only way is via CWM (not ready yet) or using dd per the first post (radio1.img is mdm.bin and radio2.img is amss.bin)
Re: flashing to and from various radios, yes, this works great from dd, nothing blocks it. Even did it on a running device with the radio loaded
Incidentally, the radios (mmcblk0p13/mdm.bin and mmcblk0p17/amss.bin are 100mb partitions containing a (~25MB) FAT16 filesystem with a bunch of components, so you can even interchange parts of the radio should you wish. Obviously lots of free space here to make the radios 4x their current size, I wonder why
Edit:
While using the Rogers radio, I noticed that some videos were having problems playing back. Flashing back to the AT&T radio fixed this. The Q6 video/audio accelerating DSP firmware is contained in the modem and likely there is a DRM component to the AT&T one not present in the Rogers one.
So, could somebody flash these to a Skyrocket or Hercules to verify the interchangeability between the three phones? I know we'll know as soon as CWM comes out but was wondering if this would help?
Da_G, Shouldn't the Bell Radio theoretically give T-mobile 3g access since the Bell lists 1700mhz as a band on their Galaxy Note Specs Page
It might work. But I think we'll have to swap out some of the q6 DSP firmware, it breaks video playback on the AT&T Note (likely due to DRM as I mentioned)
Also, the radio is GSM_HUDSON on both skyrocket and note. I'm pretty sure the radios should be interchangable between them. You can certainly try without much risk - even if you completely wipe out p13 and p17 (mdm.bin and amss.bin) the phone will still boot to both the normal system and recovery, allowing you to re-load the original radio and be back up and running. So risk is relatively minimal
ok, any chance you put it in a cwm flashable? I'll give it a go if I know there's no sbl or pbl, and odin scares me when it's something not meant for me phone.
hi guys,
I have a Samsung Galaxy S2 (i9100P), originally on orange, but since then I've moved onto T-Mobile. I have been having problems with low signal and many callers complaining that they cannot clearly hear and the sound is cutting out on both sides. T-Mobile have given me a signal booster and although the signal strength has massively improved, I still have poor call quality
Now I could be wrong here, but I think the signal issues have started since I flashed the original orange fw with NeatRom v5.6.
From searching on my pc, I've found my original orange brand fw, which was: I9100PXXLSS_I9100PBVLS2_I9100PORALS6_HOME.tar
Now I want to keep Neatrom, but I want to flash the modem and baseband which are showing as I9100XXMS4 on neatrom....I believe these could be the problem. Where can I get the correct versions that correspond to my mobile and network (EE) and how do I correctly flash these?
Thanks!
Come on guys, someone must be able to help me pls? :crying:
Just flash xxlss baseband (if it was ur original fw) in phone category in odin...
Thanks for helping me dr droid. I'll be honest mate... I don't have a clue what to do.
1. Do you have a link to a step by step guide to flash the modem fw and/or baseband? Could you show me?
2. Where do i get the correct baseband file for t-mobile network?
wowandroid said:
Thanks for helping me dr droid. I'll be honest mate... I don't have a clue what to do.
1. Do you have a link to a step by step guide to flash the modem fw and/or baseband? Could you show me?
2. Where do i get the correct baseband file for t-mobile network?
Click to expand...
Click to collapse
Download the firmware (the actual one which u said was present since the beginning)
Open the fw package with winrar
U will see a modem.bin file
Extract it to a known location
Connect phone in Download mode.
Open odin
Click on phone tab and then select ur extracted modem.bin
Flash ...
doctor_droid said:
Download the firmware (the actual one which u said was present since the beginning)
Open the fw package with winrar
U will see a modem.bin file
Extract it to a known location
Connect phone in Download mode.
Open odin
Click on phone tab and then select ur extracted modem.bin
Flash ...
Click to expand...
Click to collapse
Thanks very much dr droid. The problem I have is that I've only got the original nandroid backup with the following files:-
boot.img
cache.img
data.img
nandroid.md5
system.img
I extracted these using yaffey, but there is no file called modem.bin. Could you please tell me where it is located?
If this is not possible, where can I download the original orange fw with the following details:-
(MODEL: GT-I9100P
ANDROID VERSION: 2.3.4
BASEBAND VERSION: I9100PBVKI2
KERNEL: [email protected] #2
BUILD NO: GINGERBREAD.BVKI3)
Nandroid backups don't include the modem. Download the entire rom from Samfirmware, extract the modem.bin from that, flash as previously instructed.
Thanks mistah.
I've just done that, but it seems that my mobile's fw does not exist on their site anymore:-
Model: GT-I9100P
Product Code: GT-I9100LKNORA
Hidswver: I9100PBVKI3/I9100PORAKI3/I9100PBVKI2/I9100PBVKI3
Filename: I9100PBVKI3_I9100PORAKI3_ORA.zip
File not found
Find the most recent firmware for your country/carrier, download it, extract the modem.bin from it, flash that. If you get no joy from that, try another modem from another rom for your country/carrier. Modems are cross-compatible between roms & don't need to be used with a rom that's the same Android version/whatever, E.G - you can use modems that came bundled with GB roms if you're currently running ICS or JB & vice versa, etc, etc. Basically you can use any modem for the I9100, though I wouldn't recommend using modems specified as being for the I9100T unless you've tried every other modem first as these are specifically 'tuned' for the I9100T/the networks of carriers which sold it.
If you find none of the modems bundled with stock roms released by your carrier work for you, you can either:-
A) Root your phone, and start flashing any CWM flashable modem you can get your hands on (there are dozens, obviously - one for each stock rom released by each carrier around the world, there will be several for each carrier at least). This will be easier than downloading several dozen roms & extracting the modem.bin for each if you do get to this stage
and/or
B) Service centre/local mobile repair shop, though I would be doing A & trying as many modems as I could find on here (you will find dozens with an XDA or Google search) before doing that given that involves parting company with money.
MistahBungle said:
Find the most recent firmware for your country/carrier, download it, extract the modem.bin from it, flash that. If you get no joy from that, try another modem from another rom for your country/carrier. Modems are cross-compatible between roms & don't need to be used with a rom that's the same Android version/whatever, E.G - you can use modems that came bundled with GB roms if you're currently running ICS or JB & vice versa, etc, etc. Basically you can use any modem for the I9100, though I wouldn't recommend using modems specified as being for the I9100T unless you've tried every other modem first as these are specifically 'tuned' for the I9100T/the networks of carriers which sold it.
If you find none of the modems bundled with stock roms released by your carrier work for you, you can either:-
A) Root your phone, and start flashing any CWM flashable modem you can get your hands on (there are dozens, obviously - one for each stock rom released by each carrier around the world, there will be several for each carrier at least). This will be easier than downloading several dozen roms & extracting the modem.bin for each if you do get to this stage
and/or
B) Service centre/local mobile repair shop, though I would be doing A & trying as many modems as I could find on here (you will find dozens with an XDA or Google search) before doing that given that involves parting company with money.
Click to expand...
Click to collapse
Thanks very much Mistah.
1. I've checked on Sammobile.com and there are new i9100P orange firmwares, but since I've now moved to t-mobile, can I still use these? Also does it matter if my phone is a "P" variant?
2. My phone is already rooted with NeatRom v5.6, so how do I:-
a. Backup the current modem incase I flash the wrong modem or mess up?
b. Flash the new modem?
OK...Some clear thinking required...
1) Basically you can use any modem for the I9100 (this includes the I9100P)
2) You can't back up a modem, or not easily at any rate. And you don't need to given how easy they are to flash. If you want to go back to a previous modem, simply re-flash it. If you don't have a copy of your current modem, you might want to find a copy of it somewhere before you go flashing something else (not sure why that would be important to you given your current modem is giving you no connectivity, but, anyways...).
3) CWM flashable modems are flashable in the same manner as any other mod/kernel/rom in CWM. You should already know how to flash stuff in CWM if you're running a custom rom, if you don't, you need to start doing some searching (and how did you get a custom rom on your phone if you didn't know how to flash with it ?).
Right. I've given you more than enough info & won't be posting further to this thread, this stuff is really very simple, and we have guides/tutorials (most of which are stickied near the top of the General section) you can read if you need further info, and everything you've asked can easily be found with a search.
Up to you now...
MistahBungle said:
OK...Some clear thinking required...
1) Basically you can use any modem for the I9100 (this includes the I9100P)
2) You can't back up a modem, or not easily at any rate. And you don't need to given how easy they are to flash. If you want to go back to a previous modem, simply re-flash it. If you don't have a copy of your current modem, you might want to find a copy of it somewhere before you go flashing something else (not sure why that would be important to you given your current modem is giving you no connectivity, but, anyways...).
3) CWM flashable modems are flashable in the same manner as any other mod/kernel/rom in CWM. You should already know how to flash stuff in CWM if you're running a custom rom, if you don't, you need to start doing some searching (and how did you get a custom rom on your phone if you didn't know how to flash with it ?).
Right. I've given you more than enough info & won't be posting further to this thread, this stuff is really very simple, and we have guides/tutorials (most of which are stickied near the top of the General section) you can read if you need further info, and everything you've asked can easily be found with a search.
Up to you now...
Click to expand...
Click to collapse
No worries mate. Thanks for your help and advice.
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.
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.