Related
Hi, i seem to have gotten a problem with my phone jumping to car mode randomly, even when its plugged in, so guess it is in need of a service.
After reading some guides about going back to stuff, i just have to get confirmation that i have understood it correctly.
The only process i need to do is the following (I have s-off and hboot 1.44, latest firmware):?
1. Change the SID back to stock
2. Run the RUU.exe
3. Make it s-off again and remove tampered with revone?
Is that all or am i forgetting something crucial?
raysv said:
Hi, i seem to have gotten a problem with my phone jumping to car mode randomly, even when its plugged in, so guess it is in need of a service.
After reading some guides about going back to stuff, i just have to get confirmation that i have understood it correctly.
The only process i need to do is the following (I have s-off and hboot 1.44, latest firmware):?
1. Change the SID back to stock
2. Run the RUU.exe
3. Make it s-off again and remove tampered with revone?
Is that all or am i forgetting something crucial?
Click to expand...
Click to collapse
1- change CID back to stock
2- remove TAMPERED using either revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU.
nkk71 said:
1- change CID back to stock
2- remove TAMPERED using either revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU.
Click to expand...
Click to collapse
Thanks for the reply.
Did all the things, but it refuses to flash the ruu.. when running the ruu.exe its returning error 155 after awhile Any idea of what might be wrong?
are you using the right CID for the RUU?
stovie_steve said:
are you using the right CID for the RUU?
Click to expand...
Click to collapse
Yes I changed my CID back to the original CID, and the RUU i downloaded said on the download page that this was for this CID HTC__Y13.
My bootloader also says LOCKED
raysv said:
Yes I changed my CID back to the original CID, and the RUU i downloaded said on the download page that this was for this CID HTC__Y13.
My bootloader also says LOCKED
Click to expand...
Click to collapse
Did u also check MID?
I thought 155 was because of an unlocked bootloader, does it give any information more than 155? Maybe also try to find the log (should be somewhere in temp on ur pc)
I'll be online later today, and will check back.
Sent from my HTC One using Tapatalk
I also had that error before when I was on a later hboot (1.54 and 1.55) and would only work if I had hboot 1.44
Can you post your fastboot getvar all removing S/N and IMEI?
stovie_steve said:
I also had that error before when I was on a later hboot (1.54 and 1.55) and would only work if I had hboot 1.44
Can you post your fastboot getvar all removing S/N and IMEI?
Click to expand...
Click to collapse
Here is my getvar:
C:\Android>fastboot getvar all
(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.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(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: 4273mV
(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!
finished. total time: 0.072s
Have tried downgrading the firmware also by "unlocking" the bootloader again as described in the post over (not the revone way but the other). and try and flash the hboot 1.44.. but now it seems that I'm just getting remote denied when trying to flash.. Dosn't that indicate that the bootloader is still locked?
Have managed to downgrade the hboot and firmware... Will try the ruu again and see if it works if i can get it to stay connected to the computer via USB... Right now it just plings for 2 sekunds, and then loosing the connection again..
Thanks alot guys for the help.
Seems like it was my hboot messing up, once i downgraded the firmaware and zip before trying the ruu it seems to work Atleast no 155 error or problems arised so faar, just the green progress bar *keeps his fingers crossed*
Again, great help Now its time to ship it to service
BTW: anyone know if they are actually able to fix the usb plug since its unibody design? Or will it most likly be a replacement?
Hi guys,
I'm in need of some help, my beloved HTC One has fallen victim to the dreaded Purple Camera issue and I need to send it back.
I'm on HBOOT 1.56 and I need to turn S-ON back on as my phone says that my phone is a "Test Device" in bold red writing if you reset the phone and under About>Help
I don't want any warranty issues with HTC as being in South Africa, support is very limited as it is and they will find any excuse not to try fix it.
If anyone can give out any tips or advice I'd be happy to donate even.
I've done lots of Googling and tried a couple things but it's all for older HBOOT's than mine.
Please and thanks guys. :good:
Terros said:
Hi guys,
I'm in need of some help, my beloved HTC One has fallen victim to the dreaded Purple Camera issue and I need to send it back.
I'm on HBOOT 1.56 and I need to turn S-ON back on as my phone says that my phone is a "Test Device" in bold red writing if you reset the phone and under About>Help
I don't want any warranty issues with HTC as being in South Africa, support is very limited as it is and they will find any excuse not to try fix it.
If anyone can give out any tips or advice I'd be happy to donate even.
I've done lots of Googling and tried a couple things but it's all for older HBOOT's than mine.
Please and thanks guys. :good:
Click to expand...
Click to collapse
First, post the output of ''fastboot getvar all'' (except imei and serialno)
Do NOT S-ON for the moment.
alray said:
First, post the output of ''fastboot getvar all'' (except imei and serialno)
Do NOT S-ON for the moment.
Click to expand...
Click to collapse
Thanks for the speedy response!
This is the getvar info:
D:\htcone\fastboot>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.9
(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: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(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.065s
Terros said:
Thanks for the speedy response!
This is the getvar info:
D:\htcone\fastboot>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.9
(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: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(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.065s
Click to expand...
Click to collapse
ok so you'll need to downgrade your phone first because turning back s-on on hboot 1.56 will trigger the tampered flag in the bootloader.
use the 1.28.401.7 ruu with the guru bootloader reset tool
refer to this guide and follow instructions carefully. Again, do not s-on on hboot 1.55 and above, only do it on 1.44 or 1.54.
alray said:
First, post the output of ''fastboot getvar all'' (except imei and serialno)
Do NOT S-ON for the moment.
Click to expand...
Click to collapse
alray said:
ok so you'll need to downgrade your phone first because turning back s-on on hboot 1.56 will trigger the tampered flag in the bootloader.
use the 1.28.401.7 ruu with the guru bootloader reset tool
refer to this guide and follow instructions carefully. Again, do not s-on on hboot 1.55 and above, only do it on 1.44 or 1.54.
Click to expand...
Click to collapse
Awesome! I just downgraded to 1.44,
Can I go ahead now and use fastboot oem writesecureflag 3 to S-ON the device?
Just wanting to make 100% sure.
Terros said:
Awesome! I just downgraded to 1.44,
Can I go ahead now and use fastboot oem writesecureflag 3 to S-ON the device?
Just wanting to make 100% sure.
Click to expand...
Click to collapse
have you removed tampered and set the phone to locked, and flashed the 1.28.401.7 ruu?
nkk71 said:
have you removed tampered and set the phone to locked, and flashed the 1.28.401.7 ruu?
Click to expand...
Click to collapse
My phone still says Locked, I flashed the 1.28.401.12_hboot_1.44.zip
I haven't actually done the 1.28.401.7 RUU, Is that what I do after I flashed the 1.44 hboot?
My phone is on 4.4.2.
Terros said:
My phone still says Locked, I flashed the 1.28.401.12_hboot_1.44.zip
I haven't actually done the 1.28.401.7 RUU, Is that what I do after I flashed the 1.44 hboot?
My phone is on 4.4.2.
Click to expand...
Click to collapse
DO NOT GO S-ON
first run the RUU.EXE or the flash the RUU.ZIP
then we can consider s-on, with S-On you cannot downgrade!!! and you'll be majorly stuck.
let me know when you've done the ruu
PS: please follow the guide
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
.
nkk71 said:
DO NOT GO S-ON
first run the RUU.EXE or the flash the RUU.ZIP
then we can consider s-on, with S-On you cannot downgrade!!! and you'll be majorly stuck.
let me know when you've done the ruu
PS: please follow the guide
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
.
Click to expand...
Click to collapse
Ok thanks.
Is this the correct RUU > RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed?
Terros said:
Ok thanks.
Is this the correct RUU > RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed?
Click to expand...
Click to collapse
yes,
this one for RUU.EXE method: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
or this one for RUU.ZIP method: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
remember to check MD5 on the download, to make sure it's not corrupt
.
nkk71 said:
yes,
this one for RUU.EXE method: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
or this one for RUU.ZIP method: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
remember to check MD5 on the download, to make sure it's not corrupt
.
Click to expand...
Click to collapse
It's now updated to the RUU you listed.
What's next?
Terros said:
It's now updated to the RUU you listed.
What's next?
Click to expand...
Click to collapse
As mentioned:
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
so if your bootloader is now:
* untampered,
* LOCKED,
* and the ruu has been successfully installed.
you can go ahead and S-On your device.
.
nkk71 said:
As mentioned:
1- remove tampered set locked
2- run / flash ruu 1.28.401.7
3- boot up once to make sure everything is OK, do NOT take OTA
4- go S-ON if you really need to
so if your bootloader is now:
* untampered,
* LOCKED,
* and the ruu has been successfully installed.
you can go ahead and S-On your device.
.
Click to expand...
Click to collapse
All still LOCKED and installed RUU. So now S-OFF with the writebootflag 3 or what ever correct.
Terros said:
All still LOCKED and installed RUU. So now S-OFF with the writebootflag 3 or what ever correct.
Click to expand...
Click to collapse
You mean S-On, right.
to go s-on: fastboot oem writesecureflag 3
Hey, Im s-off on bell mobility in canada. Hboot 1.57. Was wondering what my best way to change over to a developers edition would be>
Howie3045 said:
Hey, Im s-off on bell mobility in canada. Hboot 1.57. Was wondering what my best way to change over to a developers edition would be>
Click to expand...
Click to collapse
I changed my India Rom to US dev edition Rom
1 S Off
2 Install TWRP
3 use Aroma MID changer tool change MID to PN0712000
4 change CID BS_US001
5 now flash any US dev edition firmware
6 Flash RUU of US dev edition
yatindroid said:
I changed my India Rom to US dev edition Rom
1 S Off
2 Install TWRP
3 use Aroma MID changer tool change MID to PN0712000
4 change CID BS_US001
5 now flash any US dev edition firmware
6 Flash RUU of US dev edition
Click to expand...
Click to collapse
which firmware should i install if i am using this ruu.exe http://www.htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_brightstarus_wwe_4-19-1540-9_radio_4a-23-3263-28_10-38r-1157-04l_release_353887_signed_3-exe/
my htc one isnt a dual sim. its the bell mobility one
Howie3045 said:
which firmware should i install if i am using this ruu.exe http://www.htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_brightstarus_wwe_4-19-1540-9_radio_4a-23-3263-28_10-38r-1157-04l_release_353887_signed_3-exe/
my htc one isnt a dual sim. its the bell mobility one
Click to expand...
Click to collapse
if you flash the 3.22.1540.1 decrypted ruu from htcguru.com, you dont need to flash the firmware, just follow yatin's instructions. firmware is included in the ruu.
alray said:
if you flash the 3.22.1540.1 decrypted ruu from htcguru.com, you dont need to flash the firmware, just follow yatin's instructions. firmware is included in the ruu.
Click to expand...
Click to collapse
where would i find these instructions. would love some sort of guide so i dont mess this up lol.
Howie3045 said:
where would i find these instructions. would love some sort of guide so i dont mess this up lol.
Click to expand...
Click to collapse
yatin and me can assist you in this thread.
first post the output of "fastboot getvar all" so we can determine what steps are required for you to do the conversion. dont post your IMEI nor the SERIALNO strings of your getvar
alray said:
yatin and me can assist you in this thread.
first post the output of "fastboot getvar all" so we can determine what steps are required for you to do the conversion. dont post your IMEI nor the SERIALNO strings of your getvar
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.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: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4152mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Howie3045 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.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: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4152mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
1st change cid to BS_US001
Flashing Firmware 3.22.1540.1
fastboot oem rebootRUU
fastboot flash zip firmware.zip (2 times)
fastboot flash zip firmware.zip
fastboot reboot-bootloader
after that Run RUU 4.19.1540.9 then update OTA
Howie3045 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.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: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4152mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
ok in your case, this will be very easy :good:
first backup every important file (if any) from your phone to your computer, everything will be wiped, including your sdcard content (picture, song, video)
reboot phone in bootloader mode by holding power and volume down
when in bootloader, open a terminal window from your fastboot/adb folder and type:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
then download this ruu and save it to your adb/fastboot folder. you can rename it ruu (ruu.zip), it will be easier in the terminal.
with phone still on bootloader mode, from the terminal window type:
Code:
fastboot oem rebootRUU
make sure "RUU" in rebootRUU are capital letters. you will now see a black screen with silver htc logo
type:
Code:
fastboot flash zip ruu.zip
it will say something like: "failed, flush image again immediately" so do the same command again:
Code:
fastboot flash zip ruu.zip
then
Code:
fastboot reboot
now your phone will boot normally (first boot can take longer than usual).
when phone is booted, go trough the setup process and then go in settings ---> phone ---> software update.
download and install each ota update from 3.22.1540.1 to 6.07.1540.1 (6 updates total)
or you can proceed like @yatindroid said, 2 differents ways for the same result. both method will works.
alray said:
ok in your case, this will be very easy :good:
first backup every important file (if any) from your phone to your computer, everything will be wiped, including your sdcard content (picture, song, video)
reboot phone in bootloader mode by holding power and volume down
when in bootloader, open a terminal window from your fastboot/adb folder and type:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
then download this ruu and save it to your adb/fastboot folder. you can rename it ruu (ruu.zip), it will be easier in the terminal.
with phone still on bootloader mode, from the terminal window type:
Code:
fastboot oem rebootRUU
make sure "RUU" in rebootRUU are capital letters. you will now see a black screen with silver htc logo
type:
Code:
fastboot flash zip ruu.zip
it will say something like: "failed, flush image again immediately" so do the same command again:
Code:
fastboot flash zip ruu.zip
then
Code:
fastboot reboot
now your phone will boot normally (first boot can take longer than usual).
when phone is booted, go trough the setup process and then go in settings ---> phone ---> software update.
download and install each ota update from 3.22.1540.1 to 6.07.1540.1 (6 updates total)
or you can proceed like @yatindroid said, 2 differents ways for the same result. both method will works.
Click to expand...
Click to collapse
with your method i dont have to flash firmware first? just change the CID and flash the RUU? I noticed my MID is the same as the Developer Edition anyway.
i wanna say thanks. sure i can click a button but i want you guys to know you've been very help and i appreciate it. ive been pulling my hair out with this phone every since i rooted it. I think after i do this ill be back to where i want to be. Id love to be Bell stock again but i find bell stuff hard too find. Developers Edition shud suit me just fine
Howie3045 said:
with your method i dont have to flash firmware first? just change the CID and flash the RUU? I noticed my MID is the same as the Developer Edition anyway.
Click to expand...
Click to collapse
yes you can try this way but if RUU give error try you need flash firmware
yatindroid said:
yes you can try this way but if RUU give error try you need flash firmware
Click to expand...
Click to collapse
where can i grab that firmware just in case
Howie3045 said:
with your method i dont have to flash firmware first? just change the CID and flash the RUU? I noticed my MID is the same as the Developer Edition anyway.
Click to expand...
Click to collapse
exactly.
MID is already correct
just change mid to BS_US001
and flash the 3.22.1540.1 ruu.
advantage of my method is that its simpler
disadvantage is that its an old version and you'll have to download and install 6 ota updates.
advantage of yatin's method is that its a less old version and will only require 2 ota updates
disadvantage (not really big disadvantage) is to flash the firmware first, if not the ruu.exe will not flash. Personally i don't use 4.xx.xxx.x RUU because I never found any clue that they are official ruu released by HTC (not on their website). But it seem to works fine, I think yatin converted his phone using that ruu
both solution are good, just make sure you flash the right firmware if you go with the 4.xx.1540 ruu
alray said:
exactly.
MID is already correct
just change mid to BS_US001
and flash the 3.22.1540.1 ruu.
advantage of my method is that its simpler
disadvantage is that its an old version and you'll have to download and install 6 ota updates.
advantage of yatin's method is that its a less old version and will only require 2 ota updates
disadvantage (not really big disadvantage) is to flash the firmware first, if not the ruu.exe will not flash. Personally i don't use 4.xx.xxx.x RUU because I never found any clue that they are official ruu released by HTC (not on their website). But it seem to works fine, I think yatin converted his phone using that ruu
both solution are good, just make sure you flash the right firmware if you go with the 4.xx.1540 ruu
Click to expand...
Click to collapse
bootloader will stay unlocked correct? i like simple lol. im downloading the RUU for your method now. I already have all my pictures backed up on a flash drive. ill have to back up a cpl other small things but ill prob give this a try tonight.
Howie3045 said:
bootloader will stay unlocked correct? i like simple lol. im downloading the RUU for your method now. I already have all my pictures backed up on a flash drive. ill have to back up a cpl other small things but ill prob give this a try tonight.
Click to expand...
Click to collapse
yes bootloader will stay unlocked and no need to relock it since dev edition phone came with an unlock bootloader from factory.
alray said:
yes bootloader will stay unlocked and no need to relock it since dev edition phone came with an unlock bootloader from factory.
Click to expand...
Click to collapse
I ran the RUU this morning. phone booted up fine. downloading first update as i type this. awesome. thank you guys so much
and updates are installing....very happy right now.
question though, once i get fully update to date with the dev edition, can i install TWRP and when any new updates come just install the stock recovery? i like using HTC One Tweaker and Sense 6 toolbox.
Howie3045 said:
and updates are installing....very happy right now.
question though, once i get fully update to date with the dev edition, can i install TWRP and when any new updates come just install the stock recovery? i like using HTC One Tweaker and Sense 6 toolbox.
Click to expand...
Click to collapse
if your bootloader is already unlocked, yes you can flash a custom recovery and then revert back to the stock 6.07.1540.1 recovery and install ota.
if your bootloarder is locked, you'll need to unlock it in order to flash a custom recovery and that will wipe /data/preload files and you'll will not be able to install ota directly.
to install ota, you need:
stock recovery
untouched /data/preload files
untouched /system files
Best thing to do is to make a nandroid backup right after flashing twrp. So if some /system files get modified (with a custom kernel for example) you'll be able to restore the backup, flash the stock recovery and install ota.
in last resort you can always flash your phone back to stock with a ruu and apply all ota.
alray said:
if your bootloader is already unlocked, yes you can flash a custom recovery and then revert back to the stock 6.07.1540.1 recovery and install ota.
if your bootloarder is locked, you'll need to unlock it in order to flash a custom recovery and that will wipe /data/preload files and you'll will not be able to install ota directly.
to install ota, you need:
stock recovery
untouched /data/preload files
untouched /system files
Best thing to do is to make a nandroid backup right after flashing twrp. So if some /system files get modified (with a custom kernel for example) you'll be able to restore the backup, flash the stock recovery and install ota.
in last resort you can always flash your phone back to stock with a ruu and apply all ota.
Click to expand...
Click to collapse
im back up and running with all updates. i just ran the RUU u suggested so i assume my bootloader should still be unlocked. i didnt relock it or anything
Hi everyone, I apologies if this is a bit of a silly question however I am attempting to root an android device for the first time and would just like to know what you thought about an issue which I am having.
My question is, I plan to root my phone and install TWRP recovery, if I ever needed to unroot I am under the impression I would need an RUU which matches the radio very I have. The details of the radio is 4T.29.3218.08 and the phone is from the UK (Europe). I cannot find this version anywhere. If I ever needed to unroot does this mean I would not be able to?
This is the only thing which is now stopping me from rooting my phone... Thank you in advance for your replies.
ashyk36 said:
Hi everyone, I apologies if this is a bit of a silly question however I am attempting to root an android device for the first time and would just like to know what you thought about an issue which I am having.
My question is, I plan to root my phone and install TWRP recovery, if I ever needed to unroot I am under the impression I would need an RUU which matches the radio very I have. The details of the radio is 4T.29.3218.08 and the phone is from the UK (Europe). I cannot find this version anywhere. If I ever needed to unroot does this mean I would not be able to?
This is the only thing which is now stopping me from rooting my phone... Thank you in advance for your replies.
Click to expand...
Click to collapse
post the output of "fastboot getvar all" except your imei and serialno. Radio version doesn't help much when trying to find a RUU
alray said:
post the output of "fastboot getvar all" except your imei and serialno. Radio version doesn't help much when trying to find a RUU
Click to expand...
Click to collapse
Hi, the details are as follows:
(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.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -----------------------
(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: 4095mV
(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
all: Done!
finished. total time: 0.046s
ashyk36 said:
Hi, the details are as follows:
(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.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -----------------------
(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: 4095mV
(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
all: Done!
finished. total time: 0.046s
Click to expand...
Click to collapse
your on the newest software their is no 6.x.401 RUU
to return to stock you simply flash the stock odex rom and stock recovery / do a factory reset and your Stock
you would still have an unlocked bootloader but without s-off you can't fix that (unlocked to locked)
clsA said:
your on the newest software their is no 6.x.401 RUU
to return to stock you simply flash the stock odex rom and stock recovery / do a factory reset and your Stock
you would still have an unlocked bootloader but without s-off you can't fix that (unlocked to locked)
Click to expand...
Click to collapse
So a couple of questions. Does that mean there is never going to be an RUU for my phone or is it just with time there will be more for the current version? As for flashing to the odex Rom and stock recovery, the Rom would be simple enough for TWRP recovery, how would i do the stock recovery part? Or would they be an all in one installation, installing the Rom would also install the recovery?
Thank you for your help
ashyk36 said:
So a couple of questions. Does that mean there is never going to be an RUU for my phone or is it just with time there will be more for the current version?
Click to expand...
Click to collapse
HTC doesn't release RUU each time there is a new version. Maybe with the future release of android lollipop, we don't know.
As for flashing to the odex Rom and stock recovery, the Rom would be simple enough for TWRP recovery, how would i do the stock recovery part?
Click to expand...
Click to collapse
flash the stock rom using twrp and then flash the stock recovery the same way you have flashed twrp recovery. Twrp will be overwritten by the stock recovery.
Just keep in mind that you'll need s-off if you want your warranty back (to set the bootloader back to *locked* (not relocked) and to remove the *tampered* flag)
alray said:
HTC doesn't release RUU each time there is a new version. Maybe with the future release of android lollipop, we don't know.
flash the stock rom using twrp and then flash the stock recovery the same way you have flashed twrp recovery. Twrp will be overwritten by the stock recovery.
Just keep in mind that you'll need s-off if you want your warranty back (to set the bootloader back to *locked* (not relocked) and to remove the *tampered* flag)
Click to expand...
Click to collapse
Hi thank you for your help. Just want to clarify, where would i get these stock files from and will ineed specific versions for my phone?
Were these the correct files?
http://forum.xda-developers.com/showthread.php?t=2224752
@alray if i was to keep a backup of my stock rom before i installed a custom rom, could i then restore the backup of the stock rom and then restore the stock recovery?
Where can i get the stock recovery from? Once i find it is possible i can then root
ashyk36 said:
Were these the correct files?
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
no, you are on 6.09.401.10, these files are for 6.09.401.5.
---------- Post added at 04:48 PM ---------- Previous post was at 04:45 PM ----------
ashyk36 said:
@alray if i was to keep a backup of my stock rom before i installed a custom rom, could i then restore the backup of the stock rom and then restore the stock recovery?
Click to expand...
Click to collapse
Yes but if you make a backup of your rom after unlocking the bootloader, there will be some files missing (htc preloaded apps in /data/preload) which will prevent you to use ota updates is you restore this backup. There is a 6.09.401.10 nandroid backup including the /data/preload folder on android file host.
https://www.androidfilehost.com/?fid=95832962473396068
Where can i get the stock recovery from? Once i find it is possible i can then root
Click to expand...
Click to collapse
You can extract it from any 6.09.401.10 firmware or from the 6.09.401.5 to 6.09.401.10 ota zip file.
nvm, I found it here: https://www.androidfilehost.com/?fid=95784891001603803
@alray - So my steps to stock would be:
Download and install the rom using TWRP recoveryfrom the following address:
https://www.androidfilehost.com/?fid=95832962473396068
Then install the stock recovery from the following link (Install is the same way I installed TWRP):
https://www.androidfilehost.com/?fid=95784891001603803
If the phone is still S-ON, I will not be able to change the label so will have to make it S-OFF if I need to change - just out of curiosity, if I leave the phone S-ON will this affect OTA updates?
Then factory reset the phone - I should be back to a stock phone.
Would these steps be correct?
ashyk36 said:
@alray - So my steps to stock would be:
Download and install restore (its a backup, you restore it using the restore menu in twrp, do not install like a rom) the rom using TWRP recoveryfrom the following address:
https://www.androidfilehost.com/?fid=95832962473396068
Then install the stock recovery from the following link (Install is the same way I installed TWRP):
https://www.androidfilehost.com/?fid=95784891001603803
yes:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
If the phone is still S-ON, I will not be able to change the label so will have to make it S-OFF if I need to change Exactly - just out of curiosity, if I leave the phone S-ON will this affect OTA updates? No, if you rom is 100% stock (which will be the case after restoring the above backup) and you have stock recovery, youre good for ota update. S-ON/S-OFF doesn't affect ota updates.
Then factory reset the phone - I should be back to a stock phone.
Would these steps be correct?
Click to expand...
Click to collapse
see text in red above
@alray
Thank you so much for your help. I Will go ahead and root my phone.
How to S-Off
alray said:
see text in red above
Click to expand...
Click to collapse
My phone has hit the purple tint issue which is a well known fault. I have spoken to HTC and they have said that they will fix under warranty. I need to return the phone back to stock. I know I can use the nandroid backup and the recovery in the post above but I am very confused on how to S-off.
My problem is there are so many guides (some of them being very old) on how to do this and I do not know which method to use. Could someone please point me in the right direction so I can return my phone back to stock.
Thank you so much
I have seen
http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
Would this be ok? I used an article on the same website to root
ashyk36 said:
My phone has hit the purple tint issue which is a well known fault. I have spoken to HTC and they have said that they will fix under warranty. I need to return the phone back to stock. I know I can use the nandroid backup and the recovery in the post above but I am very confused on how to S-off.
My problem is there are so many guides (some of them being very old) on how to do this and I do not know which method to use. Could someone please point me in the right direction so I can return my phone back to stock.
Thank you so much
I have seen
http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
Would this be ok? I used an article on the same website to root
Click to expand...
Click to collapse
I would highly recommend to follow nkk71's super guide (linked in my signature). Everything is well explained in details, just make sure to read everything before beginning and also read the FAQ of his guide.
To achieve s-off, you will need to use Sunshine if your hboot is 1.57 or above. Sunshine cost 25$ USD. Its the only method to achieve s-off on hboot 1.54 and above.
S-OFF is a must to remove the tampered banner and set back the bootloader to ***LOCKED*** (not ***RE-LOCKED***) so your warranty is still valid, but again everything explained in that guide. If you have any question you can ask here or in nkk71's guide. If you have questions, post an updated "fastboot getvar all" at the same time.
alray said:
I would highly recommend to follow nkk71's super guide (linked in my signature). Everything is well explained in details, just make sure to read everything before beginning and also read the FAQ of his guide.
To achieve s-off, you will need to use Sunshine if your hboot is 1.57 or above. Sunshine cost 25$ USD. Its the only method to achieve s-off on hboot 1.54 and above.
S-OFF is a must to remove the tampered banner and set back the bootloader to ***LOCKED*** (not ***RE-LOCKED***) so your warranty is still valid, but again everything explained in that guide. If you have any question you can ask here or in nkk71's guide. If you have questions, post an updated "fastboot getvar all" at the same time.
Click to expand...
Click to collapse
I believe my phone has Hboot version 1.57. Is there no way I can downgrade or is sunshine the only way to return to stock? The details of the getvar all are:
C:\HTCOneRoot>fastboot getvar all
(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.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(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: 3981mV
(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
all: Done!
alray said:
I would highly recommend to follow nkk71's super guide (linked in my signature). Everything is well explained in details, just make sure to read everything before beginning and also read the FAQ of his guide.
To achieve s-off, you will need to use Sunshine if your hboot is 1.57 or above. Sunshine cost 25$ USD. Its the only method to achieve s-off on hboot 1.54 and above.
S-OFF is a must to remove the tampered banner and set back the bootloader to ***LOCKED*** (not ***RE-LOCKED***) so your warranty is still valid, but again everything explained in that guide. If you have any question you can ask here or in nkk71's guide. If you have questions, post an updated "fastboot getvar all" at the same time.
Click to expand...
Click to collapse
The guide is really good, just one thing has thrown me though, Im not too sure which RUU to use.
I can see RUU for:
CID HTC__001
and MID PN0710000
but not baseband 4T.29.3218.08
Do I just use the files you linked me to in the posts above?
ashyk36 said:
Is there no way I can downgrade or is sunshine the only way to return to stock?
Click to expand...
Click to collapse
Downgrading requires s-off, s-off can only be achieved using Sunshine when hboot is 1.57 or newer
ashyk36 said:
The guide is really good, just one thing has thrown me though, Im not too sure which RUU to use.
I can see RUU for:
CID HTC__001
and MID PN0710000
but not baseband 4T.29.3218.08
Do I just use the files you linked me to in the posts above?
Click to expand...
Click to collapse
1.28.401.7 RUU zip
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
Baseband version is irrelevant when looking for RUUs. You want a ruu that match your CID, MID and firmware base (.401). Also you need the ruu to be hboot 1.44 (1.xx.xxx.x) so you can safely remove the tampered banner. So in our case you must use the 1.28.401.7 ruu.zip.
alray said:
Downgrading requires s-off, s-off can only be achieved using Sunshine when hboot is 1.57 or newer
1.28.401.7 RUU zip
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
Baseband version is irrelevant when looking for RUUs. You want a ruu that match your CID, MID and firmware base (.401). Also you need the ruu to be hboot 1.44 (1.xx.xxx.x) so you can safely remove the tampered banner. So in our case you must use the 1.28.401.7 ruu.zip.
Click to expand...
Click to collapse
Just so I know for the future, I know my firmware base is .401 based on the following line:
(bootloader) version-main: 6.09.401.10
Is this right? Thank you for your help!
ashyk36 said:
Just so I know for the future, I know my firmware base is .401 based on the following line:
(bootloader) version-main: 6.09.401.10
Is this right? Thank you for your help!
Click to expand...
Click to collapse
Right and also because your CID and MID are HTC__001 and PN0710000 so the corresponding software/firmware base is x.xx.401.x
Hi
I have Unlocked Bootloader, S-Off and SuperCID, installed GPE ROM via RUU.zip
Now I need to install ROM via RUU. exe but I don't see superCID on supported CID list.
Will stock GPE ROM boot with CID HTC__032?
Or... Can I flash this RUU on superCID?
This RUU is here:
http://bit.ly/1EPvdwI
Super CID will help you or better have same CID as gpe have
Because ruu checks CID & MID and can give errors
ok. I changed it to HTC__032 and RUU force closes during gathering device information on Windows 7.
On Windows 8 fastboot crashes :/
all systems are 64-bit
But... If I have GPE ROM and firmware 5.0.1 can I flash KitKat based ROM's eg ViperOne?
Gpe have CID like GOOGLE01 I'm not sure better search before changing
Your 032 certainly not help you use win 7
ViperOne need sense firmware GPE firmware not good
Bruce666 said:
ok. I changed it to HTC__032 and RUU force closes during gathering device information on Windows 7.
On Windows 8 fastboot crashes :/
all systems are 64-bit
But... If I have GPE ROM and firmware 5.0.1 can I flash KitKat based ROM's eg ViperOne?
Click to expand...
Click to collapse
read and do this, I was having the same problem: http://forums.androidcentral.com/ht...tall-4-3-ruu-windows-7-8-1-a.html#post3466555
you must install all of them one at a time with reboots inbetween each, and if you have a full RUU make sure your MID also matches, you may also have to flash the corresponding sense firmware first.
yatindroid said:
Gpe have CID like GOOGLE01 I'm not sure better search before changing
Your 032 certainly not help you use win 7
ViperOne need sense firmware GPE firmware not good
Click to expand...
Click to collapse
so... what can I do? now I have CID HTC__032 and this ROM.
RUU exe crashes, fastboot crashes. What can I do? Guru reset won't work in this case when I have GPE firmware?
Bruce666 said:
so... what can I do? now I have CID HTC__032 and this ROM.
RUU exe crashes, fastboot crashes. What can I do? Guru reset won't work in this case when I have GPE firmware?
Click to expand...
Click to collapse
Are you able to post your fastboot getvar all ?
Seanie280672 said:
Are you able to post your fastboot getvar all ?
Click to expand...
Click to collapse
yes no problem
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(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: 4193mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.115s
Bruce666 said:
yes no problem
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(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: 4193mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.115s
Click to expand...
Click to collapse
Thanks, do NOT at any point go s-on, you need to flash the stock sense firmware first then run the RUU
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
you need 4.19.401.9
Because you are s-off you will not need to re-lock the bootloader nor lock it, just run the RUU whilst your phone is still in fastbootUSB mode straight after the firmware flash.
Seanie280672 said:
Thanks, do NOT at any point go s-on, you need to flash the stock sense firmware first then run the RUU
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
you need 4.19.401.9
Click to expand...
Click to collapse
and fastboot will not crash? I'm very afraid about it
Bruce666 said:
and fastboot will not crash? I'm very afraid about it
Click to expand...
Click to collapse
When is fastboot crashing ?
Seanie280672 said:
When is fastboot crashing ?
Click to expand...
Click to collapse
in the last step. after copying in stage 1/5 fastboot crashes. Memory is untouched
Bruce666 said:
in the last step. after copying in stage 1/5 fastboot crashes. Memory is untouched
Click to expand...
Click to collapse
no it shouldnt crash, its a different type of fastboot kind of................basically when you install an RUU, the software is installed first and the last thing the RUU does is flash the firmware, however, because you have GPE firmware on your phone, the software install is failing, only way around it is to flash the firmware first, see here: http://forum.xda-developers.com/showthread.php?t=2733523 don't follow this guide, its just to give you an idea of what we are doing.
To flash a firmware you must be in bootloader/fastbootUSB mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip (there will be some nerving pauses, just let it run, make sure it says successful before the next command) then:
Fastboot reboot-bootloader
Run RUU now..........
Seanie280672 said:
no it shouldnt crash, its a different type of fastboot kind of................basically when you install an RUU, the software is installed first and the last thing the RUU does is flash the firmware, however, because you have GPE firmware on your phone, the software install is failing, only way around it is to flash the firmware first, see here: http://forum.xda-developers.com/showthread.php?t=2733523
To flash a firmware you must be in bootloader/fastbootUSB mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip (there will be some nerving pauses, just let it run, make sure it says successful before the next command) then:
Fastboot reboot-bootloader
Run RUU now..........
Click to expand...
Click to collapse
ok but this is RUU.exe not zip. is flashing firmware wiping all data?
Bruce666 said:
ok but this is RUU.exe not zip. is flashing firmware wiping all data?
Click to expand...
Click to collapse
you need to download the firmware file from the link I gave you earlier: 4.19.401.9 firmware, put it in the same folder as fastboot files, then boot your phone to fastbootUSB mode and follow the commands above.
heres the link again: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
the RUU will wipe your phone when you install it.
Seanie280672 said:
you need to download the firmware file from the link I gave you earlier: 4.19.401.9 firmware, put it in the same folder as fastboot files, then boot your phone to fastbootUSB mode and follow the commands above.
the RUU will wipe your phone when you install it.
Click to expand...
Click to collapse
ok. but will ROM I have flashed boot on this Firmware? coz I have RUU.exe
Bruce666 said:
ok. but will ROM I have flashed boot on this Firmware? coz I have RUU.exe
Click to expand...
Click to collapse
Run the RUU.exe after you have flashed the firmware, after the firmware and the RUU, you will be back on stock Sense, remember to flash the firmware twice, follow the commands above
Seanie280672 said:
Run the RUU.exe after you have flashed the firmware, after the firmware and the RUU, you will be back on stock Sense, remember to flash the firmware twice, follow the commands above
Click to expand...
Click to collapse
ok. but will ROM i have boot on this firmware?
Bruce666 said:
ok. but will ROM i have boot on this firmware?
Click to expand...
Click to collapse
what rom do you have ?
Seanie280672 said:
what rom do you have ?
Click to expand...
Click to collapse
I have this ROM
http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927