Develop Bugs

[Q] Questions about flashing radios

Hi,
I just flashed a 2.3.3 stock-rooted ROM and well, as everyone is saying, the battery is draining way too fast!
On the actual post where i got the ROM, they provide a radio, but im a little curious about this who radio thingy.
1- I have a nandroid, restoring will bring back old radio?
2- is there a way to backup the radio if the answer to question1 is NO
3- what are the risks, and does it happen alot?, or is it a rare case?
4- they say it can brick the phone, is there any possible way to get out of that state?

1- I have a nandroid, restoring will bring back old radio?
No
2- is there a way to backup the radio if the answer to question1 is NO
Download your original radio from this thread
3- what are the risks, and does it happen alot?, or is it a rare case?
Just read the Radio Thread.
4- they say it can brick the phone, is there any possible way to get out of that state?
Once it is bricked, just send it for warranty. Most probably, they will change with a new one since they can't really know what you have done to the phone.

Hmmm, if it gets bricked, then i wont have my phone for MONTHS! since im in a different country than where i brought it, and i dont have HTC support here.
anyway, i couldnt find my radio type in the link you gave me - mine being:
12.28b.60.140eU_26.03.02.15_M3
but ofc this is the one that came with the 1.32 FW when i was degrading, so can i just extract the radio.img from the PD98IMG.zip file and the flash it? or will it cause problems?

You don't (can't) flash radio's in the same way as a ROM. Read the radio thread.
PD98IMG or the safer method IMO is fastboot (search if unsure what fastboot is).
Sent from my Ericsson T39m

na, i know what fastboot is....
but what im saying is...say i update to a new radio, and its worse than the last, can't i just take the radio.img from the 1.32 PD98IMG.zip file and use fastboot to flash it back?
Or say i found the 12.28b.60.140eU_26.03.02.15_M3.zip radio file, can i flash that?
OR is the only way to go back to the radio by flashing a RUU?(because i heard that installs a new radio).
i have radio and eng S-OFF.

CodeNameUnknown1 said:
but what im saying is...say i update to a new radio, and its worse than the last, can't i just take the radio.img from the 1.32 PD98IMG.zip file and use fastboot to flash it back?
Click to expand...
Click to collapse
Not tested that method sorry.
CodeNameUnknown1 said:
Or say i found the 12.28b.60.140eU_26.03.02.15_M3.zip radio file, can i flash that?
Click to expand...
Click to collapse
Yes.
The great thing about Radio S-OFF and ENG S-OFF is it allows you to play with radio's.
Just to clarify, and this is aimed at others new to all this, the term "flash" in this case is referring to using fastboot command (think of it like adb but with phone in HBOOT - put very simplistically) to push the file to the phone.

kol man, thanks, ...
i think the 1st method would work, cuz at the end of the day, when flashing the whole PD98IMG.zip it flashes the radio along with other stuff ... so just taking it out would, i presume, would work ...
i'll update my radio soon, maybe, and if its bad, then i'll try the method! ...

No worries.
In theory method one should be ok as the zip is essentially a bundle of files and scripts. The only reason for hesitation is some .img files are slightly modified specifically for us with PD98IMG files.
But if it does work (and hopefully if not you don't get a brick) that would be good news as I often hunt down non PD98IMG versions of things and it would save me some effort.
Please, if not too much trouble, do keep us updated (no pun).

wait .... by doing that i can get it bricked?!!?!?!?!? loool
then i guess im not doing it!, lol, im still in love with my desire hd!!!

IF, a BIG IF, the radio.img file within a ROM PD98IMG file has been tweaked in some way there could be a risk that pushing the file through fastboot could brick the phone. Doing anything with Radio files is possible the most dangerous thing you can do (certainly it's the only thing I do frequently that still makes me hold my breath).
My advice would be, if there is a "normal" zip file of the radio I'd take that and push it via fastboot (after checking the md5hash).
That may be an answer, see if the md5hash of the radio.img is the same from both sources.

i cant find my original exact radio.
i have found some radio near my current one( 12.28b.60.140eU_26.03.02.15_M3) but they have a difference in the letters (i.e. Radio_12.28b.60.140e_26.03.02.26_M - without the 'U' and its .26_M, no M3 or .15)
whats the difference, and what do they mean? -- i googled this but couldnt find an answer.

I have a question for radio.
(will borow these theme, if you dont mind)
I have ship s-off (i read that i can't flash radio becouse of this)
my Radio is 26.03.02.15_M3
This is an old version, and i would like to have a new version, becouse i have a lot of problems by flashing newer custom roms, wich have other radios recomended i quess :? ?
1. question: Is possible that i have problems flashing new rooms becouse i have an old radio ?
2. question: how to get from ship s-off to eng s-off? The standard root procedure dont work :s
Thanx for answers

gagi´d hype said:
I have ship s-off (i read that i can't flash radio becouse of this)
Click to expand...
Click to collapse
You NEED Radio (ship) S-OFF (as a start)
gagi´d hype said:
1. question: Is possible that i have problems flashing new rooms becouse i have an old radio ?
Click to expand...
Click to collapse
No. But some ROM's work better with more up to date radio. What ROM are you wishing to try?
gagi´d hype said:
2. question: how to get from ship s-off to eng s-off? The standard root procedure dont work :s
Click to expand...
Click to collapse
Follow the guides in the development forum.
http://forum.xda-developers.com/showthread.php?t=855403

Mr_JMM said:
You NEED Radio (ship) S-OFF (as a start)
No. But some ROM's work better with more up to date radio. What ROM are you wishing to try?
Follow the guides in the development forum.
http://forum.xda-developers.com/showthread.php?t=855403
Click to expand...
Click to collapse
I have tryed a lot of rooms, at the and i have an Revolutin HD with adw louncher and density on 180 (the best screan for me)
I flashed then Revolution HD with GB, i think its an 5.1.3 version, and the rom dont work properly.. I have load again the adw louncher and do the density, but there was a looot of bugs, with people app, with screen (lot of freezes) etc..
i dont know what is the problems, is it the radio or just GB room don't allow the unsense louncher and desity settings..

CodeNameUnknown1 said:
i cant find my original exact radio.
i have found some radio near my current one( 12.28b.60.140eU_26.03.02.15_M3) but they have a difference in the letters (i.e. Radio_12.28b.60.140e_26.03.02.26_M - without the 'U' and its .26_M, no M3 or .15).
Click to expand...
Click to collapse
Honest answer is I am unsure other than various protocols by various networks / manufactures (The "U" ROM I believe was provided by a specific network). There is something in there that determines if it is specific to HSDPA vs EDGE etc. but again, my memory fails me.
If you're willing to go on say so alone go for the second one as that's been tested thoroughly however, it is old so if you feel your signal, wifi, GPS isn't as good as it should be and when you're feeling more confident it could be worth trying some of the more recent ones
[EDIT]
Going back to something I said earlier, a PD98IMG file can be JUST a radio. If you don't want to use fastboot commands then here is a thread that contains PD98IMG versions of the radios.

gagi´d hype said:
I have tryed a lot of rooms, at the and i have an Revolutin HD with adw louncher and density on 180 (the best screan for me)
I flashed then Revolution HD with GB, i think its an 5.1.3 version, and the rom dont work properly.. I have load again the adw louncher and do the density, but there was a looot of bugs, with people app, with screen (lot of freezes) etc..
i dont know what is the problems, is it the radio or just GB room don't allow the unsense louncher and desity settings..
Click to expand...
Click to collapse
Not every ROM (and with it the Kernel) and especially home launcher apps are happy with resolution changes. Whenever you experience bugs like this the first step is reset things like resolution and then if still bugs remove any launcher you have added the ROM.
ARHD (Revolution) is a fantastic ROM and should be bug free.
Try LeeDroids as that is my favourite and I've never had a problem with it.

Mr_JMM said:
Not every ROM (and with it the Kernel) and especially home launcher apps are happy with resolution changes. Whenever you experience bugs like this the first step is reset things like resolution and then if still bugs remove any launcher you have added the ROM.
ARHD (Revolution) is a fantastic ROM and should be bug free.
Try LeeDroids as that is my favourite and I've never had a problem with it.
Click to expand...
Click to collapse
I have flash to the eng s-off now
I see taht a lot of rooms have problems with resolution settings, (i am a litlle angry becouse the resolution on standard sense display is like the people are blind )
That is why i use an adw louncher, and on 2.2 ARHD everything work perfect..
i hope that i will solve the problem with radio, (if not i wil goo to standard density)
ok, thank you very much for the help..

gagi´d hype said:
i hope that i will solve the problem with radio, (if not i wil goo to standard density)
Click to expand...
Click to collapse
The radio has nothing to do with your bugs.
The radio controls mobile signal, wifi, gps and bluetooth.

[Q] How to update from a very old (v3) rom to a new Jellybean (v12) rom

I've been away from the ROM scene for quite some time now, but some of the new Jellybean features (coupled with constant pestering via an OTA update) have persuaded me it's time to upgrade.
I'm currently running Football's maXimus Rom v3.1, which is an old ICS rom. I'd like to upgrade to his latest version, but i'm struggling to remember/work out how!
I'm currently running hboot v0.95, and i'm pretty sure this needs to be updated to a version 1.3x, which i've no idea how to achieve! In addition, i've seen a video Football posted in his thread which refers to an updater_script.zip file, which I can't find either!
So far i've re-installed the android SDK, downloaded the latest version of the ROM and popped into the root directory of my OneX, and downloaded the fastboot kit for v12. What else do I need to do before getting some Jellybeen goodness?

In this Thread you will find anything you need related to hboot.
After this just flash rom and kernel as usually

MeLViN-oNe said:
In this Thread you will find anything you need related to hboot.
After this just flash rom and kernel as usually
Click to expand...
Click to collapse
Brilliant, that tool looks absolutely perfect!
One final (hopefully!) question - i've set up the JBFW tool and placed the relevant files in the folder, but my CID comes up as 1111111 - does this mean I can't upgrade? And if so, is there anything I can do to change this?
Also, in the thread you linked to it mentions that 'everythings included except the RUU' - do I need to source an RUU? (and find out what one is!)
Thanks again!

It means you have super cid.
You can flash any rom you want without any cid restrictions. Still i would like you to get a 2nd opinion on what way to proceed.

Is your device s-off ?
You can proceed with flashing anyway

[Q] What's the use in updating your hboot version?

Hello everybody,
as the title suggests: (Why) should I update my hboot?
Yes, I've searched, yes I've read. I'm sure I could find the concise answer if I invested several hours of reading various highly informative threads, but maybe somebody can put it down in a few, easy to understand sentences, or point me to a post / wiki entry where it's explained concisely?
My situation: I have the HTC One X (Tegra 3 version), rooted, S-ON, with the 0.43 hboot at the moment. I have installed several ICS sense roms in the past, and am currently running JB (4.1) AOSP (/CM/PA/...) roms. This all works nicely, but I really don't understand all the talk about different hboot versions, needed RUUs, etc.
So I have several more detailed questions:
If I got it right, I need a newer hboot version to run Sense JB Roms - correct?
To upgrade to a newer hboot version, I need to download the correct RUU and install this, correct?
How do I find the "correct" RUU? And am I right that the RUU is an offical exe file, installing the Stock Rom on an unlocked phone only (meaning I have to relock first)?
Is it correct that hboot version more current than my original, never updated one will cause problems (GPS, direct wifi, volume, bt, ...') with basically ALL Non-Sense roms?
Is it correct that once upgraded, I have no option whatsoever to downgrade?
What is the interaction between the hboot and the installed kernel - do some kernels work better with certain hboot versions?
Sorry for the flood of questions. As you can see, I really tried to find the answers. In some cases I'm rather sure of what I think, but some questions leave me baffled. At the moment it seems to me that I have to decide between either a Non-Sense JB, or a Sense JB, but I cannot switch between them (and retain all functionality of my phone).
Thanks in advance,
Thor

if you upgrade it, you will be able to flash jb based roms, as you already know, there are jb roms out, which boots on any version of hboot, some dont, thats why you need to upgrade, for example, im running the blade rom v3.0.0 which its great, but i couldnt flash if i didnt upgrade the hboot.

pull.me.under said:
Hello everybody,
as the title suggests: (Why) should I update my hboot?
Yes, I've searched, yes I've read. I'm sure I could find the concise answer if I invested several hours of reading various highly informative threads, but maybe somebody can put it down in a few, easy to understand sentences, or point me to a post / wiki entry where it's explained concisely?
My situation: I have the HTC One X (Tegra 3 version), rooted, S-ON, with the 0.43 hboot at the moment. I have installed several ICS sense roms in the past, and am currently running JB (4.1) AOSP (/CM/PA/...) roms. This all works nicely, but I really don't understand all the talk about different hboot versions, needed RUUs, etc.
So I have several more detailed questions:
If I got it right, I need a newer hboot version to run Sense JB Roms - correct?
To upgrade to a newer hboot version, I need to download the correct RUU and install this, correct?
How do I find the "correct" RUU? And am I right that the RUU is an offical exe file, installing the Stock Rom on an unlocked phone only (meaning I have to relock first)?
Is it correct that hboot version more current than my original, never updated one will cause problems (GPS, direct wifi, volume, bt, ...') with basically ALL Non-Sense roms?
Is it correct that once upgraded, I have no option whatsoever to downgrade?
What is the interaction between the hboot and the installed kernel - do some kernels work better with certain hboot versions?
Sorry for the flood of questions. As you can see, I really tried to find the answers. In some cases I'm rather sure of what I think, but some questions leave me baffled. At the moment it seems to me that I have to decide between either a Non-Sense JB, or a Sense JB, but I cannot switch between them (and retain all functionality of my phone).
Thanks in advance,
Thor
Click to expand...
Click to collapse
here are some good news ,some new Non-Sensed Roms like 4.2.1 AOKP beta release are able to run on all HBoots and there is also Trip's ROM which works for Hboots also ,so with no time all Hboots will be able to run at all kinds of ROMS over there for HOX ,

Have you come across the following site...i guess it explains pretty well..If it doesnt solve ur curiosity, u can ask it here..!! Every1s here to help..!!
http://www.flow-wolf.net/2012/10/htc-one-x-perfect-guide-for-beginners.html

^ I read that site a few days ago and it was the best explanation I've see.
sent from my highgrade HTC one x

pull.me.under said:
Hello everybody,
as the title suggests: (Why) should I update my hboot?
Yes, I've searched, yes I've read. I'm sure I could find the concise answer if I invested several hours of reading various highly informative threads, but maybe somebody can put it down in a few, easy to understand sentences, or point me to a post / wiki entry where it's explained concisely?
My situation: I have the HTC One X (Tegra 3 version), rooted, S-ON, with the 0.43 hboot at the moment. I have installed several ICS sense roms in the past, and am currently running JB (4.1) AOSP (/CM/PA/...) roms. This all works nicely, but I really don't understand all the talk about different hboot versions, needed RUUs, etc.
So I have several more detailed questions:
If I got it right, I need a newer hboot version to run Sense JB Roms - correct?
To upgrade to a newer hboot version, I need to download the correct RUU and install this, correct?
How do I find the "correct" RUU? And am I right that the RUU is an offical exe file, installing the Stock Rom on an unlocked phone only (meaning I have to relock first)?
Is it correct that hboot version more current than my original, never updated one will cause problems (GPS, direct wifi, volume, bt, ...') with basically ALL Non-Sense roms?
Is it correct that once upgraded, I have no option whatsoever to downgrade?
What is the interaction between the hboot and the installed kernel - do some kernels work better with certain hboot versions?
Sorry for the flood of questions. As you can see, I really tried to find the answers. In some cases I'm rather sure of what I think, but some questions leave me baffled. At the moment it seems to me that I have to decide between either a Non-Sense JB, or a Sense JB, but I cannot switch between them (and retain all functionality of my phone).
Thanks in advance,
Thor
Click to expand...
Click to collapse
[*]If I got it right, I need a newer hboot version to run Sense JB Roms - correct?
Yes perfectly right.
[*]To upgrade to a newer hboot version, I need to download the correct RUU and install this, correct?
Yes, that is ONE OF THE methods to do it. Another method is, you can use this tool. (It doesn't require you to relock you phone)
[*]How do I find the "correct" RUU? And am I right that the RUU is an offical exe file, installing the Stock Rom on an unlocked phone only (meaning I have to relock first)?
First, head over here and check whether your CID has received the JB update (upgraded hboot). If it hasnt then you will have to wait.
If it has then you can search for your RUU.
[*]Is it correct that hboot version more current than my original, never updated one will cause problems (GPS, direct wifi, volume, bt, ...') with basically ALL Non-Sense roms?
Nope, it will ONLY cause a problem with the non-sense ROMS that were built on the older base , i.e. the ones running android 4.1.2 , newer ROMS like android 4.2.1 builds will work perfect, and that too only gps is a problem. Also, most of the devs have found the patch to fix this problem.
[*]Is it correct that once upgraded, I have no option whatsoever to downgrade?
yes, that is correct.
[*]What is the interaction between the hboot and the installed kernel - do some kernels work better with certain hboot versions?
There is no such relation. The only relation is that the kernels wont work only, i.e. the kernels built on the older source code wont work at all on the upgraded hboot. And there are no custom JB kernels as of yet as HTC hasnt released the source code yet.
Hope this helped.

anks257 said:
[...]
[*]Is it correct that hboot version more current than my original, never updated one will cause problems (GPS, direct wifi, volume, bt, ...') with basically ALL Non-Sense roms?
Nope, it will ONLY cause a problem with the non-sense ROMS that were built on the older base , i.e. the ones running android 4.1.2 , newer ROMS like android 4.2.1 builds will work perfect, and that too only gps is a problem. Also, most of the devs have found the patch to fix this problem.
[...]
[*]What is the interaction between the hboot and the installed kernel - do some kernels work better with certain hboot versions?
There is no such relation. The only relation is that the kernels wont work only, i.e. the kernels built on the older source code wont work at all on the upgraded hboot. And there are no custom JB kernels as of yet as HTC hasnt released the source code yet.
Hope this helped.
Click to expand...
Click to collapse
Thanks for this VERY helpful reply! What I don't understand about the two points I've quoted: You say that most of the devs have found fixes so that 4.2.1 roms run perfectly, but at the same time that there are no custom JB kernels. I thought the gps problem had to be fixed in the kernel? But that's probably just my misassumption.
Even if my phone hadn't hadn't just badly broken, I'd stick to the old hboot for a while longer then. I don't want to switch to JB 4.2.1 yet, as there seems no way to get pdroid running on that.
Thanks for taking the time to answer (this goes to all of you who replied)!
Thorsten

What they mean is that they have patched the ramdisk in the 4.2 ROMs to work with the older 4.1 kernel's that we do have the sources for
Sent from my HTC One X using xda app-developers app

[Q] Jelly Bean HBOOTs...

So, I have a question... I've had a look around and I can't find an answer to it, but if it's already been asked just point me to the right place .
Basically, when Jelly Bean ROMs first came out, I was told I had to update my HBOOT, which I haven't done yet (still waiting on O2 to release the update for CID O2__001). Now, however, I've found JB ROMs that say they work on all HBOOTs (my current HBOOT is the same 1.12.0000 that the phone came with, I've not changed it). So:
1) Does this literally mean all HBOOTs? Can I install these ROMs on my One X in it's current state without a problem?
2) And, if this is the case now, I'm curious as to what changed, that means I don't have to update my HBOOT anymore?
Thanks, and sorry if I'm being daft...
Edit:
These are the ROMs I'm referring to (one is AOKP, one is CM10 and the other is AOSP):
http://forum.xda-developers.com/showthread.php?t=2052610
http://forum.xda-developers.com/showthread.php?t=1784185
http://forum.xda-developers.com/showthread.php?t=2013506

Correct, they work on ALL hboot versions, because they are non-sense roms. I can't explain more in-depht,but they work and that is the main thing.
The Sense JB roms still require updated hboot.

gk007 said:
So, I have a question... I've had a look around and I can't find an answer to it, but if it's already been asked just point me to the right place .
Basically, when Jelly Bean ROMs first came out, I was told I had to update my HBOOT, which I haven't done yet (still waiting on O2 to release the update for CID O2__001). Now, however, I've found JB ROMs that say they work on all HBOOTs (my current HBOOT is the same 1.12.0000 that the phone came with, I've not changed it). So:
1) Does this literally mean all HBOOTs? Can I install these ROMs on my One X in it's current state without a problem?
2) And, if this is the case now, I'm curious as to what changed, that means I don't have to update my HBOOT anymore?
Thanks, and sorry if I'm being daft...
Edit:
These are the ROMs I'm referring to (one is AOKP, one is CM10 and the other is AOSP):
http://forum.xda-developers.com/showthread.php?t=2052610
http://forum.xda-developers.com/showthread.php?t=1784185
http://forum.xda-developers.com/showthread.php?t=2013506
Click to expand...
Click to collapse
It you want to flash a Jelly Bean SENSE Rom you have to update your hboot to 1.3x.
There are aosp Jelly Bean Roms that work with all hboots, thats why you don't have to update your hboot.
The only thing I wonder about is, if there is an advantage between 1.31 and 1.39?

TToivanen said:
Correct, they work on ALL hboot versions, because they are non-sense roms. I can't explain more in-depht,but they work and that is the main thing.
The Sense JB roms still require updated hboot.
Click to expand...
Click to collapse
Ah, okay, thanks so much! I'm not bothered about Sense at all (Vanilla is much better )
Also, do you know if the tablet mode working in the latest AOKP build?

Not a word about it in ROM control if that's what you mean.
You can, however, enable tablet mode by setting dpi under 210. I personally don't like it, 'cause everything looked so tiny and was difficult to use.

[Q] Newb questions on bloatware and updating

Hi all,
My new M8 has the original stock 1.54.707.7 on it. I just installed TWRP and SuperSU. No other tamperings were done.
In the last few days the phone nags me to install the update of 2.22.707.3 but from what I read here, I need to return to stock recovery before I do that.
My questions are:
1) Is updating OTA considered easier and safer than flashing manually the version of my choice (most updated stock)?
2) Currently, all my bloatware are still installed, because I was not able to remove it in titanium backup (it crashed my phone!!). I read somewhere that I need to also do S-OFF before I can remove them? Is it true? I also read that after removing even a single piece of bloat, I can no longer update OTA. Is that true also? In case it is, my only option is to update to latest stock by flashing manually?
3) Will updating the version relock the bootloader and will force me to unlock it again?
4) If I'm not happy with the new version, is a full nandroid backup from TWRP enough to restore my phone to 1.54.707.7?
My apologies if I'm asking questions with obvious answers. I assure you that I read all information I could find, on and off XDA.
Thanks in advance,
Tal

talla1 said:
Hi all,
My new M8 has the original stock 1.54.707.7 on it. I just installed TWRP and SuperSU. No other tamperings were done.
In the last few days the phone nags me to install the update of 2.22.707.3 but from what I read here, I need to return to stock recovery before I do that.
My questions are:
1) Is updating OTA considered easier and safer than flashing manually the version of my choice (most updated stock)?
Click to expand...
Click to collapse
It is not really safer to do either one, but if you want to update firmware you will have to do an OTA (unless you are S-Off)
2) Currently, all my bloatware are still installed, because I was not able to remove it in titanium backup (it crashed my phone!!). I read somewhere that I need to also do S-OFF before I can remove them? Is it true? I also read that after removing even a single piece of bloat, I can no longer update OTA. Is that true also? In case it is, my only option is to update to latest stock by flashing manually?
Click to expand...
Click to collapse
If your bloatware is all still there it should be as easy as flashing back your stock recovery, accepting the OTA, and reflashing TWRP. Yes, if you remove bloatware it will make your job harder (but not much). You would then have to restore a nandroid from this thread (http://forum.xda-developers.com/showthread.php?t=2701376) but make sure you follow the directions closely!
3) Will updating the version relock the bootloader and will force me to unlock it again?
Click to expand...
Click to collapse
No.
4) If I'm not happy with the new version, is a full nandroid backup from TWRP enough to restore my phone to 1.54.707.7?
Click to expand...
Click to collapse
Yes. However, I know for a fact that the OTA to Android 4.4.3 updates your firmware, which I am not sure is quite as easy to reverse. But let me put it this way... You probably will not want to go back after these OTAs. They will only make your phone better.

Drax TD said:
However, I know for a fact that the OTA to Android 4.4.3 updates your firmware, which I am not sure is quite as easy to reverse.
Click to expand...
Click to collapse
With S-on, reverting firmware is impossible.
Drax TD said:
But let me put it this way... You probably will not want to go back after these OTAs. They will only make your phone better.
Click to expand...
Click to collapse
I agree. And remember that a lot of security updates are made with each OTA. So unless you experience some major bugs, its really not a good idea to step backwards.
---------- Post added at 02:42 PM ---------- Previous post was at 02:14 PM ----------
talla1 said:
1) Is updating OTA considered easier and safer than flashing manually the version of my choice (most updated stock)?
Click to expand...
Click to collapse
Agree with above notion, that OTA is not necessarily "safer". And "easier" I suppose is debatable in your case. If you don't want to s-off, you might choose to OTA to get the latest firmware (hboot, radio, etc.), then install custom recovery and root again.
If you want S-off and complete freedom, I'd just do that, stay modded and not mess with the OTA.
These are probably some pretty complex topics for a n00b, so read around and learn as firmware, s-off, etc. are already being discussed in lots of other threads.
talla1 said:
2) Currently, all my bloatware are still installed, because I was not able to remove it in titanium backup (it crashed my phone!!). I read somewhere that I need to also do S-OFF before I can remove them? Is it true? I also read that after removing even a single piece of bloat, I can no longer update OTA. Is that true also? In case it is, my only option is to update to latest stock by flashing manually?
Click to expand...
Click to collapse
Nope, not true. You need a modded kernel, to remove the system write protection.
http://forum.xda-developers.com/showthread.php?t=2701816

Thanks for the info Drax and Redpoint!
After doing some more reading, I decided to move over to Android Revolution custom rom.
I figured that I should stop insisting on staying with the original stock if the difficulties are piling up against me. I chose Android Revolution as I do like the sense look and feel and don't want to give up the built in features of the device (like use of the special camera app or sense ui launcher).
I got a nandroid backup and also titanium backup of all my apps.
Wish me luck now..
Regarding your answers, I'm still confused about firmware upgrading/reverting. Android revolution comes with a firmware based on 2.22.401.4 and my phone currently have 1.54.707.7. Your answers imply that restoring my 1.54.707.7 nandroid backup will NOT work? So why am I bothering with the backup in the first place?

talla1 said:
Regarding your answers, I'm still confused about firmware upgrading/reverting. Android revolution comes with a firmware based on 2.22.401.4 and my phone currently have 1.54.707.7. Your answers imply that restoring my 1.54.707.7 nandroid backup will NOT work? So why am I bothering with the backup in the first place?
Click to expand...
Click to collapse
Flashing a custom rom will never modify your firmware. The only ways to update firmware are to:
1 - Return to stock and accept OTA
2 - (only if you are S-off) flash firmware manually
You will be running the rom with a different firmware than what it is built for, which probably won't cause problems, but certainly could. As an example, ViperOne 2.0.0 is completely functional on the original m8 firmware, but has an extremely long boot time (5 minutes). I can't give specifics on other things which I have not tested, but that is one example. You can feel free to go ahead and flash whatever roms you want as they will not touch your firmware. If you want to change firmware, see directions above.

Drax TD said:
Flashing a custom rom will never modify your firmware. The only ways to update firmware are to:
1 - Return to stock and accept OTA
2 - (only if you are S-off) flash firmware manually
You will be running the rom with a different firmware than what it is built for, which probably won't cause problems, but certainly could. As an example, ViperOne 2.0.0 is completely functional on the original m8 firmware, but has an extremely long boot time (5 minutes). I can't give specifics on other things which I have not tested, but that is one example. You can feel free to go ahead and flash whatever roms you want as they will not touch your firmware. If you want to change firmware, see directions above.
Click to expand...
Click to collapse
Well, I moved over to Android Revolution HD, and now I have two issues that I know of, presumabely because of the mismatched firmware:
1) long boot time, like you already anticipated I would have.
2) I can't play most of mp3 files! They just play silence, even though they worked correctly before the update!!
Now, I had no idea that ROM and FIRMWARE are two different concepts. I always thought they were synonims.
How should I go about to fix this? I thought to:
1) Backup my current state with nandroid.
2) Restore my stock nandroid backup
3) install stock recovery
4) accept OTA to update my firmware
5) install TWRP
6) Restore my Android revolution backup
Does this sounds reasonable? Will it be easier to do s-off and flash firmware myself?
Thanks in advance!
Tal

talla1 said:
Well, I moved over to Android Revolution HD, and now I have two issues that I know of, presumabely because of the mismatched firmware:
1) long boot time, like you already anticipated I would have.
2) I can't play most of mp3 files! They just play silence, even though they worked correctly before the update!!
Now, I had no idea that ROM and FIRMWARE are two different concepts. I always thought they were synonims.
How should I go about to fix this? I thought to:
1) Backup my current state with nandroid.
2) Restore my stock nandroid backup
3) install stock recovery
4) accept OTA to update my firmware
5) install TWRP
6) Restore my Android revolution backup
Does this sounds reasonable? Will it be easier to do s-off and flash firmware myself?
Thanks in advance!
Tal
Click to expand...
Click to collapse
You steps are good enough to fix the long boot time problem (item 1)
Item 2 - you need to reflash ROM and AVOID selecting Harmon Kardon mod. HK mod works on S-Off device only

ckpv5 said:
You steps are good enough to fix the long boot time problem (item 1)
Item 2 - you need to reflash ROM and AVOID selecting Harmon Kardon mod. HK mod works on S-Off device only
Click to expand...
Click to collapse
Thanks for the quick answers!
Regarding 2, I suspected as such, so I tried disabling it from the settings menu and it didn't help.. Shouldn't it have worked..? I will definately try reflashing though.
Regarding 1, as I said before, being a total HTC noob, I only found out about the concept of firmwares just yesterday and it's a shame that the instructions for Android Revolution doesn't say a word of warning about that (as far as my eyes can see). The OTA I have is for 2.22.707.3 and I see Android Revolution is based on 2.22.401.4. Is it close enough to not cause any known issues?
If I'm already reflashing, it would also be nice to understand what the rest of the Android Revolution mods means (there was something there about sqlite optimizations and some others..) I couldn't find explanations anywhere on xda or the web.
Thanks again! I must say that as this being a newer device and less popular than i9300, the information is still a little scarce, but the people here are really nice and helpful!

talla1 said:
The OTA I have is for 2.22.707.3 and I see Android Revolution is based on 2.22.401.4. Is it close enough to not cause any known issues?
Click to expand...
Click to collapse
What you need to see is the firmware is 2.22.xxx.x or higher. Or the hboot is 3.18 or higher to have the ROM work flawlessly.
See in my sig .. with 2.22.707.3 I can use any custom Sense ROM without issues. In fact it works better as the radio region is correct for my region. If you're from Asia, it is not wise to have a EU radio region even it works.
Previously on other device like HTC One X people were talking about hboot and now people are talking about firmware 2.22 ... actually it means the same thing. You need a newer firmware/hboot to run 4.4.3 ROM.
I won't comment about mods/tweaks as I don't use them. You can search more info of them on XDA.
A tip how to search thing .. on google type for example "sqlite optimizations xda", you'll find many info on that.
It says sqlite optimizations - Faster access to contacts, messages etc...

ckpv5 said:
What you need to see is the firmware is 2.22.xxx.x or higher. Or the hboot is 3.18 or higher to have the ROM work flawlessly.
See in my sig .. with 2.22.707.3 I can use any custom Sense ROM without issues. In fact it works better as the radio region is correct for my region. If you're from Asia, it is not wise to have a EU radio region even it works.
Previously on other device like HTC One X people were talking about hboot and now people are talking about firmware 2.22 ... actually it means the same thing. You need a newer firmware/hboot to run 4.4.3 ROM.
I won't comment about mods/tweaks as I don't use them. You can search more info of them on XDA.
A tip how to search thing .. on google type for example "sqlite optimizations xda", you'll find many info on that.
It says sqlite optimizations - Faster access to contacts, messages etc...
Click to expand...
Click to collapse
Thanks again for the quick response..
I see from your sig that I'm going to end up with the same version as yours, so I should be OK, but I don't understand HOW DO YOU KNOW this stuff?? If I want to UNDERSTAND this and not just follow instructions blindly - what do I do? More specifically:
1) What IS the version of the firmware? Isn't 2.22.707.3 the stock ROM version? I understand that flashing OTA also upgrades my firmware at the same time, but isn't it strange that it doesn't have a specific number?
2) Is hboot 3.18 means that the BOOTLOADER version is 3.18? Is updating OTA also updates hboot as part of the firmware? I couldn't find any explanations on what exactly IS hboot (not in searching and not in the FAQ).
3) How do you know what is the exact prerequisites for Android Revolution (or any rom for that matter)? How do you know you need 2.22.xx firmware and 3.18 hboot? Is there an obvious reason that I don't understand as to why this information is not written explicitly in the post?
Thanks allot.
Tal

talla1 said:
....but I don't understand HOW DO YOU KNOW this stuff?? If I want to UNDERSTAND this and not just follow instructions blindly - what do I do? More specifically:
Click to expand...
Click to collapse
Read a lot, there are many fantastic information on XDA and learn from experience ... thing that I did and still doing since my first HTC device, an ELF in 2008.
talla1 said:
1) What IS the version of the firmware? Isn't 2.22.707.3 the stock ROM version? I understand that flashing OTA also upgrades my firmware at the same time, but isn't it strange that it doesn't have a specific number?
Click to expand...
Click to collapse
Firmware does have a version no. It is written on the android-info.txt. You can find it in the firmware.zip
ROM version is written on build.prop
talla1 said:
2) Is hboot 3.18 means that the BOOTLOADER version is 3.18? Is updating OTA also updates hboot as part of the firmware? I couldn't find any explanations on what exactly IS hboot (not in searching and not in the FAQ).
Click to expand...
Click to collapse
More or less yes ... when you boot to bootloader ... it is clearly written there as hboot-3.18.0.0000 if it is 3.18, 3.16.0.0000 if it is 3.16
hboot is something like a bios in a PC. This is where all partitions are, like system partition, user partition, recovery partition and so on.
See ... I can find one info on hboot : http://forum.xda-developers.com/showthread.php?t=2700666
talla1 said:
3) How do you know what is the exact prerequisites for Android Revolution (or any rom for that matter)? How do you know you need 2.22.xx firmware and 3.18 hboot? Is there an obvious reason that I don't understand as to why this information is not written explicitly in the post?
Click to expand...
Click to collapse
When a ROM base is 2.22.xxx.x then you need a firmware same or bigger than 2.22.xxx.x
People with 2.23.xxx.x firmware don't need to downgrade to 2.22.xxx.x as the firmware is new enough for the ROM with base 2.22.xxx.x
Why the information is not written in the thread, that is up to OP. Most of the time OP expect people will know what to do when there is a new base ROM.

ckpv5 said:
You steps are good enough to fix the long boot time problem (item 1)
Item 2 - you need to reflash ROM and AVOID selecting Harmon Kardon mod. HK mod works on S-Off device only
Click to expand...
Click to collapse
Hi,
Well, I did the steps above and also reflashed ARHD without HK mod. Everything looks (and sounds) great now. In retrospect, it's not as bad as what I had to go through with my operator locked i9300 (finding out too late about EFS versions that gets automatically updated, and the fact that this partition not included in the nandroid backup and I can't restore the backup I made).
I still think that not mentioning the firmware thing in the ARHD post is a clear noob trap. And also the fact about the HK mod needing s-off. Now how would I ever guessed that disabling from settings is not enough to fix it and I need to reflash without it...?
Anyways, thanks allot for the personal escort. It made the ordeal allot less horrible.
Tal