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
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
Hi all,
I have installed RD-MIUI Jelly Bean 4.1.2 (http://miuiandroid.com/community/th...-bean-4-1-2-2-11-16-en-cm10-16-11-2012.17645/) on my HOX and it is working fine (a few bugs, but they are known).
My question is: why could I install it in the first place??? I didn't touch the hboot, but for many roms it looks like I need to upgrade it.
Why, for example; I am not supposed to be able to install Android Revolution HD 15?
See:
http://forum.xda-developers.com/showthread.php?t=1843585
http://forum.xda-developers.com/showthread.php?t=1957376
http://forum.xda-developers.com/showthread.php?t=1843585
My CID is HTCCN701 - so no firmware for it.
Can someone can explain to me how:
cid
hboot
kernel
rom
are related? And, although I understand the word and the wiki description, maybe a bit of explanation of what are concretely these entities, like which file is responsible for what, how these are layered, etc... I have a programming background, but I am still a bit lost concerning the architecture of android and its devices...
Thanks in advance!
froal said:
Hi all,
I have installed RD-MIUI Jelly Bean 4.1.2 (http://miuiandroid.com/community/th...-bean-4-1-2-2-11-16-en-cm10-16-11-2012.17645/) on my HOX and it is working fine (a few bugs, but they are known).
My question is: why could I install it in the first place??? I didn't touch the hboot, but for many roms it looks like I need to upgrade it.
Why, for example; I am not supposed to be able to install Android Revolution HD 15?
See:
http://forum.xda-developers.com/showthread.php?t=1843585
http://forum.xda-developers.com/showthread.php?t=1957376
http://forum.xda-developers.com/showthread.php?t=1843585
My CID is HTCCN701 - so no firmware for it.
Can someone can explain to me how:
cid
hboot
kernel
rom
are related? And, although I understand the word and the wiki description, maybe a bit of explanation of what are concretely these entities, like which file is responsible for what, how these are layered, etc... I have a programming background, but I am still a bit lost concerning the architecture of android and its devices...
Thanks in advance!
Click to expand...
Click to collapse
Upgrading the hboot is only required for Sense-based Jelly Bean ROMs. You will not require an upgraded Hboot to use AOSP/AOKP/CM10 based ROMs.
CID - basically just identifies region/carrier of phone
ROM - variations of the android OS, usually comes with custom software/tweaks etc.
Hboot - not too sure, but different versions have an effect on wifi, reception.
kernel - basically a component that serves as the bridge between software and hardware and allows them to communicate between each other.
tomascus said:
Upgrading the hboot is only required for Sense-based Jelly Bean ROMs. You will not require an upgraded Hboot to use AOSP/AOKP/CM10 based ROMs.
CID - basically just identifies region/carrier of phone
ROM - variations of the android OS, usually comes with custom software/tweaks etc.
Hboot - not too sure, but different versions have an effect on wifi, reception.
kernel - basically a component that serves as the bridge between software and hardware and allows them to communicate between each other.
Click to expand...
Click to collapse
Just see the hboot as the BIOS on a pc
Guys, thanks for the clarification!
Another question though... How come I would need to upgrade my hboot (keeping the BIOS analogy) so that Jellybean-based Sense can be ran properly? Is that because Sense has access to low layers? From your explanation, I would have thought the kernel would do that job...
Indeed, if we compare to a PC, I usually don't need to upgrade my BIOS when I want to change my OS... Hence the reason why I am confused
Well the hboot (bootloader) part interacts with the kernel and this will talk with the rom....
Because the kernel and rom are updated with the new JB update, it needed an update from the hboot too so it can interact in correct way. I think this is the easiest way to explain it
hboot - kernel - rom.
PLEASE CORRECT ME IF I'M WRONG
I have been unclear about this as well (great question). This sounds like a good explanation (hey Marcel!). But I'm curious as to why my CID is HTC_203 and I'm on ARHD v15.0 and it says in the OP of that rom that I need to "upgrade my firmware" and when I look on the firmware thread http://forum.xda-developers.com/showthread.php?t=1957376 it says that my CID should have hboot 1.31. So, apparently it's not absolutely necessary to have the latest firmware? My rom seems to be working fine. Also, if I now want to use an ICS rom, will my CID/firmware (hboot) be an issue?
Ugh, can't believe how much more complex this phone is compared to my old Nexus! lol (but it sure is beautiful!)
scott62185 said:
I have been unclear about this as well (great question). This sounds like a good explanation (hey Marcel!). But I'm curious as to why my CID is HTC_203 and I'm on ARHD v15.0 and it says in the OP of that rom that I need to "upgrade my firmware" and when I look on the firmware thread http://forum.xda-developers.com/showthread.php?t=1957376 it says that my CID should have hboot 1.31. So, apparently it's not absolutely necessary to have the latest firmware? My rom seems to be working fine. Also, if I now want to use an ICS rom, will my CID/firmware (hboot) be an issue?
Ugh, can't believe how much more complex this phone is compared to my old Nexus! lol (but it sure is beautiful!)
Click to expand...
Click to collapse
You have to check the hboot number if its higher as 1.12 then you have the JB hboot update. A JB rom will run on a lower hboot but that is only for the de-sensed roms !
And hboot number for ICS roms is irrelevant :thumbup:
MarcelHofs said:
You have to check the hboot number if its higher as 1.12 then you have the JB hboot update. A JB rom will run on a lower hboot but that is only for the de-sensed roms !
And hboot number for ICS roms is irrelevant :thumbup:
Click to expand...
Click to collapse
Oh, wow. I see. :good:
Hboot can communicate with the hardware directly and controls all the security of the phone partitions.
Aside from booting the kernel
WiFi and other hardware bugs(dead sensors/sound and touch static electricity) were caused by incompatible hardware code between different hardware versions.
Edit: you only need to upgrade the hboot if you want to install a jb sense rom(stock or custom, restricted by sense+ software)
Sent from my EndeavorU
Vcek said:
Hboot can communicate with the hardware directly and controls all the security of the phone partitions.
Aside from booting the kernel
WiFi and other hardware bugs(dead sensors/sound and touch static electricity) were caused by incompatible hardware code between different hardware versions.
Edit: you only need to upgrade the hboot if you want to install a jb sense rom(stock or custom, restricted by sense+ software)
Sent from my EndeavorU
Click to expand...
Click to collapse
You mean I can flash a non-sense rom such as CM10 on my phone although I don't have a compatible cid?
From what i've read from the guide threads, you're supposed to have a cid similar to "HTC_001" or something like that to be able to flash a JB rom into the HTC one X. Am I wrong?
7ind said:
You mean I can flash a non-sense rom such as CM10 on my phone although I don't have a compatible cid?
From what i've read from the guide threads, you're supposed to have a cid similar to "HTC_001" or something like that to be able to flash a JB rom into the HTC one X. Am I wrong?
Click to expand...
Click to collapse
Yeah. In fact, you're better off not upgrading hboot for non Sense JB.
BenPope said:
Yeah. In fact, you're better off not upgrading hboot for non Sense JB.
Click to expand...
Click to collapse
Hmm, why is it better not to upgrade your hboot? (just curious)
Sent from my EndeavorU using Tapatalk 2
BenPope said:
Yeah. In fact, you're better off not upgrading hboot for non Sense JB.
Click to expand...
Click to collapse
Thanks! My night has just changed.
Would it be too much asking for the best CM10 rom link? I know they're there, but they're a bunch and I'm not really sure which I should flash.
Actually, I think I may flash this one: youtube. com/watch?v=elDvcVot7qo
Good enough?
Thanks again (Incredibly quick answer btw, I'm impressed)
scott62185 said:
Hmm, why is it better not to upgrade your hboot? (just curious)
Click to expand...
Click to collapse
Depending on which version you can go to, you might have problems. 1.33 and 1.36 should be ok, but with earlier versions you might find bugs.
Also, if you update it, for non Sense ROMs, you'll need a non standard boot.img, and at the moment, most of them don't work with GPS.
7ind said:
Thanks! My night has just changed.
Would it be too much asking for the best CM10 rom link? I know they're there, but they're a bunch and I'm not really sure which I should flash.
Actually, I think I may flash this one: youtube. com/watch?v=elDvcVot7qo
Good enough?
Thanks again (Incredibly quick answer btw, I'm impressed)
Click to expand...
Click to collapse
i would personally go for the official CM10(4.1.2) nightlies at cyanogenmod.com because i don't mind flashing a daily new update(doesn't require wipe data). I had defy with CM10 and as fast as I noticed any bug it was fixed in the next day's release. But I don't recommend this if you are looking for a permanent rom.
---------- Post added at 04:48 AM ---------- Previous post was at 04:45 AM ----------
BenPope said:
Depending on which version you can go to, you might have problems. 1.33 and 1.36 should be ok, but with earlier versions you might find bugs.
Also, if you update it, for non Sense ROMs, you'll need a non standard boot.img, and at the moment, most of them don't work with GPS.
Click to expand...
Click to collapse
I would like to add that the chance of finding a security hole in newer hboots is smaller , and I bet that no one would want to miss applying an S-OFF exploit.
Vcek said:
i would personally go for the official CM10(4.1.2) nightlies at cyanogenmod because i don't mind flashing a daily new update(doesn't require wipe data). I had defy with CM10 and as fast as I noticed any bug it was fixed in the next day's release. But I don't recommend this if you are looking for a permanent rom.
---------- Post added at 04:48 AM ---------- Previous post was at 04:45 AM ----------
I would like to add that the chance of finding a security hole in newer hboots is smaller , and I bet that no one would want to miss applying an S-OFF exploit.
Click to expand...
Click to collapse
Does GPS work on these nighties?
I just flashed the one that I mentioned and I've already gotten 3 reboots. Definitely not keeping it.
Gps should work if you didn't update the hboot.
Sent from my EndeavorU
Vcek said:
Gps should work if you didn't update the hboot.
Sent from my EndeavorU
Click to expand...
Click to collapse
I ****ed it up.
I was getting reboot after reboot so I tried restoring my stock rom from de clockwork mode. Now all I get is the HTC One X boot logo.
I forgot to move the stock boot.img from my phone to the pc and now I don't know how to push it from the phone to the pc without system.
Any ideas?
edit: alright, I really need some help right now. I'm freaking out. All I need is to send the stock boot.img I have on my backup to my pc so i can flash it via fastboot usb.
7ind said:
I forgot to move the stock boot.img from my phone to the pc and now I don't know how to push it from the phone to the pc without system.
Any ideas?
Click to expand...
Click to collapse
Mount the storage as USB from CWM.
BenPope said:
Mount the storage as USB from CWM.
Click to expand...
Click to collapse
"E: Unable to open ums lunfile (No such file or di...)"
It's getting scary. I don't want my phone to die.
btw, I hit "mount usb storage", I guess that's what you told to me, right?
I think the problem may be usb debugging. Idk if i have it enabled.
edit: I pulled it of, flash the buggy cm10 rom again, put the other rom files in the SD car and enabled usb debugging. It's charging now, I'll flash this new rom later, maybe at 40%.
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.
Hi all, I'll try not to seem so n00bish although I am when it comes to android.
I have a HTC One X (Tegra), CID HTC_023 and hboot version 1.39. I have unlocked the bootloader, backed up with CWM and rooted the phone.
Reading through the forums I see some have encountered problems with hboot 1.39 and custom roms with disabled touchscreens (I think I experienced this when TWRP refused to acknowledge touch screen presses) and there was mention of stock kernels, modules and modified boot.img files (as yet I cant find any page on the internet that defines these in the context of flashing custom roms), specifically in this thread
http://forum.xda-developers.com/showthread.php?p=37058924#post37058924
My goal is to get CyanogenMod on my phone due to the higher AVRCP version it has (if anyone knows of other stable roms with AVRCP 1.3+ please let me know), I downloaded the latest nightly build (all that is offered on their site) which includes a boot.img file. Would I be safe to flash that file?
Thanks, if you would like me to elaborate on anything, let me know.
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