Has anyone the stock radio.img (or something else)? My radio changed with a custum rom to 4T.xxxxxx but as far as I remember mine was originally 4A.xxxxxx . I need the one from the latest version (7.19.401.51).
I am pretty much full stock again but only the radio bugs me.
Thanks for every reply!
Or Cun said:
Has anyone the stock radio.img (or something else)? My radio changed with a custum rom to 4T.xxxxxx but as far as I remember mine was originally 4A.xxxxxx . I need the one from the latest version (7.19.401.51).
I am pretty much full stock again but only the radio bugs me.
Thanks for every reply!
Click to expand...
Click to collapse
Flashing custom roms doesn't change your radio. Unless it's a guru reset Rom. But then it is an option during the installer and will always be the correct radio for the Rom.
Also 4A.xxxxxx are the older radios the latest ones start with 4T.xxxxxxx. Where are you reading your radio version from? In Android Settings? or with fastboot getvar command?
Sent from my HTC One using Tapatalk
Danny201281 said:
Flashing custom roms doesn't change your radio. Unless it's a guru reset Rom. But then it is an option during the installer and will always be the correct radio for the Rom.
Also 4A.xxxxxx are the older radios the latest ones start with 4T.xxxxxxx. Where are you reading your radio version from? In Android Settings? or with fastboot getvar command?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It stands in the bootloader and yes it was a guru reset.
So, you mean that 4A is just older then 4T and everything is the same, right?
Or Cun said:
It stands in the bootloader and yes it was a guru reset.
So, you mean that 4A is just older then 4T and everything is the same, right?
Click to expand...
Click to collapse
If the guru reset matches your current firmware then it will be fine. If your not sure. Post the output of
Code:
fastboot getvar all
Please remove e your IMEI and Serial numbers before posting.
And a link to the guru reset you flashed. :good:
Sent from my HTC One using Tapatalk
Danny201281 said:
If the guru reset matches your current firmware then it will be fine. If your not sure. Post the output of
Code:
fastboot getvar all
Please remove e your IMEI and Serial numbers before posting.
And a link to the guru reset you flashed. :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Code:
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4029mV
(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.125s
sadly I can´t remember which guru reset I used but it was 4.3 JB and sense 5 for my device.
Or Cun said:
Code:
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4029mV
(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.125s
sadly I can´t remember which guru reset I used but it was 4.3 JB and sense 5 for my device.
Click to expand...
Click to collapse
Ok so what are your reasons for going back to stock. Warranty? OTA updates? Or you just want your device stock?
I ask because your device is s-on with lollipop firmware. If you want to claim on the warranty you need to be s-off.
For OTA updates or just because you want a stock device it's just a case of flashing the correct Rom or RUU. If you've flashed a JB stock reset that will be no good as your firmware requires a lollipop Rom.
Sent from my HTC One using Tapatalk
I just wanted the stock firmware. I flashed the 4.3 guru reset back in 2014 when it was not as old as it is now. And there was nowhere a ruu with radio 4A. and the next best one was with 4T.
Or Cun said:
I just wanted the stock firmware. I flashed the 4.3 guru reset back in 2014 when it was not as old as it is now. And there was nowhere a ruu with radio 4A. and the next best one was with 4T.
Click to expand...
Click to collapse
In which case I would just flash the lollipop ruu. It will set your device back to full stock firmware and rom. You g can download the RUU here https://www.androidfilehost.com/?fid=24369303960689843
You will need to relock your bootloader because your s-on. Ànd backup any important data as this will wipe your device. Then flash the RUU with htc_fastboot. Which you can download here https://www.androidfilehost.com/?fid=95916177934550031
Download htc_fastboot and the RUU. Copy both files to your existing fastboot folder and rename the RUU zip file to something simple. e.g "ruu"
Boot your device to the bootloader and connect fastboot usb. Then relock your bootloader and flash the RUU with the following commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Wait for reboot
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
The device will reboot during the flash, and the progress bar on the phone won't quite reach 100% that's normal. Wait till the command windows competes it's output with a successful message then
Code:
fastboot reboot
That's it you now have latest stock rom and firmware. You can unlock the bootloader again if you want by flashing the Unlock code.bin the same as the first time and flash twrp recovery, or leave it as it is in stock condition :good:
Sent from my SM-T230 using Tapatalk
Or Cun said:
And there was nowhere a ruu with radio 4A. and the next best one was with 4T.
Click to expand...
Click to collapse
Btw, when looking for a RUU, radio versions are irrelevant. You want to find a RUU that match your version-main. All 7.xx.xxx.x versions now have the same 4T.35.3218.16_10.33Q.1718.01L radio version so if looking for a RUU using the radio version, it will bring you tons of RUUs and only one of them will fit your phone, that one Danny201281 linked above.. :good:
Thank you both very much. Then my problem should be solved. Again, thank you!
hello just wanted to say a big thankyou for this guide. Been on a couple of days trying to get my htc one m7 running again following various guides on you tube. This one has finally sorted out my phone back to stock after it flipped out during a delete data from an app. Thanks again. One happy man
big thanks for this post. It helped me alot during saving my old "dead" One M7 after getting S-ON & relocked and got back to stock again.
Thank YOU! YOU HELP ME! BEST TOPIC EVER! YEEEEEEEEEES YEEEEEEEEEEES
Related
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Nic2112 said:
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Click to expand...
Click to collapse
post output of "fastboot getvar all"
remove S/N & IMEI before posting
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Nic2112 said:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Click to expand...
Click to collapse
your previous CID was BM_001, right?
look into nkk71 SuperGUIDE in my signature
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
kamilmirza said:
your previous CID was BM_001, right?
Click to expand...
Click to collapse
I believe so, yes.
Nic2112 said:
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
Click to expand...
Click to collapse
yes sadly there is only nandroid of BM right now
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Nic2112 said:
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Click to expand...
Click to collapse
yeah maybe that could be the problem
why not try the nandroid and see how it goes?
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Oh Wow, there is a guide for Canadian HTC One, didn't know that!
Are you sure that a Telus RUU will work on a Bell phone? They use different networks I think
SaHiLzZ said:
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Click to expand...
Click to collapse
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
SaHiLzZ said:
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
Click to expand...
Click to collapse
I know how to go back to 1.44, I have done that before.
So what you are saying is that if I have the nandroid installed, and stock recovery from your thread, the phone will detect the OTA? It should install no problem because it will be a standard recovery.
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
SaHiLzZ said:
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
Click to expand...
Click to collapse
Thatk you, one last question before I try this, the OTA, will it replace the radios and firmware as well to Bell's? I guess it depends on what they put in the OTA.
Yes, OTA generally contain new OS, HBOOT, Recovery, and RADIO, practically a full RUU replacement, but not all. IF you are S-ON, you will need to lock bootloader after loading stock recovery, but if you are S-OFF, that doesnt matter, and I will suggest to stay S-OFF!
Please help
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
ginuwine96 said:
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
Click to expand...
Click to collapse
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Not sure what file I need
majmoz said:
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Click to expand...
Click to collapse
This is my phones Info I am not sure what file to use for it ?
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
ginuwine96 said:
This is my phones Info I am not sure what file to use for it ?
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
Click to expand...
Click to collapse
If you're going to follow my guide, you'll need to use CWM method, using this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/
make sure to have read it once or twice, to be sure you're comfortable with the process
hallo
i have installed a custom rom to my htc one and now it is in a boot loop and when i try to go to recovery it just freeze at the htc logo
i have tryet to instal cwm recovery and twrp recovery and stock recovery with no luck hope you guys can help me
sorry for my bad english
Anemicnine40 said:
hallo
i have installed a custom rom to my htc one and now it is in a boot loop and when i try to go to recovery it just freeze at the htc logo
i have tryet to instal cwm recovery and twrp recovery and stock recovery with no luck hope you guys can help me
sorry for my bad english
Click to expand...
Click to collapse
Which custom rom?
Which TWRP version?
Post the output of ''fastboot getvar all'' except IMEI and SN
did you ''fastboot erase cache'' ?
alray said:
Which custom rom?
Which TWRP version?
Post the output of ''fastboot getvar all'' except IMEI and SN
did you ''fastboot erase cache'' ?
Click to expand...
Click to collapse
cant remember the name of the rom
twrp version 2,5,0,0 -2,6,3,3- 2,7,0,0
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3840mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
yes i erase cache after every flash
Anemicnine40 said:
cant remember the name of the rom
twrp version 2,5,0,0 -2,6,3,3- 2,7,0,0
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3840mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
yes i erase cache after every flash
Click to expand...
Click to collapse
use at least twrp 2.6.3.3. if you can't remember the name of the rom you are flashing then you don't know what you are doing and I can't help you.
at least with s-off you can restore your phone with any ruu.
alray said:
use at least twrp 2.6.3.3. if you can't remember the name of the rom you are flashing then you don't know what you are doing and I can't help you.
at least with s-off you can restore your phone with any ruu.
Click to expand...
Click to collapse
how do i restore with ruu i have tried but i get fail every time i tried to do it
Anemicnine40 said:
how do i restore with ruu i have tried but i get fail every time i tried to do it
Click to expand...
Click to collapse
which ruu have you tried? please don't say you can't remember....
alray said:
which ruu have you tried? please don't say you can't remember....
Click to expand...
Click to collapse
jmzstockattoneodex
jmzstockattonedeodex
cos-0,8_4,3-20130922-unofficial-m7ul.zip
HTC__Y13-2.17.401.2.7z
One_4.19.401.11_odexed.zip
Um, there is a difference between "RUU" and "ROM"
Do a quick Google search and when you are ready come back here and we can help some more..
Sent from my HTC One using xda app-developers app
NxNW said:
Um, there is a difference between "RUU" and "ROM"
Do a quick Google search and when you are ready come back here and we can help some more..
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
it isnt roms its ruu files
Yeah, still not sure we're communicating here.
If it didn't come from HTC, it's not a RUU.
Have a look at http://androidruu.com/?developer=M7
*Those* are RUU's.
You need to use the right one for your phone. (If your cidnum is unusual, such as HTC_Y13, there may not *be* an official RUU for your phone. See http://forum.xda-developers.com/showthread.php?t=2287505)
RUU's nuke all the data on your phone and fix all the partitions (recovery, HBOOT, radio, everything) on your phone, leaving it completely stock.
They need a Windows PC with HTC drivers to run.
What did *you* think RUU means?
Sent from my HTC One using xda app-developers app
alray said:
which ruu have you tried? please don't say you can't remember....
Click to expand...
Click to collapse
NxNW said:
Um, there is a difference between "RUU" and "ROM"
Do a quick Google search and when you are ready come back here and we can help some more..
Click to expand...
Click to collapse
Anemicnine40 said:
jmzstockattoneodex
jmzstockattonedeodex
cos-0,8_4,3-20130922-unofficial-m7ul.zip
HTC__Y13-2.17.401.2.7z
One_4.19.401.11_odexed.zip
Click to expand...
Click to collapse
Anemicnine40 said:
it isnt roms its ruu files
Click to expand...
Click to collapse
i think you should slow down and start reading a bit... maybe a lot.
you have (supposedly):
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
not trying to sound condescending, or anything, but if you think the ones you mentioned above are RUUs, then you should seriously do some more research.
some of those don't even look like M7 ROMs, and if you can find a real signed RUU which is deodexed... then WOW.
NxNW said:
Yeah, still not sure we're communicating here.
If it didn't come from HTC, it's not a RUU.
Have a look at http://androidruu.com/?developer=M7
*Those* are RUU's.
You need to use the right one for your phone. (If your cidnum is unusual, such as HTC_Y13, there may not *be* an official RUU for your phone. See http://forum.xda-developers.com/showthread.php?t=2287505)
RUU's nuke all the data on your phone and fix all the partitions (recovery, HBOOT, radio, everything) on your phone, leaving it completely stock.
They need a Windows PC with HTC drivers to run.
What did *you* think RUU means?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
sorry that im not so much in it i use google to find the things and that is what i got
Anemicnine40 said:
sorry that im not so much in it i use google to find the things and that is what i got
Click to expand...
Click to collapse
you can find m7 ruu on www.htc1guru.com or androidruu.com
you are s-off which mean you can flash both signed or decrypted ruu.
ruu.exe are flashed from windows OS. You plug your phone with usb cable and you launch the ruu.exe
ruu.zip can be flashed from any OS when your phone is in RUU mode (fastboot oem rebootRUU) using windows command prompt, linux terminal or mac terminal.
To flash a ruu it must be intended for your phone CID and MID
With S-ON (not your case) you also need a ruu that is signed and same or higher version of your phone. + bootloader must be locked/relocked
With S-OFF (your case) you can flash any ruu that match your CID/MID even if its a downgrade and bootloader can be locked/unlocked/relocked
Now the ruu you should use is this one: http://www.htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe/
This is the latest version for your phone and it match your MID (PN0710000) and your CID (HTC__Y13)
stays s-off and bootloader unlocked unless you send your phone for warranty repair.
so I'm trying to flash the new Venom 8.0.0 but to do that I gotta update the firmware but I can't see what firmware I have since fastboot getvar mainver gives the following results:
"mainver:
finished. total time: 0.000s"
Anyone know whats wrong?
Thanks.
Rogueaholic said:
so I'm trying to flash the new Venom 8.0.0 but to do that I gotta update the firmware but I can't see what firmware I have since fastboot getvar mainver gives the following results:
"mainver:
finished. total time: 0.000s"
Anyone know whats wrong?
Thanks.
Click to expand...
Click to collapse
its an issue with flashing a custom recovery, post your fastboot getvar all please without imei and serial number and we can probably tell you what you version main is.
Rogueaholic said:
so I'm trying to flash the new Venom 8.0.0 but to do that I gotta update the firmware but I can't see what firmware I have since fastboot getvar mainver gives the following results:
"mainver:
finished. total time: 0.000s"
Anyone know whats wrong?
Thanks.
Click to expand...
Click to collapse
yeah twrp had a bug that hides the mainver... I can tell you first hand if your on hboot 1.54 your software version is 2.x or 3.x at the highest
and the lollipop roms are not going to work until you update the firmware (7.x)
Flash an old Stock Rom like this >> https://www.androidfilehost.com/?w=files&flid=22071
and use Rumrunner to get s-off
clsA said:
yeah twrp had a bug that hides the mainver... I can tell you first hand if your on hboot 1.54 your software version is 2.x or 3.x at the highest
and the lollipop roms are not going to work until you update the firmware (7.x)
Flash an old Stock Rom like this >> https://www.androidfilehost.com/?w=files&flid=22071
and use Rumrunner to get s-off
Click to expand...
Click to collapse
(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: xxxxx
(bootloader) imei: xxxxx
(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: 3835mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
I have 4.4.3 venom rom atm if that changes anything
Rogueaholic said:
(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: xxxxx
(bootloader) imei: xxxxx
(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: 3835mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
I have 4.4.3 venom rom atm if that changes anything
Click to expand...
Click to collapse
your phone is already s-off, you can flash any RUU you like, then update to the latest, then flash a custom recovery and then flash Venom rom if thats what you want.
Seanie280672 said:
your phone is already s-off, you can flash any RUU you like.
Click to expand...
Click to collapse
Yeah I just got that one done but whenever I type
fastboot oem rebootRUU
and then fastboot flash zip 6.09.401.5-FULL_STOCK_WIPE.zip
it just says "<waiting for device>" waited for 30 minutes and nothing happened :s rebooted 5 times and tried same process every time.
Thanks for the quick responses!
EDIT: fastboot oem rebootRUU works but the fastboot flash zip doesn't.
Rogueaholic said:
Yeah I just got that one done but whenever I type
fastboot oem rebootRUU
and then fastboot flash zip 6.09.401.5-FULL_STOCK_WIPE.zip
it just says "<waiting for device>" waited for 30 minutes and nothing happened :s rebooted 5 times and tried same process every time.
Thanks for the quick responses!
EDIT: fastboot oem rebootRUU works but the fastboot flash zip doesn't.
Click to expand...
Click to collapse
when you get to RUU mode, check your computer see's the phone in device manager, waiting for device is a driver problem.
and just flash straight to 7.19.401.2, follow the instructions here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 download much further down the page, make sure you get the right one, 3rd one up from the bottom.
Seanie280672 said:
when you get to RUU mode, check your computer see's the phone in device manager, waiting for device is a driver problem.
and just flash straight to 7.19.401.2, follow the instructions here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 download much further down the page, make sure you get the right one, 3rd one up from the bottom.
Click to expand...
Click to collapse
Well around 10 minutes ago it randomly worked.. But you think if I flash 7.19.401.2 I could get the venom 8.0 ROM up and running?
Sorry for the stupid questions :d
EDIT: I'm retarded, sorry. Found the answer: yes
ViperOne 8.0.0 (March 8)
Re-based on 7.19.401.2
Thanks so much!
Rogueaholic said:
Well around 10 minutes ago it randomly worked.. But you think if I flash 7.19.401.2 I could get the venom 8.0 ROM up and running?
Sorry for the stupid questions :d
Click to expand...
Click to collapse
not stupid, better to ask, are you after stock rom at all or just want to get your firmware up to speed ?
if you dont want stock rom at all, then no point flashing that file, just flash the firmware for it from here: https://www.androidfilehost.com/?fid=95916177934534374
then flash twrp 2.8.5.0 recovery, copy viper to the internal storage and flash it.
Hey guys,
So a year ago I gave my girlfriend my old M7 because she still had an old Sony Ericsson and I thought it was time for an upgrade.
Now she's living with me and I wanted to update the M7 to (preferably) Lollipop as it's still suck on 4.4.4
The current ROM is cm-1120141008-SNAPSHOT and I think the phone has the super CID so I should be able to use every rom (iirc).
My question now is: How would I start to update this thing to Lollipop? Do I need to update the firmware or something? Because thats basically my problem.
Some tips or a guide on how I need to continue would be nice. Maybe some suggestions for new roms as well. Thanks in Advance!
EDIT: So I looked it up in bootloader and I have super CID and S-OFF. The hboot version is 1.57.0000. RADIO is 4T.29.3218.08
If you need any more info I'd be happy to post it.
kulturvortex said:
Hey guys,
So a year ago I gave my girlfriend my old M7 because she still had an old Sony Ericsson and I thought it was time for an upgrade.
Now she's living with me and I wanted to update the M7 to (preferably) Lollipop as it's still suck on 4.4.4
The current ROM is cm-1120141008-SNAPSHOT and I think the phone has the super CID so I should be able to use every rom (iirc).
My question now is: How would I start to update this thing to Lollipop? Do I need to update the firmware or something? Because thats basically my problem.
Some tips or a guide on how I need to continue would be nice. Maybe some suggestions for new roms as well. Thanks in Advance!
EDIT: So I looked it up in bootloader and I have super CID and S-OFF. The hboot version is 1.57.0000. RADIO is 4T.29.3218.08
If you need any more info I'd be happy to post it.
Click to expand...
Click to collapse
Can you post the output of "fastboot getvar all" (remove your imei and serialno)
You want the stock lollipop rom? HTC Sense? Google Play edition? Cyanogenmod?
alray said:
Can you post the output of "fastboot getvar all" (remove your imei and serialno)
You want the stock lollipop rom? HTC Sense? Google Play edition? Cyanogenmod?
Click to expand...
Click to collapse
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3971mV
(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
all: Done!
finished. total time: 0.063s
There you go, thanks for the quick reply!
Uhm for a ROM I'd like something thats good with battery life. She doesn't need much customizing. Jut something that works good and doesn't have any major bugs. I'm open to everything.
kulturvortex said:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3971mV
(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
all: Done!
finished. total time: 0.063s
There you go, thanks for the quick reply!
Uhm for a ROM I'd like something thats good with battery life. She doesn't need much customizing. Jut something that works good and doesn't have any major bugs. I'm open to everything.
Click to expand...
Click to collapse
If you want to avoid buggy rom I would stay away from Cyanogenmod as there is no stable build of CM12 yet for the M7 (only nightly builds).
Updating to stock lollipop + HTC sense or stock lollipop GPE version using a ruu might be the simplest solution. You could also update the firmware and flash a lollipop custom rom. Its up to you. I can help you in both cases.
alray said:
If you want to avoid buggy rom I would stay away from Cyanogenmod as there is no stable build of CM12 yet for the M7 (only nightly builds).
Updating to stock lollipop + HTC sense or stock lollipop GPE version using a ruu might be the simplest solution. You could also update the firmware and flash a lollipop custom rom. Its up to you. I can help you in both cases.
Click to expand...
Click to collapse
Well then Stock Lollipop GPE via RUU it is! Thanks for your help. Much appreciated. I always forget how to flash and root phones as soon as I switch to another model..
kulturvortex said:
Well then Stock Lollipop GPE via RUU it is! Thanks for your help. Much appreciated. I always forget how to flash and root phones as soon as I switch to another model..
Click to expand...
Click to collapse
Download the GPE ruu (5.11.1700.3) and save it in the same folder where adb.exe and fastboot.exe are installed on your computer
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944.
Change your MID number to PN0712000 using this tool or this guide
Then flash the GPE ruu:
Open the command window and type:
Code:
fastboot oem rebootRUU
Your phone will reboot in ruu mode, you should see a black screen with silver HTC logo.
Code:
fastboot flash zip PN07IMG_M7_UL_L50_STOCK_UI_MR_Google_WWE_5.11.1700.3_ ... .30.3218.21_10.33I.1718.01L_release_403339_signed.zip
fastboot flash zip PN07IMG_M7_UL_L50_STOCK_UI_MR_Google_WWE_5.11.1700.3_ ... .30.3218.21_10.33I.1718.01L_release_403339_signed.zip
fastboot reboot
Then check for ota update, you should have one or two iirc.
Flashing the ruu will wipe everything from the phone like if it was brand new so backup your important files before if any.
That seemed to have worked! Thank you so much. She's now setting it up. I'll comment or will send you a pm if I have any further questions or problems! Thanks again!
kulturvortex said:
That seemed to have worked! Thank you so much. She's now setting it up. I'll comment or will send you a pm if I have any further questions or problems! Thanks again!
Click to expand...
Click to collapse
No problem you're welcome :good:
HEY,
I own an HTC M7 I rooted my device but now the person that is gonna buy my phone want it unrooted. which is the best method to do it?
Thanks in advance
cdlt1290 said:
HEY,
I own an HTC M7 I rooted my device but now the person that is gonna buy my phone want it unrooted. which is the best method to do it?
Thanks in advance
Click to expand...
Click to collapse
RUU is the best method to return your phone to complete stock
donkeykong1 said:
RUU is the best method to return your phone to complete stock
Click to expand...
Click to collapse
can you recommend me one, I hace the HTC One M7 unlocked
cdlt1290 said:
can you recommend me one, I hace the HTC One M7 unlocked
Click to expand...
Click to collapse
Post your fastboot getvar all output, but erase your IMEI and serial number from it. That way we will be able to point you in the right direction
What a coincidence!
I'm about to "unroot" my old HTC M7 for my kid so he can play Pokemon Go on it.
It has TWRP 3.0.2-0 on it, and the fastboot getvar of it looks like this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4121mV
(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
Click to expand...
Click to collapse
I hope you do not mind helping me too.
htc-hd2 said:
What a coincidence!
I'm about to "unroot" my old HTC M7 for my kid so he can play Pokemon Go on it.
It has TWRP 3.0.2-0 on it, and the fastboot getvar of it looks like this:
I hope you do not mind helping me too.
Click to expand...
Click to collapse
I'm new at this, can you tell me please how did you get the fastboot getvar?
thanks but I figure it out, I´m trying to sell my device and the buyer needs it to play the same Pokemon Go that is why she want it unroot.
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.708.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4044mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1866a1a9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Thanks for you help
Hmmm rethinking this now.
Not sure if this "old" device will be able to play Pokémon Go when flashed to the original "old" ROM!
it needs Android 4.4+
htc-hd2 said:
Hmmm rethinking this now.
Not sure if this "old" device will be able to play Pokémon Go when flashed to the original "old" ROM!
it needs Android 4.4+
Click to expand...
Click to collapse
This old device received officiall Android Lollipop years ago, so you'll be fine with pokemon go. I'm gonna see if I have my old h-boot stored for you when I come home from work. I think you can go directly to the last one because your phone is s-off, but I'm not sure about that because your h-boot is very old. If you can hold on for about 12 hours, I'll point you to the right direction then
donkeykong1 said:
This old device received officiall Android Lollipop years ago, so you'll be fine with pokemon go. I'm gonna see if I have my old h-boot stored for you when I come home from work. I think you can go directly to the last one because your phone is s-off, but I'm not sure about that because your h-boot is very old. If you can hold on for about 12 hours, I'll point you to the right direction then
Click to expand...
Click to collapse
what about me you think you can help me? I think I have S-On
htc-hd2 said:
Hmmm rethinking this now.
Not sure if this "old" device will be able to play Pokémon Go when flashed to the original "old" ROM!
it needs Android 4.4+
Click to expand...
Click to collapse
donkeykong1 said:
This old device received officiall Android Lollipop years ago, so you'll be fine with pokemon go. I'm gonna see if I have my old h-boot stored for you when I come home from work. I think you can go directly to the last one because your phone is s-off, but I'm not sure about that because your h-boot is very old. If you can hold on for about 12 hours, I'll point you to the right direction then
Click to expand...
Click to collapse
Should update his firmware to 7.19.401.2 using the full firmware zip and than he can flash the 7.19.401.51 RUU.
cdlt1290 said:
what about me you think you can help me? I think I have S-On
Click to expand...
Click to collapse
Downgrade your version-main # to 7.18.708.2 using the guide at the end of this post (how to downgrade with s-on). Once done flash the 7.18.708.21 RUU using instruction of this post. Finally you'll have to take 2 ota update so you're back on 7.18.708.51 (if you need to unlock/root again make sure to install update before)
alray said:
Should update his firmware to 7.19.401.2 using the full firmware zip and than he can flash the 7.19.401.51 RUU.
Downgrade your version-main # to 7.18.708.2 using the guide at the end of this post (how to downgrade with s-on). Once done flash the 7.18.708.21 RUU using instruction of this post. Finally you'll have to take 2 ota update so you're back on 7.18.708.51 (if you need to unlock/root again make sure to install update before)
Click to expand...
Click to collapse
Hi thanks for the help, I did everything you said but in the last step when i was trying to flash the RUU, but the first command was
6.fastboot oem rebootRUU and then the device restart i supposed and a black screen with HTC logo appear and didn´t let me put the second command that is 7.fastboot flash zip RUU.zip
what did I did wrong? hope you can help me
cdlt1290 said:
Hi thanks for the help, I did everything you said but in the last step when i was trying to flash the RUU, but the first command was
6.fastboot oem rebootRUU and then the device restart i supposed and a black screen with HTC logo appear and didn�´t let me put the second command that is 7.fastboot flash zip RUU.zip
what did I did wrong? hope you can help me
Click to expand...
Click to collapse
fastboot oem rebootRUU will make your phoned reboot in ruu mode (that black screen with silver htc logo). Once in ruu mode, it's time to flash the ruu using "fastboot flashing zip ruu.zip". During the flashings process you should get an error saying "flush image again immediately", the phone will reboot itself in ruu mode again and the flashing will continue,it's all normal.
Sent from my HTC One using XDA Labs
alray said:
fastboot oem rebootRUU will make your phoned reboot in ruu mode (that black screen with silver htc logo). Once in ruu mode, it's time to flash the ruu using "fastboot flashing zip ruu.zip". During the flashings process you should get an error saying "flush image again immediately", the phone will reboot itself in ruu mode again and the flashing will continue,it's all normal.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
thank I did it! i wasn't using htc_fastboot that was the problem! thanks very much for your help, last question how do I check it`s unrooted?
Thank you all for the help / info.
I'm away for the weekend so I'm not able to "flash" anything till Monday.
For now have a nice weekend.
cdlt1290 said:
thank I did it! i wasn't using htc_fastboot that was the problem! thanks very much for your help, last question how do I check it`s unrooted?
Click to expand...
Click to collapse
If the ruu flashed fine, it's not rooted anymore. Root files are stored on the /system partition which is wiped and flashed back to stock with the ruu.
Sent from my HTC One using XDA Labs
I'm about to flash the phone.
Can this all be done with TWRP, or do I need to go the ADB way?
htc-hd2 said:
I'm about to flash the phone.
Can this all be done with TWRP, or do I need to go the ADB way?
Click to expand...
Click to collapse
Flashing firmware or RUU is done using fastboot commands in RUU mode, not with twrp, neither with adb.
Okay.
I've updated the firmware to 7.19.401.2
Fastboot getvar of it looks like this:
(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.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA354W903711
(bootloader) imei: 354436051520417
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4299mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I've 7.19.401.51 RUU (PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip) ready to be flashed.
Now I've had a look at some howto's, but I'm still lost on what to do next!
I feel such an idiot :/
htc-hd2 said:
Okay.
I've updated the firmware to 7.19.401.2
Fastboot getvar of it looks like this:
I've 7.19.401.51 RUU (PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip) ready to be flashed.
Now I've had a look at some howto's, but I'm still lost on what to do next!
I feel such an idiot :/
Click to expand...
Click to collapse
Now flashing the ruu using htc_fastboot.exe
Look at the stickies in the general section to find the lollipop ruu collection thread. Instructions how to flash are provided at post #1.
Sent from my HTC One using XDA Labs