Jump to content

HTC EVO 4G LTE


P_M_G

Recommended Posts

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

I am on Jellybean, but 4.3. I updated with one of the last ruu months ago just to check out Sense 5. I've rooted and tried flashing a few 4.1.1 Roms without much luck. It has been forever since I have rooted and flashed Roms to an HTC device so I'm not very up to date with S-off or anything additional that may be necessary. I guess you could say the Nexus has spoiled me some.

 

I don't recall the ruu throwing a specific error. It just said "failed" and rebooted the phone.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I am on Jellybean, but 4.3. I updated with one of the last ruu months ago just to check out Sense 5. I've rooted and tried flashing a few 4.1.1 Roms without much luck. It has been forever since I have rooted and flashed Roms to an HTC device so I'm not very up to date with S-off or anything additional that may be necessary. I guess you could say the Nexus has spoiled me some.

I don't recall the ruu throwing a specific error. It just said "failed" and rebooted the phone.

Sent from my Nexus 5 using Tapatalk

Oh ok I forgot about the 4.3 method. Anyway I don't think it's possible to flash an older ruu because the newer bootloader from 4.3 won't be compatible with the older ruu which is why it failed. If you were already s-off then it's probably possible though. Rooting and getting s-off might be your only option but without that it's a definite no go.
  • Like 1
Link to comment
Share on other sites

Oh ok I forgot about the 4.3 method. Anyway I don't think it's possible to flash an older ruu because the newer bootloader from 4.3 won't be compatible with the older ruu which is why it failed. If you were already s-off then it's probably possible though. Rooting and getting s-off might be your only option but without that it's a definite no go.

Alright so s-off will be tomorrow's adventure then! Thanks for the help.

 

Sent from my Nexus 5 using Tapatalk

  • Like 1
Link to comment
Share on other sites

  • 2 months later...

Software update for the EVO 4G LTE.

 

Nothing fancy, just a security update. No bump up the Android ladder. Showed up on my wife's phone, but not mine - probably because I'm on the last semi-official update, and she isn't. Not very big, just a little over 16 Mb.

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

    • On Reddit, someone asked (skeptically) if the US Cellular buyout would result in better service.  I'd been pondering this very issue, and decided to cross-post my response here: I've been pondering the question in the title and I've come to the conclusion that the answer is that it's possible. Hear me out. Unlike some of the small carriers that work exclusively with one larger carrier, all three major carriers roam on US Cellular today in at least some areas, so far as I know. If that network ceases to exist, then the carriers would presumably want to recover those areas of lost service by building out natively. Thus, people in those areas who may only have service from US Cellular or from US Cellular and one other may gain competition from other carriers backfilling that loss. How likely is it? I'm not sure. But it's definitely feasible. Most notably, AT&T did their big roaming deal with US Cellular in support of FirstNet in places where they lacked native coverage. They can't just lose a huge chunk of coverage whole still making FirstNet happy; I suspect they'll have to build out and recover at least some of that area, if not most of it. So it'd be indirect, but I could imagine it. - Trip
    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
  • Recently Browsing

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