Related
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
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
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
So I've recently decided to get the newer version of the Cyanogenmod for my One X (Android 4.2). However, after finding out that I get an error each time I try to install the new version, I did some searching and realized that I needed the newer version of HBOOT. I now know how, but I get the warning that after doing so, I will be unable to install a non-sense ROM. Is that so, and if true, is there a way around it apart from installing an earlier version of Cyanogenmod? Thank you
Not true afaik. Aosp roms runs fine on the higher hboots (JB). In fact there are JB non sense roms that need a JB hboot to run ! Do you have some links where that is written ?
http://forum.xda-developers.com/showthread.php?t=1786696
Quote: 'supports only newer hboots (1.28 and above)' - written in red. I think I have 1.12.
It confirms that you need a JB hboot of 1.28 at least....or higher, so it wont run on 1.12. You need to update the hboot in order to run it......so the question about not being able to run a Aosp rom on the higher hboots is not true ! You need one to run them
Thanks - just wanted to check to make sure I don't do anything wrong by upgrading the HBOOT.
Nope ....go right ahaed and flash CM10.1 after
I did a little too much screwing around with my One V earlier today, and I'm honestly afraid that I've hard-bricked it at this point. I have middling experience when it comes to RUU installs and flashing/experimenting with new ROMs and kernels - but my last root/ROM flash attempt didn't go as planned. I'd installed the stock RUU earlier in the day in order to get the radio update (which, as I now realize, was more or less pointless as the new radio sounds like it's a pain to deal with), and had just finished unlocking and rooting the phone. I booted into TWRP to flash my favorite ROM, and I'm pretty sure this is where I messed up: rather than just wiping System, Cache, Dalvik, and Factory Resetting, I opted to wipe everything I could select in that menu. Please don't ask why (I was tired and out of it, and had planned on re-formatting my SD card at some point - it made sense at the time...) - I now realize how stupid this was, and I'm going out of my mind trying to fix it.
I thought it would be a simple matter of flashing the RUU file I currently have, but alas, I now have hboot 1.57 and the newest radio version - so I get an "hboot is older!" error when I attempt to install this older RUU. I can't locate an RUU based on hboot 1.57, and I'm not sure whether I'm just looking in the wrong places or interpreting RUU filenames incorrectly (perhaps certain RUUs would prove compatible despite incorporating a slightly downgraded hboot...?).
Any help you can offer would be greatly appreciated - if you need any more information from me in order to provide a solution, please let me know and I'll respond as quickly as I can.
EDIT: I have a CDMA One V.
don't boots said:
I did a little too much screwing around with my One V earlier today, and I'm honestly afraid that I've hard-bricked it at this point. I have middling experience when it comes to RUU installs and flashing/experimenting with new ROMs and kernels - but my last root/ROM flash attempt didn't go as planned. I'd installed the stock RUU earlier in the day in order to get the radio update (which, as I now realize, was more or less pointless as the new radio sounds like it's a pain to deal with), and had just finished unlocking and rooting the phone. I booted into TWRP to flash my favorite ROM, and I'm pretty sure this is where I messed up: rather than just wiping System, Cache, Dalvik, and Factory Resetting, I opted to wipe everything I could select in that menu. Please don't ask why (I was tired and out of it, and had planned on re-formatting my SD card at some point - it made sense at the time...) - I now realize how stupid this was, and I'm going out of my mind trying to fix it.
I thought it would be a simple matter of flashing the RUU file I currently have, but alas, I now have hboot 1.57 and the newest radio version - so I get an "hboot is older!" error when I attempt to install this older RUU. I can't locate an RUU based on hboot 1.57, and I'm not sure whether I'm just looking in the wrong places or interpreting RUU filenames incorrectly (perhaps certain RUUs would prove compatible despite incorporating a slightly downgraded hboot...?).
Any help you can offer would be greatly appreciated - if you need any more information from me in order to provide a solution, please let me know and I'll respond as quickly as I can.
EDIT: I have a CDMA One V.
Click to expand...
Click to collapse
Well i dont have a CDMA one v but i know that the RUU for hboot greater than v1.17 had not been released.. So the best method to recover stock ROM is using a stock ROM backup with the same hboot and radio version , if anyone bought a one v recently he should be on the latest hboot and radio version , you can get a stock backup from such a person or search on xda for such a backup..
There isn't a RUU for the Hboot 1.57 and the newest radio. Sorry to give the bad news. You will either have to use a nandroid backup or install one of the custom roms such as RhythmicRom, e3remeSense or myOneV. Good luck on your rooting journey!
Thanks. I ended up successfully installing Rhythmic, but I can't get x3reme Sense (my preferred ROM) to work, for some reason (which is sort of ironic - I know Rhythmic incorporates a fix to allow for compatibility, but I thought one of the OTA updates was supposed to prevent installing anything not based on Sense). Oh, well.
If you'll use this kernel, then x3reme Sense will boot. I tried it for a while, but for a sense based rom I prefer myOne. If you want to try it, Cyanprimo will boot and run fine with the RhythmicRom v1.2 kernel. That is my daily driver(at least for now).
http://forum.xda-developers.com/showthread.php?t=2261819