Develop Bugs

My DHD stuck on htc logo

hi I tried to install IceColdSandwich-1.2.0 Rom on my DHD but after i did it my device stuck on htc logo and never boot the problem is i am new in this stuff and i can't get my device back to life i 'v downloaded the ice cream sandwich using
clock work mode and my Hboot screen shows:
****UNLOCKED*****
ACE PVT S-on RL
Hboot -2.00.0029
MICROP-0438
Radio-26.14.04.28_M
eMMc-boot
Dec 22 2011,14:28:19
and i don't know what Ruu to install
please help and thx

Your phone isn't rooted. How did you manage to flash recovery onto it in first place?
Search for advanced ace hack kit on xda. Read a LOT about how to use it and once ready, let the kit do its thing. After that you'll be S OFF and able to flash any custom ROM.
Sent from my HTC Desire HD with Beats Audio using XDA App

He unlocked it using the official HTC dev tool. It allows you to flash a custom recovery.
This is an obligatory to the op. Please research before you go and do stuff to your phone. I just don't get how someone will take a risk on there phones.
The reason it didn't boot is because you have to flash the boot image seperately. One simply can't just flash a rom, in cwr and call it a day if you did it using HTC tool.
What you need to do is. Boot back.into hboot select fastboot.
Take the boot image from your rom and place in your folder where fastboot and adb are located.
Then run the command
Fastboot flash boot boot.Img
Fastboot reboot

Its not working
marsdta said:
He unlocked it using the official HTC dev tool. It allows you to flash a custom recovery.
This is an obligatory to the op. Please research before you go and do stuff to your phone. I just don't get how someone will take a risk on there phones.
The reason it didn't boot is because you have to flash the boot image seperately. One simply can't just flash a rom, in cwr and call it a day if you did it using HTC tool.
What you need to do is. Boot back.into hboot select fastboot.
Take the boot image from your rom and place in your folder where fastboot and adb are located.
Then run the command
Fastboot flash boot boot.Img
Fastboot reboot
Click to expand...
Click to collapse
yeah you are right I used htc dev to unlock my DHD but I tried to took boot.img from the Ice cream sandwich Rom and it did not workout with me please if you know any way help me
and thx for your reply

AAHK
This is the AAHK (Advanced Ace Hack Kit) thread.
It is ONE click Root, S-Off & SIM unlock kit.
Read carefully, go step-by-step and than you'll be ready to go.
This is how I unlocked and unleashed my beast

ordevski said:
This is the AAHK (Advanced Ace Hack Kit) thread.
It is ONE click Root, S-Off & SIM unlock kit.
Read carefully, go step-by-step and than you'll be ready to go.
This is how I unlocked and unleashed my beast
Click to expand...
Click to collapse
thanks but i only can access to Hboot menu and i can enter the clock work mode but the AAHK doesn't workout with me

Run a fitting RUU, relock your Bootloader and use AAHK afterwards.
(if you would have taken some time to get into this stuff, you wouldn't be messed up right now "Official HTC Unlock" is not that brilliant compared to AAHK ).
You say you don't know which RUU to use.
Where did you buy your phone? Was/Is it branded?
DN41

DN41 said:
Run a fitting RUU, relock your Bootloader and use AAHK afterwards.
(if you would have taken some time to get into this stuff, you wouldn't be messed up right now "Official HTC Unlock" is not that brilliant compared to AAHK ).
You say you don't know which RUU to use.
Where did you buy your phone? Was/Is it branded?
DN41
Click to expand...
Click to collapse
no my phone isn't branded and the version of my android was 2.3.5 , HTc sense 3.0 software number 3.13.415.2
and AAHK need downgrade to workout with me so I gave it a chance but every thing went wrong
thx for your help anyway

Try one of those, i think the latest should be fine.
[ROM]Ace Test & Stock ROMS [RE-UPLOADED]
DN41

ok i will thank you but do you know error "155" and how to solve it and if Ruu works with s-on or not and thx again

When do you get this 155-error?
If using a fitting RUU, it will always work afaik But I'm pretty sure.
DN41

DN41 said:
When do you get this 155-error?
If using a fitting RUU, it will always work afaik But I'm pretty sure.
DN41
Click to expand...
Click to collapse
I didn't really know what you meant by afaik
I tried alot of RUU but they all keeps popup with error 155 and i don't know how to fix it and i don't know how to fix this problem but i really need to work it out and thx for all of you

"As far as I know"
Did you try flashing it in fastboot mode?
Get your device into bootloader and choose fastboot. Try to run the RUU again.
DN41
Sent from my DHD @ ARHD 6.3.1

i did but its always error 155 comes up i don't know what to do but i really need my DHD back

Ok, another idea:
You have that stock RUU fitting your phone?
Open explorer here: C:\Users\"YOUR USERNAME"\Appdata\Local\Temp\
Then Run the RUU, it will extract the files to some folder in here, you will see it pop up when opening the RUU (or you run it and simply use search).
Inside there'll be a "rom.zip".
{
"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"
}
Rename it to PD98IMG.zip, push it to your SD card (in root, not into a folder) and boot your phone into bootloader.
It should check the file and then you have to select "yes" to flash it. Should be fine after it.
DN41

thx I tried to do this before but it keeps tell wrong Image

So you're a hundred percent sure, that you've got a fitting image? Cant believe that it would block a fitting image that method.
Which version did you try? Most recent one?
And BTW: would be great it you would tell before what you already tried instead of letting me explain it and then say "oh i already did that"
DN41
EDIT: I guess it doesnt take the Rom because of the high hboot version (yours is somewhere around 2, "normal" ones around 0.84). Maybe it would be the best to contact HTC's Support regarding that you used their official unlock instead of AAHK.
Sent from my DHD @ ARHD 6.3.1

Just root it using the ace hack kit..might ne worthwhile?
Sent from my Desire HD using XDA Premium App

DN41 said:
So you're a hundred percent sure, that you've got a fitting image? Cant believe that it would block a fitting image that method.
Which version did you try? Most recent one?
And BTW: would be great it you would tell before what you already tried instead of letting me explain it and then say "oh i already did that"
DN41
EDIT: I guess it doesnt take the Rom because of the high hboot version (yours is somewhere around 2, "normal" ones around 0.84). Maybe it would be the best to contact HTC's Support regarding that you used their official unlock instead of AAHK.
Sent from my DHD @ ARHD 6.3.1
Click to expand...
Click to collapse
I am sorry i didn't tell but I really need my phone back so I am trying every idea comes to my mind and I tried a lot of versions but no one works
thx again for your help

[Q] after new ota cant unlock boot loader and adb doesnt see device

Ok so this is what i did
i installed stock recovery and locked bootloader using this TUT http://forum.xda-developers.com/showthread.php?t=2470340&highlight=unlock+bootloader
everything went good had some issue with update and nandroided back to original took the updates everything good to this point now on 4.3
I am still s off boot loader shows locked now my problems started
tried to unlock using same TUT as above won't go
made sure debug was checked
adb does not see my device but fastboot does
tried to fastboot flash recovery no go says remote not allowed
tried to fastboot flash boot image no go says remote not allowed
I think it has to do with boot loader being locked but without adb how do I unlock any help would be appreciated

update
I have removed and reinstalled the latest drivers I can see phone in windows and browse it no problems.
I reinstalled adb and rumrunner for my version .15 do i need to ruu something?
any help appreciated

bregga said:
I have removed and reinstalled the latest drivers I can see phone in windows and browse it no problems.
I reinstalled adb and rumrunner for my version .15 do i need to ruu something?
any help appreciated
Click to expand...
Click to collapse
This isn't gonna be what you want to hear probably.
You should not have relocked your bootloader before taking the OTA.
In my opinion, you should not have taken the OTA at all.
I made rooted stock roms, so that 3,000 people didnt have to do the stock rom, recovery, restore boogie.
This also reduces the risk of these types of mishaps.
The bootloader does not need to be relocked to take an ota.
You now have a locked bootloader and are on an OTA version which does not yet have a Rumrunner version.
If you cannot get your unlock token to take, you are SOL until Rumrunner updates.
You said you grabbed the version for .15, well that is what you were on prior to the OTA, you are now on 2.10.605.1 as far as I know.
If I am wrong, someone else correct me. Maybe I am missing something here...it has been a long day.
EDIT:
Sounds like you got it somewhat worked out.
A rooted boot.img would help your adb situation, such as the one I put in the stock rooted roms.

another update
I ran ruu and installed rumrunner hboot and flashed a twrp recovery both went fine using fastboot commands and i have a custom recovery again
and root but still cant adb its weird I have never had a issue with adb before

santod040 said:
This isn't gonna be what you want to hear probably.
You should not have relocked your bootloader before taking the OTA.
In my opinion, you should not have taken the OTA at all.
I made rooted stock roms, so that 3,000 people didnt have to do the stock rom, recovery, restore boogie.
This also reduces the risk of these types of mishaps.
The bootloader does not need to be relocked to take an ota.
You now have a locked bootloader and are on an OTA version which does not yet have a Rumrunner version.
If you cannot get your unlock token to take, you are SOL until Rumrunner updates.
You said you grabbed the version for .15, well that is what you were on prior to the OTA, you are now on 2.10.605.1 as far as I know.
If I am wrong, someone else correct me. Maybe I am missing something here...it has been a long day.
EDIT:
Sounds like you got it somewhat worked out.
A rooted boot.img would help your adb situation, such as the one I put in the stock rooted roms.
Click to expand...
Click to collapse
I had no problem taking the OTA myself.
I posted how i did it earlier here step 2: http://forum.xda-developers.com/showpost.php?p=48677845&postcount=2
I am kinda lost on a few things as to why you should not take the OTA if a can flash superuser after wards?

carm01 said:
I had no problem taking the OTA myself.
I posted how i did it earlier here step 2: http://forum.xda-developers.com/showpost.php?p=48677845&postcount=2
I am kinda lost on a few things as to why you should not take the OTA if a can flash superuser after wards?
Click to expand...
Click to collapse
I'm not saying that you can't take the OTA. Obviously you can, I posted roms made from it, right?
I did say there is no need to relock.
I'm not gonna go over it a bunch as to why it's just not a wise idea for the common user.
But you must have noticed the flood of users getting confused, and/or stuck when trying to do so.
It's not that hard to do it successfully, no.
Is it really necessary to go through that, when the same thing can be had by simply flashing the firmware and rooted rom?
I guess my point isn't so much that you can't take the OTA, as much as it is, why? It's a bad habit for a rooted user to get into honestly.
Why go through that? You can flash the stock rooted firmware and rom and not have to do the hokey pokey and turn yourself around.
But maybe I see it differently, I don't know.

santod040
I locked the bootloader because in the threads it says it needs to be locked to take update.
in the TUT it also states that
"this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock."
Thought it spoofed the software to make it think it was locked oh well no biggie I thought if bootloader was unlocked or relocked ota's would fail like mine was getting error 410
santod040 I have been looking at your roms and "i'm not trying to kiss your but" they look nice and get good reviews but I wanted to stay stock
nusense is the one i was really looking at hard but like i said wanted to run stock
I can wait for a new rumrunner no problem there and if it never gets done oh well I am now rooted and have twrp installed and kitkat next month "well the way verizon is everyone else will have kitkat and we will have to wait a month or so before we get it"
and i have not seen anyone else say that adb does not work with 4.3 update that is why I was asking about it to see if anyone else had a issue with adb not working after update and what if anything they did to get it back without adb rumrunner is not going to work for me anyway

bregga said:
I locked the bootloader because in the threads it says it needs to be locked to take update.
in the TUT it also states that
"this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock."
Thought it spoofed the software to make it think it was locked oh well no biggie I thought if bootloader was unlocked or relocked ota's would fail like mine was getting error 410
santod040 I have been looking at your roms and "i'm not trying to kiss your but" they look nice and get good reviews but I wanted to stay stock
nusense is the one i was really looking at hard but like i said wanted to run stock
I can wait for a new rumrunner no problem there and if it never gets done oh well I am now rooted and have twrp installed and kitkat next month "well the way verizon is everyone else will have kitkat and we will have to wait a month or so before we get it"
and i have not seen anyone else say that adb does not work with 4.3 update that is why I was asking about it to see if anyone else had a issue with adb not working after update and what if anything they did to get it back without adb rumrunner is not going to work for me anyway
Click to expand...
Click to collapse
I can understand wanting to stay stock.
I was just suggesting flashing a pure stock rooted rom.
As I said though, relocking was not necessary.

[HOW-TO][UNOFFICIALY] BlackRose HBOOT from Incredible S

Okay, so, incase anyone is wondering, I took the liberty of testing it, and VIVO (Incredible S) HBOOTs work fine on the VIVO_W
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is BlackRose HBOOT?, See here: http://forum.xda-developers.com/showthread.php?t=1509236
Proof:
{
"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"
}
How To (This is how I did it, if there is a simpler way, please tell me) :
Step 1: First off, Gain S-OFF using AlphaRev
Step 2a: Flash the "vivo_downgrade.img" via fastboot "fastboot flash hboot vivo_downgrade.img"
Step 2b: Flash the VIVO Engineering HBOOT "fastboot flash hboot vivo_enghboot.img"
Step 3: Flash BlackRose HBOOT from IncS "fastboot flash hboot hboot_blackrose.img"
Step 4: Enjoy ENG commands and other great features on the latest Inc S hboot, and retain S-OFF

OK I've been here for bit n still can't understand why it would need a different bootloader? Dinc2 have tins of available memory n with S off its fully flashable. Maybe a a missed the memo but help fill us in please? What advantage will this bring n extra feature will occur?
Sent from my SCH-I545 using Tapatalk

This has the engineering hboot commands like changing mid and serial #, and other things I don't understand
Sent from my HTC One using XDA Premium 4 mobile app

FordNate said:
OK I've been here for bit n still can't understand why it would need a different bootloader? Dinc2 have tins of available memory n with S off its fully flashable. Maybe a a missed the memo but help fill us in please? What advantage will this bring n extra feature will occur?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Also i believe blackrose changes system partition too, something to do with newer roms , check out op in viper
Thread , nits had to do something to the data and systems folders . you can find out more on the incS dev thread
Whoareyou said:
This has the engineering hboot commands like changing mid and serial #, and other things I don't understand
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using Tapatalk

I've been hacking phones for a while, back since I used windows mobile and also had a razor v3. From what I've read and understood about the engineering and custom bootloaders, they get us one step closer to being able to load custom firmware (not just android) on our phones, such as full operating systems (linux, windows, etc). Also, it gives us the potential to meddle with things like Whoareyou mentioned, the serial IDs and MEIDs, which aren't LEGALLY allowed to be changed because they are assigned to each individual device. The holy grail of utilities is the simunlock command for those with locked incredible 2's who don't want to purchase the unlock code from some potentially unreliable sources. It should be able to go in and load a flag to unlock the sim card to be usable on other carriers.
EDIT:
In doing more reading on the BlackRose page specifically, the developer had already begun discussion about loading alternate bootloaders to potentially load things like Windows phone 7 and other operating systems, but with this bootloader, you should also be able to use the full list of commands listed here:
http://dl.xda-developers.com/attach.../2/8/8/7/EVO3D_Extended_Fastboot_Commands.txt
Keep in mind, those codes ARE only confirmed for the EVO3D. Nobody has done this sort of thing with the Incredible 2 yet (to my knowledge) so much of this is dark waters for us.

lightninjay said:
I've been hacking phones for a while, back since I used windows mobile and also had a razor v3. From what I've read and understood about the engineering and custom bootloaders, they get us one step closer to being able to load custom firmware (not just android) on our phones, such as full operating systems (linux, windows, etc). Also, it gives us the potential to meddle with things like Whoareyou mentioned, the serial IDs and MEIDs, which aren't LEGALLY allowed to be changed because they are assigned to each individual device. The holy grail of utilities is the simunlock command for those with locked incredible 2's who don't want to purchase the unlock code from some potentially unreliable sources. It should be able to go in and load a flag to unlock the sim card to be usable on other carriers.
EDIT:
In doing more reading on the BlackRose page specifically, the developer had already begun discussion about loading alternate bootloaders to potentially load things like Windows phone 7 and other operating systems, but with this bootloader, you should also be able to use the full list of commands listed here:
http://dl.xda-developers.com/attach.../2/8/8/7/EVO3D_Extended_Fastboot_Commands.txt
Keep in mind, those codes ARE only confirmed for the EVO3D. Nobody has done this sort of thing with the Incredible 2 yet (to my knowledge) so much of this is dark waters for us.
Click to expand...
Click to collapse
Link is 410 - Gone code?? yeah got me on that one too. Since my Indestructible2 is not my DD and just sits there (looking sad but running KK at least on a wifi network) I might look more into this. I'd love for it to become a "hot" phone.

My recovery partition has failed after flashing this. Tried all available recoveries. Flashing is successful but rebooting to recovery always gives an eternal white HTC screen. Anyone else facing this issue?

Yes, I just experienced that, not sure why it does that, to get into recovery just switch back to the vivo downgrade hboot using the dd command from adb or terminal
I think recoveries need to be updated to support blackrose but im not really sure
Sent from my HTC One using XDA Premium 4 mobile app

I am stuck on 2.3.3 with no root. So there is no question of terminal commands.
Is there any other way to switch back the hboot?

ahmadmalik88 said:
I am stuck on 2.3.3 with no root. So there is no question of terminal commands.
Is there any other way to switch back the hboot?
Click to expand...
Click to collapse
Have you tried rooting without recovery, like temproot with superoneclick?
You have to use dd to revert be a use blackrose has hboot downgrade prevention
Sent from my HTC One using XDA Premium 4 mobile app

I succeeded in rooting with SuperOneClick but the hboot didn't downgrade. I used the following command:
dd if=/sdcard/hboot.nb0 of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
Any idea what to try next?

ahmadmalik88 said:
I succeeded in rooting with SuperOneClick but the hboot didn't downgrade. I used the following command:
Any idea what to try next?
Click to expand...
Click to collapse
that shouldhave worked, make sure your using the "vivo_downgrade" hboot, it worked for me.

Please Help
After installing BlackRose my rom wouldnt boot and I tried to boot into recovery but I get stuck at the HTC white screen. Then I tried to flash hboot but it says cant roll back version, and I cant do this "dd if=/sdcard/hboot.nb0 of=/dev/block/mmcblk0p18" because my rom wont boot. Then I tried installing an RUU and it works but it doesnt overwrite BlackRose, and I tried the dd command and it says permission denied so I tried to root my RUU but that requires custom recovery... Is there any way to fix this I fixed it

duffieldj1 said:
after installing blackrose my rom wouldnt boot and i tried to boot into recovery but i get stuck at the htc white screen. Then i tried to flash hboot but it says cant roll back version, and i cant do this "dd if=/sdcard/hboot.nb0 of=/dev/block/mmcblk0p18" because my rom wont boot. Then i tried installing an ruu and it works but it doesnt overwrite blackrose, and i tried the dd command and it says permission denied so i tried to root my ruu but that requires custom recovery... Is there any way to fix this i fixed it
Click to expand...
Click to collapse
please tell me how

Lol I wouldn't of touched this with a ten foot pole and some one else's phone
Sent from my One using xda app-developers app

chillybean said:
Lol I wouldn't of touched this with a ten foot pole and some one else's phone
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
i touched it first... just saying...
downed nothing n did nothing to my dinc2 from gere. i got all i needed to know

FordNate said:
i touched it first... just saying...
downed nothing n did nothing to my dinc2 from gere. i got all i needed to know
Click to expand...
Click to collapse
pleas am having blackrose hboot issue on my incredible 2 because I first thought it was incredeble s but after hboot upgrade and radio refuse to upgrade that discover its incredible 2 but I can enter recovery mode and have tried returning to stock hboot but all hboot say bypassed in bootloader please help me I don't have pc that I can use to run commands .
thanks.

skeji said:
pleas am having blackrose hboot issue on my incredible 2 because I first thought it was incredeble s but after hboot upgrade and radio refuse to upgrade that discover its incredible 2 but I can enter recovery mode and have tried returning to stock hboot but all hboot say bypassed in bootloader please help me I don't have pc that I can use to run commands .
thanks.
Click to expand...
Click to collapse
i no longer have this phone. Should've read before you had an issue

duffieldj1 said:
After installing BlackRose my rom wouldnt boot and I tried to boot into recovery but I get stuck at the HTC white screen. Then I tried to flash hboot but it says cant roll back version, and I cant do this "dd if=/sdcard/hboot.nb0 of=/dev/block/mmcblk0p18" because my rom wont boot. Then I tried installing an RUU and it works but it doesnt overwrite BlackRose, and I tried the dd command and it says permission denied so I tried to root my RUU but that requires custom recovery... Is there any way to fix this I fixed it
Click to expand...
Click to collapse
please how did u manage to fix it.?

casseer15 said:
please tell me how
Click to expand...
Click to collapse
you have to reboot between hboot updates

HTC one M8 wont update, boot to recovery or factory reset. Help please :)

Hi,
Yesterday I started trying to root my phone, needless to say it didn't go too well. As the title says, I'm unable to access recovery mode, and this morning when I tried to update to andriod 6.0, that wouldn't work either.
I successfully unlocked the bootloader, I think. It says unlocked in bootloader anyway. I have now relocked it to see if it will update with a locked bootloader.
Okay, so to describe what happens when I try to boot into recovery: The HTC logo shows up for a second or so, then the screen goes black and I have to boot it up from start. Also, I noticed, don't know if this is relevant, but in order for me to get into bootloader I have to hold vol down and power for at least 20 seconds, that does't seem normal to me.
I have downloaded a RUU from an HTC site(can't link, first post), but of course that wont install because im S-ON, which I don't know what it means. Anyway, the RUU wizard tells me to get the corret one, even though im fairly sure I am using the correct one.
my CID is HTC__Y13, do't know if that is going to help.
When trying to root I followed the htconeroot websites guide. again can't link :/
I have no idea what to do from here, if anyone who actually knows how these things work could help me, I would apreciate it greatly.
Thanks in advance!

Post fastboot getvar all result without serial & imei no.
Then we'll see what you need to do.
You may need these drivers installed : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4

Hey, thanks for replying!
Here is my getvar stats. If you don't mind me asking, why should I not post serial or ime no.?
{
"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"
}
Oh, also my battery is almost fully charged, still says 0mv... Don't know why, maybe somehow my phone incorrectly detects that my battery is too low when trying to run recover/update and quits because of low battery level?

You don't post serial and imei so you don't get your phone stolen. Those numbers can let someone report the phone as stolen, and have it become rejected by the carriers and such. As for the main issue you have, I'm S-OFF personally, so I flash everything manually. I haven't dealt with much of anything with S-ON aside from pure stock which does everything on it's own.

Trauken said:
Hey, thanks for replying!
Here is my getvar stats. If you don't mind me asking, why should I not post serial or ime no.?
Oh, also my battery is almost fully charged, still says 0mv... Don't know why, maybe somehow my phone incorrectly detects that my battery is too low when trying to run recover/update and quits because of low battery level?
Click to expand...
Click to collapse
Because those are personal info .. bad people can use the data to hack or something. So it's best not to post them.
The battery show as 0 on getvar result is normal ...
back to your problem ....
Your device is not a M8 but a different device called M8s
So the custom recovery that you installed most probably for M8 and definitely won't work on M8s.
And be frank with you, I am not familiar with your kind of device. There is a separate thread for M8s - http://forum.xda-developers.com/htc-one-m8/one-m8s-general
You can ask help here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
or here : http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
maybe someone with your device version will help you

Wow! I feel so stupid now...
Thanks alot for your help guys!
I'll try using the correct stuff instead and see if I can solve things, thanks again!

By the way, what would be the easiest way to go about this?
My bootloader is locked and I can't unlock it again since I have used the wrong recovery mod... So I can't just flash the recovery mode now, can I?
Could I use the RUU to somehow restore my recovery mode ? That would be great.

You can unlock the bootloader again with the same unlock_code.bin that you applied to HtcDev.
This time use correct TWRP meant for M8s to root it. You can find it in that M8s thread.
I don't know whether there is RUU for your software version. As I mentioned above, those people in M8s thread know better.
Since your device is not rooted (most probably), why don't you do the update from 1.21.401.1 to Marshmallow 2.10.401.1 ?
You just need to reflash the stock recovery but you need to find either 1.21.401.1 0r 2.10.401.1 stock recovery.img

Well the problem is I can't reflash since my bootloader is locked, and I can't unlock my bootloader because whenever I go into the "do you really want to unlock bootloader" screen and say yes, it shows the HTC logo and then turns off again... Very frustrating.
I know I'm currently in the wrong section, but since I already have your attention and the fact that you seem to know your stuff, what do you think I should do?

Trauken said:
Well the problem is I can't reflash since my bootloader is locked, and I can't unlock my bootloader because whenever I go into the "do you really want to unlock bootloader" screen and say yes, it shows the HTC logo and then turns off again... Very frustrating.
I know I'm in the wrong section currently, but since I already have your attention and the fact that you seem to know your stuff, what do you think I should do?
Click to expand...
Click to collapse
OK .. you need to flash 1.21.401.1 signed firmware.zip
I'll try to find one (hopefully is available) but I'll do this tomorrow. It's already 1.45 am here .. I need to rest soon.
Meantime try to search/google 1.21.401.1 OTA.zip or firmware.zip. If you can find one (but make sure it is for M8s not M9 or any other device) .. you just need to run these command to flash it.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
you'll see error
fastboot flash zip firmware.zip (one more time)
fastboot reboot-bootloader
this should fix your problem . your problem now is wrong recovery installed but unable to reinstall correct recovery alone because bootloader is relocked.

Thanks man!
If only the world was made up of people like you!
Get some rest, I'm not in any hurry!
I'll try to get the RUU version that I fits my phone, I'm guessing I can't use a newer one because I'm S-ON? Anyway, you don't have to answer now.
Thanks alot again, really appreiciate your help!

Trauken said:
I'll try to get the RUU version that I fits my phone, I'm guessing I can't use a newer one because I'm S-ON? Anyway, you don't have to answer now.
Click to expand...
Click to collapse
If there is a newer one 2.10.401.1 yes you can use, you can't use older version than 1.21.401.1 like 1.11.401.1 or 1.11.401.10 , higher version is ok.
Good night.

Hey, hopefully I don't wake you up somehow.
I found what I think is the right file, it was named the same thing you told me to flash.
When using the commands you told me I get this:
I can't understand any of it really, I'll google around some more and see if I can find what is wrong.

It happened that I woke up for a drink.
Just wait for tomorrow, I already have the correct firmware.zip for you.
Edit : try this - https://drive.google.com/file/d/0B4jGj3SfskzMVElpa0MxTlpCRGM/view?usp=sharing
See whether you can download it, posted on mobile.
I'll check your progress tomorrow
The last command to exit that cmd prompt screen is fastboot reboot-bootloader

Have to get some sleep, saw your answer just now lying in bed...
Will continue as soon as I wake up
EDIT- Okay so I couldn't wait lol.
Did as you said but I get this:
Am I supposed to put the firmware.zip in the fastboot folder. I did that, I'm guessing that's right...
Here is a picture of my fastboot folder in case it is somehow useful:

Trauken said:
Did as you said but I get this:
Am I supposed to put the firmware.zip in the fastboot folder. I did that, I'm guessing that's right...
Here is a picture of my fastboot folder in case it is somehow useful:
Click to expand...
Click to collapse
It seems like the generic fastboot.exe is not working for this. You should try using the htc_fastboot.exe
https://ruu.lalleman.net/HTC_M8S(QL_UL)/Tools/Fastboot/
put the htc_fastboot.exe in your fastboot folder, then try again with commands
fastboot oem rebootRUU
htc_fastboot flash zip firmware.zip
error...
repeat htc_fastboot flash zip firmware.zip
fastboot reboot-bootloader
If this also fails, the last thing that you can do (you need microSD) ...
rename the firmware.zip to 0PKVIMG.zip (that's a zero not "O")
put 0PKVIMG.zip on your microSD (not in any folder)
on bootloader select hboot
it will scan the file and ask whether to update
volume up to update
once completed reboot
(remember to remove this 0PKVIMG.zip from microSD after reboot)

Thank you once again.
My phone now propely works thanks to you.
The htc_fastboot.exe seems to have done the trick. What is it that it actually does?
I can't stress enough how grateful I am!

Trauken said:
Thank you once again.
My phone now propely works thanks to you.
The htc_fastboot.exe seems to have done the trick. What is it that it actually does?
I can't stress enough how grateful I am!
Click to expand...
Click to collapse
Most probably the HTC encryption on the htc signed firmware.zip only can be read by htc_fastboot.exe
Great that you solved your problem .. you should update to the latest Marshmallow 2.10.401.1
As this is M8s device matter, I requested moderator to move this thread to M8s section

when i type "htc_fastboo oem rebootRUU" it restarting normally and bootloop

Temp S-OFF for HTC U12+

S-OFF is out now for HTC U12+ with Sunshine
{
"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"
}
https://twitter.com/TheRootNinja/status/1017891591531343872
https://twitter.com/firewaterdevs/status/1017152637433761795
https://forum.xda-developers.com/showpost.php?p=77066052&postcount=249

That is great! Thank you!
Could you explain a bit more about the "temp" nature at this point and why someone would need the temp solution right now before you guys figure out the permanent way?
Great work!

MNoisy said:
That is great! Thank you!
Could you explain a bit more about the "temp" nature at this point and why someone would need the temp solution right now before you guys figure out the permanent way?
Great work!
Click to expand...
Click to collapse
Starting from the HTC U11, you can't permanently S-OFF the device (SunShine never achieved it for the U11). You can find a complete explanation here:
https://forum.xda-developers.com/u11/how-to/s-off-word-t3662712/post73543715

MNoisy said:
That is great! Thank you!
Could you explain a bit more about the "temp" nature at this point and why someone would need the temp solution right now before you guys figure out the permanent way?
Great work!
Click to expand...
Click to collapse
Razorbacktrack5535 said:
Starting from the HTC U11, you can't permanently S-OFF the device (SunShine never achieved it for the U11). You can find a complete explanation here:
https://forum.xda-developers.com/u11/how-to/s-off-word-t3662712/post73543715
Click to expand...
Click to collapse
In addition: it has all the same features as permanent S-OFF, with exception of the ability to use custom hboot/aboot. Once you reboot into Android or Recovery, the device will reset back S-ON, so be careful what you do, once you achieved S-OFF.
Permanent S-OFF is to dangerous - and much more risky - on those new devices as the U11 and all more recent ones.

5m4r7ph0n36uru said:
In addition: it has all the same features as permanent S-OFF, with exception of the ability to use custom hboot/aboot. Once you reboot into Android or Recovery, the device will reset back S-ON, so be careful what you do, once you achieved S-OFF.
Permanent S-OFF is to dangerous - and much more risky - on those new devices as the U11 and all more recent ones.
Click to expand...
Click to collapse
Thank you for that information!
So for the basic essential customizers like me, I would start using this when we start getting some custom ROM's if they are unsigned, to change my model, install TWRP, or if I need supercid?

MNoisy said:
Thank you for that information!
So for the basic essential customizers like me, I would start using this when we start getting some custom ROM's if they are unsigned, to change my model, install TWRP, or if I need supercid?
Click to expand...
Click to collapse
Wouldn't recommend SuperCID anymore, as you won't be able to receive OTAs any longer - yes they changed that as well. S-OFF is only needed to change CID and thus the specific software you're running, or to flash unsigned firmware. No more no less to it actually.
And there's no actual recovery partition anymore, due to treble. Instead stock recovery shares its partition with the respective boot.img. Thus I guess TWRP might be flashed as recovery_ramdisk, or as a TWRP patched boot image - we'll see when it's out and available though.
Sent from my HTC U11 using XDA Labs

S-off gives you complete control over YOUR device. You don't necessarily need to receive OTA's if you're S-off. You can flash your firmware on your schedule, not when the carrier or manufacturer says it's ready. Flash it when you're ready. Flash what you want, when you want. If the option is there, I'm getting S-off every time.
Do your homework, research and learn. If you're too lazy to do your due diligence, don't S-off. You can truly brick your phone if you're not 100% sure of what you're doing.
If you're going to just flash ROMs or just get root access but stay stock otherwise, no need to S-off. If you want complete control over flashing everything , go S-off.
But remember with great power comes great responsibility.

Beyond flashing random firmwares willy-nilly, what's the actual point of this when all U12+ ships unlocked (at least here, in the US)...? I really don't see any reason now.

szlevi said:
Beyond flashing random firmwares willy-nilly, what's the actual point of this when all U12+ ships unlocked (at least here, in the US)...? I really don't see any reason now.
Click to expand...
Click to collapse
if there is a temp root solution u can have a completely bootloader locked saftey net passing rooted device, also the us unlocked devices just mean the sim card is unlocked for whatever carrier you want to use not bootloader unlocked

Hi! I can't to obtain s-off.I bought license via app Sunshine, but when the process begins (Sunshine will now set your device S-OFF) my phone no reboot and no to obtain s-off.
I have 1.15.401.4,unlocked,rooted.
May this need to make with LOCKED status?
Help me pls.
Sorry my english

JR 2007 said:
Hi! I can't to obtain s-off.I bought license via app Sunshine, but when the process begins (Sunshine will now set your device S-OFF) my phone no reboot and no to obtain s-off.
I have 1.15.401.4,unlocked,rooted.
May this need to make with LOCKED status?
Help me pls.
Sorry my english
Click to expand...
Click to collapse
You need to be sure you went to HTC Dev and unlocked your bootloader first. After that you need to be rooted.
If you have both of those steps done and you're getting errors, go to: https://therootninja.zendesk.com/hc/en-us and check out how to troubleshoot, and send in a support ticket.
These guys are awesome, jcase and beaups are super legit and are always willing to help with their software. Good luck

Granite1 said:
You need to be sure you went to HTC Dev and unlocked your bootloader first. After that you need to be rooted.
If you have both of those steps done and you're getting errors, go to: https://therootninja.zendesk.com/hc/en-us and check out how to troubleshoot, and send in a support ticket.
These guys are awesome, jcase and beaups are super legit and are always willing to help with their software. Good luck
Click to expand...
Click to collapse
Thank you)

also make sure you are on the stock kernel it doesnt like freak07's

kickyoace said:
also make sure you are on the stock kernel it doesnt like freak07's
Click to expand...
Click to collapse
Sunshine S-Off isn't working for me either, the orange progress bar completes multiple times until it finally reboots but it just boots back up into the ROM. I am on cleanslate kernel, maybe that is the issue?

LibertyMonger said:
Sunshine S-Off isn't working for me either, the orange progress bar completes multiple times until it finally reboots but it just boots back up into the ROM. I am on cleanslate kernel, maybe that is the issue?
Click to expand...
Click to collapse
Seems like I needs to have the stock kernel

mammothjojo88 said:
Seems like I needs to have the stock kernel
Click to expand...
Click to collapse
Yes, this was exactly the problem. I restored stock kernel and it worked first try. Thanks.
---------- Post added at 01:22 PM ---------- Previous post was at 12:32 PM ----------
Temp. S-Off helped me to fix my Slot b, it seemed slot b was corrupt, it wouldn't boot as if there wasn't a ROM on it so reverting back to the old 1.15 ROM and taking the 1.21 OTA seemed to fix it. Seemless updates worked and i am currently back on slot b finally. I tried everything beforehand and nothing would work except this.

Thanks, used sunshine to convert u12+ china to emea ROM

answer from the support:
HTC designed the u12+ to only support temp s-off, all phones after and including the 11 have been this way

I tried to achieve S-Off with 1.30.401.2 but it takes more than 10 minutes and afterwards the phone boots into the system and not bootloader/download mode. Any thoughts?

mdxdave said:
I tried to achieve S-Off with 1.30.401.2 but it takes more than 10 minutes and afterwards the phone boots into the system and not bootloader/download mode. Any thoughts?
Click to expand...
Click to collapse
I just tried it on 1.30 and it is working for me. I have no advice other than that, sorry.