So I've got two questions really. The end goal is essentially to rid myself of the OTA Update notification (which prompts me to update every 4 hours). If anyone knows how to get rid of this permanently then that's problem solved, but I've tried everything that other people have suggested relating to disabling notifications and certain parts of System App functionality etc without success. Alternatively I was thinking I could reset to stock recovery, do the update, then re-root and re-install CWM. Can anyone tell me if this file will work for me? Link to file below, as are my system details
http://www.htc1guru.com/downloads/stock-rom-downloads/
(The one titled Comments: Stock Telstra WWE (Australia) ROM 2.24.841.1 with graphical aroma installer. Includes the ability to flash the stock Recovery and also stock Radio. mid: PN0714000 cid: TELST001)
I'm running rooted stock ROM, S-ON with CWM Recovery:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.841.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks for any help, Daniel
RepomanPrime said:
So I've got two questions really. The end goal is essentially to rid myself of the OTA Update notification (which prompts me to update every 4 hours). If anyone knows how to get rid of this permanently then that's problem solved, but I've tried everything that other people have suggested relating to disabling notifications and certain parts of System App functionality etc without success. Alternatively I was thinking I could reset to stock recovery, do the update, then re-root and re-install CWM. Can anyone tell me if this file will work for me? Link to file below, as are my system details
http://www.htc1guru.com/downloads/stock-rom-downloads/
(The one titled Comments: Stock Telstra WWE (Australia) ROM 2.24.841.1 with graphical aroma installer. Includes the ability to flash the stock Recovery and also stock Radio. mid: PN0714000 cid: TELST001)
I'm running rooted stock ROM, S-ON with CWM Recovery:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.841.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks for any help, Daniel
Click to expand...
Click to collapse
No, Do not install OTA updates with the 2.24.841.1 you will softbrick your device. You need a Stock rom that matches your current 6.11.841.7 firmware or is only one version lower e.g 5.xx.841.x to safely take OTA updates. With the 2.24.842.11 rom if you install OTA's the first OTA you receive will be 3.xx.841.x and will try to downgrade your firmware, which is not possible with s-on. The OTA will fail and you'll be stuck in a bootloop. Normally this is not irreversible but has in some cases caused permanent damage to the memory chip.
If you are wanting to return to 100% Stock to reinstate your warranty you need s-off. It's the only way to downgrade your firmware and set your bootloader back to ***LOCKED*** as apposed to ***RELOCKED***. :good:
Danny201281 said:
No, Do not install OTA updates with the 2.24.841.1 you will softbrick your device. You need a Stock rom that matches your current 6.11.841.7 firmware or is only one version lower e.g 5.xx.841.x to safely take OTA updates. With the 2.24.842.11 rom if you install OTA's the first OTA you receive will be 3.xx.841.x and will try to downgrade your firmware, which is not possible with s-on. The OTA will fail and you'll be stuck in a bootloop. Normally this is not irreversible but has in some cases caused permanent damage to the memory chip.
If you are wanting to return to 100% Stock to reinstate your warranty you need s-off. It's the only way to downgrade your firmware and set your bootloader back to ***LOCKED*** as apposed to ***RELOCKED***. :good:
Click to expand...
Click to collapse
So, to summarise, I need a stock recovery matching my CID Telst001 and MID AND with firmware 5.xx.841.xx or 6.xx.841.xx? Right, sounds like a tall order. Any ideas for any ways to just suppress the notification?
PS I don't really need to restore it for warranty, only thing wrong with it as it is is the notification for the OTA update which won't leave me alone
Thanks for the reply
RepomanPrime said:
So, to summarise, I need a stock recovery matching my CID Telst001 and MID AND with firmware 5.xx.841.xx or 6.xx.841.xx? Right, sounds like a tall order. Any ideas for any ways to just suppress the notification?
PS I don't really need to restore it for warranty, only thing wrong with it as it is is the notification for the OTA update which won't leave me alone
Thanks for the reply
Click to expand...
Click to collapse
Flash a Stock based custom Rom. Such as ARHD or Maximus HD that will get rid of the notification.
I see you already posted in the Australian Users thread hopefully someone there can share a suitable stock nandroid. You can use :good:
Related
Hi all,
I've been banging my head for quite some time on why I haven't received any of the OTA updates. I'm still on 4.2.2 and seeing my friends, with different variants of course, getting KitKat... pisses me off
As you can see I'm S-on and was wondering if I really need to go through the hassle of S-Off.
Can anyone here offer a simple walkthrough or a link to download a relevant OTA or Stock ROM that could start getting me OTA updates?
In the searches I've done I couldn't find an OTA I could manually flash since none of the OTAs base versions is 2.24.401.9. Signature fail every time.
adb and fastboot fully functional.
I didn't flash any recovery or other img yet. Fresh out of the box.
Here are my device details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37BW900798
(bootloader) imei: Mod edit removed IMEI
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Help will be greatly appreciated.
Thanks,
Ita
itaita22 said:
Hi all,
I've been banging my head for quite some time on why I haven't received any of the OTA updates. I'm still on 4.2.2 and seeing my friends, with different variants of course, getting KitKat... pisses me off
As you can see I'm S-on and was wondering if I really need to go through the hassle of S-Off.
Can anyone here offer a simple walkthrough or a link to download a relevant OTA or Stock ROM that could start getting me OTA updates?
In the searches I've done I couldn't find an OTA I could manually flash since none of the OTAs base versions is 2.24.401.9. Signature fail every time.
adb and fastboot fully functional.
I didn't flash any recovery or other img yet. Fresh out of the box.
Here are my device details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37BW900798
(bootloader) imei: Mod edit removed IMEI
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Help will be greatly appreciated.
Thanks,
Ita
Click to expand...
Click to collapse
No idea why people want stock OTA...
Unlock bootloader, install TWRP, flash whatever rom you want. No need for s-off.
Simple as 1, 2, 3.
Moderator Information,
I have removed your IMEI number. This is personal information and you shouldn't post it on line.
Ghost
I have exactly the same problem. HTC One is unrooted (or whatever HTC's expression for root is), but it doesnt want to update to last version 4.4.2, which is already available for my version 3.62.401.1.
If anyhone has an idea how to get OTA for 4.4.2, please let us know.
Why not just flash ARHD 5.1...4.19.401.8.
You will have the latest rom, identical to the stock Rom, but slicker, faster and better. When HTC decide to update that Rom, ARHD will be the first to offer it. No waiting for it to become available for you country/network or variant.
Sent from my HTC One using XDA Premium HD app
cr1960 said:
No idea why people want stock OTA...
Unlock bootloader, install TWRP, flash whatever rom you want. No need for s-off.
Simple as 1, 2, 3.
Click to expand...
Click to collapse
Well, thanks.
I wish to have stock OTA so I won't need to chase after stable releases, battery drain issues, or other wonderful scenarios I know you guys handle daily.
On that matter, installing another stock will put me on track for OTA updates? Are there other factors that could prevent it?
Appreciate the help.
itaita22 said:
Well, thanks.
I wish to have stock OTA so I won't need to chase after stable releases, battery drain issues, or other wonderful scenarios I know you guys handle daily.
On that matter, installing another stock will put me on track for OTA updates? Are there other factors that could prevent it?
Appreciate the help.
Click to expand...
Click to collapse
That's fine - to each his own. My experience has been that you get great stability and even better battery (using custom kernels) with custom roms, but hey, that's just me
You'll just have to wait for your carrier to send the OTA - you can't force it.
hi,
yesterday i tried to install the update to kitkat on my one.
the download was complete und i startet to install it.
The phone bootet in to recovery(i think) and startet to install the update.
nearly at the end it crashed and i dont know why. a red triangle is shown on the display. so i restarted it.on every boot it stucks in the red triangle.
Bootloader is unlocked, S - ON and at the time of the update stock recovery.
now i tried to s-off it . didtn work (rumrunner and firewater). i installed cwm custom recovery. i dont know what i can do now to get the phone working.
fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.161.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
so i now tried flashing cyanogen mod and it works, but i want to go back to stock rom.
i havent found a RUU yet.
etsch said:
so i now tried flashing cyanogen mod and it works, but i want to go back to stock rom.
i havent found a RUU yet.
Click to expand...
Click to collapse
Why don't you install a Sense-based custom ROM like ARHD instead of completely returning to stock. Unless your intention is to claim warranty, I frankly see no advantage of RUU-ing your phone, considering that you're already on CWM and bootloader unlocked
because i want a stock rom.
now i have the phone s-off.
i changed my CID to HTC__102 (before it was VODAP102)
i flashed a stock rom from htc1guru and it works. but on the installation it was called a vodafone rom( i downloaded a non branded rom).
now i have the problem i cant update the software. now i have Android 4.2.2 but i want 4.4.2
if i check for updates i got 3 updates (Softeware Update,Software Update und HTC Sync Manger) bot software Updates are only for bugfixes
Hi guys i had problem, few days ago phone notify me about update, i thought ok it nice, I restored stock recovery and I relocked bootloader in fastboot.
I clicked the install , process ran without errors. in stock recovery and BANG 3-4 first times phone stopped on boot, i tried factory reset after boot phone giving me black screen, next I tried to flash RUU's.
Before update a I had 7.19.401.22, i flashed this version - not working, flashed 7.19.401.2 - not working, flashed 7.19.401.30 - not working although it ,the same version is after update.
I don't know what to do :crying:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37RW902282
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Flashed RUU's
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip
Jakqa said:
Hi guys i had problem, few days ago phone notify me about update, i thought ok it nice, I restored stock recovery and I relocked bootloader in fastboot.
I clicked the install , process ran without errors. in stock recovery and BANG 3-4 first times phone stopped on boot, i tried factory reset after boot phone giving me black screen, next I tried to flash RUU's.
Before update a I had 7.19.401.22, i flashed this version - not working, flashed 7.19.401.2 - not working, flashed 7.19.401.30 - not working although it ,the same version is after update.
I don't know what to do :crying:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37RW902282
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Flashed RUU's
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip
Click to expand...
Click to collapse
The ota caused a bootloop because you have installed it on a rooted phone. Unlike older updates (6.xx.xxx.x and before), you can't simply reflash the stock recovery to update. Lollipop updates can only be installed on 100% stock and non-rooted rom. That wasn't a problem in the past but its now a well know problem with all newer updates.
Your version-main is now 7.19.401.30 because, unlike the software, the firmware updated fine. You can't flash the 7.19.401.22 RUU because its now a downgrade in version (because your firmware got updated). Downgrading using a RUU requires S-OFF, your phone is S-ON. Same reason why the 7.19.401.2 won't work.
7.19.401.30 ruu is a "combined" RUU so it can't be flashed on a s-on phone.
Your option are:
unlock the bootloader, flash twrp recovery and flash a rom
or achieve s-off using sunshine and flash the .22 or the .30 ruu (you'll need to do option 1 first because you need a working rom to be able to s-off the phone)
Or maybe someone already uploaded a nandroid backup of 7.19.401.30. If you find one you can restore the backup using a custom recovery and then reflash the stock recovery.
alray said:
The ota caused a bootloop because you have installed it on a rooted phone. Unlike older updates (6.xx.xxx.x and before), you can't simply reflash the stock recovery to update. Lollipop updates can only be installed on 100% stock and non-rooted rom. That wasn't a problem in the past but its now a well know problem with all newer updates.
Your version-main is now 7.19.401.30 because, unlike the software, the firmware updated fine. You can't flash the 7.19.401.22 RUU because its now a downgrade in version (because your firmware got updated). Downgrading using a RUU requires S-OFF, your phone is S-ON. Same reason why the 7.19.401.2 won't work.
7.19.401.30 ruu is a "combined" RUU so it can't be flashed on a s-on phone.
Your option are:
unlock the bootloader, flash twrp recovery and flash a rom
or achieve s-off using sunshine and flash the .22 or the .30 ruu (you'll need to do option 1 first because you need a working rom to be able to s-off the phone)
Or maybe someone already uploaded a nandroid backup of 7.19.401.30. If you find one you can restore the backup using a custom recovery and then reflash the stock recovery.
Click to expand...
Click to collapse
1.What Kind of rom? Stock or custom - without s-off?
3.Do You know anyone who could upload a backup of 7.19.401.30?
Jakqa said:
1.What Kind of rom? Stock or custom - without s-off?
3.Do You know anyone who could upload a backup of 7.19.401.30?
Click to expand...
Click to collapse
1.a stock or stockish rom is best if you want to achieve s-off, You don't need s-off to flash a custom rom, only an unlocked bootloader + a custom recovery.
3. No, might want to ask in the update thread in the general section (see sticky threads)
I have been trying lately to go back to android 4.4.3 instead of lollipop on my M7 dual sim.. so far I found this is RUU
Code:
OTA updates (for Android 4.4.3):
OTA_M7C_DUG_K443_SENSE60_MR_HTC_Nordic_6.13.402.2-5.17.402.6_release_389543.zip - 392.32 MB
From this thread http://forum.xda-developers.com/showthread.php?t=2617159
My fastboot values:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.19.3509.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.402.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3756mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d0e3b226
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
According to the one who posted the RUU, my CID, phone model, version match, however, I saw some posts that I need to S-OFF in order to downgrade using a RUU so I kind of need help, or a some sort of guide.
Also, is it 100% sure that the OTA will work fine with my phone? Do I need anything else to be matching to downgrade using the RUU?
First thing you need is s-off. Then you need full stock ROM with preload folder (there are some apps there which get deleted when you unlock your bootloader) and stock recovery. As long as you are s-on, you can't downgrade your firmware, but you can flash KitKat ROM on Lollipop firmware
@MattTucke
the file linked isn't a RUU but an OTA update which is useless for downgrading. You will need the 6.13.402.2 Combined RUU which is only available on ir-file.com = paid account to download (I can help you with that since I currently have an account but you'll have to wait since the download speed from this site is capped to 100kb/sec)
+
you'll need to use Sunshine S-OFF which also cost money
Like mentioned above, custom kitkat roms might be an easier and cheaper option since you doesn't need to downgrade the firmware to run a Kitkat rom. But finding a Kitkat rom for a M7CDUG might not be an easy task...
I'm trying to update my firmware before updating to ARHD 93.0 from 91.0 and I have a few questions. I'm trying to figure out how to update my firmware, but I can't seem to find any firmware.zip for my phone model. What i can find though, are RUUs for it, specifically 7.21.707.5 and 7.21.707.21. I want to know if these are the correct and the latest ones and which one I should use first if they are correct, since I heard that you need to update the firmware incrementally. I'm also not sure if using these would revert my phone back to S-ON and unrooted, so I hope someone can clarify me on this. Thanks and fastboot getvar all results are as follows.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Azraelos said:
I'm trying to update my firmware before updating to ARHD 93.0 from 91.0 and I have a few questions. I'm trying to figure out how to update my firmware, but I can't seem to find any firmware.zip for my phone model. What i can find though, are RUUs for it, specifically 7.21.707.5 and 7.21.707.21. I want to know if these are the correct and the latest ones and which one I should use first if they are correct, since I heard that you need to update the firmware incrementally. I'm also not sure if using these would revert my phone back to S-ON and unrooted, so I hope someone can clarify me on this. Thanks and fastboot getvar all results are as follows.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
You don't need to flash incrementally when using a RUU and the only thing you need to flash a 7.xx.707.x RUU is a 6.xx.707.x firmware already on the phone (which you have). Install the newer RUU (.21) then take all the ota updates (should have 2, one from .21 to .30 and another one from .30 to .51). Flashing a RUU doesn't affect S-ON/S-OFF status neither the unlocked bootloader but you'll obviously loose root since flashing a RUU will flash the /system partition back to stock which is where are stored the SU binaries. Anyway this is not really an issue since ARHD is a pre-rooted rom so after youv got your firmware updated via the RUU and ota updates, you can reflash TWRP recovery and ARHD so your phone will be on the latest firmware + ARHD + root + S-OFF + unlocked BL.
Btw there are otther way to update your firmware like changing your MID and CID and flashing another firmware.zip version. E.g. MID to PN0710000 and cid to HTC__001 (or supercid) and flash the 7.19.401.2 full firmware.zip then TWRP and finally ARHD.
Both methods will make your phone ready for latest roms like ARHD.
Thanks for the reply For the 1st method, how do I go about getting the OTA updates? Does flashing the RUU mean my phone will have the stock ROM and I can just download them through HTC? For the 2nd method, if I change the MID and CID to what you said, the existing firmware will still be the same right? I thought you could only upgrade the firmware with the same middle numbers, eg. 6.xx.401.x to 7.xx.401.x and not 6.xx.707.x to 7.xx.401.x even when you change the MID and CID.
Azraelos said:
Thanks for the reply For the 1st method, how do I go about getting the OTA updates? Does flashing the RUU mean my phone will have the stock ROM and I can just download them through HTC?
Click to expand...
Click to collapse
Yes.
For the 2nd method, if I change the MID and CID to what you said, the existing firmware will still be the same right?
Click to expand...
Click to collapse
Yes, until you flash another firmware...
I thought you could only upgrade the firmware with the same middle numbers, eg. 6.xx.401.x to 7.xx.401.x and not 6.xx.707.x to 7.xx.401.x even when you change the MID and CID.
Click to expand...
Click to collapse
Not if you change the CID and MID. But it must be a firmware compatible with your variant (M7_UL) and you must convert by using a complete(full) firmware.zip file, not using a firmware.zip that was extracted from an ota update (these kind of firmware.zip must be flashed incrementally). Acomplete firmware.zip (as opposed to a firmware.zip extracted from an OTA) will be about 40-50 Mb like this one. So if going for option #2: Change CID to one of the CID compatible with x.xx.401.x base (or supercid), change MID to PN0710000, flash that 7.19.401.2 firmware, then reflash twrp and finally ARHD.