Jump to content

HTC EVO 4G LTE


P_M_G

Recommended Posts

That's really interesting. Sometimes my dialer codes work. Other times they don't. I was having a problem getting voicemail in the app. But it was only sometimes. Seems to be working correctly lately, but I wasn't able to use a dialer code correctly this morning.

 

Is there a change log between .3 and .4?

 

Sent from my EVO using Tapatalk

Besides fixing the data roaming issue, the only other change that I'm aware of is that the problems with trying to install the RUU from Windows 8/8.1 machines has been resolved. Installed mine from a Win7 machine, so I can't confirm that personally.

Link to comment
Share on other sites

  • 2 weeks later...

To htc's credit, the evo is now 2 years old. The point where phones are cut off like a wobbly semi-coherent drunk at a club.

  • Like 1
Link to comment
Share on other sites

I'm still having intermittent trouble with dialer codes and voicemail notifications. Did anyone download the .4 RUU and find these things fixed?

 

Sent from my EVO using Tapatalk

I tried the .4 update, for some reason my bluetooth would not work anymore and I was still having problems with voicemail notifications. Going back to the .3 update and see what happens.

Link to comment
Share on other sites

  • 2 weeks later...

Can the ota be taken if you have already flashed HTCs ruu's they put out for 4.3 and later bug fixes?

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Can the ota be taken if you have already flashed HTCs ruu's they put out for 4.3 and later bug fixes?

 

Sent from my Nexus 5 using Tapatalk

No you can't. Would not even see the update

 

Sent from my EVO using Tapatalk

  • Like 1
Link to comment
Share on other sites

No you can't. Would not even see the update

 

Sent from my EVO using Tapatalk

More importantly, if you have updated to 4.3, your phone is no longer vulnerable to heartbleed.

  • Like 3
Link to comment
Share on other sites

More importantly, if you have updated to 4.3, your phone is no longer vulnerable to heartbleed.

Well, duh! That's why I haven't seen it - I'm on the 1.4 release. I'll still have to check my wife's Evo when she comes back from her trip though, she hasn't updated yet (and probably won't).

Link to comment
Share on other sites

  • 1 month later...

The last update for heartbleed seemed to stop my device from roaming. Anyone else experience this issue?

I think you can flip roaming on in the settings.

Link to comment
Share on other sites

  • 3 weeks later...

Do any of you guys know how I could return my EVO LTE to to 4.1.1?  I tried using an older ruu, but it failed.

Are you rooted?  As a reminder to run an ruu your boatloader will have to be locked or it will fail.  If you are s-off though you can run it using fastboot commands.

Link to comment
Share on other sites

Are you rooted?  As a reminder to run an ruu your boatloader will have to be locked or it will fail.  If you are s-off though you can run it using fastboot commands.

 

No I'm not rooted.  I've tried a few different ruu's now so I guess rooting and flashing via fastboot will be the way to go?

Link to comment
Share on other sites

No I'm not rooted.  I've tried a few different ruu's now so I guess rooting and flashing via fastboot will be the way to go?

What are you trying to accomplish anyway?

Link to comment
Share on other sites

What are you trying to accomplish anyway?

 

No kidding.  The EVO LTE?  Its time has come and gone.  Put it to rest...

 

6b8bfd4d_328377-vlcsnap_00234_super.jpeg

 

AJ

  • Like 1
Link to comment
Share on other sites

Just trying test on a 4.0 or 4.1 android device for an application.

 

Sent from my Nexus 5 using Tapatalk

I am getting a little bit confused, if you are not rooted aren't you already on jellybean?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...