So I was an idiot and wrote S-On to my phone before I was finished flashing the RUU. I have tried firewater (obtained with Wayback Machine) and rumrunner, and both failed. I am on an old version of AHRD and HBoot 1.56. Every time I try to flash the latest RUU (6.10.531.10) from htc.com, it fails with Error 155 after trying to check the signature. I have also tried extracting the rom.zip and flashing that, but I get the same result (fails after trying to check signature).
I have tried S-OFFing with every method I've found. Using Arch Linux, using Windows, using old ROMs, new ROMs, AOSP, Sense, making sure I always use an unsecured kernel, etc. firewater deletes itself every time I try to run it, and rumrunner fails after 8 tries. I don't want to spend $25 on SunShine, so I'm looking for every alternative.
Phone info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [removed]
(bootloader) imei: [removed]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(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
iwasaperson said:
So I was an idiot and wrote S-On to my phone before I was finished flashing the RUU. I have tried firewater (obtained with Wayback Machine) and rumrunner, and both failed. I am on an old version of AHRD and HBoot 1.56. Every time I try to flash the latest RUU (6.10.531.10) from htc.com, it fails with Error 155 after trying to check the signature. I have also tried extracting the rom.zip and flashing that, but I get the same result (fails after trying to check signature).
I have tried S-OFFing with every method I've found. Using Arch Linux, using Windows, using old ROMs, new ROMs, AOSP, Sense, making sure I always use an unsecured kernel, etc. firewater deletes itself every time I try to run it, and rumrunner fails after 8 tries. I don't want to spend $25 on SunShine, so I'm looking for every alternative.
Phone info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [removed]
(bootloader) imei: [removed]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(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
Click to expand...
Click to collapse
You might try an older RUU 5.14.531.1 first before the newer RUUs.
As far as obtaining S-OFF, with your hboot Sunshine is your best option.
Related
Hi there,
I came from CM 10.1.1 by Lloir and tried to get back to Stock.
I flashed the original boot.img the stock recovery, relocked the bootloader and used every RUU exe listed in the Device essential material section.
Everytime I get the Error 140 "Bootloader Version Error".
My version-main is 1.17.401.3. The latest available RUU exe has 1.17.401.1... is this maybe why it doesn't works?
Here is my data:
fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.40.0000
(bootloader) version-baseband: 3.1204.168A.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.17.401.3
(bootloader) serialno: FA2AVW102321
(bootloader) imei: 353567050732099
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3820mV
(bootloader) devpower: 56
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
... I have read other threads where people had the same error code, but all of their solutions didn't work for me and I was dumb enough to not do a nandroid backup having STOCK RUU.
As long it doesn't work I can use CM 10.1.1... I have only to flash the right boot.img for CM for that time, so I can use the phone.
Has anyone an idea how I can solve this problem and get back to stock?
Best regards.
I've been having trouble applying the OTA update and also doing an RUU back to 4.3. Both fail w/unknown errors (stock recovery or TWRP). I just realized that doing a GetVar All in fastboot locks up. All I get is the below. Any idea what might cause this? All I did when I got the phone was unlock the bootloader via HTC and install TWRP for recovery.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4233mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
The 'too many links' error is just the nature of 1.44 hboot and the error is harmless.
BTW, if you ever think you'll want s-off go ahead and do that using revone before updating.
*Sorry for bad English*
So i have my htc one (m7), and i was trying to get it back to stock htc sense, because is was on cyanogenmod and i didn't really like it. i have used the tutorial from htc-one.wonderhowto .com ... I followed all the steps (relocked bootloader and downloaded HTC program), but the RUU wasn't compatible, i didn't know that at the time. So I was searching for another RUU, but I coudn't find a one to fit my device.
This is what *fastboot getvar all* gives me:
(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-ON
(bootloader) serialno: SH35WW909931
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
As you can see, i currently have s-on, and i can't find a proper RUU. So i tryed if there was a way to set my s-on to s-off. but i can't do that with rumrunner, since i am not able to uncheck *fastboot* in android settings, because i can't boot. Note: i have Clockworkmod Recovery installed. I live in the Netherlands.
Can anyone help me with this? i'm new to all this info so i dont know if there is an other way to simply install the stock htc rom.
I have recently decided to root my HTC one m7 to install stock android and failed, i installed kernels and roms but i didn't know i had to have s-off now my phone is in a boot loop.I have tried too install the ruu files but with no success so i am asking for someone to help me.
(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:
(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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4074mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You don't have to S-Off to install custom roms and kernels, it just makes it easier to install. To install while S-On, you must extract the boot.img file from the rom zip and install via fastboot while in bootloader mode. If you are trying to restore to stock with an RUU, you must relock the bootloader or the RUU won't run properly and fail.
Repy
I have re-locked and tried to install my ruu file but it always fails saying that my phone got disconnected .Also my "version-main" is blank.
I managed to fix it thanks for your reply es0tericcha0s you have finished my 3 day ordeal.
I have a bone stock M8 on Marshmallow. It suddenly started having com.htc.contacts errors and the phone becomes unavailable. I've done multiple recoveries, resets and cache clearing. Sometimes it comes back for awhile but soon eras out. I chatted with HTC support and they suggested reloading the rom so I downloaded the AT&T version and did all the steps per the instructions and started the update. It gets stuck on the "sending" stage and never completes. Reading the forum I saw Sync Manager can be a blocker so I didn't do it through that but no go. Am I missing something? Thanks I searched but didn't find this.
I assume you actually have the AT&T version M8?
If so, RUU stuck "sending" is common. You may need to find a Win7 PC with USB 2.0, which has the best chance of compatibility.
Back to Stock
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?