I'm fairly new to the rooting and flashing scene and had a quick question about firmware.
I'm currently running Dirty Unicorns 9/26 official build with furnace kernel 1.0.9. I wanted to try arhd 20.1, so I made a backup, factory wiped and flashed it. I went thru the aroma installer and everything installed fine, once it finished, however, it turned off and wouldn't turn back on. I finally got it working again into the bootloader, but when I try and boot it, it just hangs on the HTC logo screen with the red text.
I browsed the thread to see what the issue could be, and although I couldn't find the someone else who had that problem, most of the problems people are having are because they didn't upgrade to the latest firmware.
So is that what the issue could've been? I downloaded the new firmware, just need to flash it, but before I do, I want to ask, will I have to flash a custom recovery again if I flash the new firmware? And will I also lose my data?
I'm soff with sunshine, twrp is my recovery
Probably due to outdated firmware, you are correct. Flashing a Sense ROM based on a newer version number (1.x, 2.x, 3.x) than your current firmware will often result in long boot time The phone probably will boot, just take a really long time (like 10 minutes) with no boot animation, making many folks think its "stuck" on the boot screen. Other issues are also common, such as broken WiFi.
Although, if you intend on flashing the firmware associated withe ARHD 20 (firmware 3.28) be aware that this is an "international" based firmware, and those are known to not play well with AT&T's network (at least for past 2.x firmware). You can give it a try, but you may have reception issues and may need to flash another firmware, or at least a different radio.
I know...I'm probably gonna kick myself for admitting I can't find the firmware version I'm on...but I can't...I'm on dirty unicorns as well...want to update firmware so I can try various Roms and I don't know which one to download...im still s-on but I know there's a thread that said I can still update...just can't find the number... any number that resembles the ones in many lists. I googled it but it doesn't tell me
rjcormier said:
I know...I'm probably gonna kick myself for admitting I can't find the firmware version I'm on...but I can't...I'm on dirty unicorns as well...want to update firmware so I can try various Roms and I don't know which one to download...im still s-on but I know there's a thread that said I can still update...just can't find the number... any number that resembles the ones in many lists. I googled it but it doesn't tell me
Click to expand...
Click to collapse
Your confusion is not without reason. There is in fact technically no "number" for firmware. That being the base, its been the normal thing here on XDA to refer to the software number which the firmware deployed with. So "firmware 3.28" actually just refers to the various modules (hboot, radio, recovery, kernel, WiFi, Bluetooth, and others) that deployed with the 3.28 OTA software. But the number 3.28 is just for the OS, which can easily be changed simply by flashing the ROM; while the firmware is actually not touched when you flash a ROM. In your case, since Dirty Unicorn is AOSP, its software number probably has nothing to do with HTC's software numbering scheme.
Best you can do is go by hboot and radio number. Either boot into bootloader, and get those numbers there and post them. Or adb getvar all (delete IMEI if you cut and paste the getvar output).
Wonders_Never_Cease has all the recent AT&T firmwares posted here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
But s-off is required to update firmware manually. If you want to stay s-on and update firmware, your alternative is to return to stock ROM and recovery, and OTA to update the firmware. Or relock the bootloader and RUU. Either way, 2.23 is the latest firmware/software you can update this way, until AT&T officially rolls out 3.xx.
Your confusion is not without reason. There is in fact technically no "number" for firmware. That being the base, its been the normal thing here on XDA to refer to the software number which the firmware deployed with. So "firmware 3.28" actually just refers to the various modules (hboot, radio, recovery, kernel, WiFi, Bluetooth, and others) that deployed with the 3.28 OTA software. But the number 3.28 is just for the OS, which can easily be changed simply by flashing the ROM; while the firmware is actually not touched when you flash a ROM. In your case, since Dirty Unicorn is AOSP, its software number probably has nothing to do with HTC's software numbering scheme.
Best you can do is go by hboot and radio number. Either boot into bootloader, and get those numbers there and post them. Or adb getvar all (delete IMEI if you cut and paste the getvar output).
Wonders_Never_Cease has all the recent AT&T firmwares posted here: http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
But s-off is required to update firmware manually. If you want to stay s-on and update firmware, your alternative is to return to stock ROM and recovery, and OTA to update the firmware. Or relock the bootloader and RUU. Either way, 2.23 is the latest firmware/software you can update this way, until AT&T officially rolls out 3.xx.
Click to expand...
Click to collapse
Thank you! Soo hboot is 3.16.0.0000, and radio is 1.16.21331931
rjcormier said:
Thank you! Soo hboot is 3.16.0.0000, and radio is 1.16.21331931
Click to expand...
Click to collapse
I believe those are the hboot and radio numbers that go with the 1.58 software. You can update to 2.23 firmware by RUU (the OTA was actually pulled/cancelled). But that means you will only be able to run custom ROMs based on Sense software 2.x. The newer ROMs are based on Sense software 3.x. So if you want to run those, you either need to S-off, or wait until AT&T releases 3.x.
redpoint73 said:
I believe those are the hboot and radio numbers that go with the 1.58 software. You can update to 2.23 firmware by RUU (the OTA was actually pulled/cancelled). But that means you will only be able to run custom ROMs based on Sense software 2.x. The newer ROMs are based on Sense software 3.x. So if you want to run those, you either need to S-off, or wait until AT&T releases 3.x.
Click to expand...
Click to collapse
OK thank you for your help!
Related
I've been doing a bit of reading on the steps to flash a custom ROM on the EVO LTE. To summarize my findings (and please correct me if I'm wrong about any of the following): I've noted that there is currently no way to achieve S-OFF with newer hboot (1.15 and 1.19), but you can still unlock the bootloader with HTC's official method. The disadvantage being (other than the red disclaimer splash screen at boot time) that you cannot flash a new radio firmware with HTC's official unlock method, where as you can with S-OFF.
So my question is, under what circumstances would you want to flash a new radio firmware?
During OTA's theres usually a new radio released. That is supposed to help with various connections (data, wifi, LTE) depending on whats updated.
morfinx said:
I've been doing a bit of reading on the steps to flash a custom ROM on the EVO LTE. To summarize my findings (and please correct me if I'm wrong about any of the following): I've noted that there is currently no way to achieve S-OFF with newer hboot (1.15 and 1.19), but you can still unlock the bootloader with HTC's official method. The disadvantage being (other than the red disclaimer splash screen at boot time) that you cannot flash a new radio firmware with HTC's official unlock method, where as you can with S-OFF.
So my question is, under what circumstances would you want to flash a new radio firmware?
Click to expand...
Click to collapse
You mainly just want to make sure that you're radio is from the same firmware version as the base of the ROM you're running. So if your ROM is based on the 1.22.651.3 software, you would ideally want the radio from the same OTA. It's generally not required, but you could have compatibility issues when running different versions.
Sent from my EVO LTE
Rxpert said:
During OTA's theres usually a new radio released. That is supposed to help with various connections (data, wifi, LTE) depending on whats updated.
Click to expand...
Click to collapse
premo15 said:
You mainly just want to make sure that you're radio is from the same firmware version as the base of the ROM you're running. So if your ROM is based on the 1.22.651.3 software, you would ideally want the radio from the same OTA. It's generally not required, but you could have compatibility issues when running different versions.
Sent from my EVO LTE
Click to expand...
Click to collapse
So if I'm running a custom ROM, that means I can't get an OTA update right? In that case, if I used HTC's official unlock method and can't flash a new radio separately on my own, how do I get the new radio?
morfinx said:
So if I'm running a custom ROM, that means I can't get an OTA update right?
Click to expand...
Click to collapse
If you're running a custom ROM, you *might* be able to receive/download the OTA, but it will not update properly because the recovery mode, the OTA checks all/most of the files in /system/app and /system/framework to verify they haven't been modified since the previous OTA before applying the new OTA. This check will definitely fail if any of the files have been modified in /system/app and /system/framework, which most custom ROMs make at least some minor modifications to the files in these directories.
morfinx said:
In that case, if I used HTC's official unlock method and can't flash a new radio separately on my own, how do I get the new radio?
Click to expand...
Click to collapse
Essentially, you'll have to get back to some form of stock to allow the stock bootloader to process the radio image contained in the OTA/RUU. There might be a better way to approach this, but off the top of my head, I'd make a nandroid backup of everything, re-lock the bootloader, run the RUU from the latest OTA/software version, which will update the radio, then unlock, flash custom recovery, make a nandroid of the stock ROM/kernel as a known good backup, then reload my previous nandroid to restore the custom ROM/kernel.
As recommended above, it is generally a good idea to keep the software version in sync with the radio version, but personally I rarely update the radio and rarely have an issue .. but that is just my personal experience.
Hope that helps!
joeykrim said:
If you're running a custom ROM, you *might* be able to receive/download the OTA, but it will not update properly because the OTA checks all files in /system/app and /system/framework to verify they haven't been modified since the previous OTA before applying the new OTA. This check will definitely fail if any of the files have been modified in /system/app and /system/framework, which most custom ROMs make at least some minor modifications to the files in these directories.
Essentially, you'll have to get back to some form of stock to allow the stock bootloader to process the radio OTA. There might be a better way to approach this, but off the top of my head, I'd make a nandroid backup of everything, re-lock, run the RUU from the latest OTA/software version, which will update the radio, then unlock, and reload my previous nandroid.
Click to expand...
Click to collapse
Thanks for the explanation. Wow, that sounds like an enormous PITA.
joeykrim said:
As recommended above, it is generally a good idea to keep the software version in sync with the radio version, but personally I rarely update the radio and rarely have an issue .. but that is just my personal experience.
Hope that helps!
Click to expand...
Click to collapse
Maybe it's not as a big of a deal as I'm thinking then to not be able to update the radio (easily). I'm still on an OG EVO with S-OFF, and I haven't updated my radio for probably close to 2 years. All of my connections seem to be fine still.
I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.
Ok so im not new to the rooting scene but am new to the flashing scene. I know a good jist of it but cant seam to figure out the whole firmware process.
I want to install this ROM: http://forum.xda-developers.com/showthread.php?t=2699616
I am currently running 4.4.2 with 1.58.xx firmware unlocked S-OFF and rooted. and this ROM requires 2.22.1540.4
Now I have found the 2.22.1540.4 firmware and know that i have to relock my bootloader and such but my phone says my ID is CWS__001 and i cant find any with that.
Also if i flash the newest 2.23.xx firmware will i still be able to flash any rom using older firmware versions?
And last question say i am flashing a new firmware and it screws up, since my custom recovery gets removed how do i flash my nandroid backup.
also if successfully flash the new firmware am i able to flash my old backup to restore to a old firmware or do i need to reflash the old firmware first.
sorry for so many questions i just dont want to blow up my phone due to stupid mistakes.
EDIT: so I think i managed to update my firmware. In bootloader it shows 2.22.1540.3 under os but in the phone settings it still says 4.4.2 and 1.58.xxx. I am assuming all i need is a updated firmware to run the mods and not a updated software? correct me if im wrong.
What exactly did you flash (link it if you can)? I think you are confusing software (OS or ROM) with firmware. Firmware as its mostly commonly discussed here (updating to run 2.xx based ROMs) refers to the hboot, radio, recovery, and other modules (media, WiFi, Bluetooth and more) deployed with an RUU or OTA. You have only flashed firmware if you installed an RUU/OTA or manually flashed it with fastboot.
devonjerothe said:
Also if i flash the newest 2.23.xx firmware will i still be able to flash any rom using older firmware versions?
Click to expand...
Click to collapse
Yes, 2.23 firmware will work as well. But again, make sure you are talking about the right thing (firmware versus software/OS).
I just bought an AT&T HTC One M8 that came with android 4.4.2 KitKat. It apparently doesn't have any available android lollipop updates since checking for updates using the "AT&T Software Update" option in settings returns a "no updates available" which was weird, but I didn't mind since I was planning to root this and flash a custom rom.
I read up on guides on rooting and unlocking the bootloader which was pretty standard for most android devices. However, S-on/S-off and hboot are 2 things that are confusing me a bit right now despite doing quite a lot of searching on XDA. To my understanding, S-on/S-off is some kind of HTC protection that needs to be disabled to flash certain roms, and hboot seems to be what people are calling the HTC Bootloader (someone correct me if I'm wrong). If I'm correct, I seem to have hboot version 3.16 according to CPU-Z (I checked the Bootloader version number).
After enough reading, it seems like having the latest hboot version is relatively important for flashing many roms (3.18-3.19 I believe), but I have found no guides on how to do this. My only lead so far is the following thread with 1 reply: http://forum.xda-developers.com/att-htc-one-m8/help/update-hboot-3-18-3-19-t3236897
"Backup any personal data you want to keep (off phone, it will be wiped). Relock the bootloader, run the latest AT&T RUU."
So ok, I guess it's a good thing I'm doing this before rooting the device. However, What's the AT&T RUU? My closest guess was using the HTC Sync Manager on windows to find firmware updates manually, but upon trying this (installing htc sync manager and connecting my HTC One M8) and on the menu clickling "Check for updates", I just get an error message saying "Unable to connect to the live update service".
Then, after some more searching I found this thread: http://forum.xda-developers.com/att-htc-one-m8/help/how-update-bootloader-to-3-18-0-0000-t3006738 which said the following:
"Follow instruction on the following thread for updating firmware, and select the 3.28.1540 firmware file: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-n"
So, here I am. Unsure whether to follow this instructions since I have no idea what that firmware is or if it will brick my device, or whether it will work since I still haven't rooted or unlocked my device's bootloader and I don't have S-Off (and that thread clearly states S-Off is mandatory for flashing to work). Any ideas?
---------------------------------------------------
edit: I just found out what RUU stands for, but I have been unable to find this "Rom Update Utility". It's spoken as Windows software, but I can't find where to download it. Any help would be very appreciated
sarxion said:
I just bought an AT&T HTC One M8 that came with android 4.4.2 KitKat. It apparently doesn't have any available android lollipop updates since checking for updates using the "AT&T Software Update" option in settings returns a "no updates available" which was weird
Click to expand...
Click to collapse
Are you connected to the AT&T network?
sarxion said:
I read up on guides on rooting and unlocking the bootloader which was pretty standard for most android devices. However, S-on/S-off and hboot are 2 things that are confusing me a bit right now despite doing quite a lot of searching on XDA. To my understanding, S-on/S-off is some kind of HTC protection that needs to be disabled to flash certain roms.
Click to expand...
Click to collapse
S-off is not needed to flash any ROMs. S-off is one way to update the firmware needed to run a ROM (more on what "firmware" is in a bit), but s-off isn't strictly need to update firmware either (other ways to do it s-on).
s-off is needed to modify (hack) certain partitions that are protected even with the bootloader unlocked. Such as hboot, radio, and some others. But its only needed for those specific things; and not needed to flash custom recovery or ROMs. And note that you can still update hboot, radio, and other firmware by "official" means even with s-on.
sarxion said:
hboot seems to be what people are calling the HTC Bootloader (someone correct me if I'm wrong).
After enough reading, it seems like having the latest hboot version is relatively important for flashing many roms (3.18-3.19 I believe)
Click to expand...
Click to collapse
Yes, hboot and bootloader are the same thing, as far as HTC devices are concerned.
Not only is the latest hboot needed to flash the current ROMs, but its important to update the entire firmware package. Firmware includes not only hboot, but also a number of other critical modules such as radio, WiFi, Bluetooth, and others; that all need to be updated in order for the current ROMs to function properly.
Good news, you are on the right track, and the proper RUU will update not only hboot, but all the firmware.
sarxion said:
What's the AT&T RUU?
edit: I just found out what RUU stands for, but I have been unable to find this "Rom Update Utility". It's spoken as Windows software, but I can't find where to download it.
Click to expand...
Click to collapse
I've created an AT&T index thread to catalog such things (sticky to the top of the General AT&T M8 section). It explains what an RUU is, and has links to all AT&T RUUs. You will want the latest RUU (4.28.502.1 or 4.28.502.2 - they are mainly the same except the latter has the Stagefright fix):
http://forum.xda-developers.com/showthread.php?t=2751432
The RUU is rather self-explanatory. As mentioned previously in this thread (and on the Index) your phone will be wiped by the RUU. So backup anything you want to keep by your method of choice. Then simply download the RUU to a PC, connect the phone. Then run the RUU program, and it will walk you through the process (you basically just need to confirm a couple dialogue boxes, and the RUU will do the rest and automatically update all the software/firmware).
After that, what you want to do in short is:
1) Unlock the bootloader using HTCDev.com
2) Install TWRP 2.8.7
3) Flash your custom ROM of choice
4) Beer
There is a master list of stock recovery versions for the HTC One. How do I determine which version I should be using?
None of those. That is hardly a "master" list. It's over 3 years old, never updated past the original Kitkat (M8 release) recoveries, and woefully obsolete. You'll want your recovery number to match your OS number (main version on bootloader screen or getvar all). Also, none of those are valid for AT&T version M8 (which is what I assume you have, since this section is specifically for the AT&T M8). It would need to have "502" in the version number x.xx.502.x which specifically denotes AT&T.
Why exactly do you want stock recovery? Most folks want this, in order to get OTA updates. But you will also need a stock, never rooted ROM (unrooting doesn't work), and also must be connected to the AT&T network. It's probably easier to relock the bootloader, and update by RUU. Note that RUU will wipe all data from the phone. See RUU section in my Index thread: https://forum.xda-developers.com/showthread.php?t=2751432
If you really want stock recovery, you should be able to extract it from the firmware.zip. Find the right firmware version number from the firmware collection, and extract recovery.img from the "Stock, Full Wipe" firmware zip:
https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
That is definitely helpful. Thank you. I didn't realize that I could pull the bootloader out of the firmware.zip. The phone was AT&T and later unlocked and made in to a rooted Cyanogenmod phone. I had to un-root and install Android GPE. It's not really AT&T anymore. Now I can download OTA updates, but cannot install them because TWRP is still the bootloader. I would rather do the OTA updates since the phone is already stock-ish and resetting everything is only slightly preferable to stabbing my eye out.
Since I'm unlocked on marshmallow, it looks like I want the 6.12.1540.4 zip.
mortifyxda said:
I didn't realize that I could pull the bootloader out of the firmware.zip.
Click to expand...
Click to collapse
Recovery and bootloader are two completely different things! You can pull recovery.img from firmware.zip, and flash with fastboot. I would not do this with bootloader, which would require s-off (to flash manually) and it would still be risky. Better to flash the whole firmware.zip or RUU, if you want to update bootloader. But I don't think that is what you meant.
mortifyxda said:
I had to un-root and install Android GPE. It's not really AT&T anymore. Now I can download OTA updates, but cannot install them because TWRP is still the bootloader. I would rather do the OTA updates since the phone is already stock-ish and resetting everything is only slightly preferable to stabbing my eye out.
Since I'm unlocked on marshmallow, it looks like I want the 6.12.1540.4 zip.
Click to expand...
Click to collapse
Your description is confusing, and I think you're mixing the terms up again. 6.12.1540.4 is the version number for the US Developer's Edition, which is Sense, and not the same as Google Play Edition (GPE) which is not Sense.
To OTA, the version number of the current stock ROM needs to match your firmware number (in bootloader and getar all), and you also need matching stock recovery.
To be clear, what is the current ROM (and version number) as shown in Settings? And also do fastboot getvar all, and post the result (delete IMEI and serial number). Need those pieces of info, before I can properly advise what stock recovery to use.