I had someone inexperienced bring me this phone which they botched. They were able to use htcdev and unlock the bootloader and install TWRP, but that is all. No s-off. They must have wiped it because there is no OS on it and they want it back to stock now. So, I figured I would relock the bootloader and flash the most current ota. Nope. It isn't having it. I tried the 3.28 ota but after the check in hboot, it reads "checking" with "press power to reboot" over the top of the text. I have tried other ruu's and zips only to get checksum errors or signature verification errors. I forgot to mention that when twrp was installed, not a single custom rom would intall. They all failed. The person that brought it to me did mention something about trying to get to the google play edition firmware but they didn't know much about it. Does anyone have any ideas on where I can go from here? Anything would be very helpful. Thank you!
adb getvar all, and tell us hboot number, radio, verify it is s-on, and also what is CID?
What RUUs did you try?
Which 3.28 OTA did you try? One hasn't been released by AT&T yet.
redpoint73 said:
adb getvar all, and tell us hboot number, radio, verify it is s-on, and also what is CID?
What RUUs did you try?
Which 3.28 OTA did you try? One hasn't been released by AT&T yet.
Click to expand...
Click to collapse
C:\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45FWM10802
(bootloader) imei:
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
I have tried all the att ruu's and the unbranded 3.28. In twrp I tried sense and non sense roms, all of which failed.
Delete your IMEI from the post, as this is private info.
Sorry, I should have mentioned to delete the IMEI. Although I did not request to cut and paste all the getvar data.
EDIT: Reported to mods, and they deleted the IMEI.
---------- Post added at 03:35 PM ---------- Previous post was at 03:30 PM ----------
In bootloader, you've verified the bootloader is relocked?
Also, you tried the 2.23 RUU? I know you said you tried "all" the RUUs (it helps to be specific and list everything individually). But I ask because this RUU was released, but now its not listed on HTC's support site (as the OTA was pulled due to battery drain issues) so some people think the RUU itself was also "pulled". Although the direct RUU download still exists and works:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Also, you can try the bootable RUU, which some folks have had better luck with: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Or another approach: What version of TWRP? Some older versions were known to have some flashing issues for some folks. Any specific error messages?
With bootloader unlocked, try to fastboot erase cache, and fastboot flash the latest TWRP. Or try Philz recovery. Then try again to flash a ROM.
whoops, I forgot about the imei. Thanks. Yes, I tried 2.23 and it read no image or wrong image. I will unlock the bootloader again and install the most current twrp and give it a try. anything helps. thanks!
iRootAll said:
I tried 2.23 and it read no image or wrong image.
Click to expand...
Click to collapse
Did you try the bootable version I linked?
Have you tried installing the latest TWRP, wipe the phone and flash a nandroid backup?
Related
Trying to get an RUU to run to update the HTC One M7 from T-Mobile. I've tried both the 3.24 that the phone has, and the 4.xx new one from the Original Android Dev forum. Both of them fail. 3.xx when trying to verify information, and 4.xx after step 1/5 pushing boot. 4.xx gives error 171 USB issue. I've got the drivers installed, as well as ADB and Fastboot. It connects to the phone and the RUU file reboots it, but instead of going to bootloader it goes to a black screen with HTC in silver, then the RUU on the computer fails.
Any ideas what I might be doing wrong? I have fastboot/bootloader access, but can't boot past the HTC O1ne screen.
Edit: I GOT IT!!! If you're in the same spot as me, make sure to put the RUU in your ADB directory. It wasn't working for me, moved it, worked like a charm.
detox702 said:
Trying to get an RUU to run to update the HTC One M7 from T-Mobile. I've tried both the 3.24 that the phone has, and the 4.xx new one from the Original Android Dev forum. Both of them fail. 3.xx when trying to verify information, and 4.xx after step 1/5 pushing boot. 4.xx gives error 171 USB issue. I've got the drivers installed, as well as ADB and Fastboot. It connects to the phone and the RUU file reboots it, but instead of going to bootloader it goes to a black screen with HTC in silver, then the RUU on the computer fails.
Any ideas what I might be doing wrong? I have fastboot/bootloader access, but can't boot past the HTC O1ne screen.
Click to expand...
Click to collapse
Are you S-On or S-Off? Do you have stock recovery? Is your MID and CID the same as the RUU? Is your bootloader "Locked"? Do you have the stock hboot for the RUU you are trying to run? The hboot has to be the same or lower than hboot in the RUU!
majmoz said:
Are you S-On or S-Off? Do you have stock recovery? Is your MID and CID the same as the RUU? Is your bootloader "Locked"? Do you have the stock hboot for the RUU you are trying to run? The hboot has to be the same or lower than hboot in the RUU!
Click to expand...
Click to collapse
Everything is stock. The co-worker never bothered with rooting/etc. S-On. T-Mo phone using a T-Mo RUU. Locked bootloader. Pretty sure the hboot is the same as well.
detox702 said:
Everything is stock. The co-worker never bothered with rooting/etc. S-On. T-Mo phone using a T-Mo RUU. Locked bootloader. Pretty sure the hboot is the same as well.
Click to expand...
Click to collapse
Reboot to bootloader (FASTBOOT USB), then run the command: fastboot getvar all This will tell you the id information about the phone. There may be some light shed on the status of the phone.
majmoz said:
Reboot to bootloader (FASTBOOT USB), then run the command: fastboot getvar all This will tell you the id information about the phone. There may be some light shed on the status of the phone.
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(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: 4312mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
C:\adb>
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
C:\adb>[/QUOTE]
First of all please remove the serialno and imei from your original post. Nothing looks out of the order. Could the RUU be corrupt? Check the MD5 checksum just to be sure. Or download another RUU from a different site. I have used this site's RUU in the past.
majmoz said:
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
C:\adb>
Click to expand...
Click to collapse
First of all please remove the serialno and imei from your original post. Nothing looks out of the order. Could the RUU be corrupt? Check the MD5 checksum just to be sure. Or download another RUU from a different site. I have used this site's RUU in the past.[/QUOTE]
I apparently got it. Moved the file from C:\Downloads to C:\adb, ran it, success. Thanks for the pointers, though.
Hey guys,
My HTC One(ATT) is stuck in the HTC One logo screen. This happened earlier as well but fixed it through RUU. Since then i got upgrade from at&t to the latest 5.12.502.2 with Sense 6.
Tried with the earlier RUU but didnt work. So i am looking for RUU for the latest att update.
Can you please help me with this !!!
Thanks!!!
diganthshah said:
Hey guys,
My HTC One(ATT) is stuck in the HTC One logo screen. This happened earlier as well but fixed it through RUU. Since then i got upgrade from at&t to the latest 5.12.502.2 with Sense 6.
Tried with the earlier RUU but didnt work. So i am looking for RUU for the latest att update.
Can you please help me with this !!!
Thanks!!!
Click to expand...
Click to collapse
I haven't seen an RUU for 5.12.502.2 available anywhere yet. The last official RUU from AT&T was 3.17.502.3. The 4.18.502.7 RUU that's floating around apparently wasn't an official release and many people were having problems with it. If you are S-Off, use the 3.14.502.3 RUU then you can OTA up to the latest version.
sharksfan7 said:
I haven't seen an RUU for 5.12.502.2 available anywhere yet. The last official RUU from AT&T was 3.17.502.3. The 4.18.502.7 RUU that's floating around apparently wasn't an official release and many people were having problems with it. If you are S-Off, use the 3.14.502.3 RUU then you can OTA up to the latest version.
Click to expand...
Click to collapse
I will give the official one a shot and see if it works.. will update the results soon..
sharksfan7 said:
I haven't seen an RUU for 5.12.502.2 available anywhere yet. The last official RUU from AT&T was 3.17.502.3. The 4.18.502.7 RUU that's floating around apparently wasn't an official release and many people were having problems with it. If you are S-Off, use the 3.14.502.3 RUU then you can OTA up to the latest version.
Click to expand...
Click to collapse
I tried 3.17.502.3 .. doesn't work..
Below is the info of my device.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502&2
(bootloader) version-misc: PVT SHIP S-ON
(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: 4226mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I am not sure if this doesnt work as it is S-ON.
Original issue was "STUCK AT HTC ONE LOGO SCREEN" .. how can i proceed next ??
Thanks!!
First off. Edit your post above and remove the serial# & imei.
The RUU isn't working b/c you're S-On and on an HBOOT higher than the one in the RUU. You need to be S-OFF to downgrade. Your bootloader is locked as well. Have you ever unlocked the bootloader and flashed a custom recovery? If not, I guess the next thing to try is to do a factory reset from HBOOT. You'll lose all your data but I don't think there is a way around that at this point. But since you were trying to run the RUU I guess you've already resigned yourself to that.
Another route to take is to unlock your bootloader, flash a custom recovery, then a custom ROM.
You might want to wait for other people to chime in. Perhaps they'll have other ideas.
diganthshah said:
I tried 3.17.502.3 .. doesn't work..
Below is the info of my device.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
I am not sure if this doesnt work as it is S-ON.
Original issue was "STUCK AT HTC ONE LOGO SCREEN" .. how can i proceed next ??
Thanks!!
Click to expand...
Click to collapse
I just saw this are you still stuck ?
The easy answer is to unlock the bootloader and flash TWRP 2.6.3.3 and flash my Guru_ reset being your already on the current firmware.
If you don't want to flash the recovery again after the reset just choose no to installing stock recovery and radio and Yes to Root
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload the Rom to your phone
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
I recently found out that the only way to obtain S-Off now is to pay $25. Before I do this I'm curious to know if I even need to do that before I flash a ROM. I'm already rooted. Can't I just load the ROM onto my phone, go into recovery and flash from their? Do I really need to pay the $25?
sock00 said:
I recently found out that the only way to obtain S-Off now is to pay $25. Before I do this I'm curious to know if I even need to do that before I flash a ROM. I'm already rooted. Can't I just load the ROM onto my phone, go into recovery and flash from their? Do I really need to pay the $25?
Click to expand...
Click to collapse
You dont have to pay to obtain S-Off unless youre already on 4.4.3 in which case you'd need sunshine, just read around the forum and you can figure out how to with firewater. Its not hard you just have to do a little research. But to answer the question, yes you have to be S-Off to install custom ROMs. Here is a link to firewater http://forum.xda-developers.com/showthread.php?t=2708464
S-ON and Custom ROM's
CavyS said:
You dont have to pay to obtain S-Off unless youre already on 4.4.3 in which case you'd need sunshine, just read around the forum and you can figure out how to with firewater. Its not hard you just have to do a little research. But to answer the question, yes you have to be S-Off to install custom ROMs. Here is a link to firewater http://forum.xda-developers.com/showthread.php?t=2708464
Click to expand...
Click to collapse
I'm new to modding, and definitely still learning but am unclear on your above statement, I have HTC One (M8) 2014. Rooted SuperSu running Android Revolution HD 8.1 custom ROM. It seems I am S-ON because I am not able to flash my hboot (to remove red development text). I receive FAILED (remote: 99 unknown fail). Based on what I'm reading I am S-ON and running a custom ROM. AR HD 8.1 is based on kitkat 4.4.2. Joined today and searching for more answers. Thanks and Cheers!
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: RUU
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
shadowsports said:
I'm new to modding, and definitely still learning but am unclear on your above statement, I have HTC One (M8) 2014. Rooted SuperSu running Android Revolution HD 8.1 custom ROM. It seems I am S-ON because I am not able to flash my hboot (to remove red development text). I receive FAILED (remote: 99 unknown fail). Based on what I'm reading I am S-ON and running a custom ROM. AR HD 8.1 is based on kitkat 4.4.2. Joined today and searching for more answers. Thanks and Cheers!
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: RUU
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse
You have to be S-Off to flash hboot. Also make sure your modid and cid match up to the hboot you are flashing.
CavyS said:
You have to be S-Off to flash hboot. Also make sure your modid and cid match up to the hboot you are flashing.
Click to expand...
Click to collapse
My mod and cid both match. My issue is indeed my S-ON status. My comment was in regards to your statement that you must be S-OFF to flash custom ROMs which does not appear to be true.
I unlocked my device using HTCdev unlock. I'm still running stock FW which is why (I believe) I am S-ON. I thought unlocking my device would provide S-OFF but that does not appear to be the case as "get var" tells the story. Thanks for the reply.
shadowsports said:
My mod and cid both match. My issue is indeed my S-ON status. My comment was in regards to your statement that you must be S-OFF to flash custom ROMs which does not appear to be true.
I unlocked my device using HTCdev unlock. I'm still running stock FW which is why (I believe) I am S-ON. I thought unlocking my device would provide S-OFF but that does not appear to be the case as "get var" tells the story. Thanks for the reply.
Click to expand...
Click to collapse
Ah, yeah I was wrong in that case. I though I read while flashing VenomOne that you had to be S-Off to use it. Now that I look at it though, its only certain ROMs you have to S-Off for since when you flash VenomOne it also flashes HBoot.
CavyS said:
Now that I look at it though, its only certain ROMs you have to S-Off for since when you flash VenomOne it also flashes HBoot.
Click to expand...
Click to collapse
You sure about that? It would be highly unusual (and actually a little scary) for any ROM to touch hboot. I don't follow ViperOne closely (Venom is the team, Viper is the ROM) so maybe I'm missing something. Can you link where you see that ViperOne does something to hboot?
---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------
shadowsports said:
I unlocked my device using HTCdev unlock. I'm still running stock FW which is why (I believe) I am S-ON. I thought unlocking my device would provide S-OFF but that does not appear to be the case as "get var" tells the story.
Click to expand...
Click to collapse
Bootloader unlock has nothing to do with s-off. They are completely different things. Bootloader unlock allows install of custom recovery, flashing ROMs, kernels, root, and some other things.
S-off is needed to modify hboot, radio, and some other partitions. It means "all security off" so in many cases it also bypasses bootloader unlock, and other checks. You need to either use firewater or sunshine methods to get s-off. Most likely sunshine, as most folks have not had success with firewater; except mostly on older M8's (where fireware still worked fine). Although there have been some isolated cases of newer devices working with firewater, which is free so its worth a try (and it takes about 5 or 10 minutes to try if you are already rooted and have adb setup).
You don't need s-off to flash custom ROMs. Meaning the ROMs will still flash fine. But there is a slight caveat, in that if you are on old firmware (hboot, radio, plus other modules like WiFi, Bluetooth, media and others) from 1.xx based OS software, and try to use a 2.xx based ROM, they will not play together well and you will suffer some serious issues including long boot times (5-10 min), or broken WiFi or Bluetooth.
So while a 2.xx ROM will flash fine with s-on (in literal terms), you most likely will get some issues (maybe even making the ROM not usable) unless you update the firmware (which does require s-off).
You can update the firmware either by "unofficial" means with s-off and flashing an updated firmware. Or you with s-on, you can install the 2.23 AT&T OTA or RUU.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *removed*
(bootloader) imei: *removed*
(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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.058s
I am stuck, I can't see to get my phone to boot. You would think that I would be able to do something to fix this if I can get into recovery and bootload, but I can't get a proper system boot. I am hoping that buying a new phone isn't my only option at this point. If anyone can help me I am willing to pay if you can help me get a working phone again.
@Jameskhunter
You should edit your IMEI number out of your getvar
What exactly happened when you flashed the firmware ,any specific message that came across that you can remember
According to the getvar it looks like you flashed the GPE lollipop firmware/ruu without
S-OFF.
---------- Post added at 03:47 AM ---------- Previous post was at 03:37 AM ----------
Try this .exe of the stock ruu sense your At&t
http://forum.xda-developers.com/showthread.php?t=2860423
GPE firmware
jball said:
@Jameskhunter
You should edit your IMEI number out of your getvar
What exactly happened when you flashed the firmware ,any specific message that came across that you can remember
According to the getvar it looks like you flashed the GPE lollipop firmware/ruu without
S-OFF.
---------- Post added at 03:47 AM ---------- Previous post was at 03:37 AM ----------
Try this .exe of the stock ruu sense your At&t
http://forum.xda-developers.com/showthread.php?t=2860423
Click to expand...
Click to collapse
That is what I have been told although I didn't realize that it was GPE and I don't really understand why it let me get my phone in an usable/unrecoverable state if I had s-on. I thought that was a safety net, but the more I read I wish it was s-off. I think it would be fixable then, but in the current state I don't know how to get s-off. I did the firmware command twice and it seemed to work after the second attempt as the article noted that it would. I have never flashed a rom, before so other than reading the article and attempting to follow along didn't really know what to expect. The article had me do a fastboot oem lock and then a fastboot oem ruu as I recall. then it was something like fastboot flash zip .....zip. The problem is the roms that I have attempted to install now don't seem to install maybe if I could find the right one it would install and work good enough to allow me to become s-off and get back to more of a working state. I should of done a lot more reading before attempting this... I made some invalid assumptions about being able to recover which is my fault. I would think something is possible in this state.
I think part of the problem is that I am s-on and my main ver is higher than the RUU for my carrier version and my cid. I think I could edit those if I was s-off or do something, but I can't do that since I am s-on.
Hi
Jameskhunter said:
That is what I have been told although I didn't realize that it was GPE and I don't really understand why it let me get my phone in an usable/unrecoverable state if I had s-on. I thought that was a safety net, but the more I read I wish it was s-off. I think it would be fixable then, but in the current state I don't know how to get s-off. I did the firmware command twice and it seemed to work after the second attempt as the article noted that it would. I have never flashed a rom, before so other than reading the article and attempting to follow along didn't really know what to expect. The article had me do a fastboot oem lock and then a fastboot oem ruu as I recall. then it was something like fastboot flash zip .....zip. The problem is the roms that I have attempted to install now don't seem to install maybe if I could find the right one it would install and work good enough to allow me to become s-off and get back to more of a working state. I should of done a lot more reading before attempting this... I made some invalid assumptions about being able to recover which is my fault. I would think something is possible in this state.
I think part of the problem is that I am s-on and my main ver is higher than the RUU for my carrier version and my cid. I think I could edit those if I was s-off or do something, but I can't do that since I am s-on.
Click to expand...
Click to collapse
I have tried that RUU and it fails, I think because its main version number is lower than mine now... Which I also didn't realize was a limitation. I think the lesson here is to never flash firmware that isn't directly from the htc site although its suppose to be signed, that's a little confusing to me.
I to thought S-ON was supposed to be a safety net
What Roms have you tried sense then
If you hold power+up your phone hard restarts. then quickly hold power+down. then go to recovery. If have TWRP and this way you accessed it. you got some chance. go to https://download.cyanogenmod.org/?device=m8 and download latest nightly and see if you can flash it. That worked for me. Until I find a signed firmware/radio that is version 4.+ I am stuck with cm12.
Hello all,
I've been browsing the forums for a few days now trying to fix my issue, but nothing I have found seems to be of much help, so I have decided to register here myself and get some assistance directly.
So, I rooted my phone and flashed twrp and cyanogenmod. After several bugs and overall irritation, I have decided to just go back to stock recovery, ROM, etc. (After all, I am a mechanical engineer - software is not my forté.)
In attempting to unroot my device, however, it seems that I just messed things up even further.
Steps taken:
1) Rebooted device into fastboot
2) fastboot oem lock
3) Reboot into RUU mode (black screen w/ htc logo)
4) Ran RUU.exe
5) (bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 35.173s
At this point, I thought that maybe it was because I was still S-ON so I was going to place rumrunner on the virtual SD. Now my PC won't recognize my phone, so I don't know how to flash rumrunner to go to S-OFF or if that's even the correct next step. So basically, I have bootloader and twrp, and that's it.
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35ZW915640
(bootloader) imei: 354439051027912
(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: 3658mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
MJGiuffre said:
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Click to expand...
Click to collapse
wrong way
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
there is no ruu for your sofware, older one will not work its just how htc are made, try this ruu its the latest.( make sure you are not supercid before running it, it can mess up the phone) from your first post it looks like you are fine unless u changed it to supercid.
http://dl3.htc.com/application/RUU_...06_10.46.1718.01L_release_424933_signed_2.exe
it should work at least it worked on mine
---------- Post added at 03:07 PM ---------- Previous post was at 03:00 PM ----------
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
also u can try one of the guru resets that matches your software , or look for a stock unrooted nandroid for att htc one , u need the 5,12 sofware , older one may not work properly. also before runing a ruu make sure your bootloader is loked or relocked. good luck.