It's been awhile since I've done any sort of updating on my HTC One and it's kind of worrying me now. Since I've got my phone, I've unlocked the boot loader, rooted it, installed TWRM as my recovery and I've used CyanogenMod's ROM's (now 4.4.2).
However, I've never once updated "firmware" because I'm not sure how. I've never really updated anything whatsoever apart from my ROM/TWRP and it's got me a bit worried that every thing is so out of date. I see that I'm supposed to update kernels, firmware, hboot, etc? Is this a huge deal and how do I do this safely?
Today I got super CID over with along with removed tampered from my bootloader screen. I'm also S-Off from moving to Kitkat CM.
Can someone please help me get my phone completely up to date? I also have this constant "Superuser binaries are out of date" pop up and when I reboot into TWRP, it doesn't download anything. It's annoying as ****.
Leather Sock said:
It's been awhile since I've done any sort of updating on my HTC One and it's kind of worrying me now. Since I've got my phone, I've unlocked the boot loader, rooted it, installed TWRM as my recovery and I've used CyanogenMod's ROM's (now 4.4.2).
However, I've never once updated "firmware" because I'm not sure how. I've never really updated anything whatsoever apart from my ROM/TWRP and it's got me a bit worried that every thing is so out of date. I see that I'm supposed to update kernels, firmware, hboot, etc? Is this a huge deal and how do I do this safely?
Today I got super CID over with along with removed tampered from my bootloader screen. I'm also S-Off from moving to Kitkat CM.
Can someone please help me get my phone completely up to date? I also have this constant "Superuser binaries are out of date" pop up and when I reboot into TWRP, it doesn't download anything. It's annoying as ****.
Click to expand...
Click to collapse
I would suggest going into superuser apk on phone and try updating binaries through that. If not when it goes to tqrp asking for binaries update try update on that. And if you go to bootloader. So restart phone while holding vol down. See what hboot and firmware it says. But if I'm honest I'm not sure if cm is different to usual stock roms
Sent from my C6833 using Tapatalk
Leather Sock said:
I also have this constant "Superuser binaries are out of date" pop up and when I reboot into TWRP, it doesn't download anything. It's annoying as ****.
Click to expand...
Click to collapse
if you're using superuser (as opposed to SuperSU), TWRP doesn't automatically go to the correct folder to install it, you need to manually (in TWRP) go to:
/data/data/com.koushidutta.superuser/files
then you will see superuser.zip which you can install to update binaries.
nkk71 said:
if you're using superuser (as opposed to SuperSU), TWRP doesn't automatically go to the correct folder to install it, you need to manually (in TWRP) go to:
/data/data/com.koushidutta.superuser/files
then you will see superuser.zip which you can install to update binaries.
Click to expand...
Click to collapse
Thank you so much. Alright, so the Superuser issue is now resolved and I know how to resolve it in the future now too! However, to give an idea of what I'm currently at, this is what my device is using in terms of what's shown on my bootloader screen thing:
M7_UL PVT Ship S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.17.3250.20
How bad is that?
Leather Sock said:
Thank you so much. Alright, so the Superuser issue is now resolved and I know how to resolve it in the future now too! However, to give an idea of what I'm currently at, this is what my device is using in terms of what's shown on my bootloader screen thing:
M7_UL PVT Ship S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.17.3250.20
How bad is that?
Click to expand...
Click to collapse
S-OFF = very good
what you need?
also please post (copy/paste) a "fastboot getvar all" (excluding IMEI and s/n)
nkk71 said:
S-OFF = very good
what you need?
also please post (copy/paste) a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.17.3250.20
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.26.502.15
INFOversion-misc: PVT SHIP S-OFF
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3976mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.144s
nkk71 said:
S-OFF = very good
what you need?
also please post (copy/paste) a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
I just want to be up to date with all of the updates and stuff. I know there's "Hboot" updates and firmware updates and etc, etc. But, I don't know how important those are or what's best.
Leather Sock said:
I just want to be up to date with all of the updates and stuff. I know there's "Hboot" updates and firmware updates and etc, etc. But, I don't know how important those are or what's best.
Click to expand...
Click to collapse
what ROM you running / wanna run?
with S-Off you can upgrade/downgrade anything anytime you like, i (personal choice) use the collection of @vomer's guide (Section2): http://forum.xda-developers.com/showthread.php?t=2365506
I'm using 4.19.401.8 with ARHD 51.0 and working perfectly.
nkk71 said:
what ROM you running / wanna run?
with S-Off you can upgrade/downgrade anything anytime you like, i (personal choice) use the collection of @vomer's guide (Section2): http://forum.xda-developers.com/showthread.php?t=2365506
I'm using 4.19.401.8 with ARHD 51.0 and working perfectly.
Click to expand...
Click to collapse
So using different hboots/firmware upgrades is only to use different roms? I read somewhere that you're supposed to keep hboot up to date to newest version for performance increases and stuff. It's all very confusing to me.
Right now I'm using ARHD GPe 6.1 and it's not bad. I was using CM11 but I want to wait a few months for it to get a little more stable.
Bump please
Leather Sock said:
So using different hboots/firmware upgrades is only to use different roms? I read somewhere that you're supposed to keep hboot up to date to newest version for performance increases and stuff. It's all very confusing to me.
Right now I'm using ARHD GPe 6.1 and it's not bad. I was using CM11 but I want to wait a few months for it to get a little more stable.
Click to expand...
Click to collapse
so far (for the HTC One M7 at least) upgrading firmware is as mentioned in the OP of ARHD
Firmware package from here (recommended but not needed for now)
Click to expand...
Click to collapse
--> not necessary, but recommended.
recommended to have the firmware the same version as ROM, because as you mentioned (at least supposedly/theoretically) better performance, stability, battery, etc.
nkk71 said:
so far (for the HTC One M7 at least) upgrading firmware is as mentioned in the OP of ARHD
--> not necessary, but recommended.
recommended to have the firmware the same version as ROM, because as you mentioned (at least supposedly/theoretically) better performance, stability, battery, etc.
Click to expand...
Click to collapse
How do I install firmware upgrades? Do I have to reinstall the ROM after?
Leather Sock said:
How do I install firmware upgrades? Do I have to reinstall the ROM after?
Click to expand...
Click to collapse
you flash firmware in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip <name of firmware file>.zip
fastboot flash zip <name of firmware file>.zip <- yes TWICE!!
fastboot reboot-bootloader
since you're s-off, you can flash any firmware you like (upgrade & downgrade, signed or unsiged)
I usually use Vomer's firmwares from here: http://forum.xda-developers.com/showthread.php?t=2365506
(cause they have recovery.img and boot.img already removed, i'll get to that in a second)
But there are other, such as:
http://forum.xda-developers.com/showthread.php?t=2316726
or
http://xda7.androidrevolution.nl/db_mirror/Firmware/index.php?dir=HTC/HTC_One/ (those are original signed packages i think)
You should check the contents of the zip, for
recovery.img -> that would overwrite your custom recovery and you would have to flash it again
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
boot.img (the kernel) -> that would overwrite the kernel that comes part of the ROM
you either dirty-flash the ROM again, or extract "boot.img" from the ROM.zip and
fastboot flash boot boot.img
(that's boot NOT hboot, don't ever do fastboot flash hboot, EVER!!!)
you can also try different radios from here: http://forum.xda-developers.com/showthread.php?t=2419699
(flashable in custom recovery)
Related
Hi, i have update my HTC One to GE 4.3. All works fine but now i must return to stock because i prefer sense. The question is, how can i run ruu? I have s off and i chance my cid to HTC__001, my hboot is 1.54, i need to do something else? Tnx for reply!
RockLee91 said:
Hi, i have update my HTC One to GE 4.3. All works fine but now i must return to stock because i prefer sense. The question is, how can i run ruu? I have s off and i chance my cid to HTC__001, my hboot is 1.54, i need to do something else? Tnx for reply!
Click to expand...
Click to collapse
Simply flash a stock RUU which matches the CID or just use fastboot oem writecid 11111111 to be able to flash any RUU.
RockLee91 said:
Hi, i have update my HTC One to GE 4.3. All works fine but now i must return to stock because i prefer sense. The question is, how can i run ruu? I have s off and i chance my cid to HTC__001, my hboot is 1.54, i need to do something else? Tnx for reply!
Click to expand...
Click to collapse
if you have S-Off download any RUU and open the .EXE file on your Windows PC, then follow the instruction
Can i execute a ruu of a lower version? And can i do that with 1.54 hboot? When i try with HTC__001 cid the setup wizard give me error this is the ruu i want to flash. RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
Its the correct One?
I've tried with super cid but the result was the same... Any advice?
RockLee91 said:
I've tried with super cid but the result was the same... Any advice?
Click to expand...
Click to collapse
Try this.
1. Run the RUU and click next but no further
2. Go to your user folder ie C:\Users\Nameofuser\AppData\Local\Temp
3. Search for rom.zip and then copy it to another location on your PC
4. Stop the RUU
5. Reboot your phone into the bootloader
6. Go into fastboot
7. fastboot oem rebootRUU
8. fastboot flash zip rom.zip (will fail the first time)
9. fastboot flash zip rom.zip (should now work)
daleski75 said:
Try this.
1. Run the RUU and click next but no further
2. Go to your user folder ie C:\Users\Nameofuser\AppData\Local\Temp
3. Search for rom.zip and then copy it to another location on your PC
4. Stop the RUU
5. Reboot your phone into the bootloader
6. Go into fastboot
7. fastboot oem rebootRUU
8. fastboot flash zip rom.zip (will fail the first time)
9. fastboot flash zip rom.zip (should now work)
Click to expand...
Click to collapse
The first time i do fastboot the terminal work for a while and then get the failed message, the second time got failed message again without work, it says status read failed (too many links)
RockLee91 said:
The first time i do fastboot the terminal work for a while and then get the failed message, the second time got failed message again without work, it says status read failed (too many links)
Click to expand...
Click to collapse
Did you literally flash everything to get the GE edition as per another thread on the conversion and also did you flash the 4.3 GE hboot?
I flash the zip of the rooted GE 4.3 the same way you told me to do before.
I follow this guide : http://forum.xda-developers.com/showthread.php?t=2358781
RockLee91 said:
I flash the zip of the rooted GE 4.3 the same way you told me to do before
Click to expand...
Click to collapse
can you run fastboot getvar all and post the output here?
INFOversion: 0.5
INFOversion-bootloader: 1.54.0000
INFOversion-baseband: 4A.18.3263.15
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.06.1700.10
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: *************
INFOimei: *************
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3826mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-94cf81a8fd
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.062s
Probably a good idea to remove your IMEI and SERIAL number from your post but anyway...
Try just flashing the stock rom from this thread using CWM or TWRP and then flash the stock recovery back after.
http://forum.xda-developers.com/showthread.php?t=2224752
Done, remove from quote top pls XD
daleski75 said:
Probably a good idea to remove your IMEI and SERIAL number from your post but anyway...
Try just flashing the stock rom from this thread using CWM or TWRP and then flash the stock recovery back after.
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
how can i get custom recovery on GE 4.3?
RockLee91 said:
how can i get custom recovery on GE 4.3?
Click to expand...
Click to collapse
Flash a custom recovery as normal ie fastboot flash recovery openrecovery.img etc
i have flashed the rom that you linked me but now the phone stuck on boot screen :crying:
any advice?
SOLVED: i've flashed another rom and now work like a charm i flashed android revolution hd 12.1 ^^ tnx for all the support you saved me!
Hi guys! I have a question...
I was thinking about using a RUU to clean install a stock rom on my one...so, I was at htc-dev site and looked at downloads...
I find: the developer edition RUU, android 4.3 (the last one)...ok, this is the classic RUU, I have to execute it when I'm on "fastboot oem rebootRUU", I'm s-off, it wipes everything and I have the stock firmware and rom...and it's ok...have I got to relock the bootloader?
then....I see, just below, a zip file, as big as the RUU one, but is a zip...what is this? is the zip that the RUU flashes, but for a different use, with the raw method, on the terminal?
and, another one...I looked at the google play edition section...and I founded two zips for each version: one "stock ui" and one "framework support files"....ok, what is this?! isn't there a RUU? what if I want to flash a clean google play edition, with full wipe and stock clean firmware? what can I do with these files?
thank you for listening, and sorry for my bad english
throcker said:
Hi guys! I have a question...
I was thinking about using a RUU to clean install a stock rom on my one...so, I was at htc-dev site and looked at downloads...
I find: the developer edition RUU, android 4.3 (the last one)...ok, this is the classic RUU, I have to execute it when I'm on "fastboot oem rebootRUU", I'm s-off, it wipes everything and I have the stock firmware and rom...and it's ok...have I got to relock the bootloader?
then....I see, just below, a zip file, as big as the RUU one, but is a zip...what is this? is the zip that the RUU flashes, but for a different use, with the raw method, on the terminal?
and, another one...I looked at the google play edition section...and I founded two zips for each version: one "stock ui" and one "framework support files"....ok, what is this?! isn't there a RUU? what if I want to flash a clean google play edition, with full wipe and stock clean firmware? what can I do with these files?
thank you for listening, and sorry for my bad english
Click to expand...
Click to collapse
You must have s-off and super cid "11111111" to flash ruu that are not specific to your phone. You do not have to lock your bootloader. Again, you MUST have s-off and super cid! As long as you have those, you can pretty much convert your phone to whichever you want. I always recommend downgrading your hboot to 1.44 before doing this. You need encrypted ruu's to use the "fastboot oem rebootRUU" mode. Remember to flash stock recovery if you want OTA updates. I have never used the .exe files. I converted my att htc one to google edition, then back, then developer, then back. Its really no different than just running roms, but at least you get a new splash screen and bootloader with each.
http://forum.xda-developers.com/showthread.php?t=2358781 This is the google edition conversion link I used my first time converting my phone. if you look at post 2, it shows how to go back to stock "or pretty much any ruu"
an0ther said:
You must have s-off and super cid "11111111" to flash ruu that are not specific to your phone. You do not have to lock your bootloader. Again, you MUST have s-off and super cid! As long as you have those, you can pretty much convert your phone to whichever you want. I always recommend downgrading your hboot to 1.44 before doing this. You need encrypted ruu's to use the "fastboot oem rebootRUU" mode. Remember to flash stock recovery if you want OTA updates. I have never used the .exe files. I converted my att htc one to google edition, then back, then developer, then back. Its really no different than just running roms, but at least you get a new splash screen and bootloader with each.
http://forum.xda-developers.com/showthread.php?t=2358781 This is the google edition conversion link I used my first time converting my phone. if you look at post 2, it shows how to go back to stock "or pretty much any ruu"
Click to expand...
Click to collapse
ok, thanks for your answer, first....
I already tried the conversion, and it worked fine...but that's not what I'm looking for
I was asking how does the official source files work...
delete me
throcker said:
ok, thanks for your answer, first....
I already tried the conversion, and it worked fine...but that's not what I'm looking for
I was asking how does the official source files work...
Click to expand...
Click to collapse
What do you mean 'work'? They are used to put the phone back to a factory state, a hard reset if you will. It means you can always revert back to stock should you want/need to send it in for repair
As for GPe files, they are not for flashing and are source files to make your own software
EddyOS said:
What do you mean 'work'? They are used to put the phone back to a factory state, a hard reset if you will. It means you can always revert back to stock should you want/need to send it in for repair
As for GPe files, they are not for flashing and are source files to make your own software
Click to expand...
Click to collapse
OK that's the answer! GPE files are the source? same for the zip file next the ruu?
No, the RUU and the 1GB ZIP are the same thing but flashed in different ways...
The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation
Basic Steps but...
Not worked for me, i downloaded right htcdev rom for my desire c
Waiting for device... is appeared and no way out.
Any Ideas??
EddyOS said:
No, the RUU and the 1GB ZIP are the same thing but flashed in different ways...
The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation
Click to expand...
Click to collapse
an0ther said:
You must have s-off and super cid "11111111" to flash ruu that are not specific to your phone. You do not have to lock your bootloader. Again, you MUST have s-off and super cid! As long as you have those, you can pretty much convert your phone to whichever you want. I always recommend downgrading your hboot to 1.44 before doing this. You need encrypted ruu's to use the "fastboot oem rebootRUU" mode. Remember to flash stock recovery if you want OTA updates. I have never used the .exe files. I converted my att htc one to google edition, then back, then developer, then back. Its really no different than just running roms, but at least you get a new splash screen and bootloader with each.
http://forum.xda-developers.com/showthread.php?t=2358781 This is the google edition conversion link I used my first time converting my phone. if you look at post 2, it shows how to go back to stock "or pretty much any ruu"
Click to expand...
Click to collapse
Hey, sorry for bothering you, i am trying to revert my Htc desire 510 to stock, i do not have a backup. I found files on the htcdev.com and thought they were Roms (easy catch). Unfortunately they are not. I dont even know what to do with these files inorder to get my rom in place. pleace help me.
Zubagy said:
Hey, sorry for bothering you, i am trying to revert my Htc desire 510 to stock, i do not have a backup. I found files on the htcdev.com and thought they were Roms (easy catch). Unfortunately they are not. I dont even know what to do with these files inorder to get my rom in place. pleace help me.
Click to expand...
Click to collapse
There are no more RUU on htcdev.com, these files are kernel source code and not useful to restore your phone. Can you post the output of "fastboot getvar all" (hide your IMEI and serialno), I'll check if I can find something for you.
alray said:
There are no more RUU on htcdev.com, these files are kernel source code and not useful to restore your phone. Can you post the output of "fastboot getvar all" (hide your IMEI and serialno), I'll check if I can find something for you.
Click to expand...
Click to collapse
Thank you for your response. This is what i get
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 01.02.012_U10251_39.08.40922
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: xxxx
INFOimei: xxxx
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: a11_ul
INFOplatform: hTCBmsm8916
INFOmodelid: 0PCV20000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 295e1798
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOmfg-name: 1001
all: Done!
Zubagy said:
Thank you for your response. This is what i get
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 01.02.012_U10251_39.08.40922
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: xxxx
INFOimei: xxxx
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: a11_ul
INFOplatform: hTCBmsm8916
INFOmodelid: 0PCV20000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 295e1798
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOmfg-name: 1001
all: Done!
Click to expand...
Click to collapse
There are 3 RUU for Vodafone UK's Desire 510:
1.51.161.10
1.51.161.11
1.51.161.12
Unfortunately these files are only available from a paid site (ir-file)
Not sure which one you'll need since your version-main is blank
Here are the files name just in case you can find elsewhere than ir-file:
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.10_Radio_01.02.012_U10251_39.08.40922_release_416938_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.11_Radio_01.02.012_U10251_39.08.40922_release_427262_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.12_Radio_01.02.012_U10251_39.08.40922_release_450233_combined_signed.zip
alray said:
There are 3 RUU for Vodafone UK's Desire 510:
1.51.161.10
1.51.161.11
1.51.161.12
Unfortunately these files are only available from a paid site (ir-file)
Not sure which one you'll need since your version-main is blank
Here are the files name just in case you can find elsewhere than ir-file:
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.10_Radio_01.02.012_U10251_39.08.40922_release_416938_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.11_Radio_01.02.012_U10251_39.08.40922_release_427262_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.12_Radio_01.02.012_U10251_39.08.40922_release_450233_combined_signed.zip
Click to expand...
Click to collapse
Thankyou for your help, ill get started on looking for them. does this work, found it but still have my doubts... not yet downloaded it.
https://www.dropbox.com/s/cp3hif7sg...51_39.08.40922_release_398419_signed.rar?dl=0
Zubagy said:
Thankyou for your help, ill get started on looking for them. does this work, found it but still have my doubts... not yet downloaded it.
https://www.dropbox.com/s/cp3hif7sg...51_39.08.40922_release_398419_signed.rar?dl=0
Click to expand...
Click to collapse
no, your phone is S-ON and branded to vodafone UK so you can only use RUU for vodafone UK (x.xx.161.x).
1.51.401.1 is for HTC Europe WWE not vodafone.
alray said:
no, your phone is S-ON and branded to vodafone UK so you can only use RUU for vodafone UK (x.xx.161.x).
1.51.401.1 is for HTC Europe WWE not vodafone.
Click to expand...
Click to collapse
A developer sent me this link, looks like it is The ONE. But it looks a lower version than the ones that u mentioned above.
https://mega.nz/#!d4ZknKYT!ZhCHoiBSNJl3pBO_G-uv518ssNrGDY6UPH4EpqZ7qog
Zubagy said:
A developer sent me this link, looks like it is The ONE. But it looks a lower version than the ones that u mentioned above.
https://mega.nz/#!d4ZknKYT!ZhCHoiBSNJl3pBO_G-uv518ssNrGDY6UPH4EpqZ7qog
Click to expand...
Click to collapse
I would try this one
alray said:
I would try this one
Click to expand...
Click to collapse
Oh, ok, then let me get started with it. By the way, do u happen to know where i can also pick any custom ROMs for the 64bit, i checked out the cm12, but its gat bugs
Zubagy said:
Oh, ok, then let me get started with it. By the way, do u happen to know where i can also pick any custom ROMs for the 64bit, i checked out the cm12, but its gat bugs
Click to expand...
Click to collapse
not sure for x64 but everything should be here: http://forum.xda-developers.com/desire-510
Hi everybody,
I already checked a lot of threads in xda but it didn't solve my problem so I do it by myself...
Just got a HTC One and when I wanted to install the Google Edition ROM by bigxie with mini SDK, ADB and TWRP... I just messed up:
- OK to unlock bootloader
- S-OFF didn't work
- I accidentaly wiped everything: the OS...
I tried push a ROM with adb push rom.zip /sdcard/rom.zip but it didn't help:
- S-ON didn't allow me to install custom ROMs
- I couldn't turn my phone S-OFF because my PC didn't recognise it anymore + have no OS
- adb devices command didn't see my phone
Then I tried to relock it to install an official RUU from HTC but:
"(bootloader) signature checking...
FAILED (remote: signature verify fail)"
I guess it comes from my HBOOT-1.54, I red we have to be in 1.44 but one more time I can't downgrade my HBOOT because I'm not S-OFF.
Now my HTC One M7_UL is :
* TAMPERED *
* RELOCKED *
*** Security Warning ***
- S-ON
- HBOOT-1.54.0000
Checkmate ?
Thanks in advance...
can you unlock your phone using HTCdev? get a new token and try.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
samih7 said:
Hi everybody,
I already checked a lot of threads in xda but it didn't solve my problem so I do it by myself...
Just got a HTC One and when I wanted to install the Google Edition ROM by bigxie with mini SDK, ADB and TWRP... I just messed up:
- OK to unlock bootloader
- S-OFF didn't work
- I accidentaly wiped everything: the OS...
I tried push a ROM with adb push rom.zip /sdcard/rom.zip but it didn't help:
- S-ON didn't allow me to install custom ROMs
- I couldn't turn my phone S-OFF because my PC didn't recognise it anymore + have no OS
- adb devices command didn't see my phone
Then I tried to relock it to install an official RUU from HTC but:
"(bootloader) signature checking...
FAILED (remote: signature verify fail)"
I guess it comes from my HBOOT-1.54, I red we have to be in 1.44 but one more time I can't downgrade my HBOOT because I'm not S-OFF.
Now my HTC One M7_UL is :
* TAMPERED *
* RELOCKED *
*** Security Warning ***
- S-ON
- HBOOT-1.54.0000
Checkmate ?
Thanks in advance...
Click to expand...
Click to collapse
Do you still have a custom recovery installed?
nkk71 said:
can you unlock your phone using HTCdev? get a new token and try.
Click to expand...
Click to collapse
Thanks for your answer.
Yes, I can. Should I install TWRP or CWM afterwards ?
samih7 said:
Thanks for your answer.
Yes, I can. Should I install TWRP or CWM afterwards ?
Click to expand...
Click to collapse
doesnt matter, either will do. choose the one you prefer.
were you able to unlock bootloader?
nkk71 said:
doesnt matter, either will do. choose the one you prefer.
were you able to unlock bootloader?
Click to expand...
Click to collapse
Yes, it's now unlocked and I installed TWRP.
samih7 said:
Yes, it's now unlocked and I installed TWRP.
Click to expand...
Click to collapse
ok, can you post a "fastboot getvar all" (remove IMEI and s/n before posting)
nkk71 said:
ok, can you post a "fastboot getvar all" (remove IMEI and s/n before posting)
Click to expand...
Click to collapse
Here it is :
(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-ON
(bootloader) serialno: xxxxx
(bootloader) imei: xxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANGB10
(bootloader) battery-status: good
(bootloader) battery-voltage: 4286mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.039s
samih7 said:
Here it is :
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANGB10
finished. total time: 0.039s
Click to expand...
Click to collapse
another missing version-main , this is really getting weird.
are you still looking to go s-off? if so you're on hboot 1.54, which means a 2.24.xxx.? ROM, so download and try rumrunner with this
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
and/or
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
select WIPE, select ROOT, unselect "stock recovery"
nkk71 said:
another missing version-main , this is really getting weird.
are you still looking to go s-off? if so you're on hboot 1.54, which means a 2.24.xxx.? ROM, so download and try rumrunner with this
and/or
select WIPE, select ROOT, unselect "stock recovery"
Click to expand...
Click to collapse
If version main is the version of the OS, I don't have one. :-S
Yes I'm still looking for it and install the Google Edition ROM...
Ok I'll try it, it's downloading, I hope it'll recognise the phone.
samih7 said:
If version main is the version of the OS, I don't have one. :-S
Yes I'm still looking for it and install the Google Edition ROM...
Ok I'll try it, it's downloading, I hope it'll recognise the phone.
Click to expand...
Click to collapse
version-main is the firmware version of the phone, just seems it's disappearing a lot last couple of days.
hboot 1.54 has firmware 2.24.xxx.x, so one of the roms I linked will hopefully get you s-off using rumrunner
nkk71 said:
version-main is the firmware version of the phone, just seems it's disappearing a lot last couple of days.
hboot 1.54 has firmware 2.24.xxx.x, so one of the roms I linked will hopefully get you s-off using rumrunner
Click to expand...
Click to collapse
Ok.
So I need to push and flash the ROM on TRWP, boot on it and a screen will appear with "WIPE" then "ROOT" and unselect stock recovery ?
Thanks.
NB: When I try to do a Factory Reset in TRWP, it fails with an "Unable to mount cache" error message.
NB1: Can't flash the ROM you gave me. Since I did an "Format Data" wich removes datas & encryption on internal storage, I can't flash anything...
NB2: OK I can't mount /data, /sdcard either...
samih7 said:
Ok.
So I need to push and flash the ROM on TRWP, boot on it and a screen will appear with "WIPE" then "ROOT" and unselect stock recovery ?
Thanks.
NB: When I try to do a Factory Reset in TRWP, it fails with an "Unable to mount cache" error message.
NB1: Can't flash the ROM you gave me. Since I did an "Format Data" wich removes datas & encryption on internal storage, I can't flash anything...
Click to expand...
Click to collapse
say what?
unable to mount cache is OK, probably because of the fastboot erase cache
if push dosn't work , sideload it: http://forum.xda-developers.com/showthread.php?t=2317986
nkk71 said:
say what?
unable to mount cache is OK, probably because of the fastboot erase cache
if push dosn't work , sideload it: http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
It's ok, I found an issue by formatting /data in CWM (I deleted TWRP)
The .8 ROM is installed but the fingertouch screen wasn't usable during the installation, I don't know if it means that's not a good version ?
--
Damn man you made my day, the ROM is installed and I can use my HTC again !
Is it the official RUU ?
But unfortunately it's still S-ON.
Thanks a lot
samih7 said:
It's ok, I found an issue by formatting /data in CMW (I deleted TRPW)
The .8 ROM is installed but the fingertouch screen wasn't usable during the installation, I don't know if it means that's not a good version ?
--
Damn man you made my day, the ROM is installed and I can use my HTC again !
Is it the official RUU ?
Click to expand...
Click to collapse
touchscreen wasnt working because you probably used 6.0.3.1, get the latest from here: http://forum.xda-developers.com/showthread.php?t=2173863 (though that one takes VERY long to backup/restore nandroids), so either get 6.0.3.2 or TWRP if you do nandroids frequently.
It's getting late for me, so have to sign off in a bit, and now that your phone is up and running, we can pick this up tomorrow....
you can try rumrunner now to get yourself s-off.
I'll check back tomorrow....
You can still hit the thanks button on my posts if i helped
nkk71 said:
touchscreen wasnt working because you probably used 6.0.3.1, get the latest from here: http://forum.xda-developers.com/showthread.php?t=2173863 (though that one takes VERY long to backup/restore nandroids), so either get 6.0.3.2 or TWRP if you do nandroids frequently.
It's getting late for me, so have to sign off in a bit, and now that your phone is up and running, we can pick this up tomorrow....
you can try rumrunner now to get yourself s-off.
I'll check back tomorrow....
You can still hit the thanks button on my posts if i helped
Click to expand...
Click to collapse
No problem, take your time. Thank you for helping me !!
I hit the "thanks" but it doesn't appear anything, is it normal ?
--
I red I didn't need to get myself S-OFF to install a Custom Rom, is it true ?
I'm trying to get the Google Edition ROM again... Without success.
I flash boot.img in fastboot (& make clear cache) + flash the ROM normally (wipe cache + dalvik cache) via TWRP but my device enter in a boot loop when I reboot after installation (I just see the Google language selection, just to make me more frustrated lol...). Same with CyanogenMod.
Root Checker says "Congratulations ! This device has root access" and I unlocked the bootloader so I don't understand...
Maybe because of the CID of my phone is from Orange Poland (ORANGB10) ? I maybe should get S-OFF & Debrand ?
Thanks for your answer.
Definitely do s-off if you can. It may save you if things go south..
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
However you need unlocked bootloader + custom recovery to install custom ROMs. Not S-off.
SaHiLzZ said:
Definitely do s-off if you can. It may save you if things go south..
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
However you need unlocked bootloader + custom recovery to install custom ROMs. Not S-off.
Click to expand...
Click to collapse
I finally got S-OFF and achieved to install the stock Google Edition 4.4 ROM with this thread : http://forum.xda-developers.com/showthread.php?t=2358781
I had to SuperCID (fastboot eom writecid 11111111) because changing the android-info.txt didn't work.
Could you tell me in which case is it useful to flash stock recovery (he says it's for future OTA's) ?
Does it mean I could do updates via Software Update in Android the menu ?
NB: In the best case, I would like to get the updates via Android interface and have the most "official" Google Edition ROM (I don't want to change it, sooner or later).
Thank you.
samih7 said:
I finally got S-OFF and achieved to install the stock Google Edition 4.4 ROM with this thread : http://forum.xda-developers.com/showthread.php?t=2358781
I had to SuperCID (fastboot eom writecid 11111111) because changing the android-info.txt didn't work.
Could you tell me in which case is it useful to flash stock recovery (he says it's for future OTA's) ?
Does it mean I could do updates via Software Update in Android the menu ?
NB: In the best case, I would like to get the updates via Android interface and have the most "official" Google Edition ROM (I don't want to change it, sooner or later).
Thank you.
Click to expand...
Click to collapse
NB: In the best case, I would like to get the updates via Android interface and have the most "official" Google Edition ROM (I don't want to change it, sooner or later).
Click to expand...
Click to collapse
I wouldn't , but that's your choice :laugh:
Anyway, I didn't read the thread you linked, but to get OTAs, you need "odexed stock rom", and "stock recovery" for OTAs to work properly,
you also need to change your CID (and possibly MID) to GPe
I think GPE CID is "GOOGL001" and MID is "PN0712000" (I THINK)
So if you're stock rom + stock recovery + correct CID & MID, you'll receive future OTAs just fine,
remember to keep S-Off.
if all good, would you mind editing the main thread title to include [SOLVED]. thanks
nkk71 said:
I wouldn't , but that's your choice :laugh:
Anyway, I didn't read the thread you linked, but to get OTAs, you need "odexed stock rom", and "stock recovery" for OTAs to work properly,
you also need to change your CID (and possibly MID) to GPe
I think GPE CID is "GOOGL001" and MID is "PN0712000" (I THINK)
So if you're stock rom + stock recovery + correct CID & MID, you'll receive future OTAs just fine,
remember to keep S-Off.
if all good, would you mind editing the main thread title to include [SOLVED]. thanks
Click to expand...
Click to collapse
Why wouldn't you ? :laugh: I like Google's refinement, don't you ?
How could I verify I'm in stock recovery ?
I flashed it, and now when I click on RECOVERY in BOOT LOADER, it doesn't enter in recovery anymore: get that little Android green toy down with a red triangle.
Ok fine.
samih7 said:
Why wouldn't you ? :laugh: I like Google's refinement, don't you ?
How could I verify I'm in stock recovery ?
I flashed it, and now when I click on RECOVERY in BOOT LOADER, it doesn't enter in recovery anymore: get that little Android green toy down with a red triangle.
Ok fine.
Click to expand...
Click to collapse
"get that little Android green toy down with a red triangle" -> yep, that's stock recovery :good::good:
if you simultaneously and briefly press POWER + VOLUP + VOLDOWN, you'll get to the stock recovery menu (really tiny font). you'll have to try a couple of times to get the timing correctly.
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: XXXXXX
imei: XXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4333mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2485651 here is a list of firmware
You can downgrade your hboot and then run the RUU. Make sure it's a stock hboot and NOT a modified one (it'll say either or). You can open the firmeware zips (not extract) and open and edit the android.info text file and add in your CID and model id as required if necessary
You can then flash the RUU as normal after. No need to step down hboots
consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified.
Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this 4.18.502.7 decrypted ROM. and the instructions are from clsA:
Copy your downloaded file to your fastboot / adb folder
Rename the file Rom.zip
open a command prompt in the same folder (shift + right click - command prompt here )
adb reboot-bootloader
fastboot commands:
fastboot oem rebootRUU
wait for the Silver HTC logo
fastboot flash zip Rom.zip
the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip Rom.zip
most times the green status bar does not reach the 100% mark. So when the output in the command window is complete, you can reboot:
fastboot reboot
Click to expand...
Click to collapse
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Decrypted ROM Failed
majmoz said:
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this and the instructions are from clsA:
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Click to expand...
Click to collapse
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
consequense said:
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
Click to expand...
Click to collapse
you can try it again but flash this firmware first and it should work.
http://d-h.st/a1w
You could also use the full RUU after flashing the above firmware. http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Hello Everyone,
I have read multiple guides from here and want to emphasize what a great community this place seems to be!
I am a proud owner of an HTC One M7 with Miui installed.
I have CWM Recovery installed and am S-ON.
I have the tint problem of the camera and intend to bring it to the seller for a repair. This requires me to go back to the stock HTC Sense ROM.
Below is the output of the fastboot getvar all command:
c:\fastboot>fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-ON
(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: 4317mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.052s
Click to expand...
Click to collapse
I don't know how to choose the correct RUU. The only thing which comes close to what I have in terms of software version is this:
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
Should I use it?
Also, most of the guides start with the assumption that your phone is S-OFF (not really sure what that means exactly, but that's a different conversation).
Does that mean I can skip the steps for getting it back to S-ON from those guides and continue onward or I should get it first to S-OFF, do whatever needs to be done and then get it back to S-ON and continue with the RUU?
Thanks a lot, guys!
Best,
Wisher
WisherBG said:
Hello Everyone,
I have read multiple guides from here and want to emphasize what a great community this place seems to be!
I am a proud owner of an HTC One M7 with Miui installed.
I have CWM Recovery installed and am S-ON.
I have the tint problem of the camera and intend to bring it to the seller for a repair. This requires me to go back to the stock HTC Sense ROM.
Below is the output of the fastboot getvar all command:
I don't know how to choose the correct RUU. The only thing which comes close to what I have in terms of software version is this:
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
Should I use it?
Also, most of the guides start with the assumption that your phone is S-OFF (not really sure what that means exactly, but that's a different conversation).
Does that mean I can skip the steps for getting it back to S-ON from those guides and continue onward or I should get it first to S-OFF, do whatever needs to be done and then get it back to S-ON and continue with the RUU?
Thanks a lot, guys!
Best,
Wisher
Click to expand...
Click to collapse
That RUU will work for you, but it won't do any good for reinstating your warranty. You need to be s-off to return to 100% stock.
As you will need to set the bootloader back to ***LOCKED*** which requires s-off. With s-on the best you will get is ***RELOCKED*** and that's a sure sign the device was tampered with.
WisherBG said:
Hello Everyone,
I am a proud owner of an HTC One M7 with Miui installed.
I have CWM Recovery installed and am S-ON.
I don't know how to choose the correct RUU. The only thing which comes close to what I have in terms of software version is this:
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
Should I use it?
Thanks a lot, guys!
Best,
Wisher
Click to expand...
Click to collapse
Danny201281 said:
That RUU will work for you, but it won't do any good for reinstating your warranty. You need to be s-off to return to 100% stock.
Click to expand...
Click to collapse
this ruu won't work for you it's version is low you need same or higher version
Stock Reset Rom can help you but not 100%
S Off is only option
yatindroid said:
this ruu won't work for you it's version is low you need same or higher version
Stock Reset Rom can help you but not 100%
S Off is only option
Click to expand...
Click to collapse
Good catch I didn't spot he was on .11 not .9 :good:
Thanks for your replies.
So how do I go about getting a newer RUU?
I am currently trying to get S-OFF with rumrunner... hopefully it will work.
If I get it to be S-OFF, what should I do from that point on?
The unbranded EU Lollipop RUU (in ZIP form) is here:
http://forum.xda-developers.com/htc-one/general/htc-one-m7-european-signed-ruu-t3048384
EddyOS said:
The unbranded EU Lollipop RUU (in ZIP form) is here:
http://forum.xda-developers.com/htc-one/general/htc-one-m7-european-signed-ruu-t3048384
Click to expand...
Click to collapse
If you use that ruu you won't be able to get s-off, there is no working method to s-off hboot 1.60. You'd be better off finding a stock Rom to flash and get s-off with rumrunner. Once you update past hboot 1.57 you will have to pay $25 for sunshine to s-off and as I mentioned if you go to hboot 1.60 you will ha e to wait for a new exploit that will work with that version. No doubt that will also be an updated version of Sunshine
What's wrong with paying for S-OFF? Gotta show the Devs some love
So the current option is to find a stock 401.11 ROM?
Any ideas where to look for one?
I have found the original/stock OTA zip file for the 401.11 update from an article by Android Revolution HD.
Also the 401.11 stock firmware zip from the android revolution collection.
(sorry, I'm too new of a user and can't post the actual links but they can be found by googling "4.19.401.11 ruu" and seeing the android revolution blogspot article)
Am I correct in thinking that I should do the following:
1. Flash with this firmware (since it is the stock one).
2. Install the OTA zip with fastboot (I think there is a tutorial on how to do this). Will this work the same as installing a RUU?
3. Run rumrunner while still on hboot 1.56
4. Go to S-OFF
5. Return everything to stock
6. Apply latest OTA (lolipop etc.)
7. Pay the price if I want to have S-OFF later.
Best,
Wisher
WisherBG said:
So the current option is to find a stock 401.11 ROM?
Any ideas where to look for one?
I have found the original/stock OTA zip file for the 401.11 update from an article by Android Revolution HD.
Also the 401.11 stock firmware zip from the android revolution collection.
(sorry, I'm too new of a user and can't post the actual links but they can be found by googling "4.19.401.11 ruu" and seeing the android revolution blogspot article)
Am I correct in thinking that I should do the following:
1. Flash with this firmware (since it is the stock one).
2. Install the OTA zip with fastboot (I think there is a tutorial on how to do this). Will this work the same as installing a RUU?
3. Run rumrunner while still on hboot 1.56
4. Go to S-OFF
5. Return everything to stock
6. Apply latest OTA (lolipop etc.)
7. Pay the price if I want to have S-OFF later.
Best,
Wisher
Click to expand...
Click to collapse
No RUU, flash this inside TWRP recovery just like you would with a custom rom, only this will make your phone stock.
https://www.androidfilehost.com/?fid=23501681358545524
you cant manually flash OTA's whilst s-on, also you shouldnt need to flash firmware that you are already on.
Seanie280672 said:
No RUU, flash this inside TWRP recovery just like you would with a custom rom, only this will make your phone stock.
YOUR LINK (removed due to too new a user)
you cant manually flash OTA's whilst s-on, also you shouldnt need to flash firmware that you are already on.
Click to expand...
Click to collapse
Ok, I will be flashing with this guru reset file.
Then I should go S-OFF and follow the guide to get everything back to stock (no **UNLOCKED**, no TAMPERED, etc.).
Correct?
WisherBG said:
Ok, I will be flashing with this guru reset file.
Then I should go S-OFF and follow the guide to get everything back to stock (no **UNLOCKED**, no TAMPERED, etc.).
Correct?
Click to expand...
Click to collapse
get s-off as long as you can, do not accept any updates.
after s-off you will need to flash HBOOT 1.44 and a very early RUU, then get rid of the flags and s-on before updating.
removing the flags and then going s-on with anything higher than HBOOT 1.54 and the flags come back on the next reboot.
Seanie280672 said:
get s-off as long as you can, do not accept any updates.
after s-off you will need to flash HBOOT 1.44 and a very early RUU, then get rid of the flags and s-on before updating.
removing the flags and then going s-on with anything higher than HBOOT 1.54 and the flags come back on the next reboot.
Click to expand...
Click to collapse
Ok, thanks! I will see what I can do with the help of the guides in this forum.
Any helpful links will be highly appreciated.
Best,
Wisher
WisherBG said:
Ok, thanks! I will see what I can do with the help of the guides in this forum.
Any helpful links will be highly appreciated.
Best,
Wisher
Click to expand...
Click to collapse
just report back here once your s-off and all the guys will be more than happy to help you :good:
Seanie280672 said:
after s-off you will need to flash HBOOT 1.44 and a very early RUU, then get rid of the flags and s-on before updating.
removing the flags and then going s-on with anything higher than HBOOT 1.54 and the flags come back on the next reboot.
Click to expand...
Click to collapse
Important Thanks
Got the following with rumrunner:
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
Click to expand...
Click to collapse
However I can do "adb shell" and then "su" brings me to be a super user.
What is different to what the situation was when I was with MIUI is that now when I type "adb shell" I am not automatically root (don't have # but $ at the console). When I do "su", the $ changes to #, which basically means that I am root.
I guess rumrunner has a requirement that you are root by default when logging via adb shell.
Any idea on a fix?
Best,
Wisher
EddyOS said:
What's wrong with paying for S-OFF? Gotta show the Devs some love
Click to expand...
Click to collapse
There's nothing wrong with paying for s-off. I have purchased Sunshine myself when necessary, and made regular donations to other devs. but it's only fair to inform people of there options before you land them with a $25 solution not everyone has money to spare for that sort of thing. :good:
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
WisherBG said:
So the current option is to find a stock 401.11 ROM?
Any ideas where to look for one?
I have found the original/stock OTA zip file for the 401.11 update from an article by Android Revolution HD.
Also the 401.11 stock firmware zip from the android revolution collection.
(sorry, I'm too new of a user and can't post the actual links but they can be found by googling "4.19.401.11 ruu" and seeing the android revolution blogspot article)
Am I correct in thinking that I should do the following:
1. Flash with this firmware (since it is the stock one).
2. Install the OTA zip with fastboot (I think there is a tutorial on how to do this). Will this work the same as installing a RUU?
3. Run rumrunner while still on hboot 1.56
4. Go to S-OFF
5. Return everything to stock
6. Apply latest OTA (lolipop etc.)
7. Pay the price if I want to have S-OFF later.
Best,
Wisher
Click to expand...
Click to collapse
You should try rumrunner with the Rom @Seanie280672 posted to gain s-off. Not guaranteed to work as HTC started patching firmware at this point but if you need 100% stock it's your best chance to s-off without Sunshine.
If rumrunner won't work Sunshine is still cheaper than paying for the repair, and when you get your device back you can use Sunshine again for free, as long as it is the same device and not a replacement :good:
Seanie280672 said:
No RUU, flash this inside TWRP recovery just like you would with a custom rom, only this will make your phone stock.
https://www.androidfilehost.com/?fid=23501681358545524
you cant manually flash OTA's whilst s-on, also you shouldnt need to flash firmware that you are already on.
Click to expand...
Click to collapse
---------- Post added at 09:34 PM ---------- Previous post was at 09:31 PM ----------
WisherBG said:
Got the following with rumrunner:
However I can do "adb shell" and then "su" brings me to be a super user.
What is different to what the situation was when I was with MIUI is that now when I type "adb shell" I am not automatically root (don't have # but $ at the console). When I do "su", the $ changes to #, which basically means that I am root.
I guess rumrunner has a requirement that you are root by default when logging via adb shell.
Any idea on a fix?
Best,
Wisher
Click to expand...
Click to collapse
Did you select the option to install root when you flashed the rom?
Danny201281 said:
There's nothing wrong with paying for s-off. I have purchased Sunshine myself when necessary, and made regular donations to other devs. but it's only fair to inform people of there options before you land them with a $25 solution not everyone has money to spare for that sort of thing. :good:
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
You should try rumrunner with the Rom @Seanie280672 posted to gain s-off. Not guaranteed to work as HTC started patching firmware at this point but if you need 100% stock it's your best chance to s-off without Sunshine.
If rumrunner won't work Sunshine is still cheaper than paying for the repair, and when you get your device back you can use Sunshine again for free, as long as it is the same device and not a replacement :good:
Did you select the option to install root when you flashed the rom?
Click to expand...
Click to collapse
Thanks for the info.
I did select to have the phone rooter.
However, I remembered that I forgot to switch fastboot off while testing rumrunner with the ROM from @Seanie280672.
I have now disabled this and am trying again. If it doesn't work, will reinstall the ROM again with CWM and *make sure* to have super user privileges (although I do have the Superuser app installed now just after flashing.)
I also remember that I had some super user issues when I was trying to install MIUI and had to install some zip via CWM. I still have that zip so will try with it.
Again, thank you VERY VERY much for helping me out!
Best,
Wisher
WisherBG said:
Thanks for the info.
I did select to have the phone rooter.
However, I remembered that I forgot to switch fastboot off while testing rumrunner with the ROM from @Seanie280672.
I have now disabled this and am trying again. If it doesn't work, will reinstall the ROM again with CWM and *make sure* to have super user privileges (although I do have the Superuser app installed now just after flashing.)
I also remember that I had some super user issues when I was trying to install MIUI and had to install some zip via CWM. I still have that zip so will try with it.
Again, thank you VERY VERY much for helping me out!
Best,
Wisher
Click to expand...
Click to collapse
your better off using TWRP recovery to flash the rom, there should be an option to root during the installer, but if there isnt then TWRP will ask you if you would like to root before leaving recovery.
Seanie280672 said:
your better off using TWRP recovery to flash the rom, there should be an option to root during the installer, but if there isnt then TWRP will ask you if you would like to root before leaving recovery.
Click to expand...
Click to collapse
Did it via CWM, made sure to select to root the phone. Still, I can do "su" when in the phone shell via adb, but it won't be directly with root access after "adb shell".
Now will try with TWRP (since installing the guru reset rom also resets the recovery to the HTC stock) and report back.
Good thing is I still have the MIUI backed up to use with CWM.
I will write soon.
Best,
Wisher