This thread is related to another thread that I posted a few months ago. Sorry for reopening just didn't know what to do since it is an old thread.
Before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3819mV
(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
CURRENT STATE:
VZW Htc One (m7) *** TAMPERED ***, ***RELOCKED*** S-ON
This all started when using revone with a different firmware/hboot then the tutorial I was watching.
Any ideas at all before I quit completely?
HunterT said:
This thread is related to another thread that I posted a few months ago. Sorry for reopening just didn't know what to do since it is an old thread.
Before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3819mV
(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
CURRENT STATE:
VZW Htc One (m7) *** TAMPERED ***, ***RELOCKED*** S-ON
This all started when using revone with a different firmware/hboot then the tutorial I was watching.
Any ideas at all before I quit completely?
Click to expand...
Click to collapse
Can you boot into a rom? You are on 1.56 so if you can, you will be able to use firewater to get back to s-off.
If you can't boot up.......idk you might be screwed, not sure there is a signed RUU available for hboot 1.56.
To send back to verizon you should have flash an RUU, then switched back on locked and s-on after the RUU. Not taking any updates so you can redo the s-off if needed.
If you can't boot up from where you are at, you might be screwed, short of getting someone with a java card to crack it.
HunterT said:
This thread is related to another thread that I posted a few months ago. Sorry for reopening just didn't know what to do since it is an old thread.
Before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3819mV
(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
CURRENT STATE:
VZW Htc One (m7) *** TAMPERED ***, ***RELOCKED*** S-ON
This all started when using revone with a different firmware/hboot then the tutorial I was watching.
Any ideas at all before I quit completely?
Click to expand...
Click to collapse
Screwed man. Java card. Jtag. . Wait eternally for a signed encrypted ruu.
Sorry. S on and locked on vzw is not good
If you download the latest RUU posted in the development section and you can use a cool tool called ruuveal to recrypt it if you need to RUU your device without having s-off.
synisterwolf said:
If you download the latest RUU posted in the development section and you can use a cool tool called ruuveal to recrypt it if you need to RUU your device without having s-off.
Click to expand...
Click to collapse
Unfortunately that won't work.
As 're-encrypting it will not create the HTC signatures required for flashing to an s-on device.
santod040 said:
Unfortunately that won't work.
As 're-encrypting it will not create the HTC signatures required for flashing to an s-on device.
Click to expand...
Click to collapse
Removed by request.
Sent from my iPhone 5s using Tapatalk pro
synisterwolf said:
Actually the tool injects the signature during the encryption process and works as intended. I've done this a few times on a HTC One, Fireball, Max, thunderbolt, and sonic.
I will not post the re-encrypted file on xda due to other members being hit with DCMA takedowns and its against XDA rules.
Spoiler:
Google search will find what I've done and any user with a Linux machine can duplicate what I've posted above. That's all I will be saying on the subject so I don't jeopardize my ability to stay on this site.
Sent from my iPhone 5s using Tapatalk pro
Click to expand...
Click to collapse
Hmm, last I checked it wasn't able to re-create HTC's RSA signatures.
But that's very cool that you have been able to do so.
I think at the very least, that you would have to start with an actual RUU though, not just a zipped up dump of partitions, as is the kk ruu we currently have. Maybe I'm wrong.
But since that wasn't an actual RUU to begin with, you are saying the tool creates an HTC signature on its own?
Last I knew, the creator posted this regarding signatures:
The leading 256 bytes is the signature of the zip file, you'll need to disregard it. There's no way we can sign the zip correctly without HTC's private key.
The differing 5 bytes are the bytes I talked about.
The trailing bytes are probably a bug - I'll investigate further when I get some time but it's not a priority since it's not causing HBOOT to fail to flash the zip.
Thanks for the detailed analysis/comparison :+1:
I'm going to merge the encrypt branch onto the master branch in the next few days since it seems to be working okay.
Click to expand...
Click to collapse
Not in any way trying to argue or anything like that, just honestly didn't think it was possible to replicate an HTC signature,.
If I'm wrong, then that's great!
Related
Ok, I feel insanely stupid, but last night I flashed LiquidSmooth on my phone and everything looked awesome. I didn't realize it until this morning that the sound doesn't work on the phone (my alarm didn't wake me up), and out of curiosity, I started digging around and realized that it wasn't able to play videos and the microphone didn't work for any apps. As I looked online, I realized that I needed to update my firmware to get my functions back. Since I haven't done this before, I jumped online and followed along with a guide that told me to run the command 'fastboot oem lock' before I flashed the firmware. It was early, so I didn't think about it until I hit enter and then realized that I just relocked my phone that runs off of an unlocked recovery/ROM.
Upon booting, it shows the bootloader screen:
*** TAMPERED ***
***RELOCKED ***
***Security Warning***
M7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-1.12.42.0906
OpenDSP-v31.120.274.0617
OS-1.10.605.10 (1.10.605.15)
eMMC-boot 2048MB
Nov. 8 2013....
If I choose to try to go into the bootloader, it reboots the device and ends up right back at FASTBOOT. The only other screen I am able to get it into is the black HTC bootloader (fastboot reboot oem rebootRUU).
I've done some research on it, and it looks like I absolutely must unlock the bootloader before I can do anything, but without being able to boot into adb to run Firewater, I can't think of any other way. I feel like the OS 1.10.605.10 being red is what stands out to me, but I am unable to find a 1.10.605.10 signed/encrypted RUU to flash to it (anything unsigned fails). Also, here is the getvar information that I cam coming up with -
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.0906
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXX
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4283mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-fb8d0c81
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.083s
If anyone has any tips or ideas on where to go from here, please let me know! Thanks a ton in advance!
http://forum.xda-developers.com/showthread.php?t=2485319
Near bottom of second post is a link to the ruu for the version of your firmware so you can use rumrunner to s-off and unlock again. Be sure to download the signed one. You would flash it in ruu mode (fastboot oem rebootRUU, then fastboot flash zip ruu.zip twice to successfully flash the ruu). You could use the 4.4.3 s-on ruu, but then to unlock and s-off you would have to use sunshine.
Sent from my HTC6500LVW using XDA Free mobile app
Thank you!
I couldn't find the signed firmware anywhere else, so I nearly gave up. This totally worked and my phone is now alive and well!
Hi guys, i screwed up .... Was trying to go back to STOCK version and i think i screwed up the sensors --> Auto-Rotate doesn't work, Flashlight too, take 2 seconds to show the screen if it was off --> (by clicking the power button), double tap doesn't work too.
So i tried to go to stock, erase everything etc .... Nothing is working. Any help ? Please ...
Hello,
I would like to help, but you must provide much more details about what happened. How did you go about getting back to stock? From which rom? to which rom? Can you do a "get var all"?
Cheers
The "getvar all" as requested :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
bootloader screen :
*** Software status: Official ***
*** RELOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12.G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015, 14:15:28.0
and i don't really remember from which rom to which rom... Sorry...
Excellent, you're on the international version. However, your post includes some private information (unique identifiers) that -for your privacy and safety - shouldn't be posted. Please, either delete your post, or edit it to remove the serial number and imei.
Many people have complaints about the latest update to marshmallow, with similar system problems. For example, sensors not working properly, camera malfunction, screen malfunction, inaccessible internal & external memories, and or, sudden death
My proposed solution is simple: RE-flash your firmware & rom from stock source, then hardreset your phone to factory condition.
Cheers.
BloodyMoon95 said:
The "getvar all" as requested :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
bootloader screen :
*** Software status: Official ***
*** RELOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12.G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015, 14:15:28.0
and i don't really remember from which rom to which rom... Sorry...
Click to expand...
Click to collapse
Edited the message. Ok, your solution seems feasible. But could you guide me in every step of it? I think i am always messing up a step without realizing it.
BloodyMoon95 said:
Edited the message. Ok, your solution seems feasible. But could you guide me in every step of it? I think i am always messing up a step without realizing it.
Click to expand...
Click to collapse
Following is a link to HTC's official stock RUU, and instructions to flash it. This will install your phone's current firmware/software from scratch.
https://www.androidfilehost.com/?fid=24369303960687057
To flash the RUU zip file:
A. You need to put it at the root of your SD CARD and rename it to 0P6BIMG.zip (first character is a zero, and careful not to rename it to 0P6BIMG.zip.zip)
B. Turn your phone off, then start it into bootloader. It will recognize the 0P6BIMG.zip file and give you instructions in RED for proceeding forward.
C. Follow the instructions in RED to flash. You will lose all data as the RUU will format all partitions.
Cheers
shirreer posted the best way to flash it, so I'm just gonna add here, I bought a GSM M8, originally an Australian variant (0P6B11000) and I S-OFF'd it and converted it to the Intl version with 6.12.401.4 and it's very stable, everything works fine, including double tap, flashlight, auto rotate and all other features. Only thing that sucks is the extremely horrible battery life, which was somewhat fixed with a re-calibration, but it still drains.
Ok i am gonna trying it AGAIN actually. Already done your solution. Last time i have done this, it was bypassing the sensor_hub, which is super weird. But i'll let you know. Downloading it right now, and going to flash it soon.
Edit After Flashing :
Sensor_hub; TP (2); SBL1 (3) are bypassed....
So yea... still same situation i flashed it as you said and explained. Sensor hub is bypassed. I hard reset as you said. Nothing changed... So basically .... i am screwed ....
No one has an answer for me ?..... Come on guys .... there must be something .... FYI bluetooth not working i think.
Hey folks!
A friend of mine sent me his smartphone to repair but i'm sitting in a corner right now...
I never had a HTC before, not in my hands, not received by any other person - first try so far.
Here's the situation:
The battery from the smartphone was empty over a night.
Next day, when he want to start - it doesn't start and runs into bootloader.
He tried some things i think, but isn't really familiar with that.
The phone said in bootloader:
*** Software status: Modified ***
*** UNLOCKED ***
S-ON
For now i followed this tutorial "htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/".
I already received the "Unlock_code.bin" and uploaded to the phone - seems working, because it says "Unlocked".
After that i flashed the "openrecovery-twrp-2.7.0.2-m8.img" - seems working, because it says "OKAY".
Than, i erased the cache, try to enter recovery, but it returns immediately to bootloader. :crying:
What i've done wrong?
Any hints what happens with the phone? How can i restore to stock easily?
He don't need special tools or anything else, just a working phone so far
ambiente1 said:
Hey folks!
A friend of mine sent me his smartphone to repair but i'm sitting in a corner right now...
I never had a HTC before, not in my hands, not received by any other person - first try so far.
Here's the situation:
The battery from the smartphone was empty over a night.
Next day, when he want to start - it doesn't start and runs into bootloader.
He tried some things i think, but isn't really familiar with that.
The phone said in bootloader:
*** Software status: Modified ***
*** UNLOCKED ***
S-ON
For now i followed this tutorial "htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/".
I already received the "Unlock_code.bin" and uploaded to the phone - seems working, because it says "Unlocked".
After that i flashed the "openrecovery-twrp-2.7.0.2-m8.img" - seems working, because it says "OKAY".
Than, i erased the cache, try to enter recovery, but it returns immediately to bootloader. :crying:
What i've done wrong?
Any hints what happens with the phone? How can i restore to stock easily?
He don't need special tools or anything else, just a working phone so far
Click to expand...
Click to collapse
That recovery version is very outdated. You were using an old tutorial.
If it were me, I'd find an RUU to run. What do you get from fastboot getvar version-main? Or better yet, post the results of fastboot getvar all minus the IMEI and serial#, and someone can direct you to the proper RUU
fastboot getvar version-main
version-main: 1.16.401.10
Click to expand...
Click to collapse
fastboot getvar all
(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: 1.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ******************
(bootloader) imei: ******************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__102
(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: 1d456ef7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Click to expand...
Click to collapse
ambiente1 said:
fastboot getvar version-main
fastboot getvar all
Click to expand...
Click to collapse
There's your problem. You don't have the M8. You have the M8S. The M8 recovery won't work on that.
The M8S has a separate forum here, and you can find the proper TWRP recovery for it in this thread.
You do have very old firmware though. Hopefully that recovery version will work as it is made for newer firmware. I think it will.
I may have been an idiot and managed to remove the OS from my phone, and cannot for the life of me figure out how to get it back to working order.
The bootloader screen displays the following
*** Software status: Modified ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-
eMMC-boot 2048MB
Nov 27 2015,01:21:29.0
fastboot getval all returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
And I have TWRP v2.7.0.2 on recovery.
I am at my wits end on this, so any help would be greatly appreciated.
Since it appears you are using the US unlocked version, why not use the Windows RUU to restore it? I don't have the link handy, but you can download it from HTC. Just put your device into download mode and go. It will blow away your recovery, but that's easy enough to restore.
jshamlet said:
Since it appears you are using the US unlocked version, why not use the Windows RUU to restore it? I don't have the link handy, but you can download it from HTC. Just put your device into download mode and go. It will blow away your recovery, but that's easy enough to restore.
Click to expand...
Click to collapse
I forgot to mention I tried that, and it errored out near the end. I think I may have managed to fix it by loading the rom from Insert-coin onto an SD card, and mounted it and installed through TWRP.
Its currently optimizing apps, so I think I should be home free at this point.
I feel kinda dumb by asking for help then figuring it out myself not long after, but it happens sometimes.
Voidablemelon said:
I may have been an idiot and managed to remove the OS from my phone, and cannot for the life of me figure out how to get it back to working order.
The bootloader screen displays the following
*** Software status: Modified ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-
eMMC-boot 2048MB
Nov 27 2015,01:21:29.0
fastboot getval all returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
And I have TWRP v2.7.0.2 on recovery.
I am at my wits end on this, so any help would be greatly appreciated.
Click to expand...
Click to collapse
Your "OS" and version-main are blank because there was a bug in the TWRP version you are using.
Update to TWRP v2.8.7.0 or newer, reflash your current firmware or update it if you haven't already, and your OS and version-main will show the version of firmware you are running again.
Voidablemelon said:
I forgot to mention I tried that, and it errored out near the end. I think I may have managed to fix it by loading the rom from Insert-coin onto an SD card, and mounted it and installed through TWRP.
Its currently optimizing apps, so I think I should be home free at this point.
I feel kinda dumb by asking for help then figuring it out myself not long after, but it happens sometimes.
Click to expand...
Click to collapse
Figuring out yourself is always better than anything else,don't you felt like Einstein or something when you did it yourself w/o any help?
Voidablemelon said:
I forgot to mention I tried that, and it errored out near the end.
Click to expand...
Click to collapse
If you tell us what RUU (exact file name) and the specific error number and error message, we can probably tell you why the RUU failed.
---------- Post added at 10:39 AM ---------- Previous post was at 10:25 AM ----------
Voidablemelon said:
I may have been an idiot and managed to remove the OS from my phone, and cannot for the life of me figure out how to get it back to working order.
Click to expand...
Click to collapse
Good job figuring it out yourself.
You're not an idiot (common mistake) but here are a few good rules to live by, when modding Android devices:
1) Always make a TWRP backup of your current ROM (and user data, if desired - but that's always a good idea too) and have it handy, so you can recover from such situations (no OS). That is one of the main functions an benefits of having TWRP, the ability to make backups and use them to recover.
If you have a TWRP backup, recovering from "no OS" is simply as booting into TWRP, and restoring the backup.
My typical recommendation, is to make a TWRP backup before root (so you have a backup of the "stock" unrooted ROM) and prior to every time you flash a new ROM, or flash other mods. That way, if any of those mods go wrong, you can still revert back to a "known good" configuration.
2) If you don't have a TWRP backup on hand, know how to flash a ROM to recover from "no OS" (now you know how!)
3) I'm guessing you wiped "system" in TWRP to cause no OS (this the most usual cause)? If so, be careful what you choose to wipe in the "Advanced" wipe options of TWRP. Don't wipe anything, if you don't know what it is, or what the result will be. You've probably already learned this lesson, to some extent.
Hi all,
I have an old HTC one m8 which was working fine when I stored it away last year. Today I tried to turn it on and found myself looking at safe mode menu with the heading
"Software status: Modified"
LOCKED
Security Warning
Now I have been going through the form for the last couple of hours trying different things but they dont seem to work.
e.g) I got a ver 4.20 RUU for my phone mentioned in this link
https://forum.xda-developers.com/htc-one-m8/help/finding-ruu-t3283633
but that does not work because my phone currently is on OS-6.13 and apparently I can not downgrade to OS-4 while my phone is S-ON. (I get ERROR 159 IMAGE ERROR)
So i tried to make it S-OFF. Unfortunately from what I have read they only way to do that is through the adb tool which does not work in the fastboot mode I am currently stuck on (fastboot commands work fine from my PC). So I can't downgrade to the only RUU I have found for my modelid and cid. I have no idea how to proceed now.
my phone specs
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___102
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any ideas?
mezomizz said:
apparently I can not downgrade to OS-4 while my phone is S-ON. (I get ERROR 159 IMAGE ERROR)
Click to expand...
Click to collapse
Correct. Downgrading is not allowed with s-on.
mezomizz said:
So i tried to make it S-OFF. Unfortunately from what I have read they only way to do that is through the adb tool which does not work in the fastboot mode I am currently stuck on (fastboot commands work fine from my PC).
Click to expand...
Click to collapse
There is no (current) valid method to s-off using adb. If you are talking about firewater, that method has not worked since 2014, and nothing you do will make it work.
The valid current method to s-off is with sunshine app ($25 US) but also requires a working OS.
You also do not need s-off to get the phone working again. Since a Marshmallow version RUU for your CID/MID is not available, you can restore the stock TWRP backup from the collection in the link below: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Unlock bootloader using HTCDev.com, install custom recovery TWRP, then restore the TWRP backup 6.13.206.5 using the instruction in the link above.