So i think i am getting lost and I really want to be careful before i re-start my crack flashing habits again.
I flashed senseless ics, loved it, but wanted to go back to gb. So i went back to senseless 1.1, extracted boot.img, and adb pushed and flashed then did a nandroid back up and every thing is A-ok .
Here is my confusion.
What problems are ppl refering to with Mainver? ( what is that even )
Why do ppl have to RUU ( again what is it)
is my method right ? Which is : if the rom came with an auto script to flash from hboot then hurray, if not, then flash boot.img from adb via fast boot and flash to my liking ?
the only roms i gave been on so far : cleanrom 1.5.5, inefebellis, senesless 1.1, senseless ecs, then back to senseless 1.1 via nandroid like mentioned.
jmichaels1982 said:
So i think i am getting lost and I really want to be careful before i re-start my crack flashing habits again.
I flashed senseless ics, loved it, but wanted to go back to gb. So i went back to senseless 1.1, extracted boot.img, and adb pushed and flashed then did a nandroid back up and every thing is A-ok .
Here is my confusion.
What problems are ppl refering to with Mainver? ( what is that even )
Why do ppl have to RUU ( again what is it)
is my method right ? Which is : if the rom came with an auto script to flash from hboot then hurray, if not, then flash boot.img from adb via fast boot and flash to my liking ?
the only roms i gave been on so far : cleanrom 1.5.5, inefebellis, senesless 1.1, senseless ecs, then back to senseless 1.1 via nandroid like mentioned.
Click to expand...
Click to collapse
ruu is flashing stock. method is right with the boot.img which is also the kernel but without other kernel files found in the flashable zip. If the rom doesnt have the boot.img u can also use cleanflash tool to flash the kernel/boot into your current rom,restart,then wipe/flash rom
sent from my rezound using tapatalk
RUU files are the official software releases from HTC.
RUU files are signed. (They give proper "official" codes to hboot to get past the s=on security)
This means that they can flash all parts of the device, even the bootloader and radio firmware, which we can not normally flash because it is write locked. (do to s=on we can't flash them even with root)
Sometimes people have issues and need to get the phone back to pure stock so they use the RUU.
Mainver is data on the software version number of the kernel (I believe... it may be for some other part, either way it is version info)
Think V1... V1.2... V1.5... V1.5.5
Because of s=on we are not allowed to "downgrade/revert" to older software versions.
The leaked ICS build has a newer Mainver, some people flashed the leak unmodified, and that changed the Mainver info. Now they need to use a special trick to trick the s=on security to allow flashing of older kernels. The ICS ROMs we have now, have been modified so they do not change the Mainver. This makes it easier to go back to GB or switch to other ROMs.
Marine6680 said:
RUU files are the official software releases from HTC.
RUU files are signed. (They give proper "official" codes to hboot to get past the s=on security)
This means that they can flash all parts of the device, even the bootloader and radio firmware, which we can not normally flash because it is write locked. (do to s=on we can't flash them even with root)
Sometimes people have issues and need to get the phone back to pure stock so they use the RUU.
Mainver is data on the software version number of the kernel (I believe... it may be for some other part, either way it is version info)
Think V1... V1.2... V1.5... V1.5.5
Because of s=on we are not allowed to "downgrade/revert" to older software versions.
The leaked ICS build has a newer Mainver, some people flashed the leak unmodified, and that changed the Mainver info. Now they need to use a special trick to trick the s=on security to allow flashing of older kernels. The ICS ROMs we have now, have been modified so they do not change the Mainver. This makes it easier to go back to GB or switch to other ROMs.
Click to expand...
Click to collapse
Good write up !
waw
Thank you Thank you Thank you ! best crash course ever ...
Related
Hey all,
I'm currently running Innefabilis Deus Alpha Preview and I like it, but will wait for another update that's more stable. Anyway, I tried reverting back to Ineffabilis v1.0 (GB) but when I installed a Kernel by dsb, it says something about "Main version is older!" in fastboot. I read that if you've already flashed the latest leak (ICS), it's not easy to revert back to GB.
I'm wondering if I'm able to use CleanTool to flash dsb's Kernel instead after flashing a GB Rom. Can anyone help me? I've already tried flashing other Kernels via fastboot on my phone and have failed.
This is a common problem right now and you can do a few things...fastest and easiest way is you can flash boot.img via fastboot for short term fix. Just pull the boot.img from the ROM you are flashing. This will get you up and running...but you will run into this again.
For a long term solution...I just came across this...which should help you...
con247 said:
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore or install a rom of your choice.
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
Click to expand...
Click to collapse
get the PH98IMG from his post here...
http://forum.xda-developers.com/showpost.php?p=21442702&postcount=3
this works well. Myself I just cleaned everything up installed my GB rom, let it fail then pulled the battery and used the trusty droid to mount the sd card from the rezound and put this file on it. booted in to recovery let it do its thing and it worked perfect.
However I'm not sure if pulling the battery after the the file fails is safe, just a risk I took.
So I achieved s-off on my first try, and was feeling cocky. So, I downloaded Newt's new 4.0, with the patch for old firmware from Nil's Rom. I am writing this from my rezound now, but whenever I try to go back to chingy's gb Rom, it hangs at the 4g screen. I have tried to use the image the Rom produces, pm98img from another gingerbread Rom, incredikernal, and fast l
booting the boot.IMG file from said sources. What am I doing wrong? Besides messing with stuff I shouldn't. I thought going back to gingerbread would be simple if I stayed on old firmware. Does anyone know where to go from here? I can install Newt's xXx Rom and boot with no problem. Any help would be greatly appreciated.
Sent from my ADR6425LVW using XDA
Edit: I fixed it by using the PH98IMG ruu, then using the juonutbear hboot patch. Then reloaded Amon Ra. Flashed Chingy's rom, then my back up. There was alot of drama in the middle of all that. Mostly caused by the user. I flashed so many different things, that i would have trouble telling you what i flashed to get back. I scoured xda for several hours before attempting to try this, and hours more before i asked for help. Thanks to those that helped.
easyy fix
the 2.1 is just a patch you need to do 2.0 first which is newtoroot rom then 2.1 for the patch and yes you do need to use the sense4_boot.img again
The old ROMs didn't contain firmware. So if you installed the ICS leak RUU then you have the new firmware and need to flash the "old firmware" patch. As far as kernels go, you should always flash the kernel that came with the ROM(except for GB ROMs where you can use incredikernel).
I think this will work for you. Backup your current ROM(if you want), then flash a GB RUU, then flash a GB ROM/kernel. Make a backup of that. Now you should have a GB firmware backup and an ICS firmware backup.
MrSmith317 said:
The old ROMs didn't contain firmware. So if you installed the ICS leak RUU then you have the new firmware and need to flash the "old firmware" patch. As far as kernels go, you should always flash the kernel that came with the ROM(except for GB ROMs where you can use incredikernel).
I think this will work for you. Backup your current ROM(if you want), then flash a GB RUU, then flash a GB ROM/kernel. Make a backup of that. Now you should have a GB firmware backup and an ICS firmware backup.
Click to expand...
Click to collapse
He was saying he just installed Newt's rom,but still on GB firmware. I think all you have to do is reflash Chingy's rom, but wipe first and then make sure your installing GB's kernel. I have had similar issues , where I had to install a rom with the stock kernel first before going back to custom kernels. So maybe install Scott's earlier GB rom first or Nil's GB business sense rom they both use the stock kernel.
Not sure why that seems to work, but for awhile I had the exact same issue going from ICS to GB and back. Only solution I ever found was to wipe a few times install a rom , then stock kernel.
Mjh got it right. I have back ups of both. whenever i try to go back to gingerbread now, i get stuck at the 4g splash. i have tried several gb kernels and still no dice. i think a ruu is in order. I have the exe RUU on my pc. It is taking forever for the PM98IMG Ruu to download. Can i run exe file on my S-off phone and then use recovery to load one of my older gb roms.S-off was easy compared to this. Thanks for any and all advice.
JeramyEggs said:
Mjh got it right. I have back ups of both. whenever i try to go back to gingerbread now, i get stuck at the 4g splash. i have tried several gb kernels and still no dice. i think a ruu is in order. I have the exe RUU on my pc. It is taking forever for the PM98IMG Ruu to download. Can i run exe file on my S-off phone and then use recovery to load one of my older gb roms.S-off was easy compared to this. Thanks for any and all advice.
Click to expand...
Click to collapse
Yes, you can ruu , just remember if your on stock hboot you will have to relock and that will affect what your bootloader says. Otherwise, also make sure after the ruu to reflash amon ra recovery.
Did you try the stock ota kernel ?http://forum.xda-developers.com/showthread.php?t=1476152
Try the GB kernel on this page and see if it works before RUUing.
Sent from my ADR6425LVW using xda premium
I s offed with the ICS leaked firmware and want to downgrade to the gb radios. I have seen lots of posts saying different things and would like someone with experience doing this to tell me what you did and in what order
Sent from my ADR6425LVW using Tapatalk 2
pmania said:
I s offed with the ICS leaked firmware and want to downgrade to the gb radios. I have seen lots of posts saying different things and would like someone with experience doing this to tell me what you did and in what order
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
If your S-off and on Juopunut bear's modified Hboot, you can just download the exe. version of the GB ota found in this thread http://forum.xda-developers.com/showthread.php?t=1338916 . Just be aware that once you run it you will be completely stock again including locked bootloader. If you still want to preserve your locked status I would flash this hboot in this thread..http://forum.xda-developers.com/showthread.php?t=1618140
Now, you will still be locked but able to run fastboot commands without unlocking. Now, you have to flash Amon recovery found here..http://www.mediafire.com/?l9dgzvvsdku7g3c This is the recovery that works for GB firmware. If you upgrade back to leaked ICS then you will have to flash 3.15.
Prior to flashing Amon Ra recovery.. you may watch to do a factory reset in hte stock recovery to prevent any possible data connection issues. Once you did that and now have flashed Amon ra.. you can either flash a rooted rom to get root back or to go to developer menu in Amon ra and install SU there.
Remember if you now flash GB based roms you don't need any patches, but if you flash ICS roms you will need this patch here.. http://forum.xda-developers.com/showthread.php?t=1508118
It will be the old firmware patch you want to download.
After all this you should be set !
???
mjh68 said:
Remember if you now flash GB based roms you don't need any patches, but if you flash ICS roms you will need this patch here.. http://forum.xda-developers.com/showthread.php?t=1508118
Click to expand...
Click to collapse
Why is the 'old firmware patch' necessary when moving from GB to ICS; is something not getting properly overwritten when using a PHxxxxx.zip instead of a full RUU?
jdmba said:
Why is the 'old firmware patch' necessary when moving from GB to ICS; is something not getting properly overwritten when using a PHxxxxx.zip instead of a full RUU?
Click to expand...
Click to collapse
I am talking about if he stays on Gingerbread firmware , but wants to run ICS roms. Then he would need to flash the old firmware patch so his SD card mounts properly.
Yes, I get that ...
Yes, I understand why people need a patch after running the PHxxxx.zip
I am asking why the PHxxxx.zip leaves that a necessary step. What is missing from the PHxxxx.zip that requires this to be done.
I suspect when VZW releases their RUU, such a step will not be necessary (i.e., it will properly update the firmware). So I am trying to get to the bottom of why the PHxxxx.zip does not properly update the firmware.
mjh68 said:
If your S-off and on Juopunut bear's modified Hboot, you can just download the exe. version of the GB ota found in this thread http://forum.xda-developers.com/showthread.php?t=1338916 . Just be aware that once you run it you will be completely stock again including locked bootloader. If you still want to preserve your locked status I would flash this hboot in this thread..http://forum.xda-developers.com/showthread.php?t=1618140
Now, you will still be locked but able to run fastboot commands without unlocking. Now, you have to flash Amon recovery found here..http://www.mediafire.com/?l9dgzvvsdku7g3c This is the recovery that works for GB firmware. If you upgrade back to leaked ICS then you will have to flash 3.15.
Prior to flashing Amon Ra recovery.. you may watch to do a factory reset in hte stock recovery to prevent any possible data connection issues. Once you did that and now have flashed Amon ra.. you can either flash a rooted rom to get root back or to go to developer menu in Amon ra and install SU there.
Click to expand...
Click to collapse
Very useful information mjh. Two points/questions:
1. If the OP doesn't need to use fastboot commands, they can simply flash a PH98IMG.zip of the AmonRA recovery. They can be found in the Amon Ra thread. That way they still get custom recovery without having to change away from the stock HBoot. (I did this earlier today.)
2. Does the factory reset need to be done in AmonRa or bootloader?
---------- Post added at 05:05 PM ---------- Previous post was at 04:57 PM ----------
jdmba said:
Yes, I understand why people need a patch after running the PHxxxx.zip
I am asking why the PHxxxx.zip leaves that a necessary step. What is missing from the PHxxxx.zip that requires this to be done.
I suspect when VZW releases their RUU, such a step will not be necessary (i.e., it will properly update the firmware). So I am trying to get to the bottom of why the PHxxxx.zip does not properly update the firmware.
Click to expand...
Click to collapse
I'm not sure I follow what you're asking about here. mjh doesn't mention running the PHxxxx.zip at all. If you're S-OFF, you don't need to, as the boot image will already be installed properly in recovery.
If you're S-ON, then you have to run the PH98IMG.zip in bootloader after installing a ROM like CleanROM 4.4. That's for installing the boot image, and more or less the same PH98IMG.zip that is included in the upgrades.
The firmware fix is not a PH98IMG.zip and can be flashed in recovery, regardless of S-ON. If I understand correctly, the latest ICS firmware changes around some of the mount points (and probably other things), and thus the ICS ROMs assume those new mount points. Running the firmware patch just updates the system files to point to the right place given the old firmware. (Please correct me if I'm wrong.) As it's not normally needed (ICS ROM assumes ICS firmware), there's no reason it would be included in the PH98IMG.zip that has the boot image. Plus it's probably a different command than what the boot image flashes -- I'm not sure the bootloader can do more complex control flows like that.
destro158 said:
I'm not sure the bootloader can do more complex control flows like that.
Click to expand...
Click to collapse
Which is the basis of my question ... that a RUU will be able to properly handle the issue and the PHxxxx.zip cannot.
Thanks for trying to answer. Perhaps your last sentence is my answer.
jdmba said:
Which is the basis of my question ... that a RUU will be able to properly handle the issue and the PHxxxx.zip cannot.
Thanks for trying to answer. Perhaps your last sentence is my answer.
Click to expand...
Click to collapse
An RUU will put you on the proper firmware for the ROM you are installing. It doesn't have to deal with the issue of you possibly running a different firmware than what the ROM was built for because it will just install the right firmware.
Almost There
destro158 said:
An RUU will put you on the proper firmware for the ROM you are installing. It doesn't have to deal with the issue of you possibly running a different firmware than what the ROM was built for because it will just install the right firmware.
Click to expand...
Click to collapse
Thanks ... we are getting SUPER close to the answer to my question. I guess the final nail would be .... 'why does the PHxxxxx.zip not do that'
jdmba said:
Thanks ... we are getting SUPER close to the answer to my question. I guess the final nail would be .... 'why does the PHxxxxx.zip not do that'
Click to expand...
Click to collapse
The PH98IMG.zip does fix that. You only need the patch if you're running an ICS Rom (anything based on 3.xx firmware) while still on GB firmware (2.xx and below)
Sent from my ADR6425LVW using XDA
scubasteve85 said:
The PH98IMG.zip does fix that. You only need the patch if you're running an ICS Rom (anything based on 3.xx firmware) while still on GB firmware (2.xx and below)
Click to expand...
Click to collapse
Is there a PH which will also push the ICS firmware at the same time?
jdmba said:
Is there a PH which will also push the ICS firmware at the same time?
Click to expand...
Click to collapse
Yes. The RUU (or whatever you want to call it) just leaked is a PH98IMG.zip that will do the full hboot, firmware, radio, and Rom upgrade and is installed in the bootloader.
Sent from my ADR6425LVW using XDA
i've been wondering if anyone else has been having any issues with mean rom ics, i've flashed it twice, and even done a full wipe and everything. but it seems every time i restart (or the phone powers down) i go through about 6 - 10 crashes before it can run stable enough for me to use it at all. has anyone else had this issue or have this issue and can shed any light on what could be causing it?
Strange. Are you s-on or s-off?
Read, Search, Read again, ... Then Ask with Tapatalk 2
Im s-off via Juopunutbear. My phone came with bootloader 1.50 but I updated for ics using what was posted Here, so I could retain s-off
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
ramjet73 said:
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
Click to expand...
Click to collapse
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
AlexxSeven said:
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
Click to expand...
Click to collapse
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Hboot 1.5 s-on and I'm running meanrom ICS 2.6 .
I did the HTC unlock. Then installed Su zip from this site. Then I installed 4ext and rebooted into recovery...flashed the meanrom zip (it flashed the kernel that comes w the Rom ) and that was it. Now I'm on sw 2.89 build w the 3.0.16 kernel and like I said still s off and hboot 1.5
If anyone knows any where to get a kernel to overclock please let me know
Sent from my PG86100 using xda app-developers app
ramjet73 said:
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Click to expand...
Click to collapse
i actually decided to give it a try after making a nand backup ofc, and still had the same issues :s after re-flashing from my backup though it seems to boot fairly stable now. even between switching roms im not sure exactly why but could it have been an issue with anything that is permanent between any rom?
I have a new HTC One that doesn't have the August OTA update. I've used revone for S-OFF and unlock (agian, unlock from revone, not htcdev.com) and am getting ready to root and apply a custom ROM.
But, before I do that, I want to find out how I can get the most current firmwares/radios/etc from the OTA update, without sacrificing root/unlock capability. I'm not sure the best way to do it given that I have S-OFF and unlock via revone, and what files I need to get, beyond the radio.
^^^
Bump. I'm perm rooted, unlocked, s-off with custom recovery but still on hboot 1.44 and software is 1.26.502.12. I'd like to update my firmware too. Is there a suggested RUU or stock ROM for the m7att?
edditnyc said:
^^^
Bump. I'm perm rooted, unlocked, s-off with custom recovery but still on hboot 1.44 and software is 1.26.502.12. I'd like to update my firmware too. Is there a suggested RUU or stock ROM for the m7att?
Click to expand...
Click to collapse
I might be able to help you here. I went through all of this yesterday.
DISCLAIMER: IF YOU BREAK YOUR STUFF, IT'S NOT MY FAULT AND I PROBABLY WON'T BE ABLE TO HELP YOU FIX IT. DO ANY OF THIS AT YOUR OWN RISK AND DO YOUR OWN RESEARCH I still consider myself and Android newb (big time) as this is only my 3rd day into modding.
Go to this post: http://forum.xda-developers.com/showthread.php?t=2365506
Halfway down the first post is the "Firmware Flashing" section where you can download all the bases. Note that 3.06.1700.10 is the GE base and 3.09.401.1 is an early leak of the 4.3 base expected with the 4.3 Sense release . All but the GE one are labelled custom although I don't know what's custom about them to be honest. Also there is a link to HBOOT 1.44, get that.
I flashed all of them in order, except the (GE one) like this: 2.17.401.1-> 2.24.401.1 -> 2.24.401.8 -> 3.09.401.1
Why did I skip the GE one? Solely because the .ZIP didn't say "custom". I have no idea what is custom on it. There really shouldn't be anythin gin that GE base that would do anything bad, and thus probably no reason to not flash that one before 3.09.401.1, but I didn't, so just telling you my experience as it occurred.
!!! This will upgrade HBOOT as you go if you use the files as-is !!! (As I recall, 2.24.401.1 went to HBOOT 1.44 and 3.09.401.1 to HBOOT 1.55)
Since you are S-OFF, you can just downgrade back to HBOOT 1.44. Or, to prevent the upgrade in the first place, you can extract each zip and replace the hboot_signedbyaa.img from within each .ZIP with the HBOOT 1.44 download. Then just re-zip the file and flash it. I ended up downgrading back to HBOOT 1.44 because you can S-OFF it if you need to set yourself S-ON again for some reason.
!!! Also important, this process made my touchpanel stop working on the JB 4.1.2 stock ROM !!!!! I believe this is because the touchpanel update included in 2.24.401.1 requires JB 4.2.2, which AT&T has not pushed out for the HTC One, but it is available on International models. So, if you have no intention to put on a custom ROM that is 4.2.2 (even the international one) or 4.3, then you need to remove the touchpanel update file (tp_SYN3202.img) from all of the firmware.zip before flashing.
If you already have a 4.2.2/4.3 ROM, then leave the touchpanel file in there.
If you are JB 4.1.2 and plan to immediately go to JB 4.2.2 or 4.3, then you can update the touchpanel even though it will make it not work in JB 4.1.2. Why? When you boot into custom recovery, the touchpanel itself will work (at least with TWRP 2.6.1.0, which is what I have running). I don't know if CWM Touch will work in this scenario, but you can use the physical keys for that one. But anyway, the point here is that you can update the touchpanel then immediately flash a new ROM and the touchpanel will work again. This saves you a step of having to update the touchpanel after the new ROM.
Something else to keep in mind is Radio's. The Radio's will upgrade with these bundles and you will end up with a radio different than AT&T's newest radio. My personal opinion is to stick with the newest AT&T release radio, which you can download here: http://forum.xda-developers.com/showthread.php?t=2419699 - The one labelled AT&T latest is a flashable .ZIP you can load in custom recovery. Or you can extract the ZIP and copy radio.img over to your firmware bundles if you want it to just put in the latest radio with the rest of the firmware. You can also flash radio.img in fastboot with "fastboot flash radio radio.img".
Some people are saying the 3.09.401.1 is a little buggy. I'm not actually using my HTC One for anything but playing with ROM's right now. I'm using another phone as primary device still, so I can't provide any comments. You may want to stick with the 2.24.401.8 base which is the latest for 4.2.2 builds. That base will work fine with a 4.3 based ROM.
As for me, I currently have the 3.09.401.1 base but with the latest AT&T release radio and HBOOT 1.44 in place of what's in the original bundle download.