Is it possible to dump the G1's Radio? I know a lot of GSM users would DIE to have this radio, including myself.
The G1 runs the same processor(MSM7201A) as the Diamond, Touch Pro, and Touch HD. I'm sure there are others that I'm missing too but the radio from this device could benefit thousands of US T-Mobile users who are using the above mentioned devices to obtain US T-Mobile 3G.
I think it is a project worth looking into. What do you think?
Not trying to hijack, but simply add to the question...
On the reverse note, would it be possible to flash a TouchPro/TouchHD/Diamond radio to the G1? If it were possible, would this give us the ability to use AT&T 3g with the G1??
Certainly a valid question. I hope this takes off. If it does and people figure out how to flash a Diamond/Touch Pro/HD Radio ROM to the G1 that would benefit thousands of AT&T users as well. It would simultaneously help... Everyone.
dharvey4651 said:
Is it possible to dump the G1's Radio? I know a lot of GSM users would DIE to have this radio, including myself.
Click to expand...
Click to collapse
You can find the radio software in any standard G1 update file. Just unzip it and grab the radio.img file from the root of the zip directory.
Azlum said:
On the reverse note, would it be possible to flash a TouchPro/TouchHD/Diamond radio to the G1? If it were possible, would this give us the ability to use AT&T 3g with the G1??
Click to expand...
Click to collapse
Impossible. G1 only contains power amplifiers for two UMTS bands: 1700(AWS) and 2100. AT&T operates on 850 and 1900. You can flash all the software you want, but without the hardware to communicate with, you'd be going nowhere fast.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Would it be possible to take the G1 Radio(which you say is a .img file) and make it work on a Windows based device ex. HD(which uses a .nbh extension for it's radio) at all? If the hardware is really that different than it may not be possible but I'm still keeping my fingers crossed.
dharvey4651 said:
Would it be possible to take the G1 Radio(which you say is a .img file) and make it work on a Windows based device ex. HD(which uses a .nbh extension for it's radio) at all? If the hardware is really that different than it may not be possible but I'm still keeping my fingers crossed.
Click to expand...
Click to collapse
Well given that the baseband software package is mostly undocumented, I couldn't say whether or not a radio from G1 would work on any other HTC device (especially one operating on different wcdma bands). The likelihood is probably higher if the radios are intended for devices with the same baseband processor?
As for NBH, G1 has them too. However, NBH packages are reserved for HTC's use. End users update G1 system software in Android's recovery tool. For that reason there are currently no publically available G1 NBH files to analyze. Perhaps the WinMo subforums would be a better place to investigate repacking a radio.img into a .nb file.
What are you trying to do with the G1 radio?
My definite goal is to take the 1700Mhz radio from the G1 and port it to other HTC devices with the same processor such as the Diamond, Touch Pro, and HD. Doing so would enable T-Mobile US users of these devices to use T-Mobile's 3G network and not just stuck with edge which is possibly slower than Sprint's 1X. Too slow for me and quite a few others I'm sure.
dharvey4651 said:
My definite goal is to take the 1700Mhz radio from the G1 and port it to other HTC devices with the same processor such as the Diamond, Touch Pro, and HD. Doing so would enable T-Mobile US users of these devices to use T-Mobile's 3G network and not just stuck with edge which is possibly slower than Sprint's 1X. Too slow for me and quite a few others I'm sure.
Click to expand...
Click to collapse
Do those devices actually have 1700MHz WCDMA power amplifiers?
jashsu said:
Do those devices actually have 1700MHz WCDMA power amplifiers?
Click to expand...
Click to collapse
I couldn't tell you. I'm not sure if they do or not. I guess I was hoping someone else would know the answer to that one.
dharvey4651 said:
I couldn't tell you. I'm not sure if they do or not. I guess I was hoping someone else would know the answer to that one.
Click to expand...
Click to collapse
Since T-Mo is the only US carrier using 1700 AWS, it's highly unlikely any handset you get outside of T-Mo will have a 1700 AWS power amp. Without the hardware for 1700 AWS (aka UMTS Band IV) none of those devices will connect to T-Mo USA's 3G network. G1 also has a power amp for 2100 MHz but I believe that is used for T-Mo's European buildout.
this seems like a very interesting project. id be interested in getting a G1 radio working on my touch pro
any new news on finding a way to dump the G1 radio rom?
Related
Would it hurt to try to flash the Rogers Dream radio to our Dreams and see if it unlocks those magical UMTS 850 / 1900 bands? There were people screaming that it was a purely hardware limitation (reminds me of those people who said that there could be no performance benefit from overclocking, but they were wrong).
It really couldn't hurt to try, of course. Anyone got the Rogers radio lying around?
I totally agree with you If someone gets the radio update, i will flash on my dream and make the tests!
I've noticed that the radio version from Rogers is the same one from Sapphire (3.22.20.17)
duperin said:
I totally agree with you If someone gets the radio update, i will flash on my dream and make the tests!
I've noticed that the radio version from Rogers is the same one from Sapphire (3.22.20.17)
Click to expand...
Click to collapse
The only problem is SPL compatibility... we don't know, and I hope nobody gets brick
UMTS on AT&T would be amazing.
coolbho3000 said:
The only problem is SPL compatibility... we don't know, and I hope nobody gets brick
UMTS on AT&T would be amazing.
Click to expand...
Click to collapse
Even if I already have the latest SPL installed (1.33.2005)?
I thought the brick thing happens only if you tries to flash the SPL without the latest radio ... now I'm scared
But if the SPL reads the Rogers radio as an older radio, it would be the same effect as downgrading our radio to on older one, aka bricking the phone.(as far as we know...i don't think anyone has actually tried to downgrade radios after installing H's SPL..)
jamesd86 said:
But if the SPL reads the Rogers radio as an older radio, it would be the same effect as downgrading our radio to on older one, aka bricking the phone.(as far as we know...i don't think anyone has actually tried to downgrade radios after installing H's SPL..)
Click to expand...
Click to collapse
I think someone did, they bricked.
jamesd86 said:
But if the SPL reads the Rogers radio as an older radio, it would be the same effect as downgrading our radio to on older one, aka bricking the phone.(as far as we know...i don't think anyone has actually tried to downgrade radios after installing H's SPL..)
Click to expand...
Click to collapse
Someone tried the RC33 radio after successfully flashing H's SPL and bricked their phone. It's unknown if different radios would have the same effect, but it's a definite risk.
I'm curious about this myself, even though it wouldn't really help me since I use TMo. First step is to find out what radio chip both versions of the handset use, and whether simply flashing the firmware image can change the frequencies. At first guess, I would think it's possible, but at the same time I've never heard of anyone doing it.
hahahaha
you guys are hilarious
breaultm said:
hahahaha
you guys are hilarious
Click to expand...
Click to collapse
Care to explain why?
Ahh, the demise of the XDA forums.
I am very interested in this myself. I have taken my g1 apart and it has a stand alone umts radio connected to the main board via an 80mm coaxial cable. i am not sure if it will flash but i do know that the antenna should be different. It is supossed that the anntena for the 1700 and 2100 freqs it different than the 850 1900 ones. maybe this unit could be swapped betwen phones. I am willing to test on my G1 if you can figure this out.
Maybe I am missing something you guys are saying but the Dream doesnt have a quad band umts radio. It is only set up for TMo's 1700/2100 bands. Software wouldnt help that. You would need new software AND a new radio that could connect to the ATT bands.
chuckhriczko said:
Maybe I am missing something you guys are saying but the Dream doesnt have a quad band umts radio. It is only set up for TMo's 1700/2100 bands. Software wouldnt help that. You would need new software AND a new radio that could connect to the ATT bands.
Click to expand...
Click to collapse
Mmm. Kinda.
However, if the Rogers one is a Drea100 or Drea200 like the european devices, then it should have the same hardwareinside and it is possible if we can find the right combos of ROM and Radio.
oneof the good things of HTC using the qualcomm chipsets is that they are just governed by software in many cases, but the chipset has the same features...just not all activated.
Exactly. It is VERY common for a manufacturer to build one part and use software to control what features it has. CPU manufacturers have been doing it forever. Sometimes it is a question of fuse bits, which permanently disable a feature beyond recovery, though very often, its just a soft switch.
In fact, someone from google (I know they're not HTC) stated specifically upon my query (several months ago) that the hardware WAS quad band, just not enabled in software. Now how knowledgeable this fellow was, I can't say, but presumably being in the position to respond to questions publicly on google's forums, he must be required to answer questions truthfully or at least not answer at all... lies couldn't be tolerated. Unless he overstepped his bounds and his knowledge in the answer.
coolbho3000 said:
Would it hurt to try to flash the Rogers Dream radio to our Dreams and see if it unlocks those magical UMTS 850 / 1900 bands?
Click to expand...
Click to collapse
Hmm...
coolbho3000 said:
It really couldn't hurt to try, of course. Anyone got the Rogers radio lying around?
Click to expand...
Click to collapse
coolbho3000, meet coolbho3000.
maxawesome said:
Hmm...
coolbho3000, meet coolbho3000.
Click to expand...
Click to collapse
haha
that's good
If I have an 802.11b Wi-fi NIC in my computer, installing drivers for an 802.11g version of the same NIC will not make my NIC operate at that frequency. Furthermore, if those drivers removed the capability to use 802.11b frequencies, my NIC will now no longer connect to anything.
I think at this point the question is: does the radio support all 4 data frequencies (850/1900/1700/2100).
My understanding at this point is: No.
Ask yourself -- why would HTC wait so long to release the G1 in Canada if not because they had to manufacture a phone with different radio hardware to meet Canadian broadcasting requirements?
maxawesome said:
If I have an 802.11b Wi-fi NIC in my computer, installing drivers for an 802.11g version of the same NIC will not make my NIC operate at that frequency. Furthermore, if those drivers removed the capability to use 802.11b frequencies, my NIC will now no longer connect to anything.
I think at this point the question is: does the radio support all 4 data frequencies (850/1900/1700/2100).
My understanding at this point is: No.
Ask yourself -- why would HTC wait so long to release the G1 in Canada if not because they had to manufacture a phone with different radio hardware to meet Canadian broadcasting requirements?
Click to expand...
Click to collapse
The fact that it's a custom build perhaps?
the qualcom chip supports at&t frequencies BUT its output doesnt go directly to the antenna, it goes through amplifiers first... the t-mobile g1 has two amplifiers for the t-mo frequencies only... I really hope im wrong cause i have a T-mo G1 in canada and i have to spend 700$ to get 3G (which im paying anyway but only get edge). Anyways this pic might help you out...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I trust it cause its from ubm tech:
http://ubmtechnology.com/
Here's some pictures of the guts of a Canadian HTC Dream, compared with the G1: http://img26.imageshack.us/gal.php?g=1000387n.jpg
It's the same "base" radio chip, with different numbers below. According to the Qualcomm specifications site, the chip should be able to handle ANY 3G frequencies.
Please stop using the rom version space as a spot to put your rom's name. I just called sprint customer support and they told me that a simple version check on the phones reported back roms that were not built by their team....then the tech proceeded to read off the exact info that my phone displayed. It's not good when sprint can simply ping our device and see that it's reporting back custom rom names, version numbers and everything. This really puts a damper on things when you need to do a device exchange for something that's totally unrelated to anything flashing could do.
Or you could just flash your phone back to stock when you need support. Like we've always done.
One does not simply tell devs what to do.
*Sent from Nexus S*
or you can open your build.prop file with root explorer and write in "sprint sucks"(or anything else) instead
063_XOBX said:
Or you could just flash your phone back to stock when you need support. Like we've always done.
Click to expand...
Click to collapse
Exactly.
simms22 said:
or you can open your build.prop file with root explorer and write in "sprint sucks"(or anything else) instead
Click to expand...
Click to collapse
haha.. Oh man.. The fun we could have.
"ro.modversion=This_Is_Dan_Hesse_Get_Back_To_Work_And_Stop_Being_Big_Brother"
styckx said:
"ro.modversion=This_Is_Dan_Hesse_Get_Back_To_Work_And_Stop_Being_Big_Brother"
Click to expand...
Click to collapse
this is good.
heres an older screenshot of some build.prop edits in about phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:laugh: QuadCore Jesus Phone....
You should tell sprint to basically stfu. Stop delaying updates and don't worry about what software is on your phone period.
hp420 said:
Please stop using the rom version space as a spot to put your rom's name. I just called sprint customer support and they told me that a simple version check on the phones reported back roms that were not built by their team....then the tech proceeded to read off the exact info that my phone displayed. It's not good when sprint can simply ping our device and see that it's reporting back custom rom names, version numbers and everything. This really puts a damper on things when you need to do a device exchange for something that's totally unrelated to anything flashing could do.
Click to expand...
Click to collapse
Personally I don't think it's any of Sprints business what WE do with OUR phones and DEVS do with THEIR roms. As long as the bills paid they can kiss it in my personal opinion. Not as if anyone at a call center really knows what they are talking about anyhow. They are all reading from prompters and how to guides anyhow. Most of Sprint issues are on THEIR side anyways. WE obviously can't tell Sprint what to do.
063_XOBX said:
Or you could just flash your phone back to stock when you need support. Like we've always done.
Click to expand...
Click to collapse
yes, well I didn't exactly expect the employee to ping my build.prop from her machine, so it never occurred to me that I may have to flash stock just to call them. Obviously if I had gone down to a store or repair center I would have gone completely stock with a fresh wipe to look as if I had just tried restoring my phone to fix any issue. But like I said, it never even crossed my mind that I would have to be paranoid about it and flash just before calling them.
BTW, I totally agree....it's none of their damn business what firmware I'm running!!! I don't remember signing anything saying I would agree to keep stock firmware and kernel on the device the whole time in order to keep my service/warranty active!! I actually distinctly remember the conversation i had with the mobile dept manager at best buy when I bought my ns4g...and he told me they would accept a return for exchange with a device that's got an unlocked bootloader, custom rec, has been flashed & is rooted, etc He even told me if it got smashed to pieces the warranty would cover it. I'm not sure how truthful the last part is, but he said it
anyway, my point is we now have proof that they can ping your device and read what build you are running....and we know that means we have to be extra careful when calling too, not just visiting a store.
oh, btw...she also told me that the last attempt I made at an ota was in may when ics was released...so the fact that I had a jb build number proved I had been flashing. This means we also now know we need to take an additional step to update to the newest version via OTA at least one time prior to contacting support.
I guess its good into to know for those on sprint. But in the end screw them. I would not for a second change anything or worry one bit about it. If they gave me any crap I would tell them to f off and kill my plan and I would never pay it.
Like I did years ago over a beef with them. I was so furious with them and I actually wanted to hear from the CEO. Told them f off. Told the debt collectors to screw off. Just thinking about that nightmare again got me ticked off.
I'm on the Verizon gnex ...do you think the note3 will have a thriving development community. With kitt kat coming...will updates be timely. Also with a QUALCOMM processor will unlocking the bootloader be a problem?
chefb said:
I'm on the Verizon gnex ...do you think the note3 will have a thriving development community. With kitt kat coming...will updates be timely. Also with a QUALCOMM processor will unlocking the bootloader be a problem?
Click to expand...
Click to collapse
its at the point if you want to mod your phone it will be time to leave verizon. the s4 originally was hacked but a update killed that and the update i believe has not been hacked. the bootloaded will be locked on verizon....either stay and hope they crack it or speak with your money
My vote is that root will be achieved but if we get bootloader access we will have to be quick about it since Verizon WILL push an update immediately. But I suspect Verizon has Samsung really locking the bootloader up tight and using the experience they gain from every device prior on what fuses to blow.
cwalker0906 said:
its at the point if you want to mod your phone it will be time to leave verizon. the s4 originally was hacked but a update killed that and the update i believe has not been hacked. the bootloaded will be locked on verizon....either stay and hope they crack it or speak with your money
Click to expand...
Click to collapse
The S4 update is rooted, but the new bootloader is still locked. A workaround is in progress.
RaptorMD said:
My vote is that root will be achieved but if we get bootloader access we will have to be quick about it since Verizon WILL push an update immediately. But I suspect Verizon has Samsung really locking the bootloader up tight and using the experience they gain from every device prior on what fuses to blow.
Click to expand...
Click to collapse
You never know what's floating around on the dark corners of the internet. Pre-release kernels from shows/conference's (like IFA) N3 system dumps might already be being combed through for exploits :silly:
docnok63 said:
The S4 update is rooted, but the new bootloader is still locked. A workaround is in progress.
You never know what's floating around on the dark corners of the internet. Pre-release kernels from shows/conference's (like IFA) N3 system dumps might already be being combed through for exploits :silly:
Click to expand...
Click to collapse
One can only hope
The night is dark and full of terrors
docnok63 said:
The S4 update is
You never know what's floating around on the dark corners of the internet. Pre-release kernels from shows/conference's (like IFA) N3 system dumps might already be being combed through for exploits :silly:
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2381382
IamPro said:
The night is dark and full of terrors
Click to expand...
Click to collapse
http://i.imgur.com/iY9zigm.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
docnok63 said:
http://i.imgur.com/iY9zigm.jpg
Click to expand...
Click to collapse
docnok63 said:
You never know what's floating around on the dark corners of the internet. Pre-release kernels from shows/conference's (like IFA) N3 system dumps might already be being combed through for exploits :silly:
Click to expand...
Click to collapse
And so it begins...
Keep em coming!
<removed private messages>- jcase
谢谢 来学习一下
summer.peak said:
谢谢 来学习一下
Click to expand...
Click to collapse
I'm not even sure what that means (please speak English), but if you're referring to the allegedly insecure boot.img you posted, that's possibly really good news for N9005 users. It will not help Verizon users at all as each bootloader is carrier specific.
<Dont share private messages, nor create false drama> - jcase
You heard it hear first folks: http://www.androidpolice.com/2013/0...nd-maxx-makes-flashing-custom-roms-a-reality/
SWEET!!!!!!!!!!!!!!!!!!!
Even if there's no way through the new Samsung security...there's already a way around it:
http://www.androidcentral.com/galax...active-now-have-safestrap-support-rom-loading
docnok63 said:
Even if there's no way through the new Samsung security...there's already a way around it:
http://www.androidcentral.com/galax...active-now-have-safestrap-support-rom-loading
Click to expand...
Click to collapse
I find this news promising... but what are the chances of there being a developer addition note...?
chefb said:
I find this news promising... but what are the chances of there being a developer addition note...?
Click to expand...
Click to collapse
I'd say there's a pretty good chance. The problem, in my eyes, is that DE variants aren't released until 5-10+ weeks after the device goes to the carrier. I'd rather put my faith in the dev community and enjoy my new phone all that time. As I've said before (not sure if this thread or not), early adoption is the key to unlocking and rooting. You don't want to pick up a phone after the first OTA is released by Verizon. They'll have most certainly patched the bootloader exploit (new S4 builds are a prime example and so was the DNA).
why does your service provider verizon block custom roms? what it to them if you install what you want? sounds a bit farked to me...
entwicklun said:
why does your service provider verizon block custom roms? what it to them if you install what you want? sounds a bit farked to me...
Click to expand...
Click to collapse
They don't want you to remove the Verizon bloat preloaded on the phone and lose potential revenue.
The last time I had an HTC phone, HTC provided a bootloader unlocking tool for phones bought on contract through carriers. Is this still the case? I'd probably end up having a Verizon model.
http://forum.xda-developers.com/htc-10/how-to/unlockable-bootloader-t3357220
The GSM version will be unlockable. Unknown if Verizon will screw that up or not.
Responding to my question, Jeff Gordon - Senior Global Online Communications Manager at HTC Corp said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
God dam it. What is this bs with unlockable bootloader lately. This was my #1 choice. Now I guess I'll have to wait for the next nexus.
Sent from my Nexus 5 using XDA-Developers mobile app
@nitramus I think you have misread. For the 10 if you buy direct from HTC, it looks like the bootloader will be unlocked out of the box. If you buy from a service provider, it may be locked, but can be unlocked via the HTC website.
Might be because English is not my primary language but when I read this what I get is that it can not be unlocked.
nitramus said:
Might be because English is not my primary language but when I read this what I get is that it can not be unlocked.
Click to expand...
Click to collapse
Yeah, you're not reading it correctly. HTC is still offering dev unlocking. You will be able to unlock it.
Sweet, thanks!
Awesome news, I hope verizon doesn't screw this up...
Sent from my SM-G930V using XDA-Developers mobile app
gleggie said:
Awesome news, I hope verizon doesn't screw this up...
Sent from my SM-G930V using XDA-Developers mobile app
Click to expand...
Click to collapse
Verizon branded devices are NOT unlockable through HTC Dev. Verizon requests that HTC block their branded devices from that service. Verizon users must rely on Java card or software exploits such as sunshine to be updated to work with the 10.
Behold_this said:
Verizon branded devices are NOT unlockable through HTC Dev. Verizon requests that HTC block their branded devices from that service. Verizon users must rely on Java card or software exploits such as sunshine to be updated to work with the 10.
Click to expand...
Click to collapse
Thanks for the info, would a carrier unlocked HTC 10 work on Verizon? I've been hearing mixed information
Sent from my SM-G930V using XDA-Developers mobile app
gleggie said:
Thanks for the info, would a carrier unlocked HTC 10 work on Verizon? I've been hearing mixed information
Sent from my SM-G930V using XDA-Developers mobile app
Click to expand...
Click to collapse
That's kind of tough to answer. First, according to the specs on HTC's page it does have the correct LTE and CDMA radios to work on Verizon. That being said, you would still have to get the device activated on Verizon's Network and that can be difficult with devices Verizon does not carry.
Second, responses from official HTC employees (e.g. Mo Versi and others) state that you will need to purchase the Verizon branded model, once available, to get full support. Seems to be intentionally vague. The answer to your question: it may well work and it may well not, you have to roll the dice to find out.
Behold_this said:
That's kind of tough to answer. First, according to the specs on HTC's page it does have the correct LTE and CDMA radios to work on Verizon. That being said, you would still have to get the device activated on Verizon's Network and that can be difficult with devices Verizon does not carry.
Second, responses from official HTC employees (e.g. Mo Versi and others) state that you will need to purchase the Verizon branded model, once available, to get full support. Seems to be intentionally vague. The answer to your question: it may well work and it may well not, you have to roll the dice to find out.
Click to expand...
Click to collapse
I'm wondering if someone will figure out how to trick Verizon into thinking the unlocked version is one of its own.
Ajfink said:
I'm wondering if someone will figure out how to trick Verizon into thinking the unlocked version is one of its own.
Click to expand...
Click to collapse
You'd need to change the device CID to match Verizon's to trick them. For that, s-off is required, bootloader unlock will not give required access to change that.
Just read an article that T-Mobile and AT&T have rolled out Android 3.0 so I decided to check.
Lo' and behold, Verizon is right in lock step!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Got it as well and so far it's running smoothly
You guys have any luck when accessing the Chat Settings in Samsung Messages or are you getting an error as well?
pimpmaneaton said:
You guys have any luck when accessing the Chat Settings in Samsung Messages or are you getting an error as well?
Click to expand...
Click to collapse
Yeah getting an error here.
denson9874 said:
Yeah getting an error here.
View attachment 5161987
Click to expand...
Click to collapse
That's a different one than I am getting.
Man I haven't got the update yet and I been checking everyday lol
Is there any reason why the firmware still isn't able to download through Frija or elsewhere?
Got Mine
Got the update as well, and also got the error message when trying to use the chat features in Samsung Messages. Ran around with Verizon and Samsung and the gist of it is that it's a Samsung Messages error that will need an app update for.
I don't know if I want to use it anymore, though, because I thought it was going to use the Google RCS but it looks like it's only going to use the VZW version which, my understanding is, only works with other VZW customers with the approved phones. So looks like I'll stick with Google Messages.
what finally??? the whole world is getting it in January.
adj998 said:
Is there any reason why the firmware still isn't able to download through Frija or elsewhere?
Click to expand...
Click to collapse
I have the link to my uploaded firmware, downloaded from Frija. Here you go.
denson9874 said:
I have the link to my uploaded firmware, downloaded from Frija. Here you go.
Click to expand...
Click to collapse
I appreciate the reference but the VZW firmware is CTL4 and the update comes with a way to enable low band 5G so I need that specific firmware, I appreciate the help though!
adj998 said:
I appreciate the reference but the VZW firmware is CTL4 and the update comes with a way to enable low band 5G so I need that specific firmware, I appreciate the help though!
Click to expand...
Click to collapse
I'm pretty low band 5G is enabled on CTL2 as well
denson9874 said:
I'm pretty low band 5G is enabled on CTL2 as well
View attachment 5162417
Click to expand...
Click to collapse
yeah, I decided to say **** it and just flash CTL2. If I have to, I'll roll back in the future and reupdate to be on official VZW. It's not like I haven't done it before lol
adj998 said:
yeah, I decided to say **** it and just flash CTL2. If I have to, I'll roll back in the future and reupdate to be on official VZW. It's not like I haven't done it before lol
Click to expand...
Click to collapse
Lol join the f**k and flash crew. It's almost customary for me to download every firmware for each compatible region and see what flashes and what doesn't lol. Call me reckless.
denson9874 said:
Lol join the f**k and flash crew. It's almost customary for me to download every firmware for each compatible region and see what flashes and what doesn't lol. Call me reckless.
Click to expand...
Click to collapse
Right? Lol I still can't get 5G though, I've already swapped 6 SIM cards and nothing. It'll stick for a little while with the new SIM but after a reboot I get sent back to LTE, not even LTE+. Which is weird considering Spectrum uses the exact same towers/firmware as Verizon which is why I was confused as to why I didn't receive the CTL4 update.
adj998 said:
Right? Lol I still can't get 5G though, I've already swapped 6 SIM cards and nothing. It'll stick for a little while with the new SIM but after a reboot I get sent back to LTE, not even LTE+. Which is weird considering Spectrum uses the exact same towers/firmware as Verizon which is why I was confused as to why I didn't receive the CTL4 update.
Click to expand...
Click to collapse
That's odd. I also have the tendency to swap between LTE then 5G but generally it only occurs when I'm on Wi-Fi. After disabling it, it will stays on 5G low band. Might just be the area because VZW just flipped the switch in my area maybe a couple of weeks ago.
This was from 5 minutes ago:
This was right afterwards:
So, it changes quite a bit at times.
I got the update using Verizon firmware. The phone feels fast and 5G low band is the same as before. Now the things I dislike:
1. The Samsung clock font used on the AOD, lockscreen, and notification is a throwback to the S3 days and looks cartoony. The Roboto font was cleaner and more consistent.
2. The battery life is terrible so far. I'm dropping about 10% per hour whereas I could go a full 24 hours before.
I'm going to see if rolling back via ODIN works. Might see if the November Android 10 firmware for the U1 has low band 5G support.
denson9874 said:
That's odd. I also have the tendency to swap between LTE then 5G but generally it only occurs when I'm on Wi-Fi. After disabling it, it will stays on 5G low band. Might just be the area because VZW just flipped the switch in my area maybe a couple of weeks ago.
This was from 5 minutes ago:
View attachment 5162603
This was right afterwards:
View attachment 5162605
So, it changes quite a bit at times.
Click to expand...
Click to collapse
Hmmm might be because I'm on spectrum, so I'm using verizon network but yet at the same time I'm not verizon? I'm constantly stuck on LTE and the speeds, well pretty much suck. I don't complain much as my medical condition keeps me at home 24/7 anyways and I have 200Mbps wifi so I'm not too worried. My only issue is that I paid for a 5G device so I kinda want to see what the hype is about 5G speeds.
adj998 said:
Hmmm might be because I'm on spectrum, so I'm using verizon network but yet at the same time I'm not verizon? I'm constantly stuck on LTE and the speeds, well pretty much suck. I don't complain much as my medical condition keeps me at home 24/7 anyways and I have 200Mbps wifi so I'm not too worried. My only issue is that I paid for a 5G device so I kinda want to see what the hype is about 5G speeds.
Click to expand...
Click to collapse
I get what you mean. I don't think we'll get 5G UW anytime soon in my area but the next closest place that supports it is ATL, so at some point in time I'll go up that way to test what the whole hype is about. I generally use wifi as well, so I got the 20 ultra for the 108MP and future proofing, especially when I get BL unlock and root.