Hey there,
I got my One X, a day after it's international launch and flashed a custom soon after updating to the 1.28 OTA. I ran sense based ROMs for a little while but then switched over to AOSP ROMs and have been running them ever since.
Now my question is, is there anything on the device (radio, for eg.) that a custom ROM can't update and for which I have to flash an RUU?
rajitsingh said:
Hey there,
I got my One X, a day after it's international launch and flashed a custom soon after updating to the 1.28 OTA. I ran sense based ROMs for a little while but then switched over to AOSP ROMs and have been running them ever since.
Now my question is, is there anything on the device (radio, for eg.) that a custom ROM can't update and for which I have to flash an RUU?
Click to expand...
Click to collapse
The hboot does not get updated with a rom... other than that I believe it should all be the same pretty much.
meleelord said:
The hboot does not get updated with a rom... other than that I believe it should all be the same pretty much.
Click to expand...
Click to collapse
Pretty sure this is correct.
http://forum.xda-developers.com/wiki/HTC_One_X said:
The HTC Dev process allows access to the following partitions: /boot (but only using fastboot flash boot.img), /system, and /recovery.
You are unable to edit the hboot or radio partitions.
Click to expand...
Click to collapse
However, I believe this is out of date. Radios can be flashed by ROMs and also manually through CWM recovery.
Thanks for the replies.
I also saw football mention in his changelog once that his new ROM included new radio, so I think too that it's possible.
Not being able to update HBOOT: Can this have any effects?
there are are a few partitions which cannot be updated by anything other than a signed update
BCT
HBOOT
are two that i can think of off the top of my head
as of now there are no limitations of the current HBOOT updating fix
the latest Jellybean Sense official rom i believe requires a HBOOT Update which can be flashed by a PJ46IMG.zip
The Radio on Tegra3 devices is part of the /system partition which is Updated on a Per Rom Basis
The Bootloader shows RADIO Version from a TXT file contained within itself and is not accurate as flashing a new rom would change the radio but HBOOT will still show the same
to cut to the point there are no limitations by not updating your hboot if you are using custom roms
Thanks a ton!!!
Related
quick question: i updated my phone through the official jb update,so my hboot is now 1.36.
phone is unlocked and rooted also cmr custom recovery.
do i have to flash the custom 1.36 firmware or is the ota update one ok to install a custom rom.
reason being,just been in bootloop for an hour or so after flashing custom rom,but it could of been a bad flash on a corrupt boot.img,solved with several fastboot erase cache's and lots of re-boots
just want to check that the ota 1.36 is ok to flash a custom rom with.
thanks in advance,merry xmas.
Yeah, no difference.
Which ROM did you flash and is the standard boot.img compatible with the "JB hboot"?
insertcoin,i did extract the boot.img and flashed first-must of been a bad download,did not check the md5.
although i used the tool flasher for the boot.img,think i'll stick to cmd.
thanks for your input....
same problem
Well, appearantly you're not the only one... I tried to flash CM10 today, but didn't work either... Also got stuck in reboot. I hope someone can explain what i'm doing wrong.
You need to flash modified boot.img on newer hboots, and you would be aware of this if you read the OP carefully. Post 9308 in CM10 thread.
marcobeinema said:
Well, appearantly you're not the only one... I tried to flash CM10 today, but didn't work either... Also got stuck in reboot. I hope someone can explain what i'm doing wrong.
Click to expand...
Click to collapse
as far as i know htc havent released the one x jb kernel source yet (though the one x+ has i believe) so any non stock roms/kernels ie cm pa aokp ect are missing features = bt,gprs,ect. im not sure if there is a aosp rom/kernel that is fully working for hboot 1.36 as ive read through lots of threads and as to be expected there is a lot of conflicting information.
if any one can clear this up for me it would be appreciated
is there a non stock rom that can be run on hboot 1.36
sense based roms can be flashed on hboot 1.3.6
See my sig. It runs on all hboots.
Sent from my HTC One X
TToivanen said:
See my sig. It runs on all hboots.
Sent from my HTC One X
Click to expand...
Click to collapse
I found the thread for that ROM but the links are no longer available.
I cannot find another ROM that is able to boot on 1.36.
tuxcomputers said:
I found the thread for that ROM but the links are no longer available.
I cannot find another ROM that is able to boot on 1.36.
Click to expand...
Click to collapse
What rom are you after. All roms run on your hboot !
Does the top of your bootloader say :
Endeavouru ?
If so check here in the android dev & original android dev section for a rom......there are plenty
ICJ = http://forum.xda-developers.com/showthread.php?t=2052610
hi all , i have a problem with my one x.
i'm trying to update to JB but every time when i change the hboot from 1.12 to greater ones - 1.28 to 1.39 the onex is stuck to boot loop.
i can revert to 1.12 due tot the fact that i have S-OFF and i can also install non sense JB - as CM10 but, i would like to install the official JBRUU or at least some other custom rooms that are with the official version.
any ideas, cause i'm out of it?
sradoi said:
hi all , i have a problem with my one x.
i'm trying to update to JB but every time when i change the hboot from 1.12 to greater ones - 1.28 to 1.39 the onex is stuck to boot loop.
i can revert to 1.12 due tot the fact that i have S-OFF and i can also install non sense JB - as CM10 but, i would like to install the official JBRUU or at least some other custom rooms that are with the official version.
any ideas, cause i'm out of it?
Click to expand...
Click to collapse
Lucky you having S-OFF. S-ON is a pain.
Have you only updated HBOOT? I think you might also need a ROM and kernel that are compatible with the newer firmware
pbh4 said:
Lucky you having S-OFF. S-ON is a pain.
Have you only updated HBOOT? I think you might also need a ROM and kernel that are compatible with the newer firmware
Click to expand...
Click to collapse
I did, as soon as i'm upgrading to 1.29 or higher my one x is stuck in the boot loop.
my cid is 11111111 .
any ideas ?
by the way is there any hboot below 1.29? any place from where i can download it?
Have you flashed a compatible JB sense rom before upgrading the HBOOT,or flashing the Rom after upgrading?
Sent from something that's BETTER THAN YOURS
XxVcVxX said:
Have you flashed a compatible JB sense rom before upgrading the HBOOT,or flashing the Rom after upgrading?
Sent from something that's BETTER THAN YOURS
Click to expand...
Click to collapse
with 1.12 i was able to successfully install CM 10, nightly builds, but as soon as i have update my Hboot no other JB sense ROM has worked.
The only way to make my phone work again was to run the Europe RUU ICS 1.20.401.1 which revert my HBOot to 1.12.
Any suggestion?
I may be wrong here, as I'm new to HTC. But doesn't being s-off, as in a super-CID mean you can use any RUU? i.e. running a jb RUU would contain the correct Hboot.
I've quite a few questions regarding hboot and base versions, and would very much like some teachings from the community.
Recently, I've been quite confused regarding the hboot version(like 1.26) and rom "base" version(like 3.18.xxxxx)
With the ICS>JB update, it appeared that you must get the official OTA first in order to flash JB Roms, is it because the OTA also updated the hboot version?
If that's the case, are rom "base"s inherently restricted to certain hboot versions?
Are those ICS>JB OTAs a rare thing? Meaning that in most cases the only thing OTA-ed is a ROM/kernel itself, and nothing else? Will it benefit me to, say, go back to stock, get the official OTA for 3.19, then root/unlock bootloader again to flash new/upcoming 3.19 ROMs?
I know it's quite a few questions, but I would really be grateful for any answers! Thank you all in advance
I will give back what this community though me
ULAMSS5 said:
With the ICS>JB update, it appeared that you must get the official OTA first in order to flash JB Roms, is it because the OTA also updated the hboot version?
Click to expand...
Click to collapse
I know some ota's update the hboot version, but not all. Hboot can be updated via RRU's too. The rru must (!!) match your cid (carrier id). There are plenty information on this.
If that's the case, are rom "base"s inherently restricted to certain hboot versions?
Click to expand...
Click to collapse
What do you mean by rom base? Some custom Roms require a hboot version higher than x. Ice cold jelly (past version 2.5 I think) cannot run on hboot version 1.28 or lower. Why in details I don't know. I imagine it's like installing Adobe master collection on windows 98..
Kind Regards
TwinAdk
- Via the premium XDA app
Thanks TwinAdk, I'll add a little someting if you don't mind
ULAMSS5 said:
If that's the case, are rom "base"s inherently restricted to certain hboot versions?
Click to expand...
Click to collapse
Not necessarily ROMs, but kernels. The base version of the kernel source (0.99, 1.29, 3.14, etc, etc) is the key.
If your kernel is based on 3.14 for example, you need hboot higher or equal to 1.28.
Are those ICS>JB OTAs a rare thing?
Click to expand...
Click to collapse
Depends on your phone's CID... is it carrier branded?
Meaning that in most cases the only thing OTA-ed is a ROM/kernel itself, and nothing else? Will it benefit me to, say, go back to stock, get the official OTA for 3.19, then root/unlock bootloader again to flash new/upcoming 3.19 ROMs?
Click to expand...
Click to collapse
If you are on 3.14 base already and provided that you use custom ROMs, upgrading would not benefit at all because it won't update the firmware (hboot) You can flash 3.19-based ROMs on 3.14-based phone no problem.
Thanks guys, you've pretty much answered all my questions so easily-understandably(if there's such a word)
TToivanen, about the ICS>JB OTAs, I was actually referring to OTAs whereby hboots are updated as well. Does this like usually only happen when there's a name-change update , like Gingerbread>ICS, ICS>JB, or JB>KLP? Or are there no fixed patterns and any random version updates could also have hboot updates?
There was a hboot update in the following versions of Android:
4.0.3 > 4.0.4 (mainver 2.17)
4.0.4 > 4.1.1 (mainver 3.14)
The latest OTAs 3.18 and 3.18 did not update hboot so you'll have to wait till KLP to get an update.
Of course you can update the hboot in methods other than OTA if you wish.
Im comming from a Nexus 4. At this moment i am using stock rom with s-on on my international htc one m8. Only thing i did is rooting it and flashed a custom recovery from philz. Now my question is, how can i update to the newest firmware. It is a bit complicated compared to the nexus 4, so i dont want to do anything wrong. Ive red about relocking the bootloader and some orher stuff, but dont get it. I would appreciate any help and info i can get.. i put a screenshot of my current setup..
Sent from my HTC One_M8 using XDA Premium 4 mobile app
When you say "firmware" do you just mean the Android software version? If so, just flash in recovery a stock rooted ROM, or custom ROM based on the newer software. No need to mess with relocking the bootloader to install an official OTA update or RUU. In my opinion, here is little to no good reason to install official updates on a modded/rooted phone.
Reason I ask the first question above, many of the folks here refer to "firmware" as the other modules deployed with the OS, including hboot, radio, and other media modules. Flashing this is still possible on a modded device, just a little different.
redpoint73 said:
When you say "firmware" do you just mean the Android software version? If so, just flash in recovery a stock rooted ROM, or custom ROM based on the newer software. No need to mess with relocking the bootloader to install an official OTA update or RUU. In my opinion, here is little to no good reason to install official updates on a modded/rooted phone.
Reason I ask the first question above, many of the folks here refer to "firmware" as the other modules deployed with the OS, including hboot, radio, and other media modules. Flashing this is still possible on a modded device, just a little different.
Click to expand...
Click to collapse
Thanks for the answer. by updating the firmware i mean the complete software, just like we get it OTA. The nexus was peace of cake, just install thr new rom and radios and you were done. But this htc thing needs some practicing i think.
soylukral said:
Thanks for the answer. by updating the firmware i mean the complete software, just like we get it OTA. The nexus was peace of cake, just install thr new rom and radios and you were done. But this htc thing needs some practicing i think.
Click to expand...
Click to collapse
That part is not much different with the M8. If you want a new ROM, just flash a stock rooted ROM or custom in recovery. If you want a new radio, just get it from the following thread and flash it. Only difference, if you need S-off. so look for either firewater or sunshine s-off method.
http://forum.xda-developers.com/showthread.php?t=2736921
Yes, you can install the "complete" firmware package (search around and you will find them, usually flashed with fastboot/adb). But these are usually not necessary. If a ROM requires a newer firmware package, it will be discussed in that ROM thread.
redpoint73 said:
That part is not much different with the M8. If you want a new ROM, just flash a stock rooted ROM or custom in recovery. If you want a new radio, just get it from the following thread and flash it. Only difference, if you need S-off. so look for either firewater or sunshine s-off method.
http://forum.xda-developers.com/showthread.php?t=2736921
Yes, you can install the "complete" firmware package (search around and you will find them, usually flashed with fastboot/adb). But these are usually not necessary. If a ROM requires a newer firmware package, it will be discussed in that ROM thread.
Click to expand...
Click to collapse
So what i understand is, as long as you stay stock rooted, you can update with a stock rooted rom without having s-off. Am i right? What i dont understand is that they are talking about you cant update from 4.4.2 1.54 to 4.4.3 2.22 without relocking your bootloader..
soylukral said:
So what i understand is, as long as you stay stock rooted, you can update with a stock rooted rom without having s-off. Am i right? What i dont understand is that they are talking about you cant update from 4.4.2 1.54 to 4.4.3 2.22 without relocking your bootloader..
Click to expand...
Click to collapse
You seem to be talking about 2 different things.
If you are talking about updating (flashing) a stock rooted ROM, that would be a user created ROM posted here in Development. If that is the case, you can flash whatever ROM you want from Development while S-on.
But if you are talking about installing official OTA updates, you need to relock your bootloader with s-on; and you also need to revert to stock recovery. You can flash these with the bootloader unlocked with S-off (stock recovery is still required). The other catch is, that if you change or remove any system files while rooted, an OTA will not install.
My opinion is not to install OTAs on a rooted phone. Its extra steps and extra hassle (relocking bootloader, re-installing stock recovery). Plus, you never know what exploits have been patched with the new OTAs. For instance, the more recent hboots plugged the firewater s-off. Its a much better idea to just flash stock rooted or custom ROMs posted in Development, as they often get updated very quickly to the new software versions anyway. And that is what XDA is all about, anyway.
redpoint73 said:
You seem to be talking about 2 different things.
If you are talking about updating (flashing) a stock rooted ROM, that would be a user created ROM posted here in Development. If that is the case, you can flash whatever ROM you want from Development while S-on.
But if you are talking about installing official OTA updates, you need to relock your bootloader with s-on; and you also need to revert to stock recovery. You can flash these with the bootloader unlocked with S-off (stock recovery is still required). The other catch is, that if you change or remove any system files while rooted, an OTA will not install.
My opinion is not to install OTAs on a rooted phone. Its extra steps and extra hassle (relocking bootloader, re-installing stock recovery). Plus, you never know what exploits have been patched with the new OTAs. For instance, the more recent hboots plugged the firewater s-off. Its a much better idea to just flash stock rooted or custom ROMs posted in Development, as they often get updated very quickly to the new software versions anyway. And that is what XDA is all about, anyway.
Click to expand...
Click to collapse
sorry about asking this many questions but, the main thing is that i want to update to the latest released software 4.4.3 2.22. can you discribe me the steps i have to follow. because im sorry but it is still not 100% clear. believe me i flashed many many roms kernels tweaks and lots of other stuff, but comming from a nexus device this is a nightmare.
soylukral said:
sorry about asking this many questions but, the main thing is that i want to update to the latest released software 4.4.3 2.22. can you discribe me the steps i have to follow. because im sorry but it is still not 100% clear. believe me i flashed many many roms kernels tweaks and lots of other stuff, but comming from a nexus device this is a nightmare.
Click to expand...
Click to collapse
i was looking at ARHD 10.1 with the latest 4.4.3 2.22 software, can i just flash this over my stock rooted 4.4.2 1.54?
soylukral said:
sorry about asking this many questions
Click to expand...
Click to collapse
No worries, that is what this forum is for!
One thing I was not fully aware of, while ARHD will flash just fine over your stock ROM; folks seem to be having trouble with Android 4.4.3 (software 2.22) based ROMs and old "firmware" (reference Post #2, paragraph 2 above). This includes issues with no sound (which I suspect the "media" module within the firmware package is the culprit).
So if you want to flash a 2.22 based ROM, it looks like you need to S-off and flash the firmware package before flashing ARHD. Details on flashing the firmware package can be found by reading the ARHD thread, or also (more easily) by referring to Section 3 of this guide: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727/post53807690
Updating the "firmware" package is often not needed to just flash a custom ROM. This happens to be one of the exceptions.
redpoint73 said:
No worries, that is what this forum is for!
One thing I was not fully aware of, while ARHD will flash just fine over your stock ROM; folks seem to be having trouble with Android 4.4.3 (software 2.22) based ROMs and old "firmware" (reference Post #2, paragraph 2 above). This includes issues with no sound (which I suspect the "media" module within the firmware package is the culprit).
So if you want to flash a 2.22 based ROM, it looks like you need to S-off and flash the firmware package before flashing ARHD. Details on flashing the firmware package can be found by reading the ARHD thread, or also (more easily) by referring to Section 3 of this guide: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727/post53807690
Updating the "firmware" package is often not needed to just flash a custom ROM. This happens to be one of the exceptions.
Click to expand...
Click to collapse
thanks anyway, you did help me get wiser. what i understand is that S-OFF is a must have to be that free as on the nexus 4. i will look further. thanks again..
soylukral said:
thanks anyway, you did help me get wiser. what i understand is that S-OFF is a must have to be that free as on the nexus 4. i will look further. thanks again..
Click to expand...
Click to collapse
S-off is usually not needed to flash a ROM itself. But yes, its a must if you want to flash radio, hboot, firmware packages, and some other things.
Hello,
I am looking for the stock ROM for my HTC ONE M8 because I had a few issues before and I put the first ROM that worked. Because my phone is S-On still it was difficult to find a ROM.
I am currently on a 4.4.4 ROM which has no check for updates feature so when Android L is pushed onto my device I won't be able to get it.
My HTC One M8 is a European version and is currently unlocked to all networks. I've tried to install the official HTC ROM from the website but it hangs and nothing updates, on my task manager I can see the CPU is busy but it does nothing.
Android Version : 4.4.4
HTC Sense version : 6.0
Software number : Android Revolution HD 22.1 by mike1986
Baseband bersion 1.22.2133147A1
Build number : 3.28.401.9
have you read this page: http://forum.xda-developers.com/showthread.php?t=2701376 ?
nathankk said:
I am looking for the stock ROM for my HTC ONE M8 because I had a few issues before and I put the first ROM that worked. Because my phone is S-On still it was difficult to find a ROM.
Click to expand...
Click to collapse
Why? You can flash any M8 ROMs with s-on. And since it appears your firmware is up to date, you can flash any of the latest ROMs with any firmware mismatch issues.
nathankk said:
I am currently on a 4.4.4 ROM which has no check for updates feature so when Android L is pushed onto my device I won't be able to get it.
Click to expand...
Click to collapse
Custom ROMs won't get official OTAs.
Also, in addition to returning to stock ROM, you need to revert to stock recovery to install any OTAs. Its all described in the thread linked in the previous response.
redpoint73 said:
Why? You can flash any M8 ROMs with s-on. And since it appears your firmware is up to date, you can flash any of the latest ROMs with any firmware mismatch issues.
Custom ROMs won't get official OTAs.
Also, in addition to returning to stock ROM, you need to revert to stock recovery to install any OTAs. Its all described in the thread linked in the previous response.
Click to expand...
Click to collapse
I was under the impression with,S-On you can't flash any ROM onto it. Can I literally choose any of those CIDs and it will be compatible with my phone? Instead of messing around can I just wait for the release of lollipop and then flash the ROM that gets posted on here. I just got a little confused because on that post it has carrier names and my phone is unlocked to all networks.
nathankk said:
I was under the impression with,S-On you can't flash any ROM onto it. Can I literally choose any of those CIDs and it will be compatible with my phone? Instead of messing around can I just wait for the release of lollipop and then flash the ROM that gets posted on here. I just got a little confused because on that post it has carrier names and my phone is unlocked to all networks.
Click to expand...
Click to collapse
I think you are talking about flashing firmware or a RUU ? No... If you're s-on, you can only flash your CID. But that has nothing to do with custom roms... Which is what the others have been talking about. ?
Darth said:
I think you are talking about flashing firmware or a RUU ? No... If you're s-on, you can only flash your CID. But that has nothing to do with custom roms... Which is what the others have been talking about.
Click to expand...
Click to collapse
I'm on a custom ROM now I believe and I'm wanting to return to stock, I want to be sure before I do anything so I don't brick the phone. How do I find which CID I need to download?
nathankk said:
I was under the impression with,S-On you can't flash any ROM onto it. Can I literally choose any of those CIDs and it will be compatible with my phone?
Click to expand...
Click to collapse
Any of the stock nandroids should work (meaning they will function). But if you want the stock ROM for your CID, than obviously you need to determine the CID and restore the corresponding stock nandroid.
One reason to restore to your stock nandroid, is that if you also restore the corresponding stock recovery you will be able to receive official OTAs.
nathankk said:
Instead of messing around can I just wait for the release of lollipop and then flash the ROM that gets posted on here.
Click to expand...
Click to collapse
Yes and no. You can flash any custom ROM, including upcoming LP Sense ROMs. But what complicates the issue is that HTC has updated the firmware (hboot, radio, WiFI, etc.) for every major OS software update. If you don't update the firmware accordingly, flashing a ROM that depends on that firmware will result in some major issues (such as long boot times and broken WiFi).
Updating firmware manually requires s-off (which may be the reason why you are under the impression that ROMs can't be flashed with s-on). Or alternately, you can return to stock ROM and recovery and OTA when the LolliSense update rolls out; and this will also update the firmware.
Keep in mind, as previously mentioned your current firmware will work with any current custom ROMs that depend on 3.x firmware.
nathankk said:
I just got a little confused because on that post it has carrier names and my phone is unlocked to all networks.
Click to expand...
Click to collapse
Regardless of the fact your phone is not carrier branded, it still has a CID, probably HTC__ something or other.
fastboot getvar all will yield your CID. No need to post your getvar data, just look for where it says CID. If you post getvar data, be sure to delete IMEI and serial number, as these are personal data that should not be posted on the internet.
redpoint73 said:
Any of the stock nandroids should work (meaning they will function). But if you want the stock ROM for your CID, than obviously you need to determine the CID and restore the corresponding stock nandroid.
One reason to restore to your stock nandroid, is that if you also restore the corresponding stock recovery you will be able to receive official OTAs.
Yes and no. You can flash any custom ROM, including upcoming LP Sense ROMs. But what complicates the issue is that HTC has updated the firmware (hboot, radio, WiFI, etc.) for every major OS software update. If you don't update the firmware accordingly, flashing a ROM that depends on that firmware will result in some major issues (such as long boot times and broken WiFi).
Updating firmware manually requires s-off (which may be the reason why you are under the impression that ROMs can't be flashed with s-on). Or alternately, you can return to stock ROM and recovery and OTA when the LolliSense update rolls out; and this will also update the firmware.
Keep in mind, as previously mentioned your current firmware will work with any current custom ROMs that depend on 3.x firmware.
Regardless of the fact your phone is not carrier branded, it still has a CID, probably HTC__ something or other.
fastboot getvar all will yield your CID. No need to post your getvar data, just look for where it says CID. If you post getvar data, be sure to delete IMEI and serial number, as these are personal data that should not be posted on the internet.
Click to expand...
Click to collapse
Fantastic reply! let me buy you a beer.
nathankk said:
Fantastic reply! let me buy you a beer.
Click to expand...
Click to collapse
Heh, while I love beer, gratitude by clicking the "Thanks" button is enough!
OP, check the link in my signature. Full guide to go back to stock with the EU M8 (most of it will work with S-ON as well)
redpoint73 said:
Yes and no. You can flash any custom ROM, including upcoming LP Sense ROMs. But what complicates the issue is that HTC has updated the firmware (hboot, radio, WiFI, etc.) for every major OS software update. If you don't update the firmware accordingly, flashing a ROM that depends on that firmware will result in some major issues (such as long boot times and broken WiFi).
Updating firmware manually requires s-off (which may be the reason why you are under the impression that ROMs can't be flashed with s-on). Or alternately, you can return to stock ROM and recovery and OTA when the LolliSense update rolls out; and this will also update the firmware.
Keep in mind, as previously mentioned your current firmware will work with any current custom ROMs that depend on 3.x firmware.
Click to expand...
Click to collapse
Heads up, as of early this week (Monday?) the Dev Edition M8 is rolling out Lollipop Sense via OTA. Some custom ROMs have now updated to this base, which is 4.16 software, and requires 4.16 firmware.
But as mentioned, any 3.x software based ROM will work on your current firmware.