Develop Bugs

Help to turn my DHD S-ON

Good morning
I have one HTC DEsire HD rooted, and with Jelly Time R_28 (Android 4.1.2).
Due a problem with GPS i try install the original ROM to send the phone to HTC, but in the middle of the precess give me a error, but the phone work well, but after that i can't install another rom and can't even update that rom, that because se security has ON, in other words now in bootloader i have the following text:
ACE PVT SHIP S-ON RL
HBOOT- 2.00.0027
MICROP-0438
RADIO- 26.14.04.28_M
eMMD-boot
Sep 7 2011,19:06:24
Some could help me, I already try every tutorial in the forum, I read a lot of pages and I try everything but i still can's install other rom's and the S-ON remanis.
Thank's!

If your bootloader is unlocked then after flashing the rom, you have to flash the boot.img from the rom using fastboot
Thanks doesn't hurt....

ramdesai said:
If your bootloader is unlocked then after flashing the rom, you have to flash the boot.img from the rom using fastboot
Thanks doesn't hurt....
Click to expand...
Click to collapse
Thank's for the fast reply, I try flash the boot.img from the rom via fastboot, but i have a error when i trie do it in cmd. I have the following error mensage:
signature checking
failed <remote: signature verify fail>
finished. total time 1.203s
I use the boot.img in the .rar of the rom, and I follow that guide (http://forum.xda-developers.com/showthread.php?t=1752270).
One more time, thank you for your help.

are you sure your bootloader is unlocked??

gustavojsp said:
Thank's for the fast reply, I try flash the boot.img from the rom via fastboot, but i have a error when i trie do it in cmd. I have the following error mensage:
signature checking
failed <remote: signature verify fail>
finished. total time 1.203s
I use the boot.img in the .rar of the rom, and I follow that guide (http://forum.xda-developers.com/showthread.php?t=1752270).
One more time, thank you for your help.
Click to expand...
Click to collapse
pascuals said:
are you sure your bootloader is unlocked??
Click to expand...
Click to collapse
It Is impossible To have an unlocked bootloader with that hboot version...if You don't find the exact Ruu for your device, You will Need To create a goldcard

glevitan said:
It Is impossible To have an unlocked bootloader with that hboot version...if You don't find the exact Ruu for your device, You will Need To create a goldcard
Click to expand...
Click to collapse
Thanks for the tip. I already create a goldcard, now what do I do?

gustavojsp said:
Thanks for the tip. I already create a goldcard, now what do I do?
Click to expand...
Click to collapse
Flash a RUU that is compatible with the hboot update, but you need what build version you are currently running...

[Q] Cannot flash Stock RUU

When I got my M8, I achieved S-OFF using Sunshine. I have to do a warranty exchange.
I am now trying to flash stock RUU, but flashing fails with the error
Code:
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
I googled around and someone said this is due to a corrupted zip, but I checked the zip's md5 and it matches with the one on this forum. Any help is appreciated.

siddardhab said:
When I got my M8, I achieved S-OFF using Sunshine. I have to do a warranty exchange.
I am now trying to flash stock RUU, but flashing fails with the error
Code:
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
I googled around and someone said this is due to a corrupted zip, but I checked the zip's md5 and it matches with the one on this forum. Any help is appreciated.
Click to expand...
Click to collapse
Did you happen to run the gpe ruu?

Yes, I flashed the GPE RUU, I then followed instructions in this post
Flashed the firmware mentioned in that post
Flashed TWRP
Restored Stock Nandroid backup
Changed the Cid to Tmobile Cid
Relocked the bootloader, becasue I think flashing stock RUU requires a locked bootloader
I then flashed Stock RUU, but I can't seem to get past the above erro.

siddardhab said:
Yes, I flashed the GPE RUU, I then followed instructions in this post
Flashed the firmware mentioned in that post
Flashed TWRP
Restored Stock Nandroid backup
Changed the Cid to Tmobile Cid
Relocked the bootloader, becasue I think flashing stock RUU requires a locked bootloader
I then flashed Stock RUU, but I can't seem to get past the above erro.
Click to expand...
Click to collapse
Here's what worked for me on the same issue.
1.) Change CID to 11111111 (SuperCID)
2.) Flash firmware file from post.
3.) Flash TWRP
4.) Flash ViperRom through TWRP, and allow to boot.
5.) Run T-mobile Ruu.
I never bothered to change my CID back to T-MOB010.
This worked for me. hopefully it helps.

Hmm, well I have a question.
Since I already restored Stock Nandroid, can I just flash Stock recovery, relock the bootloader and remove the tampered flag.
Is the result going to be any different than going via RUU method?

siddardhab said:
Hmm, well I have a question.
Since I already restored Stock Nandroid, can I just flash Stock recovery, relock the bootloader and remove the tampered flag.
Is the result going to be any different than going via RUU method?
Click to expand...
Click to collapse
If you are S-Off, I don't believe that bootloader lock state matters anymore for ruu. I never relocked my bootloader. You can try flashing the stock recovery and relocking the bootloader to do the ruu. I was really just trying everything I could think of to get back to stock. I left my CID at SuperCID, never relocked my bootloader at all and everything has worked for me.

phil.culler said:
If you are S-Off, I don't believe that bootloader lock state matters anymore for ruu. I never relocked my bootloader. You can try flashing the stock recovery and relocking the bootloader to do the ruu. I was really just trying everything I could think of to get back to stock. I left my CID at SuperCID, never relocked my bootloader at all and everything has worked for me.
Click to expand...
Click to collapse
This is what I think I am going to do. Keep S-off...And everything else stock. Although I might lock the bootloader for security (plus it's so easy with Scotty1223's method).
But I'm also thinking...how do you do nandroids? Do you just run a custom recovery from ADB (without actually changing the stock recovery on the phone) and create one that way? Or do you use the HTC backup? I have never looked at the HTC backup, but I assumed was for sd data only.
Also, I know getting SuperCID essentially de-brands your phone...But what practical use does it have?

[Q] couldnt flash stock recovery

i want to flash stock recovery because i want to update ota i already have re locked my bootloader but when i try to flash stock reocvery i get following error in command prompt
C: \ fastboot> fastboot flash recovery recovery.img
sending 'revocery' (16384 KB) ...
OKAY [2.114s]
writing 'revocery' ...
(Bootloader) signature checking ...
FAILED (remote: signature verify fail)
finished. total time: 2.120s
i am sure i m flashing right stock recovery plz help me i need this stock recovery
i have s-on

Hmm check the recovery again, the usual recoveries are 14 mb or 24 mb .... Haven't seen a 16+ mb one

Mr Hofs said:
Hmm check the recovery again, the usual recoveries are 14 mb or 24 mb .... Haven't seen a 16+ mb one
Click to expand...
Click to collapse
if recovery is from older version of rom is this also might be a reason of remote signature fail?

n70shan said:
if recovery is from older version of rom is this also might be a reason of remote signature fail?
Click to expand...
Click to collapse
ok i have tried recovery from same rom version but still it says remote signature fail..... please help i need stock recovery ... what options do i have now?

n70shan said:
ok i have tried recovery from same rom version but still it says remote signature fail..... please help i need stock recovery ... what options do i have now?
Click to expand...
Click to collapse
i already have re locked my bootloader but when i try to flash stock reocvery i get following error in command prompt
Click to expand...
Click to collapse
unlock your bootloader, how do you want to flash a recovery if your bootloader is locked.

BerndM14 said:
unlock your bootloader, how do you want to flash a recovery if your bootloader is locked.
Click to expand...
Click to collapse
i m trying to flash stock recovery... is it necessary to have an unlocked bootloader for stock recovery as well?

All things regarding flashing needs to be done with an unlocked bootloader. Except ruu files on a s-on system.

[Q] Help Flashing Stock ROM onto Developer M8

Hey guys,
So I have a Developer Edition M8 (HBOOT- 3.19), and I went through multiple steps trying to get GPE onto it. Since I'm posting here, I screwed up along the way, and Google hasn't been to helpful. To put it simply, I do not have an OS on the phone right now, and need to flash stock back onto it, and am having trouble because TWRP recovery no longer wishes to run.
Here's what happened:
I was following an outdated guide to getting GPE (I didn't know it was outdated at the time) and it said to flash insertcoin in order to be able to use firewater to get S-Off. I flashed insertcoin, realized firewater was no longer supporeted, and felt like I had wasted a few hours. I then found sunshine and tried to use it, but insertcoin was not close enough to stock to be compatible, so I tried to flash a stock ROM I found on this thread here onto the phone. I am fairly certain I downloaded the correct file, as the HBOOT 3.19 leads to the 3.xx file, and my CIS is BS_US002, so I downloaded the 3.28 file available. I took the zip, placed it onto the phone, and wiped insertcoin, and tried to install the stock ROM. Well, it failed.
I went back to the drawing board, actually read the instructions, and did this: I placed the unpacked zip into the TWRP/Backups folder on the phone. I then used fastboot flash recovery FILE.IMG to flash boot.emmc.win from my computer to the phone. Now, when I try to go into recovery to wipe and recover, it no longer enters TWRP. It is stuck on the HTC screen.
What do I do from here? My main goal is just to get stock back onto the phone, and I hope I did not mess up the phone.
To put all phone info in one place:
HTC One M8 Developer Edition
HBOOT- 3.19
CID- BS_US002
Thank you!

rbalutiu said:
Hey guys,
So I have a Developer Edition M8 (HBOOT- 3.19), and I went through multiple steps trying to get GPE onto it. Since I'm posting here, I screwed up along the way, and Google hasn't been to helpful. To put it simply, I do not have an OS on the phone right now, and need to flash stock back onto it, and am having trouble because TWRP recovery no longer wishes to run.
Here's what happened:
I was following an outdated guide to getting GPE (I didn't know it was outdated at the time) and it said to flash insertcoin in order to be able to use firewater to get S-Off. I flashed insertcoin, realized firewater was no longer supporeted, and felt like I had wasted a few hours. I then found sunshine and tried to use it, but insertcoin was not close enough to stock to be compatible, so I tried to flash a stock ROM I found on this thread here onto the phone. I am fairly certain I downloaded the correct file, as the HBOOT 3.19 leads to the 3.xx file, and my CIS is BS_US002, so I downloaded the 3.28 file available. I took the zip, placed it onto the phone, and wiped insertcoin, and tried to install the stock ROM. Well, it failed.
I went back to the drawing board, actually read the instructions, and did this: I placed the unpacked zip into the TWRP/Backups folder on the phone. I then used fastboot flash recovery FILE.IMG to flash boot.emmc.win from my computer to the phone. Now, when I try to go into recovery to wipe and recover, it no longer enters TWRP. It is stuck on the HTC screen.
What do I do from here? My main goal is just to get stock back onto the phone, and I hope I did not mess up the phone.
To put all phone info in one place:
HTC One M8 Developer Edition
HBOOT- 3.19
CID- BS_US002
Thank you!
Click to expand...
Click to collapse
use this
http://dl3.htc.com/application/RUU_..._2G_20.63.4196.01_release_394319_signed_2.exe

clsA said:
use this
Click to expand...
Click to collapse
Just flash the exe onto the phone using the fastboot command? or is there something more to it?

rbalutiu said:
Just flash the exe onto the phone using the fastboot command? or is there something more to it?
Click to expand...
Click to collapse
it's a RUU just click it in windows
no flashing just put the phone in bootloader fastboot usb

clsA said:
it's a RUU just click it in windows
no flashing just put the phone in bootloader fastboot usb
Click to expand...
Click to collapse
I downloaded the RUU and tried running it: it gave me error code 155 and said that it cannot update the phone. Right below it also states to get the correct RUU and try again, although I think this is the right one.
Is there any way to troubleshoot this/fix this?

rbalutiu said:
I downloaded the RUU and tried running it: it gave me error code 155 and said that it cannot update the phone. Right below it also states to get the correct RUU and try again, although I think this is the right one.
Is there any way to troubleshoot this/fix this?
Click to expand...
Click to collapse
Flash this first
https://www.androidfilehost.com/?fid=95784891001612796
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then flash the RUU ...

clsA said:
Flash this first
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then flash the RUU ...
Click to expand...
Click to collapse
I put in both flash zip commands and both resulted in failures, stating "remote: 99 unknown fail". Was this intended or something went wrong?

rbalutiu said:
I put in both flash zip commands and both resulted in failures, stating "remote: 99 unknown fail". Was this intended or something went wrong?
Click to expand...
Click to collapse
I figured out the problem but still no solution: both of these require s-off. The bootloader is unlocked, but I currently have S-On. What can we do to either make it S-Off or put the stock ROM on the phone?

The ruu and Firmware works fine with s-on
post the command window output ..your doing something wrong

rbalutiu said:
I figured out the problem but still no solution: both of these require s-off. The bootloader is unlocked, but I currently have S-On. What can we do to either make it S-Off or put the stock ROM on the phone?
Click to expand...
Click to collapse
bootloader needs to be relocked when you are s-on, for ruu mode flashing (firmware.zip or full ruu)

nkk71 said:
bootloader needs to be relocked when you are s-on, for ruu mode flashing (firmware.zip or full ruu)
Click to expand...
Click to collapse
Thanks nkk71, but the Developer edition he has comes with the bootloader unlocked .. i never locked mine to flash the RUU ( I did s-off the phone so I'm not sure if it's needed or not)
OP: use fastboot oem lock to relock your bootloader and try the RUU again

clsA said:
Thanks nkk71, but the Developer edition he has comes with the bootloader unlocked .. i never locked mine to flash the RUU ( I did s-off the phone so I'm not sure if it's needed or not)
OP: use fastboot oem lock to relock your bootloader and try the RUU again
Click to expand...
Click to collapse
Yep, I know it's silly that the US Dev edition (bootloader unlocked by default), has to be relocked for RUU mode flash with S-ON... same thing on the M7

nkk71 said:
Yep, I know it's silly that the US Dev edition (bootloader unlocked by default), has to be relocked for RUU mode flash with S-ON... same thing on the M7
Click to expand...
Click to collapse
Progress made.
I locked bootloader, ran the RUU, got stock back onto there. Then unlocked again, rerooted, and got s-off. Now I'm trying to install the GE RUU as said by this site and its giving me something that says "FAILED <remote: 42 custom id check fail>" .
Just this one last step, what can I do to go around this and fix this?
Thank you both for your help so far!

rbalutiu said:
Progress made.
I locked bootloader, ran the RUU, got stock back onto there. Then unlocked again, rerooted, and got s-off. Now I'm trying to install the GE RUU as said by this site and its giving me something that says "FAILED <remote: 42 custom id check fail>" .
Just this one last step, what can I do to go around this and fix this?
Thank you both for your help so far!
Click to expand...
Click to collapse
you'll need to edit the android_info.txt to include your MID and CID
Should look like this
modelid: 0P6B12000
modelid: 0P6B17000
modelid: 0P6B1****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: BS_US002
cidnum: GOOGL001
mainver: 3.11.1700.5
btype:0
aareport:1
hbootpreupdate:3
Click to expand...
Click to collapse
And you'll want these new files, not the old one's on that site
Lollipop > http://forum.xda-developers.com/showthread.php?t=2708589
and the older Build: 4.4.4 - 2.12.1700.1 about half way down the page here >> http://www.graffixnyc.com/m8.php

clsA said:
you'll need to edit the android_info.txt to include your MID and CID
Should look like this
And you'll want these new files, not the old one's on that site
Lollipop > http://forum.xda-developers.com/showthread.php?t=2708589
and the older Build: 4.4.4 - 2.12.1700.1 about half way down the page here >> http://www.graffixnyc.com/m8.php
Click to expand...
Click to collapse
Thanks so much! Got 5.0.1 running on the phone, thanks for all the help!

[S-ON][LOCKED BL] RUU Flashing Problem (remote: 12 signature verify fail)

Hi!
I need a help.
1. I have S-ON device
2. I want to flash RUU 6.12.401.4. I am on same firmware, but have Google services FC and Sense home FC. I did factory reset in recovery, and it didn't help. So i want to reflesh same stock rom.
3. My bootloader is LOCKED
4. CID: HTC__032
I have used this RUU.zip file https://www.androidfilehost.com/?fid=24369303960687057
And when i flash it, I have signature verify fail error in fastboot. I dont want to UNLOCK bootloader.
Look at ss. All getvar info and RUU flashin error on ss.

Because you use wrong fastboot (generic) to flash the RUU.
Read this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
keyword is htc_fastboot

Thanks ckpv5, i will try now. I am sure it will work

@ckpv5 this is different, finally. I have to flash twice RUU.zip?

No .. only once for RUU.zip
Flashing firmware.zip usually require you to flash it twice.

ckpv5 said:
No .. only once for RUU.zip
Flashing firmware.zip usually require you to flash it twice.
Click to expand...
Click to collapse
Hello, is s-off required. I am trying to flash an RUU.zip but when I attempt I keep getting error 99. I have s-on and bootloader unlocked.

magestic1995 said:
Hello, is s-off required. I am trying to flash an RUU.zip but when I attempt I keep getting error 99. I have s-on and bootloader unlocked.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3370493