Develop Bugs

[Q] Flashing Asian firmware in a European version or vice versa

Hi I would like to know if there would be a problem if I flash the official rue of an Asian desire z with a european version or vice versa?
I bought my phone second hand and I decided to flash the 1.34.707.1 version into my originally 1.72 desire z. Now my phone cannot find updates. It keeps telling me that there is no update even if check manually.
I know that I can flash a higher version by downloading a higher rue version but what I wanted to find out if I can no longer receive ota updates because of what I did.
Since when I was in 1.72 my phone did not notify me of the 1.82 update too...
I don't know what's wrong.. Please help. Thank you.

I think if you are SuperCID and S-Off, it would work. Otherwise, it won't let you flash the ROM from another region.
Also, if you flash an official ROM, you will lose root, and you can't get it back on any ROM version higher than 1.34. For this reason, if you downgraded to 1.34 for purposes of rooting, you don't want the OTA updates, anyway.
If you're rooted and S-Off, and you want a more updated ROM version, just flash the Virtuous custom ROM. Its mostly stock 1.85, but rooted, and with a few cool added features and some optimizations.

Hi, the thing is I'm not very knowledgeable when it comes to rooting. I read the posts here specifically in the wii section and I don't think I have the skills to pull it off and risk bricking my phone.
I think my phone is not rooted or it was before but not anymore, since as mentioned I flashed an official ruu.
So basically, I should still be able to receive OTA's from HTC right? I was wondering why my phone keeps telling me there's no update when the software number is 1.34 stock and not rooted. Shouldn't it notify me that there's an update at least regardless of whether I want to or not?

If you are not rooted, why did you downgrade to 1.34?
I also don't understand why you want to flash the RUU from a different region. If you aren't SuperCID and S-Off it won't work. Why not just flash the latest official RUU for your phone versions/region if you want to be updated and don't care about root?
I'm not sure why your OTA's don't work. I'm still on 1.34 (well, back to it), and I still get notifications to update.

redpoint73 said:
If you are not rooted, why did you downgrade to 1.34?
I also don't understand why you want to flash the RUU from a different region. If you aren't SuperCID and S-Off it won't work. Why not just flash the latest official RUU for your phone versions/region if you want to be updated and don't care about root?
I'm not sure why your OTA's don't work. I'm still on 1.34 (well, back to it), and I still get notifications to update.
Click to expand...
Click to collapse
@redpoint73
I bought the phone from a friend of mine. I noticed that it had eng hboot and had s-off.
I have zero knowledge about rooting. When the gingerbread test rom for the desire z came out, I flashed the pc10img.zip via the bootloader, however since it was very buggy and laggy, I decided to flash stock desire z rom.
Having no knowledge about rooting I read some of the threads in this forum and learned that flashing an official rom i.e. the RUU would be the easiest way to return back to stock.
It worked, I am using stock rom. I experimented and found out that I can flash any of the RUU, so I chose any of the WWE release. I decided to flash an older firmware version specifically, the 1.34.707.1.
Now the problem is my phone doesn't prompt me with an update, even after checking in about phone > check for update.
I still have s-off but eng hboot is gone. To clarify I was not the one who rooted the phone, so I have no idea what to do.
Is it possible that the previous owner tweaked something in the phone that would absolutely prevent it from receiving OTA?
I am just worried since I have a feeling that the gingerbread OTA will be released in a few weeks since the update for the Desire HD is already out.
Please help and thank you again. I extremely as a NOOB!

qtlestat said:
I am just worried since I have a feeling that the gingerbread OTA will be released in a few weeks since the update for the Desire HD is already out.
Click to expand...
Click to collapse
I wouldn't worry about getting the official Gingerbread ROM OTA. It will probably be posted here or at shipped-roms.com long before you would get it OTA.

[Q[ Questions on RUU

Hey Guys,
I just had some questions regarding RUU's and sort of trying to understand them.
Do RUU's update everything that normal custom ROM's cannot, i.e. like the OTA's? So updating drivers and hboot etc?
Main reason is that if it does update everything then on the next big update I would probably want to do an RUU install even if it means loosing all data.
With regards to the RUU do I need all three of the following:
- Stock ROM
- Stock Recovery
- Locked bootloader
Or do I need JUST a locked bootloader?
Thanks

Yes you will get updates if you flash a ruu and ruu 's are pure stock ruu's are used when we need to put the stock Rom back on our device when we need to send it in for repair's and also when we prefer the stock Rom over a custom Rom I my self prefer custom Rom over a stock Rom and sometimes when a custom Rom isnt performing the way it should some people will simply go back to stock by flashing a ruu
Sent From My Viper S 1.2.0 with true s off by alpha revolutionary

jslim38 said:
Yes you will get updates if you flash a ruu and ruu 's are pure stock ruu's are used when we need to put the stock Rom back on our device when we need to send it in for repair's and also when we prefer the stock Rom over a custom Rom I my self prefer custom Rom over a stock Rom and sometimes when a custom Rom isnt performing the way it should some people will simply go back to stock by flashing a ruu
Sent From My Viper S 1.2.0 with true s off by alpha revolutionary
Click to expand...
Click to collapse
Thanks, my main reason is actually not to say on an RUU but I was hoping to install an RUU, get all the updates to my firmware and drivers, then unlock bootloader again and install a custom ROM.

They should be updated by a custom rom. Only thing that isnt touched is the HBOOT i think. But reflash stock recovery relock the bootloader then run the ruu.

Flashing an RUU first if available is the way to go personally
Sent from my HTC One X using xda premium

I readin a lot on here and I read somewhere updateing with ruu updates hboot and hboot is some sort of security so updateing it could make getting s-off harder
Sent from my HTC One X using xda premium

Updating the HBoot means adding more layers of security, which imo is not something we enjoy here on XDA
Personally, I prefer going with a custom ROM that is almost like stock (preferably ARHD) which with every update brings the improvements brought to us by HTC and even more.
Also with ARHD for example, upgrading from one version to a newer one rarely requires you to wipe all your data which is very annoying imo.

I've been on Custom roms since I had my phone so I had missed the OTA update for 1.xxx.11 and the 2.xx versions, now with the a big 3.xx version on the horizon, my main concern is if my Custom ROM's are not updating some critical firmware drivers and such that would have benefitted my phone.
Tbh it's still not clear to me what Custom ROM's cannot update, at first I thought it was just the HBOOT but then I read on a recent thread that apparently things like GPU drivers and other essential hardware firmware drivers may not get updated either which sounds like a big deal. Hence I was thinking with the release of 3.xx I should do an RUU install just to be sure and then go ahead to a Custom ROM.
I understand that having my HBOOT updated could mean S-OFF is harder but the way things are, it doesn't look like were any close to getting it either, who knows maybe even a future HBOOT update might have an easier S-OFF is HTC decide to relax it a bit from consumer pressure?

When developers get their hands on new RUUs they base their custom Roms on them, and therefore you will get the new updates in terms of drivers and other software related things.
Also, kernels bring new improvements as they are updated, and developers also build their ROMs on these kernels. However, you can flash custom kernels separately if you find one that has additional "improvements" you like.
In short, custom ROMs that are maintained/updated regularly (ARHD is one of the best imo) is all you need to stay up to date with all the new improvements.
The only reason I ever download any RUU is in case something went wrong with my phone, and I wanted to temporarily return to stock.

Ah right, I was thinking more of the S-ON security restriction not letting custom ROM's fully update everything except radio, kernel and ROM but RUU's are given the full access to update everything?

iq-dot said:
Ah right, I was thinking more of the S-ON security restriction not letting custom ROM's fully update everything except radio, kernel and ROM but RUU's are given the full access to update everything?
Click to expand...
Click to collapse
I don't think there is consensus on what can be updated and what cannot.
Here's my take: an OTA has access to everything, as does an RUU, but the point is that they flash signed images, and the phone will allow signed images to be flashed (subject to matching CID, etc.).
It's possible to flash kernel with the boot.img, and also possible to flash kernel modules, which means that drivers can be updated.
It's possible to flash "radios" (often as part of the ROM), and there is an app to get updated RILs, so it would seem that the RIL has not been confused with the radio. However, since the bootloader appears to get the radio version from a text file, rather than the radio, there's some doubt as to whether the radio is really updated (since the bootloader disagrees).
Obviously we can unlock and gain access to flashing unsigned recovery, boot (kernel/ramdisk) and ROM images.
Outside of this, it's not impossible that there are areas of the phone that still require flashing of signed images, such as for firmware updates of other bits of hardware not previously mentioned (speculatively: lower level bits of "radio", cpu microcode, gpu firmware, etc.), which may or may not be flashable with an RUU (or maybe even an OTA). However, there is nothing in an RUU that cannot be done with tools we already have, so if there was a "fastboot flash cpu_microcode" option, somebody would have found it. I haven't looked at full list of fastboot commands, but I don't recall coming across anything like that.

xbiggyl said:
When developers get their hands on new RUUs they base their custom Roms on them, and therefore you will get the new updates in terms of drivers and other software related things.
Also, kernels bring new improvements as they are updated, and developers also build their ROMs on these kernels. However, you can flash custom kernels separately if you find one that has additional "improvements" you like.
In short, custom ROMs that are maintained/updated regularly (ARHD is one of the best imo) is all you need to stay up to date with all the new improvements.
The only reason I ever download any RUU is in case something went wrong with my phone, and I wanted to temporarily return to stock.
Click to expand...
Click to collapse
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM

EddyOS said:
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM
Click to expand...
Click to collapse
Do you know what, specifically?

I don't, no, it's just a personal preference I suppose. I updated to the 2.17 RUU (UK unbranded) and then went onto a custom ROM based on the same RUU so I know everything is compatible. Whether it has any real affect I don't know but seeing as Mike used to have 'firmware' packages for other HTC handsets it would lead me to believe he would with the One X if we had S-OFF

EddyOS said:
Mike used to have 'firmware' packages for other HTC handsets it would lead me to believe he would with the One X if we had S-OFF
Click to expand...
Click to collapse
...there are a lot of masked partitions, eh? Who knows.

A lot of the partitions were listed in the S-OFF thread but as to what they actually contain/do is open to discussion - it could be a custom ROM it's own is enough but without S-OFF we'll never really know

EddyOS said:
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM
Click to expand...
Click to collapse
Have you read anywhere of any improvements offered exclusively by RUUs or you're simply speculating?
I know some partitions (that appeared to be in the HOX) are not accessible by Custom Roms, but has anyone ever claimed to have experienced an improvement in any way by flashing an RUU that people flashing custom Roms haven't?
Sent from my HTC One X using Tapatalk 2

[Q] Flashing ROMS and having S-ON

Hey guys, i just flashed my M8 using vomer's Guide, everything went great except for the S-OFF part, firewater didn't work on my variant (T-Mobile Version), i was just wondering if it will affect my phone in any way while trying to flash a custom rom, right now im looking at flashing Skydragon's GPE or Sense version

You can still flash roms with s on, just not do the GPe conversations

The ones known as RUU right?

If you flash a Sense 2.22 based custom ROM, its recommended that you flash the updated firmware package (S-off required) or else wait until the 2.22 based OTA rolls out for your version (which will include "official" firmware).
If the updated firmware is not installed, 2.22 based ROMs will usually cause some major bugs, like excessive long boot time, broken WiFi and Bluetooth, etc.
S-off is usually not "required" to flash a ROM per se. This is an exception where the older firmware modules (not included in the ROM itself) are not playing well with the newer based ROMs.

redpoint73 said:
If you flash a Sense 2.22 based custom ROM, its recommended that you flash the updated firmware package (S-off required) or else wait until the 2.22 based OTA rolls out for your version (which will include "official" firmware).
If the updated firmware is not installed, 2.22 based ROMs will usually cause some major bugs, like excessive long boot time, broken WiFi and Bluetooth, etc.
S-off is usually not "required" to flash a ROM per se. This is an exception where the older firmware modules (not included in the ROM itself) are not playing well with the newer based ROMs.
Click to expand...
Click to collapse
So if i flash Skydragon's Sense based rom i will encounter major bugs? well thats too bad
but the Skydragon GPE Rom is fine right?

Sinchero said:
So if i flash Skydragon's Sense based rom i will encounter major bugs? well thats too bad
Click to expand...
Click to collapse
You can always try it and see. I'm not sure if 100% of folks will have this issue (if you do not update firmware), but others have said you will "probably" have some major bugs.
On the other hand, if you are s-off and already have fastboot setup on your computer, the process to update firmware takes maybe 5 or 10 minutes.
Sinchero said:
but the Skydragon GPE Rom is fine right?
Click to expand...
Click to collapse
Not completely certain, you should read/search the Skkydragon GPE thread, or maybe somebody who knows can chime in.

redpoint73 said:
You can always try it and see. I'm not sure if 100% of folks will have this issue (if you do not update firmware), but others have said you will "probably" have some major bugs.
On the other hand, if you are s-off and already have fastboot setup on your computer, the process to update firmware takes maybe 5 or 10 minutes.
Not completely certain, you should read/search the Skkydragon GPE thread, or maybe somebody who knows can chime in.
Click to expand...
Click to collapse
i just found out that they have a separate version for the T-Mobile variant, maybe thats what i will install, on a side note, do you think it would be a good idea to take the plunge and pay for the sunshine method to gain S-OFF?

Sinchero said:
do you think it would be a good idea to take the plunge and pay for the sunshine method to gain S-OFF?
Click to expand...
Click to collapse
Its very much a personal choice. It you want the freedom to be able to flash firmware packages, radios, etc. at will; and $25 is something that you can afford to give away, then I'd say its recommended.
I had the luxury of being able to s-off earlier on for free, with firewater.

Well, I'm s-on and I've already had gpe edition installed.
Sent from HTC One m8, or maybe not anymore

redpoint73 said:
Its very much a personal choice. It you want the freedom to be able to flash firmware packages, radios, etc. at will; and $25 is something that you can afford to give away, then I'd say its recommended.
I had the luxury of being able to s-off earlier on for free, with firewater.
Click to expand...
Click to collapse
All right, thanks for the help, i think i will leave S-ON, maybe some time later i will decide to pay the $25 so i can have S-OFF.
mr.loverlover said:
Well, I'm s-on and I've already had gpe edition installed.
Sent from HTC One m8, or maybe not anymore
Click to expand...
Click to collapse
The Skydragon version or the stock version?

I can't remember which gpe rom I've tested, however now I'm on stock based skydragon 4.4.3 (not redbull edition, as it was too much overclocked).
Sent from HTC One m8, or maybe not anymore

Sinchero said:
All right, thanks for the help, i think i will leave S-ON, maybe some time later i will decide to pay the $25 so i can have S-OFF.
Click to expand...
Click to collapse
If the 2.22 firmware is all you want s-off for, probably not a bad idea to just wait for the T-Mobile OTA rollout. Then you can just install the new firmware "official" OTA way. Once the firmware is updated, you should be able to flash whatever you want with S-on.

redpoint73 said:
If the 2.22 firmware is all you want s-off for, probably not a bad idea to just wait for the T-Mobile OTA rollout. Then you can just install the new firmware "official" OTA way. Once the firmware is updated, you should be able to flash whatever you want with S-on.
Click to expand...
Click to collapse
That's all i want it for, maybe it is a good idea to wait for T-Mobile to roll out the update, anyway, i flashed the Skydragon GPE ROM yesterday and everything is going fine, i have yet to test battery life, since today it's my first day of use, but everything seems to be running fine, thank you for all your help.

[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

[Q] Stuck in somewhere with not wifi

Decided to take the last Software update from HTC and messed up everything.
I am unlocked with S-ON so decided to relock and start the process, now after 3 days on reading and testing different way i have this:
unlock S-on Hboot 3.18.00000
invalide radio and os info. Tried Android revolution and Maximus latest ROM on both wifi don't work.
Tried to go s-off till i got the message that my device has been patched by HTC
I don't mind to go with a ROM or full back to stock but need some help getting the device working with wifi

This has been discussed in many (probably dozens) of existing threads.
The latest ARHD and Maximus require the latest firmware, which corresponds with hboot 3.19.
You either need to update the firmware manually with S-off, or install the newest OTA (if available for your version). Alternately, use a 2.xx software based ROM to get WiFi working.

redpoint73 said:
This has been discussed in many (probably dozens) of existing threads.
The latest ARHD and Maximus require the latest firmware, which corresponds with hboot 3.19.
You either need to update the firmware manually with S-off, or install the newest OTA (if available for your version). Alternately, use a 2.xx software based ROM to get WiFi working.
Click to expand...
Click to collapse
Been reading more than the dozen mentioned and in any case thank you for the information.
Got the Wifi working installing a previous ROM as you suggest and now will start the process to get s-off and proceed. Even tried Sumshine do not mind to pay for it but can't install the apk on the phone.....
Is not my day probably

redpoint73 said:
This has been discussed in many (probably dozens) of existing threads.
The latest ARHD and Maximus require the latest firmware, which corresponds with hboot 3.19.
You either need to update the firmware manually with S-off, or install the newest OTA (if available for your version). Alternately, use a 2.xx software based ROM to get WiFi working.
Click to expand...
Click to collapse
want to update also the other that faced the same issues.
Loaded MaximusHD 7 and got wifi working
Through sunshine got s-OFF now wante to try to get all the best to have all the upgrade.
Will have to ready dozens more ot threads, if someone has help and suggestion is welcome

succe said:
want to update also the other that faced the same issues.
Loaded MaximusHD 7 and got wifi working
Through sunshine got s-OFF now wante to try to get all the best to have all the upgrade.
Will have to ready dozens more ot threads, if someone has help and suggestion is welcome
Click to expand...
Click to collapse
Just look in the Development section for the firmware collection. Or just read through the ARHD or Maximus threads (starting from the most recent posts and going back from there), and they will probably lead you to the same place. Seriously, its not that hard to search for info on XDA. I never once after modding 6 Android and 2 Windows Mobile devices before that, had to ask folks to lead me to the info. Most of us just search and find it ourselves. Reading through the thread for the ROM you are having problems with will lead you to the answer 99% of the time; and you should do this when you flash any ROM.