Database Develop

[SOLVED] Missing version-main number; trying to get back to stock

EDIT: Well this is awkward. After posting this thread I found the solution. If anyone in the future has the same problems as me, just flash one of these
http://forum.xda-developers.com/showthread.php?t=2406330
Apparently that was all that was needed.
Hello xda community,
First off, I apologize. I know questions like these get asked hundreds of times but after spending 3 days straight of digging through forum threads and making very little progress I've decided to just ask.
So I tried installing a custom rom on my HTC One. I did exactly what I usually do when flashing a new rom on my nexus 7. I had an unlocked device with the latest twrp recovery. I did an advanced wipe (which included internal storage), then I did an adb sideload to flash the rom. I must have done something wrong because the flashing didn't work and ever since then I've been trying to get back to stock rom.
I've tried running both the 3.04.651.2 RUU and the 4.06.651.4 RUU posted by O.M.J and neither worked. I've tried flashing the Guru Reset M7 Sprint 3.04.651.2 rom found on htc1guru. Twrp said the flashing was successful yet when I booted up the device it would get to the lockscreen and when I tried to unlock it, it would just show the HTC logo. After that it would endlessly reboot itself over and over. I've tried flashing the Android Revolution HD 31.6 rom and I got the same problems as when I tried to flash the htc1guru stock rom.
I can get into both the bootloader and twrp recovery without any problems so I figure not all hope is lost. Below is info about my phone. As you can see the version-main number is missing, though I don't know how important that is.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: X
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
I'm not sure if it's significant, but I did manage to flash that custom rom today. It's the Slim-m7spr-4.4.2.build.5 rom. I booted up the phone just fine (this is probably the only successful thing I've done so far).
Anyway, like I said I'm trying to get back to stock and I would appreciate any and all help. Thanks guys.

[Q] Finding the Right RUU

Could use a little help with my HTC One M7. Bought it 2nd hand online a few months back, and it came pre-flashed with InsertCoin.
Buuut, updating has become a bit of a hassle for me, especially having to manually update. I'm looking to flash the stock ROM get the OTA up and running again.
I saw the other threads and followed the instructions so I have S-OFF, and I've already removed the "TAMPERED" and "UNLOCKED" from the bootloader. I came across a pretty big hiccup along the way, though.
For some reason, the OS on my bootloader screen is blank. I've tried getting version using ADB, but the version_main is still blank. Here's what I got from ADB:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ************
(bootloader) imei: ************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3760mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.082s
Click to expand...
Click to collapse
So, I've been wondering which RUU I'm supposed to use, because, most of the other posts I've read need me to match my version_main, my radio, CIDnumber, carrier and modelID. Not knowing my version/OS, what RUU should I use?
Note: My phone isn't locked to a carrier. I live outside of the US, (in Asia) but I'm unsure if I'm using the unlocked EU version or the International version.
Thanks in advanced,
-Q

detribdino said:
Could use a little help with my HTC One M7. Bought it 2nd hand online a few months back, and it came pre-flashed with InsertCoin.
Buuut, updating has become a bit of a hassle for me, especially having to manually update. I'm looking to flash the stock ROM get the OTA up and running again.
I saw the other threads and followed the instructions so I have S-OFF, and I've already removed the "TAMPERED" and "UNLOCKED" from the bootloader. I came across a pretty big hiccup along the way, though.
For some reason, the OS on my bootloader screen is blank. I've tried getting version using ADB, but the version_main is still blank. Here's what I got from ADB:
So, I've been wondering which RUU I'm supposed to use, because, most of the other posts I've read need me to match my version_main, my radio, CIDnumber, carrier and modelID. Not knowing my version/OS, what RUU should I use?
Note: My phone isn't locked to a carrier. I live outside of the US, (in Asia) but I'm unsure if I'm using the unlocked EU version or the International version.
Thanks in advanced,
-Q
Click to expand...
Click to collapse
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
then flash the latest WWE ruu (7.19.401.2)
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

RUU according to your info is 7.18.206.2 available at link post above but that's a carrier ruu with many bloatware so flash international ruu 7.19.401.2 instructions given above

Black/White Screen and freeze boot up after OTA

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)

[Q] Relocked bootloader while using custom software, hboot won't detect power button

So, here's the thing, I already posted on a thread but it seems it's actually full of people asking and the guys answering there are stumped with our problems so I came here.
My bootloader is locked because I (stupidly ) relocked it while trying to install a newer firmware via RUU so then it just locked me out and couldn't do anything until I installed the RUU update of the same version I was running.
It's working but not as intended.
I tried unlocking the bootloader again after installing the RUU but no luck, the token works but it just won't detect my power button when I try to accept but the button works perfectly while running the system.
Here's my getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s

adkz25 said:
So, here's the thing, I already posted on a thread but it seems it's actually full of people asking and the guys answering there are stumped with our problems so I came here.
Click to expand...
Click to collapse
Actually they guy there, me, was really busy in the past days and wasn't able to answer everyone. You can't imagine how much PM and Quote I had in the last week And yes I agree with you, its really hard to troubleshoot in that thread since there's so many discussions going on at the same time.
My bootloader is locked because I (stupidly ) relocked it while trying to install a newer firmware via RUU so then it just locked me out and couldn't do anything until I installed the RUU update of the same version I was running.
It's working but not as intended.
I tried unlocking the bootloader again after installing the RUU but no luck, the token works but it just won't detect my power button when I try to accept but the button works perfectly while running the system.
Here's my getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
Click to expand...
Click to collapse
Its a pretty uncommon problem. When flashing a RUU, all partitions (except some partitions that are unique to each devices) are flashed back to stock, even the bootloader which make me believe its not a corrupt bootloader problem. So if after flashing a RUU, your phone still have some problems, its most likely an hardware problem... If the RUU flashed fine there is nothing more you can do on the software side.... THe only thing I can think is to use Sunshine S-OFF to unlock your bootloader but unfortunately it cost 25$ to use Sunshine but at least it will bypass that "power button not working only in bootloader" problem

Yeah, I figured you were real busy. )^:
I really don't mind paying for Sunshine to get S-Off but when I tried running it to get temp root it just says it failed and closes. Is there any way for me to get it working?

adkz25 said:
Yeah, I figured you were real busy. )^:
I really don't mind paying for Sunshine to get S-Off but when I tried running it to get temp root it just says it failed and closes. Is there any way for me to get it working?
Click to expand...
Click to collapse
I would try the same method they are using in the Verizon HTC One forum, get temp root using kingRoot then launch sunshine
http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099

Yay! It worked. I'm S-Off and unlocked right now so I might try to install TWRP and stuff.
KingRoot worked like a charm, I didn't even need to re-run it and try to get some prompt, it just... worked and gave me temp root.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-OFF
.
Anyway, I still have a little doubt (unrelated to this issue but you seem to know your way around). Everything I posted in this and that thread went down because I tried to install this ROM and it said I needed some firmware flashed.
What I'm trying to get to is:
Do I really need to flash that firmware?
Is it flashed via TWRP?
Are those GPE roms worth it?
Anyways, thank you for helping me out.

adkz25 said:
Yay! It worked. I'm S-Off and unlocked right now so I might try to install TWRP and stuff.
KingRoot worked like a charm, I didn't even need to re-run it and try to get some prompt, it just... worked and gave me temp root.
.
Anyway, I still have a little doubt (unrelated to this issue but you seem to know your way around). Everything I posted in this and that thread went down because I tried to install this ROM and it said I needed some firmware flashed.
What I'm trying to get to is:
Do I really need to flash that firmware?
Is it flashed via TWRP?
Are those GPE roms worth it?
Anyways, thank you for helping me out.
Click to expand...
Click to collapse
Glad it worked!
Firmware files are flashed with fastboot in ruu mode:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip "file name".zip
fastboot flash zip "file name".zip
fastboot reboot-bootloader
Then go in recovery and flash the rom
Better to flash the latest firmware without stock recovery so you don't overwrite twrp recovery with the stock recovery.
Note that this firmware is the latest GPE firmware and that if you want to go back to stock rom using a ruu you'll have to reflash a hboot 1.57 or 1.61 firmware before running a 7.xx.xxx.xx Sense ruu.
GPE roms is perfect if you want something closer to a nexus experience, otherwise stay with a Sense rom.
Sent from my HTC One using XDA Labs

M7 Trying to get back to stock-but need a helping hand

hey guys, i am now about to sell my m7 after over 2 years
a long time ago when i unlocked the boot loader, and installed tmrp i made a backup of my stock ROM. its been on a usb pen along time now. so today i used twrp to restore it. all when well i then decided to relock the bootloader using fastboot. in my ignorance i thought this was all i would need to do. upon reboot a rom update was found 6.09.401.10. i am currently 6.09.401.5. downloaded and restarted to install the update. recovery wouldnt load. okay that from the twrp flash replacing it. so of course onto xda to find a stock recovery. i believe i found it. but now i am worried- do i need to re unlock the bootloader? will i need to get the token again? or do i need the rru.exe 6.09.401.10? what is the best way to do this as unsure what to do next? as it will need ota updates. i have added my version info below just encase its needed.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37WW905236
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4197mV
(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 in advance

bacon165 said:
hey guys, i am now about to sell my m7 after over 2 years
a long time ago when i unlocked the boot loader, and installed tmrp i made a backup of my stock ROM. its been on a usb pen along time now. so today i used twrp to restore it. all when well i then decided to relock the bootloader using fastboot. in my ignorance i thought this was all i would need to do. upon reboot a rom update was found 6.09.401.10. i am currently 6.09.401.5. downloaded and restarted to install the update. recovery wouldnt load. okay that from the twrp flash replacing it. so of course onto xda to find a stock recovery. i believe i found it. but now i am worried- do i need to re unlock the bootloader? will i need to get the token again? or do i need the rru.exe 6.09.401.10? what is the best way to do this as unsure what to do next? as it will need ota updates. i have added my version info below just encase its needed.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37WW905236
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4197mV
(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 in advance
Click to expand...
Click to collapse
To flash a recovery, even if its the stock one, the bootloader must be unlocked. Unfortunately, unlocking the bootloader requires the stock recovery....
I would keep the bootloader locked and flash the latest RUU version for this phone (7.19.401.51). Look in the general section (in the sticky threads) there is one named "Lollipop RUU collection". You'll find that RUU at post #2 and instructions how to flash at post #1. Be sure to use the fastboot version (htc_fastboot) instructed at post #1 (you can't flash a 7.xx.xxx.x ruu with the fastboot version from the android sdk tools).

This is the link to the RUU. Install the file on PC (it is a big file) and connect your phone and run it.
Should return you to stock Lollipop 5.0.2 with Sense 6.
Download the right one for your variant:
htc.com/us/support/htc-one/news/ (Unlocked/Developer Edition)
htc.com/us/support/htc-one-t-mobile/news/
htc.com/us/support/htc-one-sprint/news/
htc.com/us/support/htc-one-verizon/news/
htc.com/us/support/htc-one-att/news/

alray said:
To flash a recovery, even if its the stock one, the bootloader must be unlocked. Unfortunately, unlocking the bootloader requires the stock recovery....
I would keep the bootloader locked and flash the latest RUU version for this phone (7.19.401.51). Look in the general section (in the sticky threads) there is one named "Lollipop RUU collection". You'll find that RUU at post #2 and instructions how to flash at post #1. Be sure to use the fastboot version (htc_fastboot) instructed at post #1 (you can't flash a 7.xx.xxx.x ruu with the fastboot version from the android sdk tools).
Click to expand...
Click to collapse
Thank you alray for your fast reply i am currently downloading 7.19.401.51 (signed version)
is it the downgrade instructions i need to follow?

Thank you for your reply
my version is the European (uk version)
i am currently downloading the 7.19.401.51 from xda, might take about 2 hours, i will keep you informed with my progress
thanks

bacon165 said:
is it the downgrade instructions i need to follow?
Click to expand...
Click to collapse
No, going from 6.xx.xxx.x to 7.xx.xxx.x isn't a downgrade.
Sent from my HTC One using XDA Labs

Hey Alray
I followed the instructions and the advised you gave me
my HTC M7 is now back up and running RUU installed no problem
thank you again for your guidance/advise

bacon165 said:
Hey Alray
I followed the instructions and the advised you gave me
my HTC M7 is now back up and running RUU installed no problem
thank you again for your guidance/advise
Click to expand...
Click to collapse
You're welcome
Sent from my HTC One using XDA Labs