Database Develop

Error : 43, while restoring RUU from zip

Hi All,
I am trying to get my phone back to stock and trying to flash RUU zip via fastboot, however i am getting the below error, could you please help me understand what the error means :
Code:
D:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>fastboot flash zip rom.
zip
sending 'zip' (1029979 KB)...
OKAY [ 59.742s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 186.470s
Thanks a lot

Could anyone please help me with this?

It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off

gunnyman said:
It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off
Click to expand...
Click to collapse
well so i guess there is no way currently to go back to stock with 1.544 hboot. I checked the RUU has my model id but i am s-on , so i guess i have nothing left but to sulk

gunnyman said:
It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off
Click to expand...
Click to collapse
Do you know if there is anyway for me to go 100% stock with a 4.1.2 RUU , when i am on 4.2.2 with 1.544 hboot with s-on?

No not possible.

[Q] Bricked my HTC ONE AT&T

I have a US AT&T HTC ONE M7 that shipped to me.
I unrooted it fine using htcdev and getting the unlock_code.bin. Then I uploaded a recovery TWRP just fine and got in there and saw that it worked fine. Rebooted into normal and copyed the Revolution HD zip to my phone, but reading the thread it said that i needed to update my firmware.
I followed the guide it refferenced http://forum.xda-developers.com/showthread.php?t=2183023
To here http://forum.xda-developers.com/showthread.php?t=2182823
And it said to do the command to get your cid, which I did and got idnum: CWS__001
So I looked and found that I needed to get firmware.zip from 1.29.206.11
But the link on that page takes you to a firmware of 3.06.1700.01 or something close to that. I didn't notice the numbers were different so I did the flash with fimware 3.06.1700.01 instead of the 1.29.206. 11.
Booting the phone does nothing, it sits on the HTC one screen with Beats audio. Also the AT&T chimes no longer chime when on that page and then it just sits there. When booting with the down volume button I get a black screen instead of white screen. With a dead android on the bottom instead of the 3 little androids dancing (or whatever they are doing).
I was able to get recovery back and boot into recovery but I am not sure what to do.
WIth finding instructions I have tried to download a stock RUU which I found here.
http://forum.xda-developers.com/showthread.php?t=2428276
But without any instructions to use it. I assume you need to run it from TWRP recovery but I cannot get the computer to recognize the phone anymore as a drive in order to put the RUU on the phone
I just got this phone today and wanted to root it right away and I think I broke it already.
PLEASE HELP

Are you s-off?
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
When you flashed that firmware it also flashed a kernel so try to flash a working kernel
Sent from my One using XDA Premium 4 mobile app

dirtbikerr450 said:
Are you s-off?
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
When you flashed that firmware it also flashed a kernel so try to flash a working kernel
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Honestly I have no idea what that means. I have seen S-off and s-on but I am still a n00b. I have also edited my post above as I was able to get recovery installed again. It didn't before because I had relocked it and I unlocked it again
Now the issue is that I cannot get my computer to recognize the phone as a drive to put the RUU on it

Hold power and volume down and get to fastboot/bootloader
Sent from my One using XDA Premium 4 mobile app

dirtbikerr450 said:
Hold power and volume down and get to fastboot/bootloader
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can get into that fastboot/bootloader but then what? I am here and again - it is a black screen with a dead android on the bottom which is not the same as the white screen I had before. Which clearly tells me something is wrong.
How do I load a stock kernel? Again, I have no access to the filesystem to put files onto the phone, only have access to using the commands like fastboot

I found a file on the internet
RUU_M7_UL_JB_50_Cingular.exe
Which i guess is for AT&T even thought it haven't been Cingular for years. And I go into this which says it is the HTC Android Phone ROM update utility 2.0.4.2013. Say yes to everything. It says it is going to go from 3.06.1700.10 to image version 1.26.502.12
Which is also an issue I think because the guide I found this on said that these numbers should be the same. This goes back to me flashing the 3.06.1700.10 instead of the correct firmware. I tell it to do it's thing but it errors out.
It says it will take about 10 minutes, so I wait - after about 5 minutes I get an error error [155] the ROM update utility cannot update your android phone. Please get the correct ROM update ulitity and try again.

Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app

dirtbikerr450 said:
Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just tried another firmware from that page I referenced in the OP for "x.xx.401.x - World Wide English (WWE)"
http://forum.xda-developers.com/showthread.php?t=2182823
Which came out as 2.24.401.1 and when flashing it gives me the error. failed (remote: 41 model id check fail)
I also tried to get kernels from htcdev.com/devcenter/downloads
Downloaded 1.26.502.12 and 1.26.502.10 from this page and neither worked. Giving me the error failed (remote: 12 signature verify fail)

Flash this one http://click.xda-developers.com/api...l unmodified&jsonp=vglnk_jsonp_13785283880456
Sent from my One using XDA Premium 4 mobile app

dirtbikerr450 said:
Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
dirtbikerr450 said:
Flash this one http://click.xda-developers.com/api...l unmodified&jsonp=vglnk_jsonp_13785283880456
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)

I googled S-OFF and I am not S-OFF, my top of my phone says S-ON. I followed a guide to root my phone which the last step was to install SuperSU and it worked fine. SuperSU worked fine as well so I thought I was rooted. I don't know if I was S-OFF before I flashed the firmware that caused this whole thing or not.

AMDZen said:
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
You are s-on. You should not be able to flash any firmware that's not for your phone, but because the Google edition has the same model ID as the AT&T it allowed it. I've seen a few people do this. You can not go back because on hboot 1.54 there is no s-off. The firmware you've flashed is newer than AT&T's, and you can't downgrade without s-off.
Use the custom recovery to flash a custom ROM. It will work and your phone will be fine.
You will be stuck on the Google edition firmware until AT&T releases newer firmware, or someone accomplishes s-off on 1.54 Hboot.
In the future don't flash anything that you don't fully understand.
Edit:
I should also add that I also have an AT&T One. I'm running the newest InsertCoin on the 4.3 leaked base, and my phone also has Google's firmware on it from when I did the full conversion a while back, I can testify that everything works perfectly with the firmware.
Sent from my HTC One using XDA Premium 4 mobile app

AMDZen said:
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush

crushalot said:
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush
Click to expand...
Click to collapse
Wow. This is confusing. OK the thing I flashed that messed this up was the zip file 3.06.1700.10.zip - so I am assuming that is what you mean by my AHRD. I took that, took the boot.img file out of it by itself and did as you said
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.919s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.416s
EDIT: I realized I didn't do the reboot so I did
fastboot oem rebootRUU
And then did it again, but I still got an error
fastboot flash boot boot.img
< waiting for device >
sending 'boot' (5794 KB)...
OKAY [ 0.916s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.412s
CoryTallman said:
You are s-on. You should not be able to flash any firmware that's not for your phone, but because the Google edition has the same model ID as the AT&T it allowed it. I've seen a few people do this. You can not go back because on hboot 1.54 there is no s-off. The firmware you've flashed is newer than AT&T's, and you can't downgrade without s-off.
Use the custom recovery to flash a custom ROM. It will work and your phone will be fine.
You will be stuck on the Google edition firmware until AT&T releases newer firmware, or someone accomplishes s-off on 1.54 Hboot.
In the future don't flash anything that you don't fully understand.
Edit:
I should also add that I also have an AT&T One. I'm running the newest InsertCoin on the 4.3 leaked base, and my phone also has Google's firmware on it from when I did the full conversion a while back, I can testify that everything works perfectly with the firmware.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought I did understand though. I didn't just dive into this, I researched everything all day and thought I had everything worked out. I first read teh instructions on Android Revolution HD which said that I needed to update the firmware, I followed those instructions as well and got:
fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901887
(bootloader) imei: 354439051471532
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3890mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
The cidnum that the page clearly references as needing the firmware I downloaded. Everything checked out. And now I am stuck.
Any way - I have done as you say and tried to install a ROM using fastboot as well. Keep in mind that I cannot load a ROM onto the phone and load the ROM using TWRP like all the guides I've seen say to do. I did
fastboot flash zip ROM.zip - the ROM being TrickDroid_10.0.0 and it didn't work:
fastboot flash zip ROM.zip
sending 'zip' (1068303 KB)...
OKAY [ 38.982s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 52.508s

crushalot said:
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush
Click to expand...
Click to collapse
OK Update. I was able to flash the boot after unlocking my phone again:
fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.048s
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.912s]
writing 'boot'...
OKAY [ 0.612s]
finished. total time: 1.529s
So I got that part done. I downloaded the tool and couldn't get that portion of your instructions to work. If you have the time, I installed teamviewer and set it up in my firewall so I would like to give that a try. Never used it before but I am desperate.
EDIT AGAIN: OK I got the ALL IN ONE Tool working. Apparently that doesn't run correctly if its in a folder that has a space in it. I changed the folder name that all this stuff was in to just one word no space and got it working:
sending 'boot' (5794 KB)...
OKAY [ 0.914s]
writing 'boot'...
OKAY [ 0.614s]
finished. total time: 1.530s
However the phone still doesn't boot - it still has no sound on the AT&T part of booting and then the next screen just sits there and does nothing
EDIT 2: OHHHHHHHHHHHH Light bulb went off. By AHRD you meant ARHD - meaning the custom ROM. Sadly - I never got this custom ROM installed. I was following the instructions on that site on what I needed:
Code:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
[B]Firmware package from here (recommended but not needed for now)[/B]
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
It said recommended but not needed for now. I thought it was best to do it and that's what got me in the mess. The ROM on the phone is still whatever came from the factory.

AMDZen said:
Wow. This is confusing. OK the thing I flashed that messed this up was the zip file 3.06.1700.10.zip - so I am assuming that is what you mean by my AHRD. I took that, took the boot.img file out of it by itself and did as you said
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.919s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.416s
EDIT: I realized I didn't do the reboot so I did
fastboot oem rebootRUU
And then did it again, but I still got an error
fastboot flash boot boot.img
< waiting for device >
sending 'boot' (5794 KB)...
OKAY [ 0.916s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.412s
I thought I did understand though. I didn't just dive into this, I researched everything all day and thought I had everything worked out. I first read teh instructions on Android Revolution HD which said that I needed to update the firmware, I followed those instructions as well and got:
fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901887
(bootloader) imei: 354439051471532
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3890mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
The cidnum that the page clearly references as needing the firmware I downloaded. Everything checked out. And now I am stuck.
Any way - I have done as you say and tried to install a ROM using fastboot as well. Keep in mind that I cannot load a ROM onto the phone and load the ROM using TWRP like all the guides I've seen say to do. I did
fastboot flash zip ROM.zip - the ROM being TrickDroid_10.0.0 and it didn't work:
fastboot flash zip ROM.zip
sending 'zip' (1068303 KB)...
OKAY [ 38.982s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 52.508s
Click to expand...
Click to collapse
Hold on now. You are doing a lot things wrong, but the good news is since you are s-on, you can't screw up bad. I was talking about the kernel from the rom (Android_Revolution_HD-One_20.1.zip) which I thought you had installed already.
So do I understand correctly that you did the firmware update first before flashing the Android Revolution rom, so you have the stock software (rom) installed?
However you don't have the rom file (Android_Revolution_HD-One_20.1.zip) or any others on your sdcard?
You can't flash a rom (TrickDroid) in fastboot mode.
Why exactly can't you sideload or push a rom to install from TWRP which it sounds like you have installed? Does your touch interface work in TWRP recovery?
If it doesn't then you just need to flash the latest version. Sideload is ok but you might have better luck by putting the rom file in your adb folder and issue this command while the system is booted into twrp recovery:
Code:
adb push TrickDroid.zip /data/media/0/
Then the rom will be on the root of your sdcard partition and you can install with TWRP.
---------- Post added at 03:02 AM ---------- Previous post was at 02:59 AM ----------
I saw your edit, but I didn't have mine posted in time to let you know about the kernel. Your best bet now is to install a custom rom. I didn't realize you had relocked.
Let me know where your recovery stands and if you have a rom file on the sdcard.

crushalot said:
Hold on now. You are doing a lot things wrong, but the good news is since you are s-on, you can't screw up bad. I was talking about the kernel from the rom (Android_Revolution_HD-One_20.1.zip) which I thought you had installed already.
So do I understand correctly that you did the firmware update first before flashing the Android Revolution rom, so you have the stock software (rom) installed?
However you don't have the rom file (Android_Revolution_HD-One_20.1.zip) or any others on your sdcard?
You can't flash a rom (TrickDroid) in fastboot mode.
Why exactly can't you sideload or push a rom to install from TWRP which it sounds like you have installed? Does your touch interface work in TWRP recovery?
If it doesn't then you just need to flash the latest version. Sideload is ok but you might have better luck by putting the rom file in your adb folder and issue this command while the system is booted into twrp recovery:
Code:
adb push TrickDroid.zip /data/media/0/
Then the rom will be on the root of your sdcard partition and you can install with TWRP.
---------- Post added at 03:02 AM ---------- Previous post was at 02:59 AM ----------
I saw your edit, but I didn't have mine posted in time to let you know about the kernel. Your best bet now is to install a custom rom. I didn't realize you had relocked.
Let me know where your recovery stands and if you have a rom file on the sdcard.
Click to expand...
Click to collapse
Yes on the highlighted in both cases. I'm in LUCK. Thanks so much for your help. I took the boot.img out of the stock RUU - RUU_M7_UL_JB_50_Cingular - 1.26.502.12 - Decrypted.img and ran fastboot to flash that and it booted up. I am now on a working HTC ONE
:victory::highfive:

AMDZen said:
Yes on the highlighted in both cases. I'm in LUCK. Thanks so much for your help. I took the boot.img out of the stock RUU - RUU_M7_UL_JB_50_Cingular - 1.26.502.12 - Decrypted.img and ran fastboot to flash that and it booted up. I am now on a working HTC ONE
:victory::highfive:
Click to expand...
Click to collapse
Glad your back up.

crushalot said:
Glad your back up.
Click to expand...
Click to collapse
So now I have installed ARHD custom ROM using TWRP as well.
Based on everything that has happened and the things the other person was saying about being on a newer firmware. Are there any issues I should be aware of for having this going forward?

AMDZen said:
So now I have installed ARHD custom ROM using TWRP as well.
Based on everything that has happened and the things the other person was saying about being on a newer firmware. Are there any issues I should be aware of for having this going forward?
Click to expand...
Click to collapse
Just that you can't gain s-off until a new hack is discovered for hboot 1.54. Also I am not sure if it will allow you switch back to the HTC firmware (as opposed to the Google Edition which is an unbranded bootloader) when a new base is release since you have s-on. Shouldn't be a big deal. You will probably be able to run most roms on that firmware for a long time.

[Q] Bricked Phone?

How's it going guys,been stressing and working on my phone all day today.
i was running Bad boys rom,while runnning twrp
i flashed viper one,and phone kept booting up to the bootloader only and noticed that it was or tuned back into S-On.
i went back into recovery to try and flash back to bad boys rom,and the phone would boot up but had tons of FC's ,so i went back to recovery and erased everything off my phone and tried to install the rom once again,but noticed the roms were wiped off as well.
i can flash a recovery, im currentyl on twrp 2.6.3.0 ( openrecovery-twrp-2.6.3.0-m7wls.img)
all the drivers on the phone work,i know this because when i push a recovery it installs via adb,
but when i open up CMD and put in "adb devices" it throws "list of devices" but my phone serial code doesnt appear.
i tried adb pushing a rom via sideload on recovery but nothing happens ,now my phone wont boot up to anything,it stays in the white HTC logo screen unless i force it to go to bootloader.
its as if the whole system was wiped and it wont let me push anything.
info of the phone:
sprint htc one
current bootloader state : Tampered / Unlocked
S-ON
----
ps: i already tried putting it in fastboot mode and running a RUU but the RUU wont let me downgrade the system image,says the phone is currently in 4.0.xxx(kit kat) and i was trying to RUU to 3.xx, i thought this would work,but no go.
is my phone really bricked? i mean,i can access recovery but not push any files to flash via adb or sideload , any help guys? please.
EDIT:
like i said the phone is unlocked with S-ON
is there any way i can atleast reset the tampered notice and lock it back again ? ive searched all day and it seems the only way is through rumrunner or/and Revone , but those 2 options require the phone to be S-OFF,which im having issues setting it to since i cant get the phone to boot to anyhting.
::::::::::::::::::::SOLVED::::::::::::::::::::::
so the other twrp recoveries werent letting me sideload,i flashed recovery-clockwork-touch-6.0.3.1-m7wls.img , which then it let me flash via sideload,installed bad boys rom, it booted up but it would stay in the yellow sprint page,when i would push the power button it would let me see the taskbar and would give me FC's on the dialer,so i found the baseband/radio and flashed via sideload,and BOOM! got my phone working again lol.so stoked. thanks guys!

Look HERE
As for you being s-on again the only way that would happen is if you told it to by typing a command to change it.
Also adb devices work while booted to OS or recovery
fastboot devices works in fastboot

BD619 said:
Look HERE
As for you being s-on again the only way that would happen is if you told it to by typing a command to change it.
Also adb devices work while booted to OS or recovery
fastboot devices works in fastboot
Click to expand...
Click to collapse
while flashing the Firmware, it gives me this :
C:\Android>Fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (43373 KB)...
OKAY [ 3.991s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 9.898s
any further help ? :/

johndoehizzle said:
while flashing the Firmware, it gives me this :
C:\Android>Fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (43373 KB)...
OKAY [ 3.991s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 9.898s
any further help ? :/
Click to expand...
Click to collapse
Which firmware are you trying to flash?

BD619 said:
Which firmware are you trying to flash?
Click to expand...
Click to collapse
ive tried about 2 different ones, the latest and one for 3.xx, tried them both and get fails but different error/ fail codes for each firmware

johndoehizzle said:
ive tried about 2 different ones, the latest and one for 3.xx, tried them both and get fails but different error/ fail codes for each firmware
Click to expand...
Click to collapse
Did you re-lock?

BD619 said:
Did you re-lock?
Click to expand...
Click to collapse
yeah i relocked / says tampered, i cant remember if when i relock,if it gives me any errors,tomorrow i will unlock it and relock it again and copy and paste the command prompt results, i really need to get my phone going,hopefully one of you guys can help me out,...i really appreciate the help , im broke as hell right now so any help i can get is really useful guys.
thanks alot

any more help please?

quick update: when i was trying to push the file/ sideload , i was hitting shift + right click to open up cmd,which when i put "adb devices" it wouldnt show me the phone being listed,so i when into Start,and looked up CMD and opened it up as an Admin , put the phone into sideload in recovery and it seems like its actually pushing the ROM ,hopefully this works, its at 72% right now. < fingers crossed>

HTC One M8 Skips Recovery Mode

This has been bugging the living crap out of me and I am not sure what the solution is. When I get into HBOOT and select Recovery it goes to the HTC screen, says Entering Recovery..., and then goes back to fastboot. I have flashed the recommended recoveries from TWRP (2.7.0.1) and CWM (Philz) and get the same result from both. I also cleared the cache before flashing and after flashing based on other posts I have found around the forums. Does anyone know what would possibly cause this issue? Bootloader has been unlocked as well.
HBOOT-3.18.0.0000
RADIO-1.08.20.0707_2
OS-1.12.651.1
I am just trying to get in the recovery to flash the new MM roms out there. Any help is appreciated.

macegoth said:
This has been bugging the living crap out of me and I am not sure what the solution is. When I get into HBOOT and select Recovery it goes to the HTC screen, says Entering Recovery..., and then goes back to fastboot. I have flashed the recommended recoveries from TWRP (2.7.0.1) and CWM (Philz) and get the same result from both. I also cleared the cache before flashing and after flashing based on other posts I have found around the forums. Does anyone know what would possibly cause this issue? Bootloader has been unlocked as well.
HBOOT-3.18.0.0000
RADIO-1.08.20.0707_2
OS-1.12.651.1
I am just trying to get in the recovery to flash the new MM roms out there. Any help is appreciated.
Click to expand...
Click to collapse
You're firmware is VERY old. You should update it. Also, those "recommended recoveries" are not so recommended
Sent from my m8whl using Tapatalk

So basically I broke down and bought a license for Sunshine and now my phone is S-OFF. I am still not able to install any updates because recovery isn't working. What steps should I take to fix these issues such as what updates and recovery to attempt to flash for 1.12.651.1
I am new to this and I am just really frustrated by this issue and not quite understanding what I need to do. Thanks for any help!
Edit: I tried the TWRP Manager and this solution did not work.
Second Edit: I thought I would post my getvar all results
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.08.20.0707_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.651.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) product: mec_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ50000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 36899d18
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.087s

1. Download and flash this firmware... 6.20.651.3 Full Firmware...(fastboot flashable): https://www.androidfilehost.com/?fid=24391638059059188
2. Follow these instructions on how to flash said firmware...
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot-bootloader (normally you would just reboot but the new kernel/boot.img may prohibit that from happening)
3. Click this link towards the top of the page to download the latest RUU
Sprint_HTC_One_M8_non-HK_6.20.651.3_RUU
4. Right click downloaded RUU and Run as Admin (it will take 10+ mins so be patient)
5. You should now be updated to MM
6. Download the latest TWRP from here https://dl.twrp.me/m8/ ( make sure the bootloader is unlocked)
7. Flash a rooted MM rom or download and flash the latest SuperSU from here https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Sidenote:
If you are having problems connecting to data and making calls after going through this process you might have to go back and flash the modified firmwares(boot.img and recovery removed) from the version you are on now to the latest...reason being is each update may include bits you don't have with the latest.

Sloth said:
1. Download and flash this firmware... 6.20.651.3 Full Firmware...(fastboot flashable): https://www.androidfilehost.com/?fid=24391638059059188
2. Follow these instructions on how to flash said firmware...
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot-bootloader (normally you would just reboot but the new kernel/boot.img may prohibit that from happening)
3. Click this link towards the top of the page to download the latest RUU
Sprint_HTC_One_M8_non-HK_6.20.651.3_RUU
4. Right click downloaded RUU and Run as Admin (it will take 10+ mins so be patient)
5. You should now be updated to MM
6. Download the latest TWRP from here https://dl.twrp.me/m8/ ( make sure the bootloader is unlocked)
7. Flash a rooted MM rom or download and flash the latest SuperSU from here https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Sidenote:
If you are having problems connecting to data and making calls after going through this process you might have to go back and flash the modified firmwares(boot.img and recovery removed) from the version you are on now to the latest...reason being is each update may include bits you don't have with the latest.
Click to expand...
Click to collapse
I attempted to flash the firmware, but it failed with:
C:\WINDOWS\system32>fastboot flash zip C:\Users\David\Downloads\6.20.651.3_full_firmware.zip
target reported max download size of 1830612992 bytes
sending 'zip' (54983 KB)...
OKAY [ 2.605s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 4.977s
Edit: I attempted to change my CID to be SuperCID, but it failed when I tried:
C:\WINDOWS\system32>fastboot oem writecid 1111111
...
(bootloader) fail: [writecid] Invalid cid
OKAY [ 0.017s]
finished. total time: 0.018s

Did you follow the instructions in #2 above?

modelid: 0PAJ50000
Is an M9 is it not?

Sloth said:
Did you follow the instructions in #2 above?
Click to expand...
Click to collapse
I followed the directions that you posted in #2. I tried again by renaming it to firmware.zip and got the same error:
C:\WINDOWS\system32>fastboot flash zip C:\Users\David\Downloads\firmware.zip
target reported max download size of 1830612992 bytes
sending 'zip' (54983 KB)...
OKAY [ 2.605s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 4.977s
Sloth said:
modelid: 0PAJ50000
Is an M9 is it not?
Click to expand...
Click to collapse
When I purchased the phone it said HTC One M8 and the CID-SPCS_001 looks like it is an M8 as well. Looking up the M9 I know it is not that one because this phone is a white plastic body with only an 8MP camera. It is the same innards, but has lower grade parts for the body and camera.

I did some googling and it appears you have an E8 not an M8 you can re-post your question here
http://forum.xda-developers.com/one-e8/help

Someone please help me fix my HTC One M9

Okay, so all day, I've been trying to fix this damn phone because of a root fail. I unlocked the bootloader, installed SuperSU and now the phone just reboots with a white screen and red words saying this build is for development purposdes only. I can get to download and bootloader mode fine though. Its S-On Bootloader Unlocked. I would honestly settle for it to be set to factory settings as I just need the phone fixed. Rooting has been so stressful. I don't care about losing data.
I'm thinking it failed because I used an SDHC 32GB Micro SD Card? Ive been trying to use a recovery img, Im using HTC Android Phone ROM Update Utility and thats not working. It asks to update the ROm version from 3.35.401.12 to image version (shows nothing). Then it says image error 158 (cannot update my android phone).
When flashing a recovery image, I get:
C:\Users\shaif\Downloads\Root M9>fastboot flash recovery recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (32848 KB)...
OKAY [ 2.503s]
writing 'recovery'...
(bootloader) HOSD CL#671758
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.792s]
finished. total time: 5.301s
Still not working.
Also tried fastboot oem rebootRUU but that took me to a screen that says Security Warning
Someone please help me, Im desperate

Shaifhemraj said:
Okay, so all day, I've been trying to fix this damn phone because of a root fail. I unlocked the bootloader, installed SuperSU and now the phone just reboots with a white screen and red words saying this build is for development purposdes only. I can get to download and bootloader mode fine though. Its S-On Bootloader Unlocked. I would honestly settle for it to be set to factory settings as I just need the phone fixed. Rooting has been so stressful. I don't care about losing data.
I'm thinking it failed because I used an SDHC 32GB Micro SD Card? Ive been trying to use a recovery img, Im using HTC Android Phone ROM Update Utility and thats not working. It asks to update the ROm version from 3.35.401.12 to image version (shows nothing). Then it says image error 158 (cannot update my android phone).
When flashing a recovery image, I get:
C:\Users\shaif\Downloads\Root M9>fastboot flash recovery recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (32848 KB)...
OKAY [ 2.503s]
writing 'recovery'...
(bootloader) HOSD CL#671758
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.792s]
finished. total time: 5.301s
Still not working.
Also tried fastboot oem rebootRUU but that took me to a screen that says Security Warning
Someone please help me, Im desperate
Click to expand...
Click to collapse
I'm not sure if I can get you back to stock or not, but I can help move on to a custom ROM like Resurrection Remix. Just pm me sometime if you wanna give it a try.

Shaifhemraj said:
Okay, so all day, I've been trying to fix this damn phone because of a root fail. I unlocked the bootloader, installed SuperSU and now the phone just reboots with a white screen and red words saying this build is for development purposdes only. I can get to download and bootloader mode fine though. Its S-On Bootloader Unlocked. I would honestly settle for it to be set to factory settings as I just need the phone fixed. Rooting has been so stressful. I don't care about losing data.
I'm thinking it failed because I used an SDHC 32GB Micro SD Card? Ive been trying to use a recovery img, Im using HTC Android Phone ROM Update Utility and thats not working. It asks to update the ROm version from 3.35.401.12 to image version (shows nothing). Then it says image error 158 (cannot update my android phone).
When flashing a recovery image, I get:
C:\Users\shaif\Downloads\Root M9>fastboot flash recovery recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (32848 KB)...
OKAY [ 2.503s]
writing 'recovery'...
(bootloader) HOSD CL#671758
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.792s]
finished. total time: 5.301s
Still not working.
Also tried fastboot oem rebootRUU but that took me to a screen that says Security Warning
Someone please help me, Im desperate
Click to expand...
Click to collapse
Here's a handful of sites that have step-by-step instructions on unlocking the bootloader on an HTC One M9 device.
This list of links begins with the Official HTC Developers link on unlocking the bootloader (i was surprised to find):
http://www.htcdev.com/bootloader/
https://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
http://www.droidviews.com/how-to-unlock-bootloader-on-htc-one-m9/
https://www.androidexplained.com/htc-one-m9-unlock-bootloader/
They weren't hard to find using Google.
I wish you the best of luck!
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************