Does anyone know.... - HTC Rezound

I'm just wondering, I purchased a phone on ebay (not knowing it was flashed/rooted). The boot animation says "clean rom" so after researching this site and the forums for this device, I see that it's probably a rom you guys are familiar with and it seems to be ICS based (from what I can see). With that being said, does this mean when they actually RELEASE the stock ICS that I probably won't get the update to my phone? Because I really would like to see what their stock version will be like. Can anyone answer that question or has it even been asked before?

you can't take the OTA rooted or while unlocked but you can flash the RUU once it gets posted after relocking your phone. hopefully by then we will have s-off.

mighty_markus12 said:
you can't take the OTA rooted or while unlocked but you can flash the RUU once it gets posted after relocking your phone. hopefully by then we will have s-off.
Click to expand...
Click to collapse
So does this mean I will no longer be able to receive updates to my phone with this "s-off" or what ever? That sucks, and I can't seem to follow the steps that have been given to get it back to a stock rom or "ruu" what ever THAT means. lol ****that moment when you realize you might look dumb or "newbish" for posting what you just posted****

Your phone has been hacked a little bit, and it's always going to have tell-tale signs.
The worst case scenario is that you have to manually install the next official update and manually relock the phone, which will always say "Relocked" in the boot menu. But if you do everything by the book you should be able to get it back to stock in every other way, including taking subsequent updates over the air normally.
If they get s-off working and you're willing to experiment, it may be possible to completely revert the phone to stock. But that's quite a bit more hackage in order to get your phone "unhacked."

cpurick said:
Your phone has been hacked a little bit, and it's always going to have tell-tale signs.
The worst case scenario is that you have to manually install the next official update and manually relock the phone, which will always say "Relocked" in the boot menu. But if you do everything by the book you should be able to get it back to stock in every other way, including taking subsequent updates over the air normally.
If they get s-off working and you're willing to experiment, it may be possible to completely revert the phone to stock. But that's quite a bit more hackage in order to get your phone "unhacked."
Click to expand...
Click to collapse
To be honest, the only thing I really want is to be able to get it stock on the basis of the apps, getting system updates etc. I'm not concerned with it having evidence of being "tampered with" "hacked" or "rooted". lol It already says "re-locked" The problem is the instructions I've gotten on here seem to go over my head. I might have to be walked through it like a little 3 or 4 year old being taught to sound out little words for the first time. lol Hey, I'm just saying..... No seriously though, I have a MAC and all of the instructions here seem to be based on having a PC

This can be done. But you're going to need to have somebody who knows what they're doing relock and reset your phone from the official ICS RUU after it's released, probably from a PC. There's nothing can be done before then.

cpurick said:
This can be done. But you're going to need to have somebody who knows what they're doing relock and reset your phone from the official ICS RUU after it's released, probably from a PC. There's nothing can be done before then.
Click to expand...
Click to collapse
So this means I'll need to basically need to take or send it to someone to get this done? I don't know why all of these instructions seem like their in spanish to me now, about 3 years ago I used to flash and unlock WM devices almost every other day. I guess I should've never stopped, but once the g1 came out and switched to android devices I stopped flashing and now I'm lost because I need to "tamper with" my phone again, but can't seem to get going at all. I mean SERIOUSLY, I used to flash WM devices so often that if a certain period of time went by without me finding a rom worth "flashing" I'd start having withdrawals. Now i'm feeling like an absolute IDIOT when it comes to getting into these android devices. I think part of that has to do with the fact that I only had PC's and now not only am I trying to tamper with android for my first time, but I only have mac computers as well.

Go to settings, about phone, software information, more, and write what your baseband version is.

http://forum.xda-developers.com/showthread.php?t=1417839
This thread may help you getting osx and fastboot going so you can relock and run an ruu. As was stated above, what is your baseband? If the previous owner flashed the leaked ics you will not be able to go all the way back to stock until either an official ics is released or the s-off tool is released. Good luck!
Sent from my ADR6425LVW using XDA

Unless you have issues, I would leave it as is for the time being. Take time to learn how to do all the stuff you need to do.
The custom ROMs really do make the phone better, you may find you want to keep it in the end. Battery life is much better on a good ROM.
When the official update comes out, we will have a new ROM based on the update within a day or two at most of the release anyway.
The baseband (the radio firmware) is also important. And unfortunately we can not downgrade to older basebands due to not having S=off. So if you are on the newest leaked version then you can run the old stock software.
BTW S=off (or S=on) is a security flag located in the firmware. S=on limits what parts of the phone you can flash and change. S=off gives you full access, it will allow you to downgrade as well. S=off also makes it easier to brick your phone because it does let you change software that is bootstrap essential, the baseband and hboot (sort of like BIOS) for example.
I separate the idea of bootstrap from boot. Most people associate booting with the OS, but bricking effects the firmware initializing the hardware that allows the OS to load and boot. So you get to see the old school term used.

Kennnny1 said:
http://forum.xda-developers.com/showthread.php?t=1417839
This thread may help you getting osx and fastboot going so you can relock and run an ruu. As was stated above, what is your baseband? If the previous owner flashed the leaked ics you will not be able to go all the way back to stock until either an official ics is released or the s-off tool is released. Good luck!
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
The baseband is 1.22.10.0310r, 1.22.10.0308r It also says clean rom 4.1. I don't mind waiting until an offcial ics is released, but I will I be able to receive THAT instead having to have a "dev equivalent" version is what I'm wondering....

It's like I said. Those radios are new, and part of a firmware upgrade that can't be completely backed out. Your simplest bet is to wait for the official ICS release, and then you (or someone more technical) can apply it manually. After doing that and relocking your phone, it should start to take updates automatically again. You'll also have the full factory-installed "bloatware" suite of software.
It's possible to downgrade all the other parts of your software manually back to the latest stock release, but it's expected that your current upgraded firmware version will continue to prevent you from taking OTA releases. It would be good training, actually, though you'll get better results and more support from a PC than on a Mac. If you figured out how to do all this, then you could get your phone back on the HTC software track yourself.
Depending on your flexibility, maybe you can find someone here you could send your phone to who can put it back on the official release track. But even they won't be able to put a permanent fix on it until the official ICS release comes out and somebody uploads it as a manually-installable package.
---------- Post added at 10:08 AM ---------- Previous post was at 09:29 AM ----------
EDIT:
So did the seller not mention on eBay that the phone had been customized?
Some of the responses lean toward telling you how to flash your phone for yourself. Is that something you'd have any interest in? Do you really want to go back to stock, or do you just want to see the difference?
Are you having any problems with the phone?
The custom ROMs are better, overall, but they usually have one or two bugs that you have to learn to live with. (Which is not to say that stock ROMS are bug-free, though the final versions of stock ROMs tend to be very, very stable.) But if you are on custom ROMs, then you're completely off the automatic update path, and everything will have to be done manually.
So unless you want to learn how to flash your own phone, the only way to get updates is to set it back to stock so HTC and Verizon can handle the updates for you. And therein lies the dilemma, because that in itself is something which must be flashed manually from where you're currently at.
(Oh, and you're probably going to end up losing any of your own customizations in the process, though the data on your SD card should be safe.)

cpurick said:
It's like I said. Those radios are new, and part of a firmware upgrade that can't be completely backed out. Your simplest bet is to wait for the official ICS release, and then you (or someone more technical) can apply it manually. After doing that and relocking your phone, it should start to take updates automatically again. You'll also have the full factory-installed "bloatware" suite of software.
It's possible to downgrade all the other parts of your software manually back to the latest stock release, but it's expected that your current upgraded firmware version will continue to prevent you from taking OTA releases. It would be good training, actually, though you'll get better results and more support from a PC than on a Mac. If you figured out how to do all this, then you could get your phone back on the HTC software track yourself.
Depending on your flexibility, maybe you can find someone here you could send your phone to who can put it back on the official release track. But even they won't be able to put a permanent fix on it until the official ICS release comes out and somebody uploads it as a manually-installable package.
---------- Post added at 10:08 AM ---------- Previous post was at 09:29 AM ----------
EDIT:
So did the seller not mention on eBay that the phone had been customized?
Some of the responses lean toward telling you how to flash your phone for yourself. Is that something you'd have any interest in? Do you really want to go back to stock, or do you just want to see the difference?
Are you having any problems with the phone?
The custom ROMs are better, overall, but they usually have one or two bugs that you have to learn to live with. (Which is not to say that stock ROMS are bug-free, though the final versions of stock ROMs tend to be very, very stable.) But if you are on custom ROMs, then you're completely off the automatic update path, and everything will have to be done manually.
So unless you want to learn how to flash your own phone, the only way to get updates is to set it back to stock so HTC and Verizon can handle the updates for you. And therein lies the dilemma, because that in itself is something which must be flashed manually from where you're currently at.
(Oh, and you're probably going to end up losing any of your own customizations in the process, though the data on your SD card should be safe.)
Click to expand...
Click to collapse
Well, I've kind of decided to just keep what I have. I don't have any issues other and it seems to run smoothly. What I REALLY want to see is what the official update will be like as being "stock released" when it comes out and was concerned that I might not be able to get the update because of the "clean rom" I have now being ICS based (as far as I can see). Other than that, I'm fine until then.

You really should consider leaving negative feedback if they ebay seller did not state in the auction that the phone was rooted and running a custom rom. If I sell a phone and im too lazy to revert it to stock ill ALWAYS state its rooted and what its running in the auction etc

mdunn1066 said:
You really should consider leaving negative feedback if they ebay seller did not state in the auction that the phone was rooted and running a custom rom. If I sell a phone and im too lazy to revert it to stock ill ALWAYS state its rooted and what its running in the auction etc
Click to expand...
Click to collapse
Good point, I mentioned it in the feeback portion and rated him low on the "item described accurately" portion

I would just wait til offiical ics is released. I am sure there will be instructions here on xda on how to relock and flash the new official ics ruu. It will involve downloading some files and entering items into command prompt from PC.
sent from my Rezound

stelv said:
I would just wait til offiical ics is released. I am sure there will be instructions here on xda on how to relock and flash the new official ics ruu. It will involve downloading some files and entering items into command prompt from PC.
sent from my Rezound
Click to expand...
Click to collapse
The problem is I don't HAVE a PC. It's already "re-locked" though. I just want to be able to receive the update without having to deal with any other flashing etc. But from what I was told, I should be able to since the current flashed rom is nearly stock (clean rom) and I'm already re-locked. But I guess we'll just see....

refuse2bstopped said:
The problem is I don't HAVE a PC. It's already "re-locked" though. I just want to be able to receive the update without having to deal with any other flashing etc. But from what I was told, I should be able to since the current flashed rom is nearly stock (clean rom) and I'm already re-locked. But I guess we'll just see....
Click to expand...
Click to collapse
seems like people are giving you information that is kinda all over the place.
Lemme try and help clear this up, since you are in a odd scenario.
You are running cleanrom 4.1 on a re-locked phone. For starters, cleanrom 4.1 is based off the current ics LEAK and is not an official OTA update. Chances are high you won't be able to get the OTA if the rom is not a stock rom, and also because chances are you don't have a stock recovery even though it is relocked. Since you are currently on the latest leaked firmware, not an official firmware, you can run the RUU for the phone and go back to stock. In your case, your kinda lucky with this, as you don't technically need a computer to run it. You would need someone to extract the PH98IMG.zip file from the RUU.EXE file for you to run when the OTA comes out through Hboot.
Be for warned, doing it like this, will wipe all data.
I would say you should run the leaked RUU on the phone, as since it is a beta testing Leak, you should still get the OTA, and that way the phone will think it is completely stock and get the latest update.
If you wanna do this, ask and we can help you.

nosympathy said:
seems like people are giving you information that is kinda all over the place.
Lemme try and help clear this up, since you are in a odd scenario.
You are running cleanrom 4.1 on a re-locked phone. For starters, cleanrom 4.1 is based off the current ics LEAK and is not an official OTA update. Chances are high you won't be able to get the OTA if the rom is not a stock rom, and also because chances are you don't have a stock recovery even though it is relocked. Since you are currently on the latest leaked firmware, not an official firmware, you can run the RUU for the phone and go back to stock. In your case, your kinda lucky with this, as you don't technically need a computer to run it. You would need someone to extract the PH98IMG.zip file from the RUU.EXE file for you to run when the OTA comes out through Hboot.
Be for warned, doing it like this, will wipe all data.
I would say you should run the leaked RUU on the phone, as since it is a beta testing Leak, you should still get the OTA, and that way the phone will think it is completely stock and get the latest update.
If you wanna do this, ask and we can help you.
Click to expand...
Click to collapse
Yes, I'm VERY interested, I'm not worried much about the data wipe, between what's backed up to my google account and my SD card, I'll be fine with a data wipe. My battery life is also HORRIBLE for some reason with this rom, but since I've not had it stock yet, I guess I can't REALLY say it's good or bad. But my Droid Bionic's battery life was at least twice as good as this phone's seem to be and I don't use it any more than I did the Bionic.

I will tell you right now the battery life will most likely get worse if you go to stock.
Now if the person who sold it installed a custom kernel rather than the one Scott includes in his ROM (scott makes clean ROM) then battery life could be worse than it should be.
Second, this is a 4.3 inch HD screen... it eats battery like a starving animal.
Third, try cleanROM developers edition (a very striped out cleaned up stock based ROM) or cleanROM senseless. I am running cleanROM developers edition and I get double to triple the battery life over stock.
Unless I actually use the phone... When I use it a lot, I do not get that big of a jump. When using the phone the battery life will be similar due to the screen and CPU use remains similar to what stock would be. (which you would expect, the screen will always use the same power, same for CPU) Its when the phone is in standby mode that you see the real gains. Because all the extra junk that is in the stock software is pulled out and isn't constantly running in the background, waking the phone, starting the cell radio to phone home, etc.
Senseless and the Developers edition have their quirks caused by removing so much of the stock sense based apps and functions and replacing with AOSP versions. Thinks like the caller ID not showing up on the screen until you unlock the phone because the sense phone/dialer can not talk to the AOSP lockscreen. Nothing major just different.

Related

You guys are confusing

Please don't be angry. I am severely confused over this whole update thing. With the bootloader, and the leaked rom, and the official ota rom.....good lord it's like my mind is trying to hump a doorknob.
Anyway... I have 2.2.2, rooted (although by which method, I cannot remember). I do not have any mods. I have side-loading enabled. I have tethering enabled.
What is the safest way, in plain english, to update to the newest version? I don't know what SBF means, I don't know what CWM means, I don't know what RSD means.
All I want as an end result is a rooted version of the latest, OTA update with an unlocked bootloader.
Please help the ignorant
Edit: I guess I should tell you that I'm in the US on an ATT atrix.
You may want to confirm with someone with more experience, but this worked for me (rooted 1.8.3, OTA 2.5.91), I'm too damn new to even post the link ... pm me I guess hah
k4zyn said:
Please don't be angry. I am severely confused over this whole update thing. With the bootloader, and the leaked rom, and the official ota rom.....good lord it's like my mind is trying to hump a doorknob.
Anyway... I have 2.2.2, rooted (although by which method, I cannot remember). I do not have any mods. I have side-loading enabled. I have tethering enabled.
What is the safest way, in plain english, to update to the newest version? I don't know what SBF means, I don't know what CWM means, I don't know what RSD means.
All I want as an end result is a rooted version of the latest, OTA update with an unlocked bootloader.
Please help the ignorant
Edit: I guess I should tell you that I'm in the US on an ATT atrix.
Click to expand...
Click to collapse
if you do the over the air update you will not have an unlocked bootloader unless you do it before there are custom roms that are just as good and stable as the official ones that will root unlock your bootloader and upgrade if you want to do all of this follow my guide here : http://forum.xda-developers.com/showthread.php?t=1179506
Just to enlighten things a bit...
a SBF (i believe it stands for system binary file?) is a file that contains an official (made by the manufacturer) ROM for a cellphone. The entire operating system and kernel.
RSD (a.k.a. RSDlite) is a software designed by motorola, to use on your computer to install these SBFs on a cellphone via USB connection.
CWM is a piece of software for your phone that is accessible during boot, before the OS loads.
- After installed, to use it, you have to turn on the phone holding both the power button and the volume down buttons. The phone screen will show "fastboot". That's only one option in a series of options that you can scroll through using the "volume down" button, and that you select using the "volume up" button. Scrolling down, you'll find the option "Android Recovery", which will access whatever CWM you put in place.
- It's function is to allow the installation of ROMs and Kernels. Its basically a simpler alternative to RSD, requiring no pc to function.
And to update your device, first you must install RSDlite on your computer, and install the Pudding SBF on your phone using it. After that, You have to install Tenfar's CWM on your phone. Then you'll choose one of the avaiable ROMs (there's the stock one posted up by kennethpenn, a version of the stock one with a few upgrades, and several customized ones), which you will install using CWM.
The detailed steps are on the NOOB GUIDES fixed post on one of the Atrix's foruns, but I beleive those explanations shall make that road a little less bumpier.
Simple answer
Hi I'd just like to add my 2 cents from the update experience.
If you are rooted prior to the update, installing the official update of gingerbread from Motorola will make you lose root privileges-plain and simple.
In my case unlike you I did not have sideloading enabled. That was the only difference in your situation and mine. So that's a question for a Senior member to answer.
If I were you, I'd just go ahead and update regardless. This forum has a lot of information in resurrection of the bricked phones in the 1% chance that it may happen. 99% you will update to the gingerbready awesomeness.
Another piece of advice is that after exploring a lot of features of the stock rom, i felt that the launcher is the Achilles heel of motoblur or blur UI as they call it now. Try using adw launcher?. It's fast and fantastic. Completely customizable.
This ends my 0.02$.
The way to get unconfused is through education. Find a couple of hours and a pen/paper.
Read the wiki here.
Watch the videos here.
Take notes and follow up in the threads, if you have questions.
kind of a noob myself, but find everything pretty simple. This is an awesome ROM with what you are looking for.
http://forum.xda-developers.com/showthread.php?t=1160649
So I need an SD card ey? Hmm. Ok, well, thanks for the info.
I thought we had a wiki somewhere. Oh wait! We DO!
I have a very similar problem on the lines of i have no idea what the hell is going on and what ppl are saying...!!
But what a bigger problem is is that i have a Orange UK version phone, tho i dont use Orange network... and apparently everything is for ATT phones... so im not sure if any of these things are even compatible with my phone...!?! im running froyo 2.2.2 and want to somehow get onto 2.3.4 but just dont know how...?!?!?!

A crash course on the Rezound and modding

There seems to be a lot of confusion about what things are or how they work together so I'm gonna try and build a post to explain some things. If i get any of this wrong, feel free to call me out and I'll correct it. I can generally be relied upon to make mistakes.
First let's start with the various things that you're gonna be hearing about or messing with on your phone.
Hboot or bootloader
This is pretty much the lowest level thing you're gonna mess with. This is what makes the phone boot up, and where you can flash all sorts of things like new hboots, kernels, and whole roms depending on how they are packaged. You can get here by either powering off your phone then powering on with volume down + power, or by selecting "reboot to bootloader" in most custom roms. If you've entered your hboot from a powered off state, you'll start in hboot, also known as the bootloader. The bootloader is where you will load ph98img.zip files, factory reset, boot to recovery, or enter fastboot. Fastboot is the section of the bootloader that will allow you to run fastboot commands from your PC/mac/whatever to load things like boot images, recovery images, return your phone to an s-on state, etc. It's a very powerful interface. From here you have menu options which will allow you to reboot, power off, or return to the bootloader.
If you've entered hboot from the adb reboot bootloader command or your custom rom, you will start in fastboot, and can enter the bootloader from here.
When entering the bootloader using either method, the first thing the phone will do is look for a PH98IMG.zip file. If it finds one, it will want to install it. You'll have the option of installing it, or rebooting. That's it. This is why you want to get rid of the ph98img.zip files from the root of your sd card once you've used them - if you pooch your rom, you're not getting into recovery or fastboot until you remove that file. If you can't boot your phone, you better hope you have another SD card or a micro sd card reader kicking around somewhere. You can boot into fastboot by powering off the phone, then powering it on by holding power and volume down keys at the same time.
A word of warning - this is one of the few places you can actually "brick" your phone. Don't mess around with installing hboots unless you are absolutely certain that you a) have a need and b) have an md5 checksum of the file and have verified that checksum on your own gear. Generally speaking, the only time you need to flash the hboot is when you are upgrading in some way, for example when going from GB to ICS.
Quick note - when people refer to the "SD card patch" they are referring to a patch that allows you to use the GB firmware with ICS roms. This is largely unneeded at this time, since the main purpose was for folks who wanted to run ICS roms without upgrading their hboot - there's no going backward with hboot unless you have s-off.
Radio files
this is how your phone works with the radio. you can brick your phone here, too, so always check md5 before installing, and ask yourself if you really need to be installing it. new radio versions are generally given the credit for things like increased signal strength, faster 3g/4g, better power consumption, etc. these are often paired with a kernel, as well.
Recovery
This is a software layer that you can flash to your phone that allows you to boot the phone into a utility state where you can install roms, flash things like patches or modifications, backup your rom/kernel, etc. When people refer to a nandroid backup, they are referring to a backup made here. It's a snapshot of your phone that lets you mess with things and restore back to that point in time should you screw something up. You pretty much can't brick your phone at this level - it's all just files and filesystems. You can also mount your SD card to reader mode for connection to a computer, do a factory reset of data, and a few other fun things like root your rom here. You should only root your rom if it is a stock rom that has not been rooted yet. Rooting a rooted rom will usually unroot your root so you don't have root.
There are a couple of different recoveries. The rezound community seems to use primarily amon-ra, which is what i use, but there is also clockwork recovery as well. Recovery is usually installed by booting your phone into fastboot and running the "fastboot flash recovery <recovery file>" command. Recovery can also be installed via the flash_image binary found in the RomManager package (ex: flash_image recovery amonra.img). This eliminates the need for fastboot altogether. Just need a terminal, root, and the flash_image binary.
Kernel
This is basically the primary component of an OS. The kernel is where a lot of the functionality of the phone are made or broken. the setting that prevents use of setcpu to change the way the CPU is governed is here. The thing that prevents bluetooth from working right on sense 4 roms? Kernel. Everyone is waiting eagerly for the ICS kernel source to be released so custom kernels can be made that resolve these issues and more. You can flash a kernel via recovery if you've done s-off to your phone, or via a ph98img.zip file in the bootloader. With s-off, kernels can also be backed up in recovery. The kernel is often given much of the credit or blame for the performance of your phone, overheating, etc.
Roms
Your phone's OS, sometimes incorrectly referred to as firmware. It's not - the firmware is the stuff we've already covered that can brick your phone. Think of your phone more as a tiny computer, with the rom being the distribution that you're using. This is pretty apt since it's basically linux, and just like linux, the actual OS is just files and partitions. Because the radio interface layer requires sense, the bulk of our roms are all based on sense roms, and all the functional ones are. Developers modify them to add features, remove bloat or sense components, or take sense roms from other phones and adapt them for our own. You install a rom through recovery.
Never claim to have "bricked" your phone when installing a rom. You can't, and doing so only points out that you don't really know how your phone works. This is embarrassing and best avoided when possible so jerks like me do not tell you what a n00b you are, and to go read threads like this one. Since you're here, we can assume that you've bothered to research things before asking stupid questions, so bravo! In all seriousness, you can no more brick your phone by messing up the rom than you'd brick your PC by screwing up your windows install. You can always start again from the beginning and reinstall. You might lose apps and settings, but this is the nature of the beast. Always nandroid before messing about, and you'll be fine. Nandroid is covered further later on.
RUUs
Strictly speaking, the things that we refer to as RUUs aren't. Everyone calls them that anyway, and I don't see it going away anytime soon. Technically, however, an RUU is HTC's Rom Updater Utility, and it's an executable that gets run on your PC, not something you load to SD card and flash in your bootloader. That said, RUU has come to mean factory signed software/firmware packages that are released by the manufacturer or leaked. They come in the form of a ph98img.zip file that can install pretty much anything - hboot, radio, kernel, rom, etc. What is installed varies from package to package.
Installing an ruu can only be accomplished on a phone that is currently not in an htc dev unlocked state, or a phone that has s-off. when installing one of these that includes an hboot, you'll need to reinstall recovery as well - installing a new hboot via RUU will always require this as the custom recovery is overwritten with the stock recovery.
If your phone has not yet had the s-off procedure done and you intend to do so, make sure the RUU you are about to install does not break the s-off exploit. Doing so will lock you into that RUU until the dev updates the exploit to work with the new hboot (if included in the RUU) or another RUU is released.
HTCdev
This is the method HTC gives us to unlock our phones. it allows us to install recoveries and roms, but not a lot else. you cannot downgrade your hboot or radio files with this, for example. you can install kernels via ph98img.zip file, but not through recovery. basically, it's HTC's way of letting us mess with our phones but without (hopefully) giving us enough control to brick them. this is considered better than nothing, but much less than ideal since you still don't have total control over what your phone does and how. doing this does essentially void your warranty, though to date there have been no confirmed reports of this affecting a return via either warranty or insurance.
With your phone in a stock state, you can apply only factory signed RUUs. Roms and kernels are closed to you, and you can move only forward with your radio and hboot, never backward.
With your phone in an HTCdev unlocked state, you can apply unsigned RUUs that contain a boot, system, and recovery image - all components must be present.
To get your phone into this state, visit HTCdev.com.
S-Off
This sets your security flag on the phone to off.Stock, your phone comes with this flag set to on. Our s-off method does it at the radio layer, and at this time is thought to be irreversible by update. It isn't, though - it's just unlikely because there are legitimate s-off phones out there. Still, it's always a good idea to wait to see if that shiny new RUU is gonna make your phone boring again before you install it. To be safe, wait for an RUU that has the hboot removed and just applies kernel, radio, and system files. You can turn it back on with fastboot should you wish, however. Htcdev unlocking, a bit of wire or a paperclip, and a decent set of timing is required for this. In my opinion it is best to do this once you are sure your phone does not have problems that require a warranty return, but it should be done before upgrading to new, untested OTAs/RUUs. There's always the chance that HTC will block the exploit that gives us this, at which point you're stuck until the devs figure out another way or someone comes up with some crazy method like the evo 3d guys. Many are nervous about this process, and for good reason. While the devs have done everything they can to make this bulletproof, it is best to enter into this mod with as much knowledge as possible, just like any other mod. It's also best to be relaxed, have an internet connection other than your phone, and not have anywhere you have to be right away in case things go like you don't expect. Should things go wrong, don't freak out. Ask questions. Many "bricked" phones have been restored with simple application of knowledge.
Things s-off does: Allows you to flash kernels from recovery, allows you to flash any hboot and radio you want. Lets you install any "ruu" you want with any combination of boot image, system, and recovery, rather than the entire package. Makes rom installation easier on devs due to kernel installation in recovery.
Many have scoffed at s-off, claiming it does nothing that unlocking doesn't do already. This isn't really the case, as we've all seen how important the ability to downgrade firmware and radios can be. Personally, I think of a phone with s-on in much the same way I think of eating steak through a trash bag. If you have the option not to, what the hell are you doing?
Things s-off does not do: magically turn your phone into an open platform to which devs will instantly flock to give you the aosp roms you believe yourself entitled to. What will do that? Glad you asked.
RIL - radio interface layer
Basically, the RIL is a driver for the radio - it lets the radio interface with the software running on the phone. This is a new problem that effects 4g phones. It sucks. Basically, your manufacturers (also verizon, but you can assume they don't want you to do anything other than pay them.) don't want you touching their precious radio chipset with your grubby little paws. We don't have source code, and they're not talking. Of course we already have software on our phone that has the RIL stuff we need, right? Yes... sort of. For any sense roms we want to use. This is why we don't have aosp. For aosp, one of three things needs to happen:
1) Manufacturers grow a soul and give us source in the form of a leak or they go mad and just release it. This is pretty much as likely as Verizon deciding that they are doing away with early termination fees.
2) Someone reverse engineers our RIL and makes their own RIL software. This is as likely as my wife developing new roms for her Incredible 2. The one she blames for her school's ****ty email server and wants to trade in for an iphone.
3) Someone develops an interim layer that translates aosp to sense and back again. This was done on the thunderbolt, but it was wonky. Certain individuals are confident that this will be easier done on ICS and are working on it. Some AOSP action would be pretty damn awesome, but don't expect it, demand it, or hold your breath for it. It's hard, and is going to require a very intense combination of skill, knowledge, and tenacity.
Now i know what you're thinking - the Nexus is a CDMA 4g phone and they can do whatever the hell they want. Do they have an open RIL? The answer is no. They have an aosp (Android Open Source Project) RIL though, which amounts to basically the same thing. If it is any consolation they can't have sense roms as a result. Those poor bastards, right? This is why many are torn between the Nexus and the Rezound. The Nexus is open and a dev's paradise - CM9, AOKP, MIUI, ****ty roms that some kid slapped a godawful theme on - it's all there. The Rezound has better radios, better screen, and better build quality (subjective) but no aosp. If you're reading this you've already chosen or had the choice made for you by verizon's $50 sale.
Fast Boot
But Derek, you say, you already talked about fastboot in the bootloader section. We get it. Nay nay. This is fast boot. Note the space. Basically, HTC roms include a tech that puts the phone into a hibernation state rather than powering off. You'll find it in the power menu. When this box is checked, your phone will go from powered off to your home screen in a very short period of time - 15 seconds on my phone, vs the normal 45 second boot time. If you pull the battery, you will have a normal boot time. Personally, I could take or leave this feature. I almost never shut my phone off, and when I do, I want it to actually shut off because i'm shutting it down because I need a cold boot. It's up to you how useful this feature is to you.
Perflock, CPU Frequency, and Governers
Many people have had poor experiences running the ICS leaks due to the CPU maxing out. The stock HTC kernel uses perflock, which constantly resets the frequency and scaling of your CPU. This means that the use of programs like setcpu or system tuner to change the min/max frequencies or governer of your CPU will cause it to essentially run in a state where it is either using the max frequency, or the minimum, without scaling up and down according to need. Some CPU monitoring apps will cause a similar reaction. The best way to avoid all this unpleasantness and get the best battery life out of your phone is to simply leave it be and let it do it's thing, because quite frankly you can't stop it anyway. If you absolutely must see what your CPU is doing, I have had good results with CPU Monitor by Coconuts. I still don't recommend keeping this active full time as I suspect it still impacts performance and battery life, but many do without any obvious adverse results. As a side note, the HTC kernel uses the On Demand governer, which steps up the CPU frequency quickly when needed and scales it back down slowly. Clearly, HTC's focus was on performance rather than battery life, here. Once kernel source for ICS is released, devs can build custom kernels which do not include perflock, and add other nice features as well like full power usb charging. Once this occurs, we will be free to use setcpu to scale our CPUs up or down to our hearts content and use whatever governer we like. Until then the best advice is simply to leave it alone.
I will be updating this and adding to it constantly. I'm not an expert, just an average user who is trying to put some useful info in the same place. Please shoot me a PM with suggestions/things I got wrong and I will update this post and credit you.
Contributors who have helped make this more accurate
scotty1223, esheesle
Section for General Education Type Things
Titanium Backup
Quite possibly the most useful software you will use on your rooted android device. Well worth buying. This software will allow you to backup pretty much everything on your phone to your sd-card, dropbox, box account, etc. It even lets you pull data from nandroid backups. This is the best way I know of to backup your apps and restore them when switching to a new rom. Not only do you not need to go digging through the my apps section of the play store to reinstall every damn app, you can restore with the data from the time of the backup. That means config for a lot of apps, game saves, etc. Note that most SMS apps and launchers will require you to use the backup included in their software, as Ti Backup doesn't grab these things. Forgot to backup your apps and data but made a nandroid backup? No problem. It can read your nandroid backup and pull those things right out of it.
It can also screw up your rom install to the point where you might as well factory reset, if you use it wrong. Basically, you never ever want to use it for anything other than apps you've installed from the app store and their data. Restoring system apps, unless you know what you're doing, is a bad idea. Restoring system data, no matter how tempting, is an even worse idea. It's very likely to screw you up. There are circumstances in which it may not do so, but if you are reading this and this is new info, you don't know them. Stay away. Most devs will outright tell you not to use it with their rom since people will inevitably ignore the warnings and do it anyway. It makes switching roms an absolute breeze though - I can switch roms and have my software setup exactly how it was before in less time than it takes to download a rom from Android Police. Granted, that's a good hour, but you get what I'm saying. It's a huge time saver. Backup your user apps and data, but touch system apps or data at your own peril.
What to do if you think you're bricked
Step 1: Chill out and slow down. Seriously. Unless your phone isn't doing anything at all when powered up, it's probably recoverable. Double check your MD5 sums before pushing things like hboots and radios, and you should be OK. If you've screwed up the s-off process, make a post describing exactly what you've done and how, then wait for responses. Do not demand them. You can also join #juopunutbear on freenode, where the devs hang out. They're not always right there, but I've seen them help dozens of people out of some sticky places, and they'll help you if they can. They really know their stuff.
For general Rezound problems, you can join #rezound on andirc.net. There's usually some knowledgable guys hanging out there, willing to help. Remember, the very best thing you can do is take the time to gather enough knowledge to be confident that the steps you are going to take to fix the phone are the right ones, and why. Flipping out about your "bricked" phone and throwing anything you can at it is much more likely to make things worse, and annoy the people trying to help you. For example, if you are s-on and in a state where you need to reinstall a stock RUU package, you only have as many chances to get it right as there are newer RUUs than what is on your phone already. If you don't know enough about things to know what is wrong and why, you're not terribly likely to know the best way to fix it. Keep calm and carry on.
What will installing this ______ do to my phone? What do I need to do to install them?
Now that we have s-off and all these new ICS leaks, we've all gotten a bit flash happy. This has led many to ask what they can install, how, and what needs to be done. I'll try and address as much of this as I can by talking about the different states your phone might be in.
Totally stock - You have only one choice. You can install the full RUU, or not. That means you're getting whatever radio, hboot, kernel, and rom come with that RUU. Once you've installed that RUU, you can't install anything but a newer RUU after that. Remember that with RUUs, you need to reboot twice - there are two installation steps in hboot that require a reboot in between. Note that some RUUs will wipe your SD card. Nice of them, isn't it?
HTCDev unlocked - You can install kernels via hboot, a custom recovery via fastboot or hboot if packaged, and custom roms. If you want to install new radio files or an hboot, then you'll want to make a nandroid backup in recovery, relock your phone, and install the RUU via hboot. You cannot install the RUU without relocking first. You can then unlock your phone via HTCdev again, flash recovery, and restore from your nandroid backup. Like a totally stock phone, you can only go forward with hboot and radios, never backward. You have more options than the stock guys, but are still limited. But you also can't brick your phone. Again, some RUUs will wipe your SD card.
S-off - You can do anything you want. Flash any radio or hboot you want. Flash any kernel you like. If a new RUU comes out and you want to try it, just install it. You'll need to reinstall recovery, but that's it. Want to use the new leak's radio and kernel but not the rom itself? Flash 'em. But for the love of god, check the MD5 checksum before you flash. Apps like root explorer will let you see the MD5 of a file right from your phone's SD card. Flashing a bad radio or hboot can brick your phone. With great power comes great responsibility. Flashing hboot, kernels, and radio files do not require you to factory reset your device, nor will they do so. It is advisable to clear your cache and dalvik cache in recovery after installing a new kernel, but that will not affect the data on your device.
So let's say you've got s-off, and you're running a rom you like, but you want that new radio, hboot, and kernel. First, don't touch the hboot unless you have a reason to. That's a risk that you don't need to take most of the time. To flash the radio, find someone who has extracted the radio and repackaged it into a PH98IMG.zip that contains just the radio. Copy it to your SD card, check the MD5, and flash via hboot. To install the kernel, either grab it from someone who has packaged it, or pull the boot.img from the RUU zip. Check your md5, boot your phone to fastboot, and run:
fastboot flash boot <path to boot.img file>
You need fastboot on your PC, of course. Also, bear in mind that with a new kernel on an older rom, you may need to apply patches to make everything work properly, like wifi. Devs will generally release these patches and post them. Simply copy them to your SD card and install in recovery.
Where are all these files?
The Dev section. Go in there, and poke around. It doesn't take long after a leak is released to see that leak taken apart, rooted, deodexed, stripped of its kernel and radio files, etc. Read what people are saying, and asking. Generally, the first post will be updated to have everything you need, but the thread may have what you're looking for as well. What you don't want to do is ask where things are when the same question has been asked several times over already, often three pages back. Sometimes things can be hard to find, but it's good to make the effort. The community will be better for it.
What's a rooted rom? Deodexed? Busybox? Zipalign?
Rooted is fairly self explanatory. It's the process of packaging a superuser app with a rom that will allow you to operate your phone with root access. You'll need this for the good stuff like removing bloat, installing most wireless tethering apps, ad blockers, titanium backup, etc. Verizon wishes you wouldn't do this, so you know it's awesome.
Deodexing basically removes an optimization, called odexing, that basically takes bits of an apk and puts them elsewhere for optimization purposes. Deodexing packages everything back into the apk so you can use different apks without fear of conflicting code, etc. This is what makes a lot of mods possible.
Busybox provides several stripped down versions of unix tools in a single package. A lot of things like titanium backup depend on this. Generally when someone roots a rom they also busybox it.
A zipaligned rom is a rom that has had its application packages optimized for quick access by aligning them on 4 byte boundaries. This allows android to access resources without having to explicitly read them. You don't necessarily need to understand this one - just think of it as being optimized.
Contributions are appreciated and will be credited in the main post. In the interest of keeping this thread clean without a million different versions of the OP, please edit your post down to a basic "suggestions added" or something similar once I've noted your additions. That way things stay readable and don't confuse the readers. Ideally, a PM would be best, leaving the comments free for questions and the like. My goal is to jam as much knowledge in this thread as I can, and I'll continue working on it as I see new questions that commonly pop up.
tspderek said:
I literally meant the phrase "suggestions sent." i would prefer PMs or cleaned up posts after suggestions are included in the original post for cleanliness' sake and to keep down redundant info.
Click to expand...
Click to collapse
so,in other words,youd like your posts,followed by no posts,or "thanks" posts,with no real discussion.
my only issue with that,is simply any of us are capable of sending suggestions that are not correct,or that are correct but an opinion. are you filtering somehow what you add? or just adding everything everyone sends?
its your thread,ill accept your request,but i personally would like to see everyones personal contributions and how you incorporate them.
readers should be smart enuff to seperate the first 3 information posts from the rest of the discussions. my 2 cents
I literally meant the phrase "suggestions sent." i would prefer PMs or cleaned up posts after suggestions are included in the original post for cleanliness' sake and to keep down redundant info.
..
Khayos said:
Suggestion: Sticky! (then delete me)
Click to expand...
Click to collapse
it's been sticky since about an hour after it was written last night...
Thank you for writing this. It should be a requirement to read this before someone can post again.
Thanks for this! I was just thinking that this is getting REALLY confusing...I appreciate the Primer!
tspderek said:
There seems to be a lot of confusion about what things are or how they work together so I'm gonna try and build a post to explain some things. ...
<snip>
Click to expand...
Click to collapse
I had been contemplating a post to ask questions that this addresses; for myself, it is very timely as well as very helpful.
I've seen terms in the forum used interchangeably that really are not, and this helps clarify that. Consistent use of terminology could go a long way to help with the abundance of questions and misunderstandings that exist.
Again, many thanks.
Nice post. Thanks!
I was waiting for the OTA to go official before even thinking about s-off but now you got me thinkin' about it.
If the OTA is good but I just want it de-oxed and de-bloated should I bother with S-Off?
My Dinc was so easy with UnRevoked, wish this one was as easy as that!
my personal feeling is that i like my phone to have s-off, so i can use the radio that works best for me and have full control of my phone. if i've already voided the warranty with htcdev, then why not? it's not a difficult process if you research and prepare everything ahead of time. know the steps, have your tools ready, and you'll be fine. took me one try on my phone.
it's really up to you, though. it's your phone. there is a risk of bricking that isn't there with htcdev. it's low unless you make poor decisions or skip steps, but it does exist - that's what s-off does. it opens the door for you to help or hurt yourself.
Very Useful
This is very well written. I wish I had this when I started my journey with Android. This is my first post btw. Iv been doing this for about 6 months now and hate that i cant post in Developement section. But i appreciate the time it took to make this. Very nice!
Edit.. Second post. Fogot about the first one
Sweet, will be following this closely! Thanks for posting!
Thanks for posting this it helped clear a lot of things up for me. This is my first smartphone and so I'm still learning about this stuff. I think some people forget that not everyone understands all of the jargon. I'm learning more and more about what I can do everyday and this has certainly helped.
Installing RUU
tspderek said:
Installing an ruu can only be accomplished on a phone that is currently not in an htc dev unlocked state, or a phone that has s-off. when installing one of these that includes an hboot, you'll need to reinstall recovery as well - installing a new hboot via RUU will always require this as the custom recovery is overwritten with the stock recovery.
Click to expand...
Click to collapse
tspderek said:
With your phone in a stock state, you can apply only factory signed RUUs. Roms and kernels are closed to you, and you can move only forward with your radio and hboot, never backward.
With your phone in an HTCdev unlocked state, you can apply unsigned RUUs that contain a boot, system, and recovery image - all components must be present.
Click to expand...
Click to collapse
I'm confused. I am S-ON (scared of brick), bootloader unlocked, and running CleanROM Pro 4.3. I want to update to the newest firmware and then the newest version of CleanROM. Do I have to re-lock my bootloader in order to install ICS firmware? I'm looking at the 3.14.605.5 Ice Cream Sandwich ZIP RUU (http://forum.xda-developers.com/showthread.php?t=1365654). How do I go about installing that?
Any help would be appreciated, thanks!
pumpkinsoftruth said:
I'm confused. I am S-ON (scared of brick), bootloader unlocked, and running CleanROM Pro 4.3. I want to update to the newest firmware and then the newest version of CleanROM. Do I have to re-lock my bootloader in order to install ICS firmware? I'm looking at the 3.14.605.5 Ice Cream Sandwich ZIP RUU (http://forum.xda-developers.com/showthread.php?t=1365654). How do I go about installing that?
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
yes, you need to lock it back up then apply the ruu.
or, take the path of awesome, and s-off that bad boy. what i'd actually do is install the latest leak RUU, s-off from that platform, then install amon-ra and whatever rom you want. that way your bootloader will already be upgraded, and your radio files. as new leaks come out you'll be able to apply radio files and kernels independently.
tspderek said:
yes, you need to lock it back up then apply the ruu.
or, take the path of awesome, and s-off that bad boy. what i'd actually do is install the latest leak RUU, s-off from that platform, then install amon-ra and whatever rom you want. that way your bootloader will already be upgraded, and your radio files. as new leaks come out you'll be able to apply radio files and kernels independently.
Click to expand...
Click to collapse
Ok, so...
1. Re-lock Bootloader
2. Install latest RUU
3. Unlock Bootloader and Root
4. S-OFF
5. Install Amon-RA
6. Install ROM
Sounds simple enough. Thanks.
Ok so I've taken your advice and removed setcpu and installed the one recommended in the post however is there any way to also monitor battery temp that won't interfere with things the same way setcpu does?
Sent from my ADR6425LVW using XDA
pumpkinsoftruth said:
Ok, so...
1. Re-lock Bootloader
2. Install latest RUU
3. Unlock Bootloader and Root
4. S-OFF
5. Install Amon-RA
6. Install ROM
Sounds simple enough. Thanks.
Click to expand...
Click to collapse
Step 4.5, install the patched hboot they offer you!

Simple guide to [VM firmware recovery thread] v2

Please go here now: http://forum.xda-developers.com/showthread.php?t=1653777
Mods should unsticky mine and sticky that instead.
Go to the above link if your a victim of virgin mobile firmware.
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
hockey4life0099 said:
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
Click to expand...
Click to collapse
So you have no data at all? I'd try a ##data# reset first.
hockey4life0099 said:
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
Click to expand...
Click to collapse
Never assume. Just because VM has a different firmware, that doesn't mean that Sprint 3d's will too. We do not fully know what the differences are between the 2 devices.
Thus the reason for this and other fix threads. I would suggest trying this fix, and see if it helps, and hope that there is a firmware fix in the future.
I will tell you how I restored my data. I first downloaded the following stock rom.
Stock 2.08.651.2 With HTC/Sprint Spyware Removed
http://forum.xda-developers.com/showthread.php?t=1285975
After flashing to the stock rooted rom above I then went into my dialer and typed in ##my MSL number# (Example: ##000000#) To get your MSL number simply download MSL reader from the market. I then clicked on edit and then edited my MDN with all zeros and MSID with all zeros. I pressed the menu button and then pressed reset. After the phone rebooted the phone activation screen came up when I unlocked the phone and it was able to automatically activate it and I got 3G data.
jlechner said:
So you have no data at all? I'd try a ##data# reset first.
Click to expand...
Click to collapse
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
hockey4life0099 said:
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
Click to expand...
Click to collapse
This is the issue some are having. I would say it's because of the VM firmware we flashed. Did you try the PRI version downgrade that takes you back to 003 even though it shows 005? or does yours still say 004?
hockey4life0099 said:
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
Click to expand...
Click to collapse
Hockey, I have not seen this issue yet on my rom, PM me if you want to try mine, and let me know if you see any difference. I wonder if some of the SMS issues have to do with the ICS rom itself. BTW do not post my ROM anywhere as I do not release my stuff public, just want to help out a fellow hardcore flasher.
Cheers
jlechner said:
This is the issue some are having. I would say it's because of the VM firmware we flashed. Did you try the PRI version downgrade that takes you back to 003 even though it shows 005? or does yours still say 004?
Click to expand...
Click to collapse
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Freeza or Unknownforce, I have a guy getting a replacement phone tomorrow. He wants to help. I figured we could have him pull the partitions, please advise.
hockey4life0099 said:
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Click to expand...
Click to collapse
Touch base with Mikey.
hockey4life0099 said:
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Click to expand...
Click to collapse
Oh perhaps you need to be on PRI version 1.42_003? I never ran into issues on chad's downgrad PRI either though.
This thread can't be deleted. This has good info we need up.
I know it says Chad in it, but should we just take the name out?
Well, if we did, then we won't give credit where it's due.
Anyways,
Is there any general thought on the rough percentage of people this works 100% for?
Mikee4fun said:
Oh perhaps you need to be on PRI version 1.42_003? I never ran into issues on chad's downgrad PRI either though.
Click to expand...
Click to collapse
is there a way to get to 1.42_003?
Thank god there's another one of these!
Ok so I got back from sprint again and the were totally in awe and had no idea whatsoever was wrong with my phone They ordered me a new one and it'll be here on like tuesday or wednesday and i'll see if I can get it not activated already.
Btw the sprint people are totally dumb.... They were talking to a couple and saying yeah, the more storage a phone has the faster it'll be! He said that 32gb phones out performed 16gb phones.... I was like wtf man... Also he was trying to sell them the galaxy s 2's and was telling them that they're new phones. Wtf sprint salesman, wtf...
hockey4life0099 said:
is there a way to get to 1.42_003?
Click to expand...
Click to collapse
The 005 mod is actually 003, from my understanding.
Sent from my Sprint/Virgin Mobile hybrid.
jlechner said:
Freeza or Unknownforce, I have a guy getting a replacement phone tomorrow. He wants to help. I figured we could have him pull the partitions, please advise.
Click to expand...
Click to collapse
Thanks, but I think we have everything we need at this point. I'm writing code right now for the patching part of the process. Not that I have everything that I need just yet, but at least getting that part out of the way for when I do have the correct information.
I've located everything that I have to change in my own partition to fix it (All the differences) next I'm going to compare these offsets with those of the partitions that freeza gives me and see if they line up the same... there's going to be some major coding needed for this, because it did manipulate some of the "flow" I think in the way it lists out certain information in the file, like rom name, and phone number and stuff...
I'm not the fastest coder, but I have basically all I need at this point for my own device... I just want to verify that it's similar code on others' devices as well before I get too far ahead of myself here and have to backtrack. I'm actually going to re-code the downgrade tool to make it part of that, probably rename it to a "multitool" of some kind and simply put it into the already stickied thread, and have closeone update his cd with it so that people can do this with ease.
The best part of this all is that the bricking process isn't going to be a stupid timing thing like it is when downgrading... a single command can brick an already S-OFF phone the way we need it. So no confusing timing issues with this one! Just a nice easy set of instructions. Phew.
Short and sweet basic steps right now:
1.) Nand Backup
2.) Brick
3.) Run "multitool" Plug unplug, yadda yadda.
4.) Boot phone back up to 1.40 S-ON
5.) Run 1.13 RUU
6.) Revolutionary S-OFF
7.) Flash 2.17 Firmware
8.) Flash recovery
9.) Restore Backup
10.) Drink Beer
More details to follow.
hockey4life0099 said:
is there a way to get to 1.42_003?
Click to expand...
Click to collapse
Yes, you need to go through the adb push process stated in the OP. I can assist you if you want through team viewer if you don't want to tackle it.
Unknownforce said:
Thanks, but I think we have everything we need at this point. I'm writing code right now for the patching part of the process. Not that I have everything that I need just yet, but at least getting that part out of the way for when I do have the correct information.
I've located everything that I have to change in my own partition to fix it (All the differences) next I'm going to compare these offsets with those of the partitions that freeza gives me and see if they line up the same... there's going to be some major coding needed for this, because it did manipulate some of the "flow" I think in the way it lists out certain information in the file, like rom name, and phone number and stuff...
I'm not the fastest coder, but I have basically all I need at this point for my own device... I just want to verify that it's similar code on others' devices as well before I get too far ahead of myself here and have to backtrack. I'm actually going to re-code the downgrade tool to make it part of that, probably rename it to a "multitool" of some kind and simply put it into the already stickied thread, and have closeone update his cd with it so that people can do this with ease.
The best part of this all is that the bricking process isn't going to be a stupid timing thing like it is when downgrading... a single command can brick an already S-OFF phone the way we need it. So no confusing timing issues with this one! Just a nice easy set of instructions. Phew.
Short and sweet basic steps right now:
1.) Nand Backup
2.) Brick
3.) Run "multitool" Plug unplug, yadda yadda.
4.) Boot phone back up to 1.40 S-ON
5.) Run 1.13 RUU
6.) Revolutionary S-OFF
7.) Flash 2.17 Firmware
8.) Flash recovery
9.) Restore Backup
10.) Drink Beer
More details to follow.
Click to expand...
Click to collapse
Cool thanks!
Sent from my Sprint/Virgin Mobile hybrid.

4.4.3 update not showing

Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
They pulled the AT&T update. Soooo....just gotta wait.....
ibma said:
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
redpoint73 said:
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
Click to expand...
Click to collapse
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Signal will not show 4g or 4glte like AT&T [email protected] [email protected]
You could relock and unroot,but then no reason to flash a custom rom.
Those two settings are in settings. And on the m8 443 euro builds some are reporting lesser [email protected]
There are AT&T ROM's available that are tailored to us AT&T/GSM networks
ibma said:
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Click to expand...
Click to collapse
ibma said:
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Click to expand...
Click to collapse
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
Just use this guide to flash the ruu for 4.4.3. It only works on att m8. MAKE SURE YOU READ THE DIRECTIONS! You just need to relock your boot loader if you are not s-off
http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
ibma said:
I have no idea what im doing lol, im following a tut to install revolution hd rom
Click to expand...
Click to collapse
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
redpoint73 said:
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
Click to expand...
Click to collapse
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
ibma said:
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
Click to expand...
Click to collapse
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
redpoint73 said:
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
Click to expand...
Click to collapse
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
ibma said:
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
Click to expand...
Click to collapse
Not enough info. What exactly does the error say?
S-on or S-off. Did you relock the bootloader?
Any response if you type (using adb):
adb devices
Improper HTC/ADB drivers or using Microsoft USB 3.0 drivers on USB 3 port on Windows 8.x instead of Intel USB drivers would be my first two guess. The ladder of the two issues would be most likely scenario if RUU communicates with device while booted into Android OS but fails to connect when the device is in fastboot/boot loader mode.
-Sent from a payphone...

[Q] Flashed Revolution HD and all incoming calls go to voicemail on AT&T M8

Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
homthtrnut said:
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
Click to expand...
Click to collapse
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Just need to dig in and get it done!
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I can do anything that is new to me with good instructions. I WAS able to unlock, root, and flash a ROM with good success following the steps. What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk. Before I started anything , I backed it up using HTC SYNC on my laptop. Is that useful in returning it to stock? Or is that just for media and texts and such? Maybe what I should do is check the forum where the Revo users are and see what they say. Sorry if it sounds like Im thinking out loud but Im a noob at forums and flashing. And Im getting burnt out on having a phone that doesnt receive calls properly. Not to mention burnt out from working all day and coming home to try and solve this mystery. OK I wont mention it. Thanks to those who have attempted to give me input here to try to figure this thing out.
Just a lil something to think about...,youll not have dialer, vvm messages,contacts integrated,signal will probably be not as good,and no VoLTE when using euro ROM's. Stand alone vvm app may or may not install from playstore if you use it. My suggestion,flash back to stock,wait alil while and get an official Lollipop release from ATT.
Flash a twrp backup of latest 4.4.4
Flash stock recovery from latest 4.4.4
Steps above will put you back to as close to stock as possible,without relocking bootloader and reflashing the exe ruu file.
homthtrnut said:
What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk.
Click to expand...
Click to collapse
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Flashed firmware successfully.........darn .zip.zip tricksters!!!! Anyway!
redpoint73 said:
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Click to expand...
Click to collapse
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done. Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do. I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious. Now to see if I can receive calls again. Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
homthtrnut said:
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done.
I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious.
Click to expand...
Click to collapse
Do yourself a huge favor, and turn off the Windows option (if you haven't already) to hide known file extensions. The option is usually enabled by default. I suspect its mainly meant to prevent non-tech savvy PC users from deleting or modifying file extensions and rendering files unusable (or at least not associated with a program to open it).
For most folks who are going to be messing with things like modding phones, and even halfway familiar with the file extensions, the option to hide them is counter-productive and confusing.
The recommendation to rename the file to firmware.zip is valid. This is done since the files are often named things like 4.16.401 to differentiate the firmwares from each other (such as in firmware collections). Technically, you didn't rename the file to firmware.zip (although Windows make it look like you did), you actually named it firmware.zip.zip, even though Windows didn't display it that way.
homthtrnut said:
Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do.
Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
Click to expand...
Click to collapse
To unlock the bootloader again, simply go through the HTCDev.com process to get another unlock bin token, then run the fastboot command with that token again (like you did the first time).
On past devices, it was sometimes possible to reuse the original token (run the fastboot command with it). But an XDA user commented that doesn't work on this device (and that you need to get a new token). But you can always try it, if you want.
Flashed firmware and now stuck in HBOOT! I REALLY NEED HELP NOW
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258 and after numerous attempts to flash I finally got it to go by getting rid of the renamed .zip at the end. ( It was already a zip file) I think a lot of people have had that problem. Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again. Can anyone point me? I'll buy you a beer! or 12
homthtrnut said:
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258
Click to expand...
Click to collapse
401 firmware is Euro based firmware. AT&T is 501.
homthtrnut said:
Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again.
Click to expand...
Click to collapse
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
hboot and radio numbers currently on m8
redpoint73 said:
401 firmware is Euro based firmware. AT&T is 501.
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
That is the Android 4.4.4 radio. Meaning the 401 firmware you linked and tried to flash didn't take. And it won't with s-on, unless its signed and hacked to accept AT&T's CID (which I don't think there is any 401 firmware that meets those requirements).
Agree with the above response, in that the easiest way to get the phone up and running again is relock the bootloader and RUU to stock.
Since your device is hboot 3.19, you are stuck with s-on and that means you are stuck on KitKat firmware until AT&T releases Lollipop officially.
That also means you can only run ROMs that support 4.4.4 firmware (no LP based Sense ROMs), otherwise you will run into various serious bugs like the call issue on ARHD (or broken WiFi). There are some LP GPE and AOSP ROMs that support the 4.4.4 firmware, if you want to go that route.
Was just starting out, not enough experience.
bford152 said:
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
Click to expand...
Click to collapse
The above phone was eventually returned. Now I have an unlocked, s off M8. With help from PearlyMon I was able to do it all about a month ago. Now I'm just waiting to work up the nerve to flash a customer Rom and also add in the H/K sound feature. Really liked the HD Revolution Rom, I just didn't have the wherewithall to find and install the proper firmware. This time around will be better. On third M8 now. First one, brand new slipped out of workshirt pocket and faceplanted on a tile floor. First damn day! Didn't have the otter box defender case like I should've. 2nd and 3rd ones have been refurbs. So who knows how much use the battery saw before? So I'd like a nice Rom that has built in low battery drain. Every day it seems to drain off a little sooner. Went to black background today to help it out a little. Anyway, haven't been on this forum much since the above problem and thought I'd touch base with you and say thanks. Have a nice one.
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
jon145 said:
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
Click to expand...
Click to collapse
Some folks have been having issues with "international" based custom ROMs on AT&T's LTE network. It seems that AT&T has been making some changes to LTE, possibly in preparation for Voice over LTE (VoLTE, which AT&T calls "HD Voice"), that are messing up voice calls on "international" ROMs.
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
You might try WNC's ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Its based on the Lollipop Developer's Edition ROM, which is intended for use on AT&T's network. He's working on a version based on the AT&T 4.28 update, but its still in testing and not posted yet.
Yeah I've been running the SD 9.0 for several days and no love here in Dallas ... I could speculate for days since D is AT&T's home city.
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
jon145 said:
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
Click to expand...
Click to collapse
He has a beta in testing right now. Just ping him, and he will probably send you a link to the test build. Probably the only reason he would say "no" is if he is going to release soon anyway.
redpoint73 said:
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
Click to expand...
Click to collapse
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
rhughes93 said:
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
Click to expand...
Click to collapse
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
redpoint73 said:
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
Click to expand...
Click to collapse
So I re-flashed SkyDragon, and I think I was not understanding the difference between AROMA installer and the software itself. When I did it the first time, I think I did select T-mobile with wifi calling in AROMA, but AT&T within the software SIM setup. It did not work. Now after getting the stock ROM working, I re-flashed, chose the Other GSM/WWE/whatever option within AROMA, AT&T within the software, and all is right in the world. I may also try the same with Venom this weekend now that I have good restore options, though I don't recall if it had similar options in AROMA or not.

Categories

Resources