Develop Bugs

★ ☆ [MOD] Remove Red Text on Splash screen | hboots | m7vzw | Dark Boot

Does the red development text on the splash screen bother you after unlocking your device?
If so, I have a modified hboot for you that takes care of it.
This was simply hex edited by me to remove the text from the screen, no other changes were made.
I have tested it and it is 100% proven to work without any side effects.
FROM THIS >>>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TO THIS >>>
Let's get to it!
You must be S-Off to do this!
To Install:
Download your No Red Text hboot or Faux Locked hboot from the bottom of this post:
Modified 1.10.605.08 hboot
Modified 1.10.605.10 hboot
Modified 1.10.605.15 hboot
Modified 2.10.605.1 hboot
Modified 3.11.605.1 hboot
Modified 4.10.605.3 hboot
Modified 5.28.605.2 hboot
Modified 6.22.605.3 hboot
Modified 6.22.605.4 hboot
Modified 6.22.605.6 hboot *LATEST*​
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip nameoffile_hboot.zip (this flashes the modified hboot zip file)
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:​
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and not see the red text anymore.
If you have any questions or issues, let me know.
Now for my RED TEXT:
Disclaimer​You are aware that writing to the security protected partitions increases your risk to lose the device exponentially.
You understand and agree that i cannot be held responsible for such or any other damages.
The flash process is theoretically safe and tested, however you are the brains behind the wheel and you are solely responsible for the execution of the process.
I will not accept any responsibility. The method itself is developed by Google and HTC, i only provide access and information to it and you execute it.
You understand that you should not do it if you are not willing to accept this risk.
If you plan on reverting to stock-relocked, for any reason:
You should follow the above steps first, but use this Stock Restore hboot instead.
Do this before you relock the bootloader.​
-FAUX LOCKED HBOOTS-
(not really Locked and S-on but appear that way)
Since I initially posted this:
I had a couple requests for a modified hboot that shows the device as being Locked and S-On, while being completely unlocked and S-Off.
I went ahead and made that as per request and have tested it as well.
The process is the same as the one I wrote above, with the exception of the filename.
1.54 - 1.10.605.08 Faux Locked hboot.
1.54 - 1.10.605.10 Faux Locked hboot
1.54 - 1.10.605.15 Faux Locked hboot
1.55 - 2.10.605.1 Faux Locked hboot
1.56 - 3.11.605.1 Faux Locked hboot
1.57 - 4.10.605.3 Faux Locked hboot
1.xx - 5.28.605.2 Faux Locked hboot
1.61 - 6.22.605.3 Faux Locked hboot
1.61 - 6.22.605.4 Faux Locked hboot
- 6.22.605.6 Faux Locked hboot *LATEST*​
Enjoy and be careful!!
XDA:DevDB Information
Santods Hboot Mods - m7vzw, Tool/Utility for the Verizon HTC One
Contributors
santod040
Version Information
Status: Stable
Created 2014-08-19
Last Updated 2015-12-22

Dark hboot mod
DARK BOOTLOADER
I have modified and repackaged the Google Play Edition Dark Bootloader for safe flashing on the Verizon HTC ONE(m7)!
This was NOT originally made for the m7vzw.
You understand that although it has been well tested and used by me, that you are flashing this at your own risk!
Now that we got that out of the way, here is a picture of it and a download link!
Follow the same steps I outlined in the Original Post above.
ENJOY!
DOWNLOAD:
UPDATED from latest GPE 5.1 OTA - 09-17-15
Santods Dark Bootloader for m7vzw
Santods Dark Bootloader for m7vzw
​

dude awesome job!!
is this based off of the .8 hboot or the .10?

andybones said:
dude awesome job!!
is this based off of the .8 hboot or the .10?
Click to expand...
Click to collapse
Thanks, I didn't see any difference in the hboots though.
So it's just pulled from the decrypted .08 RUU and it works fine for either one. (tested)

santod040 said:
Thanks, I didn't see any difference in the hboots though.
So it's just pulled from the decrypted .08 RUU.
Click to expand...
Click to collapse
Perfect thank you so much!
this is awesome!

Done and done. Why does stuff like that make me nuts enough to jack with a perfectly good hboot? IDK. Thanks! Now If I can find a way to separate the ringer and notifications on a rom based on stock. It is my white whale.

I'm getting a dns error when trying to push the zip???

daddygene said:
I'm getting a dns error when trying to push the zip???
Click to expand...
Click to collapse
I've never heard of such an error trying to do a task such as this.
Are you trying to use usb/adb/fastboot through a Virtual Machine or wireless adb or something?
You should be able to flash the zip if you were able to get the device to boot into RUU mode via command prompt from previous step.
I'm not sure how to help you without more information about your configuration or the specific error.
Try and get a screen capture if you can't grab the output from the terminal.
That's the best I can tell you without more to go on.

santod040 said:
I've never heard of such an error trying to do a task such as this.
Are you trying to use usb/adb/fastboot through a Virtual Machine or wireless adb or something?
You should be able to flash the zip if you were able to get the device to boot into RUU mode via command prompt from previous step.
I'm not sure how to help you without more information about your configuration or the specific error.
Try and get a screen capture if you can't grab the output from the terminal.
That's the best I can tell you without more to go on.
Click to expand...
Click to collapse
See attached screenshot:

daddygene said:
See attached screenshot:
Click to expand...
Click to collapse
try putting fastboot in front of the flash line

Yea have to put fastboot. But thanks this is awesome
Sent from my HTC One VZW using Tapatalk 4

Thanks guys, seems I left that out, OP updated.

Doh! Stupid me. Thanks guys.

MD5
Can OP provide an MD5? I'm not about to flash an Hboot with making sure the file downloaded correctly!
Thanks so much in advance, and for making the Hboot available!
EDIT: Nevermind. It is in the link. Thanks!

Worked like a charm! Thank you!

santod040 said:
Does the red development text on the splash screen bother you after unlocking your device?
If so, I have a modified hboot for you that takes care of it.
This was simply hex edited by me to remove the text from the screen, no other changes were made.
I have tested it and it is 100% proven to work without any side effects.
FROM THIS
TO THIS
Let's get to it!
You must be S-Off to do this!
To Install:
Download this Modified hboot zip file. MD5: af8b71f96353aee0e6d64e190a19afc6
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip Santods_1.54_hboot.zip (this flashes the modified hboot zip file)
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:​
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and not see the red text anymore.
This WILL work on either the .08 or the .10 software version.
All Verizon HTC Ones, no matter what rom, kernel, etc,..
We only have the one hboot version so far from HTC/Vzw and that's what was used.
If you have any questions or issues, let me know.
Now for my RED TEXT:
Disclaimer​You are aware that writing to the security protected partitions increases your risk to lose the device exponentially.
You understand and agree that i cannot be held responsible for such or any other damages.
The flash process is theoretically safe and tested, however you are the brains behind the wheel and you are solely responsible for the execution of the process.
I will not accept any responsibility. The method itself is developed by Google and HTC, i only provide access and information to it and you execute it.
You understand that you should not do it if you are not willing to accept this risk.
If you plan on reverting to stock-relocked, for any reason:
You should follow the above steps first, but use this Stock Restore hboot instead.
Do this before you relock the bootloader.​
Click to expand...
Click to collapse
Any chance that u could make one that says locked and s-on? Basically one that looks not tampered at all
Sent from my SCH-I545 using Tapatalk

beanstown106 said:
Any chance that u could make one that says locked and s-on? Basically one that looks not tampered at all
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah, I could probably do that.
I will try and get to it later today for you.

santod040 said:
Yeah, I could probably do that.
I will try and get to it later today for you.
Click to expand...
Click to collapse
I am interested in that too.

beanstown106 said:
Any chance that u could make one that says locked and s-on? Basically one that looks not tampered at all
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Reefer Madness said:
I am interested in that too.
Click to expand...
Click to collapse
Faux Locked 1.54 hboot can now be found at the bottom of the OP.
I did test it before uploading and it works just as expected.
Enjoy :good:

santod040 said:
Yeah, I could probably do that.
I will try and get to it later today for you.
Click to expand...
Click to collapse
I'm sure you know about the regawMOD customizer?
what are your views on that?
I never made a plug-in or messed with hex editor but it seems if you can make this hboot request, you could easily make the plug-in.
just curious on where you stand on that MOD.
It's quite a bit of fun once working.
http://forum.xda-developers.com/showthread.php?t=1786498
---------- Post added at 02:14 PM ---------- Previous post was at 02:14 PM ----------
santod040 said:
Faux Locked 1.54 hboot can now be found at the bottom of the OP.
I did test it before uploading and it works just as expected.
Enjoy :good:
Click to expand...
Click to collapse
damn you are good!

Can't install ROM or update

I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.

kosraeboy said:
I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.
Click to expand...
Click to collapse
Hi
Can you give some details of the phone? CID?, international version?, S-On or off?, etc?
In short i think it is a good idea to update to a more recent bootloader. Then get yourself on to a newer ROM.
You might also want to consider twrp (big) as a new recovery.
This forum has lots of info.
Also take a look at www.onexroot.com
Thanks

The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.

kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
What is your error in CWM?

kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.

Noobdead said:
What is your error in CWM?
Click to expand...
Click to collapse
Hopefully this image works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

grwalker said:
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.
Click to expand...
Click to collapse
The CID Number is: OPTUS0001
Here is bootloader screen.

kosraeboy said:
The CID Number is: OPTUS0001
Here is bootloader screen.
Click to expand...
Click to collapse
Can you post the boot loader screen shot again please. The link didn't work

Trying again
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.

kosraeboy said:
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.
Click to expand...
Click to collapse
Nope, link still doesn't work. Use the attachments button when replying to attached the screenshot.
If that still doesn't work then let me know what the first three lines are when you are in fastboot mode. (Hold Vol down and power until you enter fastboot). The reason i want this info is to confirm you have the international version of HOX. If the second line contains the words "Endeavoru" then you have the international version, and we can then find the right ROM and recovery for you to use.
Also this is the link to download Hboot 1.36 for OPTUS001. http://d-h.st/users/ClydeB1/?fld_id=8110. Download this and keep it handy.
I am assuming that your bootloader is unlocked. First line tells you this. Did you use the site http://www.htcdev.com/bootloader/? Do you still have the unlock token?

Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks

kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version

kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks

grwalker said:
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks
Click to expand...
Click to collapse
Step 1 must to be after step 2, because if he flash firmware after recovery will be with stock recovery and not be possible to flash rom with stock recovery and must to flash again custom recovery. But how I think he is not a good with android devices don't have good skil to flash the firmware by him self. I suggest to answare my question and then to see if we can find RUU

Thank you both. Sorry for the delay in responding. Family emergency and I've not had time. I'll follow up in a day or so.

Sorry for the delay
Thant said:
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version
Click to expand...
Click to collapse
Hi Thant:
The result is: version-main: 1.29.980.11

kosraeboy said:
Hi Thant:
The result is: version-main: 1.29.980.11
Click to expand...
Click to collapse
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:

Thant said:
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:
Click to expand...
Click to collapse
Thanks. I'll try it and let you know.

I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?

kosraeboy said:
I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?
Click to expand...
Click to collapse
GO and see if the RUU will finish if yes this is good if give you error we will see what will do.
Yes they are the same but if RUU finish you will be complete stock and then will update wia Wi-Fi stock rom to latest hboot. Don't forget to relock your bootloader
replay if rUU finish and dont forget to make nandroid backup when you install new rom after update to latest hboot for your carrier

[SOLVED]Friend messed up his phone-gave it to me to fix-seems to be stuck in fastboot

Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.

eboy_gb said:
Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.
Click to expand...
Click to collapse
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.

Kyuubi10 said:
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.
Click to expand...
Click to collapse
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....

eboy_gb said:
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
If you can access TWRP the download a nandroid of stock, and follow the advice I already gave above.
Flash stock nandroid 4.25/4.20, from TWRP, then from fastboot flash stock recovery.
Reboot and wait for OTA updates.

All is well, got the running properly now - thanks everyone!

eboy_gb said:
All is well, got the running properly now - thanks everyone!
Click to expand...
Click to collapse
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems

Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.

xunholyx said:
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.
Click to expand...
Click to collapse
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Sent from my htc_m8 using XDA Labs

Kyuubi10 said:
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Click to expand...
Click to collapse
Corrupting system won't affect the OS number on the bootloader screen. "OS" is a bit misleading, it actually indicates the firmware number, not the ROM version.
The bug is easily reproduced by flashing certain TWRP versions (not sure exactly which ones). Its very common. We see this pop up by folks almost on a daily basis (OS number blank) especially folks using older TWRP versions.
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
Kyuubi10 said:
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems
Click to expand...
Click to collapse
Additionally, its not clear whether your suggestion is what actually worked for him (and exactly what nandroid build, etc.). OP should post the solution that worked, 1) for benefit of "helpers" like you, to confirm your fix is what worked; and 2) for the benefit of others that may run into the same issue.
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
The phone would not boot since the bootloader was relocked. This is what happens when you relock by definition, as relocking expects RUU to be run.
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
eboy_gb said:
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
RUU existing for the Desire Z (I had the same phone); and in fact for as long as HTC has been making Android devices.
RUU = ROM Update Utility
Its usually a Windows executable (although the zip format can be extracted to work with fastboot flash, or put right on an SD card) that will completely re-image the phone to stock firmware and software. You need to run the RUU that matches the phones carrier version (CID) and model (MID), and not all versions have RUU. Otherwise, the RUU will fail and not install anything.
RUU also requires a locked or relocked bootloader (although this requirement is bypassed with s-off).
RUU will also wipe any user data on the phone (including internal storage "media").

M8 - No recovery, cant flash recovery or original ruu

My case in details:
I just bought htc m8 from another user and on its back the model ID was "0P6B100 "
I found that it has twrp recovery installed and super cid "11111111", i also notice in boot loader that its model "m8_wlv" which i think it is different from the model id written on the back that shows a Europe version while "wlv" referes to Verizon version.
**I don't know the phone original CID
The info found on boot loader:
----
locked
official software
m8_wlv pvt
s-off
cid-11111111
hboot 3.16.0.0000
radio 0.89.xx.xxxx
-----
I notice that there is no update tab available and noticed from many posts later that this occur because of the super cid
there is also conflict in battery charging percentage.. if my charge is 5% and I plug the charger it stuck on same percentage tell i restart to know the correct percent i charge to....
so i take a decision to download the official ruu, to receive updates or charge normally without conflicts in percentage numbers
i download ruu referes to Verizon because of the "wlv" found in boot loader...
I installed it from the pc via fasboot, and it installed safely without any problem...
After installation i found that this isn't my official rom , and my sim is not supported , also updates are only allowed in cdma mode
back to the boot loader to found that " official software version" is gone and also there is no twrp recovery or even stock recovery, when i hit recovery from boot loader it switch to the red triangle and every time i must press up bottom and power to restart
i failed to flash new recovery or twrp recovery from pc or sd card , i always get errors for that...
also the adb i am using in fastboot folder in not working, when writing any adb commands it always says
"error: device <null> not found
I download the ul RUU in order to flash it back but i always get an error in fastboot about header checking or model id failed
now what shall i can do in order to restore my phone original stock rom ? i don't want custom roms or anything from this staff.. all what i want is restoring my original stock rom and stock recovery.
is this because the conflict in the model id or the "m8_wlv" shown in bootloader ?

My comments below in red font:
kedaaho said:
i also notice in boot loader that its model "m8_wlv" which i think it is different from the model id written on the back that shows a Europe version while "wlv" referes to Verizon version.
You need to go by what it says in bootloader, the back cover info is not reliable. The back cover was probably replaced to remove the Verizon logo. We've seen this a lot on these forums (back cover replaced to remove carrier logos).
I notice that there is no update tab available and noticed from many posts later that this occur because of the super cid
SuperCID does not affect OTA updates. However, I believe the VZN version will only get OTA updates when connected to the VZN network. So that is your main issue with getting official updates.
i download ruu referes to Verizon because of the "wlv" found in boot loader...
I installed it from the pc via fasboot, and it installed safely without any problem...
After installation i found that this isn't my official rom , and my sim is not supported
back to the boot loader to found that " official software version" is gone and also there is no twrp recovery or even stock recovery, when i hit recovery from boot loader it switch to the red triangle and every time i must press up bottom and power to restart
Where did you get this RUU, and what is the exact file name? Its obviously not an official RUU; and I suspect its an RUU cobbled together by devs before the official ZVN RUU was available; such as this, or similar. It indicates its rooted, which would explain the modified software flag.
i failed to flash new recovery or twrp recovery from pc or sd card , i always get errors for that...
also the adb i am using in fastboot folder in not working, when writing any adb commands it always says
"error: device <null> not found
You can't flash recovery with a locked bootloader; and that is what LOCKED on the bootloader screen indicates.
I download the ul RUU in order to flash it back but i always get an error in fastboot about header checking or model id failed
Its fortunate for you that RUU failed. Do NOT attempt to flash this, or any other version RUU besides VZN They is not compatible, and may even cause a permanent radio brick due to partition differences with the VZN version.
Click to expand...
Click to collapse
Do a fastboot getvar all, and post the results (delete IMEI and serial numbers before posting). Mostly, I want to see the current MID.

redpoint73 said:
Do a fastboot getvar all, and post the results (delete IMEI and serial numbers before posting). Mostly, I want to see the current MID.
Click to expand...
Click to collapse
**Many thanks redpoint73 for replying, here is the results of getvar all
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
** the updates are disabled now but also before I flash VZN rom they are not avilable, i dont know exactly what rom i was on before the VZN but it was different cause it don't has any of the VZN logos or VZN applications like in the one I have.
** The Ruu downloaded and installed name is M8_VZW "0P6BIMG.zip" and i download it from here:
http://forum.xda-developers.com/showthread.php?t=2727831

Official VZN RUUs are posted here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845

redpoint73 said:
Official VZN RUUs are posted here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
I already downloaded the marshmallow version "VZWM8_S_ON_6_0" from this link this morning but it fails to flash using fastboot:
** shall I try flashing using another method ?
**shall I download the official Hboot too from same link ?
**what versions for hboot and ruu shall be downloaded ? current firmware "4.4.2 " or the marshmallow that i want to upgrade too ?

My answers below in red font:
kedaaho said:
I already downloaded VZWM8_S_ON_6_0 from this link this morning but it fails to flash using fastboot
Try using htc_fastboot instead of the "generic" Google fastboot (disregard step #1 and renaming of the RUU.zip - just use the same RUU as before and you don't need to rename as long as you use the proper file name in the command): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
** shall I try flashing using another method ? You can certainly try the SD card method. Really, its probably the most straightforward method, as long as you have an SD card.
**shall I download the official Hboot too from same link ? No, hboot alone won't help your issue.
**what versions for hboot and ruu shall be downloaded ? same to android version i have "4.4.2 "]or the marshmallow that i want to upgrade too ?
Since you are s-off, technically any (VZN M8) RUU version should work (with s-on, you can only run RUU with same or greater versions - no downgrading). Although MM may cause a separate error running the RUU, so maybe try 5.0.1.
Click to expand...
Click to collapse

Many thanks dear,
The marshmallow version "VZWM8_S_ON_6_0" installed successfully via SD card
now the recovery is working , official status on boot loader
But it still A VZN software: The splash logo, the VZN applications, the notification of sim not supported, no stock browser(only chrome), no FM radio and updates are only available in CDMA mode
I believe the first rom came with my phone is not a VZN cause it don't contain any of this staff and also it showed on boot loader as an official rom !! for a reason i don't know it's only problem was no software updates ... and that's why i uninstalled it.
*is there any clean unlocked international official roms supported for m8_wlv "0P6B20000"?
Thanks again and again

Again, my responses in red font below:
kedaaho said:
But it still A VZN software, the splash logo, the VZN applications, the notification of sim not supported and updates are only in CDMA mode
I believe the first rom came with my phone is not a VZN cause it don't contain any of this staff and also it showed on boot loader as an official rom !!
*is there any clean unlocked international official roms supported for m8_wlv "0P6B20000"?
I don't know of any official software for the VZN version that doesn't have the VZN bloat and branding.
for a reason i don't know it's only problem was no software updates ... and that's why i uninstalled it.
This phone won't update OTA unless its connected to VZN, I already stated that. There's nothing you can do, that can change that AFAIK.
*shall I install a custom rom?, what is the best custom stable rom runing marshmallow advice?
If you want to get rid of carrier bloat and branding, than a custom ROM is probably your best bet. I don't personally own the VZN version. But I can tell you, that you can only use ROMs that specifically support the VZN M8 (otherwise you have to flash the proper kernel for it to work on the VZN M8).
Click to expand...
Click to collapse

redpoint73 said:
You can't flash recovery with a locked bootloader; and that is what LOCKED on the bootloader screen indicates
Click to expand...
Click to collapse
Now I want to root my device in order to use "Battery calibration" tool and thats because:
My battery percentage drain quickly and stuck on 2% for more than half an hour, also it stuck and dont update while charging and to know the real battery percentage everytime i must reboot to bootloader screen and reboot again..
I tried many thinks like :
*full drain
*full charge
*wipe cash from recovery screen
*restore to factory from recovery screen
*reseting the cash method "volume up +volume down+ power key for 2 min"
And all failed, my last chance is to use the battery calibration tool and it requires rooting.

Flash stock rom with broken HTC M8

Hello,
I've got a damaged HTC m8 That lost the system and s-off, i know the MID and CID, Already have a working Recovery manager (TWRP),but when i try to install cyanogen it stucks in the cyanogen logo pulsing then reboots, i'd like to know if there's a way to make it S-off and install a stock rom in it.
Attachements contain the information.

Eislei said:
Hello,
I've got a damaged HTC m8 That lost the system and s-off, i know the MID and CID, Already have a working Recovery manager (TWRP),but when i try to install cyanogen it stucks in the cyanogen logo pulsing then reboots, i'd like to know if there's a way to make it S-off and install a stock rom in it.
Attachements contain the information.
Click to expand...
Click to collapse
Your M8 is sprint, your firmware is too old, that's why newer rom's wont boot. Try flashing this cm11 http://get.cm/get/jenkins/90466/cm-11-20141112-SNAPSHOT-M12-m8.zip . I'll try to find stockish sprint 4.4.x rom so you can do S-off.
https://www.androidfilehost.com/?fid=23622183712460230 Viper is based on stock, you can try to flash this and see if boots and if boots, do s-off via sunshina($25) and flash latest sprint ruu

Eislei said:
I've got a damaged HTC m8 That lost the system and s-off
Click to expand...
Click to collapse
What does that mean "damaged"? It just started not booting, and lost s-off? Or did you physically damage it? Describe exactly what happened, in detail; otherwise we can't help properly.

Only software damaged, the phone worked for a week and shut down, even with full charge, then it didn't want to turn on at all, and no system is found in it now, it's not my phone i just took it from a friend to repair it, but it appears that there's no backup system

Imotep95 said:
Your M8 is sprint, your firmware is too old, that's why newer rom's wont boot. Try flashing this cm11 http://get.cm/get/jenkins/90466/cm-11-20141112-SNAPSHOT-M12-m8.zip . I'll try to find stockish sprint 4.4.x rom so you can do S-off.
https://www.androidfilehost.com/?fid=23622183712460230 Viper is based on stock, you can try to flash this and see if boots and if boots, do s-off via sunshina($25) and flash latest sprint ruu
Click to expand...
Click to collapse
Will try cyanogen first, because i tried CM12 / 13 And it get stuck in boot loop while it's trying to load
Downloading viper too.
Update :
When i installed Viper, and i swipe to unlock the lock screen, there's only an HTC logo for minutes, then i go past the configuration (like it's its first use), at the 4th step the phone reboots on its own
Thanks

Eislei said:
Will try cyanogen first, because i tried CM12 / 13 And it get stuck in boot loop while it's trying to load
Downloading viper too.
Update :
When i installed Viper, and i swipe to unlock the lock screen, there's only an HTC logo for minutes, then i go past the configuration (like it's its first use), at the 4th step the phone reboots on its own
Thanks
Click to expand...
Click to collapse
So, the phone just shuts down? Than it's the hardware issue.

Imotep95 said:
So, the phone just shuts down? Than it's the hardware issue.
Click to expand...
Click to collapse
Thanks you.
No, now it's working perfectly, left it on for the day, it didn't reboot once, the only hiccup is the camera app, no matter how many camera apps i download they crash on launch.
For now i think i'll S-Off the phone and install a stock sprint firmware, if it's possible of course.

Eislei said:
For now i think i'll S-Off the phone and install a stock sprint firmware, if it's possible of course.
Click to expand...
Click to collapse
You don't need s-off to return to stock. Additionally the only current method to s-off is sunshine, which costs $25; unless sunshine was previously used to s-off, in that case it may work again for no additional charge. But sunshine requires a stockish (Sense) ROM, anyway.
---------- Post added at 10:20 AM ---------- Previous post was at 09:56 AM ----------
Something looks really screwy here. The radio baseband in the first post isn't a number that corresponds to Sprint. It should be 1.08xxx or 1.09xxx according to this: http://forum.xda-developers.com/showthread.php?t=2700666
The radio number 1.22.21331147A1.29 is for the Euro WWE version. Since the phone was s-off as you stated, it appears somebody tried to flash a WWE radio/firmware to the phone, in an attempt to "convert" it to a Euro version. I'm surprised the phone isn't radio bricked.
I suggest you relock the bootloader and try to RUU back to stock using one of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=2729173
This should return the phone to the proper Sprint firmware.
Be warned, and I can't and won't be held responsible for anything that happens from this suggestion. Official RUU is normally very safe. But in the case where a botched conversion was previously performed, all bets are off. Severe radio issues are possible.

redpoint73 said:
You don't need s-off to return to stock. Additionally the only current method to s-off is sunshine, which costs $25; unless sunshine was previously used to s-off, in that case it may work again for no additional charge. But sunshine requires a stockish (Sense) ROM, anyway.
---------- Post added at 10:20 AM ---------- Previous post was at 09:56 AM ----------
Something looks really screwy here. The radio baseband in the first post isn't a number that corresponds to Sprint. It should be 1.08xxx or 1.09xxx according to this: http://forum.xda-developers.com/showthread.php?t=2700666
The radio number 1.22.21331147A1.29 is for the Euro WWE version. Since the phone was s-off as you stated, it appears somebody tried to flash a WWE radio/firmware to the phone, in an attempt to "convert" it to a Euro version. I'm surprised the phone isn't radio bricked.
I suggest you relock the bootloader and try to RUU back to stock using one of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=2729173
This should return the phone to the proper Sprint firmware.
Be warned, and I can't and won't be held responsible for anything that happens from this suggestion. Official RUU is normally very safe. But in the case where a botched conversion was previously performed, all bets are off. Severe radio issues are possible.
Click to expand...
Click to collapse
Tried the Non hk version and HK versions, but to no result, and yes the radio version is what took my attention when i opened the fastboot menu.
I'll try that this weekend and take screenshots of the result, because whenever i try to install them they show me a message that the device is not compatible for some reason.
I tried revolution HD, it installs but when it reboot it goes back to fastboot, tried viper (as stock), i have the setup wizard, after i skip the wifi settings it shows a screen for a split second at reboot the phone.

Eislei said:
Tried the Non hk version and HK versions, but to no result, and yes the radio version is what took my attention when i opened the fastboot menu.
I'll try that this weekend and take screenshots of the result, because whenever i try to install them they show me a message that the device is not compatible for some reason.
Click to expand...
Click to collapse
Which version numbers (file name) did you try exactly.
Try the Lolliop RUU 4.25.651 and see what happens. RUU to Marshmallow (RUUs 6.20) is slightly more complicated (you have to flash the MM firmware first, then RUU - this might be the reason for the error).

redpoint73 said:
Which version numbers (file name) did you try exactly.
Try the Lolliop RUU 4.25.651 and see what happens. RUU to Marshmallow (RUUs 6.20) is slightly more complicated (you have to flash the MM firmware first, then RUU - this might be the reason for the error).
Click to expand...
Click to collapse
http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe
I tried this one, but at some point it says it's not the right device for some reason

Eislei said:
http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe
I tried this one, but at some point it says it's not the right device for some reason
Click to expand...
Click to collapse
It likely seeing the firmware is the wrong number (doesn't correspond to Sprint firmware) and that is why its telling you wrong RUU.
Your best bet is to fastboot flash firmware.zip for 4.25.651.14. Then try RUU again.
http://forum.xda-developers.com/showthread.php?t=2729173