Database Develop

Softbricked, no OS, twrp recovery, S on. SOLVED!!!!

Hey everyone, (((((SOLVED)))))
so here is the situation.
-HTC One Bell Canada
-S on
-Twrp Recovery newest version
-No OS or backup (I accidentally deleted it)
-Windows 7 64bit
-I have fastboot files, adb files/sdk and the 3.23.666.1 Bell mobility RUU zip with no exe
I just want to get my phone back to stock then after i'll reroot and create a backup of stock so I won't have this happen again.
here is what's on my bootloader screen
Tampered
unlocked
hboot 1.55
I have tried a lot of the similar situation fixes on google and here but I couldn't find anything that has put me in a better place.
when I fastboot with
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
I tried to sideload with twerp and advanced then adb sideload and all I get is error/cannot flash zip.
Also tried installing rumrunner to get my s off but luck either.
I have also tried 4 other RUUs from htcdev and a few other places.
If there is any info you need please ask, thank you in advance.
You guys are my last hope....

christianpencz said:
Hey everyone,
so here is the situation.
-HTC One Bell Canada
-S on
-Twrp Recovery newest version
-No OS or backup (I accidentally deleted it)
-Windows 7 64bit
-I have fastboot files, adb files/sdk and the 3.23.666.1 Bell mobility RUU zip with no exe
I just want to get my phone back to stock then after i'll reroot and create a backup of stock so I won't have this happen again.
here is what's on my bootloader screen
Tampered
unlocked
hboot 1.55
I have tried a lot of the similar situation fixes on google and here but I couldn't find anything that has put me in a better place.
when I fastboot with
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
I tried to sideload with twerp and advanced then adb sideload and all I get is error/cannot flash zip.
Also tried installing rumrunner to get my s off but luck either.
I have also tried 4 other RUUs from htcdev and a few other places.
If there is any info you need please ask, thank you in advance.
You guys are my last hope....
Click to expand...
Click to collapse
Don't panic my friend, you just forgot to relock your bootloader first
Code:
fastboot oem lock

Why don't you just adb push a custom rom to your phone and flash that
Sent from my iPad using Tapatalk

Uxepro said:
Don't panic my friend, you just forgot to relock your bootloader first
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thanks Uxepro, but I have tried to flash with and without the bootloader unlocked. I get 2 different error messages, which I posted originally (12 signature verify and the 24 parsing android info fail).
If there is a step i'm missing could you tell me the step by step just in case I did something stupid.

christianpencz said:
Thanks Uxepro, but I have tried to flash with and without the bootloader unlocked. I get 2 different error messages, which I posted originally (12 signature verify and the 24 parsing android info fail).
If there is a step i'm missing could you tell me the step by step just in case I did something stupid.
Click to expand...
Click to collapse
To flash ruu with s-on you need 2 things:
Locked or relocked bootloader
Signed ruu (not decrypted)
Sent from my HTC One using xda app-developers app

christianpencz said:
I have .... the 3.23.666.1 Bell mobility RUU zip with no exe
Click to expand...
Click to collapse
1- Where did you get that from, link please
christianpencz said:
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
Click to expand...
Click to collapse
2- please copy/paste command prompt (all of it), not just the msg you get, everything from start to beginning

nateboi81 said:
Why don't you just adb push a custom rom to your phone and flash that
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I really like the stock Sense OS. At the same time I love apps like greenify and titanium backup. I might try to flash one just in the mean time though.

christianpencz said:
I really like the stock Sense OS. At the same time I love apps like greenify and titanium backup. I might try to flash one just in the mean time though.
Click to expand...
Click to collapse
check @ClydeB1 index thread for all ROMs etc, http://forum.xda-developers.com/showthread.php?t=2438026
Lot's of Sense ROMs available, all of them good, some very close to stock, others with plenty of tweaks... you'll just have to read a bit, and try a few to see which one works for you.
I'm personally using ARHD 51.0 at the moment and loving it; but that is a personal choice.... you need to try a few to see what works for you

Since you have twrp recovery, you can restore a nandroid backup http://www.htc1guru.com/downloads/stock-nandroid-downloads/ has a collection. these are stock backups, or any nandroid will work. Once the backup restored and the phone booted, go back to twrp and you can flash any rom if you want.
I had the same situation before and that's how I solved it, that if you prefer custom roms to just being stock.

alray said:
To flash ruu with s-on you need 2 things:
Locked or relocked bootloader
Signed ruu (not decrypted)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thank you nobody said it clear to me like that. So is that why it says signature fail, caused it not a signed ruu?
Quote:
Originally Posted by christianpencz View Post
I have .... the 3.23.666.1 Bell mobility RUU zip with no exe
1- Where did you get that from, link please
Click to expand...
Click to collapse
1. http://www.htc1guru.com/dld/ota_m7_ul_jb43_sense50_mr_bm_3-23-666-1-1-29-666-17_r_release-zip/
Quote:
Originally Posted by christianpencz View Post
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
2- please copy/paste command prompt (all of it), not just the msg you get, everything from start to beginning
Click to expand...
Click to collapse
2.
Code:
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.152s
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.046s]
finished. total time: 0.046s
C:\Fastboot>fastboot flash zip ruu.zip
sending 'zip' (1054139 KB)...
OKAY [ 54.199s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.630s
Quote:
Originally Posted by christianpencz View Post
I really like the stock Sense OS. At the same time I love apps like greenify and titanium backup. I might try to flash one just in the mean time though.
check @ClydeB1 index thread for all ROMs etc, http://forum.xda-developers.com/show....php?t=2438026
Lot's of Sense ROMs available, all of them good, some very close to stock, others with plenty of tweaks... you'll just have to read a bit, and try a few to see which one works for you.
I'm personally using ARHD 51.0 at the moment and loving it; but that is a personal choice.... you need to try a few to see what works for you
Click to expand...
Click to collapse
I'll try that in the meantime. Thank you (I have to use my htc one s till I get my one back up and running lol great phone just not the same at all haha.)
Since you have twrp recovery, you can restore a nandroid backup http://www.htc1guru.com/downloads/st...oid-downloads/ has a collection. these are stock backups, or any nandroid will work. Once the backup restored and the phone booted, go back to twrp and you can flash any rom if you want.
I had the same situation before and that's how I solved it, that if you prefer custom roms to just being stock.
Click to expand...
Click to collapse
I got mine from there too. But mine didn't work....can you give me the steps with the codes, maybe I missed something....I'm very new at this.
So if I get the stock/nandroid back up on my phone, does that mean when I flash a different rom I can use the backup to go back to stock?
Thanks for your help so far everyone I really appreciate it.

nkk71 said:
1- Where did you get that from, link please
1. http://www.htc1guru.com/dld/ota_m7_ul_jb43_sense50_mr_bm_3-23-666-1-1-29-666-17_r_release-zip/
2- please copy/paste command prompt (all of it), not just the msg you get, everything from start to beginning
Click to expand...
Click to collapse
2.
Code:
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.152s
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.046s]
finished. total time: 0.046s
C:\Fastboot>fastboot flash zip ruu.zip
sending 'zip' (1054139 KB)...
OKAY [ 54.199s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.630s
nkk71 said:
check @ClydeB1 index thread for all ROMs etc, http://forum.xda-developers.com/showthread.php?t=2438026
Lot's of Sense ROMs available, all of them good, some very close to stock, others with plenty of tweaks... you'll just have to read a bit, and try a few to see which one works for you.
I'm personally using ARHD 51.0 at the moment and loving it; but that is a personal choice.... you need to try a few to see what works for you
Click to expand...
Click to collapse
I'll try that in the meantime. Thank you (I have to use my htc one s till I get my one back up and running lol great phone just not the same at all haha.)
Emhalwis said:
Since you have twrp recovery, you can restore a nandroid backup http://www.htc1guru.com/downloads/stock-nandroid-downloads/ has a collection. these are stock backups, or any nandroid will work. Once the backup restored and the phone booted, go back to twrp and you can flash any rom if you want.
I had the same situation before and that's how I solved it, that if you prefer custom roms to just being stock.
Click to expand...
Click to collapse
I got mine from there too. But mine didn't work....can you give me the steps with the codes, maybe I missed something....I'm very new at this.
So if I get the stock/nandroid back up on my phone, does that mean when I flash a different rom I can use the backup to go back to stock?
Thanks for your help so far everyone I really appreciate it.

christianpencz said:
2.
Code:
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.152s
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.046s]
finished. total time: 0.046s
C:\Fastboot>fastboot flash zip ruu.zip
sending 'zip' (1054139 KB)...
OKAY [ 54.199s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.630s
So if I get the stock/nandroid back up on my phone, does that mean when I flash a different rom I can use the backup to go back to stock?
Thanks for your help so far everyone I really appreciate it.
Click to expand...
Click to collapse
First off the file your using is not a RUU it's an OTA
OTA M7 UL JB43 SENSE50 MR BM 3.23.666.1-1.29.666.17 R Release
their not the same thing OTA is flashed with a stock recovery on a Stock phone.
The nandroid backup / restore is your best bet at this point

clsA said:
First off the file your using is not a RUU it's an OTA
OTA M7 UL JB43 SENSE50 MR BM 3.23.666.1-1.29.666.17 R Release
their not the same thing OTA is flashed with a stock recovery on a Stock phone.
The nandroid backup / restore is your best bet at this point
Click to expand...
Click to collapse
so should I do exactly the same thing and steps just use the nandroid file instead?

christianpencz said:
so should I do exactly the same thing and steps just use the nandroid file instead?
Click to expand...
Click to collapse
No .. you have to push the files to your phones sdcard, TWRP directory where your backups are stored and restore the backup
it will look like this without the *****
C:\fastboot>adb devices
List of devices attached
HT343******* recovery
C:\fastboot>adb push backup /data/media/0/TWRP/BACKUPS/HT343*******/backup
push: backup/firmware_3.62.401.1.zip -> /data/media/0/TWRP/BACKUPS/HT343******/
backup/firmware_3.62.401.1.zip
1 file pushed. 0 files skipped.
3881 KB/s (28795564 bytes in 7.245s)
Click to expand...
Click to collapse
I just used one file as an example .. you'll have many files in your backup

clsA said:
No .. you have to push the files to your phones sdcard, TWRP directory where your backups are stored and restore the backup
it will look like this without the *****
I just used one file as an example .. you'll have many files in your backup
Click to expand...
Click to collapse
Can we restore directly from a zip in twrp? Every time I did I extracted the zip before on my pc then pushed the .md5 and .win files in /TWRP/BACKUPS/HT*********/backup

alray said:
Can we restore directly from a zip in twrp? Every time I did I extracted the zip before on my pc then pushed the .md5 and .win files in /TWRP/BACKUPS/HT*********/backup
Click to expand...
Click to collapse
no it has to be extracted like you said
I just pushed a zip as an example to show the full path needed

clsA said:
no it has to be extracted like you said
I just pushed a zip as an example to show the full path needed
Click to expand...
Click to collapse
ok nmv I was a little confused and didnt read your previous post correctly

alray said:
Can we restore directly from a zip in twrp? Every time I did I extracted the zip before on my pc then pushed the .md5 and .win files in /TWRP/BACKUPS/HT*********/backup
Click to expand...
Click to collapse
clsA said:
no it has to be extracted like you said
I just pushed a zip as an example to show the full path needed
Click to expand...
Click to collapse
clsA said:
No .. you have to push the files to your phones sdcard, TWRP directory where your backups are stored and restore the backup
it will look like this without the *****
I just used one file as an example .. you'll have many files in your backup
Click to expand...
Click to collapse
I sort of understand what you guys mean.....if I change the name of zip file to like nanbackup does that matter?
I know almost nothing about this process, can you do it in code form and a bit simpler.....sorry I'm a bit noobish

christianpencz said:
I sort of understand what you guys mean.....if I change the name of zip file to like nanbackup does that matter?
I know almost nothing about this process, can you do it in code form and a bit simpler.....sorry I'm a bit noobish
Click to expand...
Click to collapse
if you extract the zip to a folder named "nanbackup'' and you move that folder in your adb/fastboot folder then i think the right command should be:
Code:
adb push nanbackup /data/media/0/TWRP/BACKUPS/HT********/nanbackup/
note the space between nanbackup and /data/......
and you should be able to see the backup in twrp after the push is completed
Maybe @CiSa can confirm that before you proceed...

alray said:
if you extract the zip to a folder named "nanbackup'' and you move that folder in your adb/fastboot folder then i think the right command should be:
Code:
adb push nanbackup /data/media/0/TWRP/BACKUPS/HT********/nanbackup/
note the space between /nanbackup and /data/......
and you should be able to see the backup in twrp after the push is completed
Maybe @CiSa can confirm that before you proceed...
Click to expand...
Click to collapse
thank you, so before I try this...what do i actually type where it says HT******
or how can I find out what to put?

[Q] possible to s-off or unlock bootloader with usb debug off???

Hello
I have HTC one m7_u cid 332 hboot 1.55
For my phone there is no stock RUU searched every where
Phone is hang on HTC logo
I can go to fast boot menu tryed to unlock bootloader with htcdev but not work
My question is there any way to s-off or unlock boot loader without USB debugging on ?????
Tanx

afghan-gsm-mastermind said:
Hello
I have HTC one m7_u cid 332 hboot 1.55
For my phone there is no stock RUU searched every where
Phone is hang on HTC logo
I can go to fast boot menu tryed to unlock bootloader with htcdev but not work
My question is there any way to s-off or unlock boot loader without USB debugging on ?????
Tanx
Click to expand...
Click to collapse
bootloader is unlocked with fastboot not adb, so usb debugging is not required. Btw usb debugging only affect the usb connection when the phone is booted in the OS so its does not affect bootloader unlocking, fastboot commands or adb commands from recovery.

alray said:
bootloader is unlocked with fastboot not adb, so usb debugging is not required. Btw usb debugging only affect the usb connection when the phone is booted in the OS so its does not affect bootloader unlocking, fastboot commands or adb commands from recovery.
Click to expand...
Click to collapse
I tried unlocking bootloader with htcdev all thing gose OK but after restart phone is lock again I should say phone is dead and hang on HTC logo

Waiting for help .......

afghan-gsm-mastermind said:
Waiting for help .......
Click to expand...
Click to collapse
how are we suppose to help you with a locked bootloader ?

clsA said:
how are we suppose to help you with a locked bootloader ?
Click to expand...
Click to collapse
I've told him this in a previous thread. . Without an unlocked bootloader he is stuck.. He has to unlock first...
Sent from my GT-I9505 using XDA Premium 4 mobile app

s-on, No Os, unlocked, got twrp. Cant install stock RUU!!
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot

AnonZA said:
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
Click to expand...
Click to collapse
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
Sent from my GT-I9505 using XDA Premium 4 mobile app

AnonZA said:
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
Click to expand...
Click to collapse
sounds like your trying to sideload a RUU.zip .. that won't work
to flash RUU.zip use
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip <<yes two times
fastboot reboot
you just need the rom.zip in the same folder as fastboot

HTC__016
bored_stupid said:
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 3847mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
clsA: I tried those command million of times. It kept coming back with "boot loader signature verification..." My phone is WIPED as you can see. So usb debugging is off presumably..
Click to expand...
Click to collapse

You have the international M7 ul so download and install this rom. Follow the guide on installing
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Sent from my GT-I9505 using XDA Premium 4 mobile app

I Formatted partition using "How to: Fix a corrupted DATA partition on the HTC One" Then tried these commands (1) fastboot oem rebootRUU (2) fastboot flash zip rom.zip
{C:\Users\####\Desktop\Mini SDK>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1239446 KB)...
OKAY [ 46.879s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.244s
I think my next step is a stock stock RUU right?
Thanks a lot for the help..

Wrong one Apparently..
bored_stupid said:
You have the international M7 ul so download and install this rom. Follow the guide on installing
(LINK)
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran with admin rights, went through all the windows till i said update.. then i get error code 155, and that error code means incorrect ROM according to the programs readme!
What other ROM should I try?
Sorry to be such a pain.. I just need to use my device again.. lol

AnonZA said:
I Formatted partition using "How to: Fix a corrupted DATA partition on the HTC One" Then tried these commands (1) fastboot oem rebootRUU (2) fastboot flash zip rom.zip
{C:\Users\####\Desktop\Mini SDK>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1239446 KB)...
OKAY [ 46.879s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.244s
I think my next step is a stock stock RUU right?
Thanks a lot for the help..
Click to expand...
Click to collapse
Basically you are trying to flash a file in the bootloader that is not intended to be flashed that way. Use custom recovery or it may be an update, in that case it needs stock recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app

[Q] M7 bricked! stuck in bootloader/fastboot, cant flash anything or access recovery

Hi there.
My phone is a m7_ul, with s-on, Hboot unlocked.
Code:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4a.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
Mar 5 2014, 15:58:33.0
My phone has been bricked for a while. Originally water damaged, it at first wouldn't take any custom roms or wouldn't set back to stock, but eventually I managed to get it there and it was working fine, except that at random the phone died or rebooted. Eventually I tried putting a custom ROM on it again, and that didn't quite work, because of the phone randomly rebooting. And I guess here is where I went wrong (I can literally imagine you guys flinch when I say this): I hit 'factory recovery' in bootloader.
So now I can't do anything, besides going from hboot/bootloader onto 'fastboot' (and 'show barcode'). Going from hboot/bootloader onto 'recovery' brings me to fastboot. Even 'power down' or 'reboot bootloader' from fastboot brings me back to fastboot. Sometimes at random times the phone becomes unresponsive even in fastboot so that I have to do a hard reset with power and vol-down keys. The phone charges fine, only switches off when the battery is flat. As soon as it has enough power it goes into fastboot mode.
Plugged into my win8 machine it shows in device manager as 'my htc' (but not on the 'this pc'-view!).
In fastboot, I get the serial number when I enter 'fastboot devices', which is great. With 'fastboot getvar all' I get the following:
Code:
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.26.3263.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3742mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
HOWEVER Trying to flash a custom recovery (like the latest TWRP or CWM), I get following error:
Code:
c:\Android>fastboot flash recovery twrp/recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9948 KB)...
OKAY [ 1.332s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.505s
I tried this with numerous recoveries, but no luck. I managed to fastboot erase cache no problem.
but yeah. since i cant flash any recovery, i cant flash any new custom or stock rom. please please help.

herchenm said:
Hi there.
My phone is a m7_ul, with s-on, Hboot unlocked.
Code:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4a.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
HOWEVER Trying to flash a custom recovery (like the latest TWRP or CWM), I get following error:
[CODE]c:\Android>fastboot flash recovery [COLOR="Blue"]twrp/recovery.img[/COLOR]
target reported max download size of 1514139648 bytes
sending 'recovery' (9948 KB)...
OKAY [ 1.332s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.505s
I tried this with numerous recoveries, but no luck. I managed to fastboot erase cache no problem.
but yeah. since i cant flash any recovery, i cant flash any new custom or stock rom. please please help.
Click to expand...
Click to collapse
Remove the imei and serialno from your post.
Since you are on Win 8, you might try Win 7 or Ubuntu (nkk71 has instructions Q5).

I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc.
There are certainly other ways to recover. Anyone?
---------- Post added at 09:15 PM ---------- Previous post was at 09:09 PM ----------
I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc. This rom (http://forum.xda-developers.com/showthread.php?t=2676986) will leave you with a 1.54 hboot, so you won't downgrade to 1.44 and get stuck as the previous poster suggests.
There are certainly other ways to recover. Anyone?

majmoz said:
Remove the imei and serialno from your post.
Click to expand...
Click to collapse
done.
majmoz said:
Since you are on Win 8, you might try Win 7 or Ubuntu (nkk71 has instructions Q5).
Click to expand...
Click to collapse
not sure how that would help me? the phone is being detected and displays as 'my htc' in the windows device manager as well as with the "fastboot devices" command.
this is not the problem.
the problem is that i can't flash anything because of the returned error (image update error), which needs to be fixed but i dont know how

davidrol said:
I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc.
There are certainly other ways to recover. Anyone?
---------- Post added at 09:15 PM ---------- Previous post was at 09:09 PM ----------
I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc. This rom (http://forum.xda-developers.com/showthread.php?t=2676986) will leave you with a 1.54 hboot, so you won't downgrade to 1.44 and get stuck as the previous poster suggests.
There are certainly other ways to recover. Anyone?
Click to expand...
Click to collapse
I don't mind losing all my data. I think the phone is pretty bricked as it is, so if I could get it to work with your help, that'd be a win. Screw keeping the data haha.
I will try flashing the ROM you linked to and get back to you.
davidrol said:
you can always flash in, oemRUU mode, a signed RUU and later flash recovery
Click to expand...
Click to collapse
What do you mean with that? How do I do that? I can't get into recovery (as I cant flash that via the fastboot command) so I cant adb push/sideload
Please help

davidrol said:
This rom (http://forum.xda-developers.com/showthread.php?t=2676986) will leave you with a 1.54 hboot, so you won't downgrade to 1.44 and get stuck as the previous poster suggests.
Click to expand...
Click to collapse
can i still use that though its AT&T and my cidnum is VODAP102?
also, how do I install that ROM if I have no recovery? Im confused.

herchenm said:
can i still use that though its AT&T and my cidnum is VODAP102?
also, how do I install that ROM if I have no recovery? Im confused.
Click to expand...
Click to collapse
No you can't flash that one. You will have to find a signed RUU that matches your VODAP102 cidnum and your model number. Here's the link describing how to flash an RU in fastboot: http://forum.xda-developers.com/showthread.php?t=2251800.

davidrol said:
No you can't flash that one. You will have to find a signed RUU that matches your VODAP102 cidnum and your model number. Here's the link describing how to flash an RU in fastboot: http://forum.xda-developers.com/showthread.php?t=2251800.
Click to expand...
Click to collapse
Am I right in assuming that there isn't any RUU for my cid etc. needs? Haven't been able to found one yet maybe you can help?
Thanks for the link as well! Guess I'm gonna have to find the right RUU first

There is a way to change your cid in fastboot. I haven't the needed to so you'll need to do the research. If changing your cid isn't a problem, heres something: http://www.htc1guru.com/dld/ruu_m7_u_jb_50_htc_europe_1-29-401-2_r_radio_4a-14-3250-13_10-33-. You wont be able to flash an incorrect ruu with s-on (security on).
Sent from my SAMSUNG-SGH-I957 using xda

herchenm said:
can i still use that though its AT&T and my cidnum is VODAP102?
also, how do I install that ROM if I have no recovery? Im confused.
Click to expand...
Click to collapse
your using the wrong command to flash recovery
do it like this
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
you get the file here >> http://techerrata.com/browse/twrp2/m7
Get 2.6.3.3 no other
Your s-on you can't change CID and MID to match an AT&T RUU
your best to flash a Guru reset or a stock .401 Rom

Here's the link to change your cid to supercid: http://forum.xda-developers.com/showthread.php?t=2317536
---------- Post added at 07:33 PM ---------- Previous post was at 07:10 PM ----------
Also, put the twrp file in the same-folder-as-fastboot.

clsA said:
your using the wrong command to flash recovery
do it like this
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
you get the file here >> http://techerrata.com/browse/twrp2/m7
Get 2.6.3.3 no other
Your s-on you can't change CID and MID to match an AT&T RUU
your best to flash a Guru reset or a stock .401 Rom
Click to expand...
Click to collapse
I've been using exactly that command, and like I said, I keep getting the same error (see first post). Nonetheless I tried the recovery you linked to as well, and got the same error:
Code:
c:\Android>fastboot flash recovery or_twrp/openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.336s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.615s
I really cannot flash any recoveries.
davidrol said:
Here's the link to change your cid to supercid: http://forum.xda-developers.com/showthread.php?t=2317536
---------- Post added at 07:33 PM ---------- Previous post was at 07:10 PM ----------
Also, put the twrp file in the same-folder-as-fastboot.
Click to expand...
Click to collapse
following the instructions on the guide you linked to I get following error:
Code:
c:\Android>fastboot oem readcid
...
(bootloader) cid: VODAP102
OKAY [ 0.002s]
finished. total time: 0.003s
c:\Android>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.001s]
finished. total time: 0.003s
So I cant seem to change the CID :S

I tried changing s-on to s-off so I can change the CID. I used the moonshine s-off (http://forum.xda-developers.com/showthread.php?t=2291087 and downloaded the moonshine_m7_1.29.401.13.zip (which was the only .401 rom)
deinstalled HTC Sync Manager.
command 'fastboot devices' returned the serial number and that the phone is in fastboot-mode.
extracted the zip-file onto my computer into a separate folder, ran the distiller.exe. I confirm everything, it starts running, and then I get following error:
Code:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason touch, unplug, lick or maim your device !!
Checking for updates......
Please wait....
..........
ERROR: run distiller again and READ
Press ENTER to exit
maybe I downloaded the wrong zip-file from Moonshine? Maybe i need to try this one, cause it's vodafone and obvs my CID is Voda? moonshine_m7_1.29.161.11.zip
What do you think?

Try rumrunner

SaHiLzZ said:
Try rumrunner
Click to expand...
Click to collapse
tried that. similar result:
Code:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exit

herchenm said:
I've been using exactly that command, and like I said, I keep getting the same error (see first post). Nonetheless I tried the recovery you linked to as well, and got the same error:
Code:
c:\Android>fastboot flash recovery or_twrp/openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.336s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.615s
Click to expand...
Click to collapse
i hate to be the bearer of bad news, but pretty sure your phone is a goner
can you try the following command:
fastboot oem rebootRUU
do you get to RUU mode?
you're probably also unable to relock and unlock you device, correct?

nkk71 said:
i hate to be the bearer of bad news, but pretty sure your phone is a goner
can you try the following command:
fastboot oem rebootRUU
do you get to RUU mode?
you're probably also unable to relock and unlock you device, correct?
Click to expand...
Click to collapse
fastboot oem rebootRUU gives me the following (but the bootloader isnt locked, which I think I need to do first, no?)
Code:
c:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.065s]
finished. total time: 1.067s

herchenm said:
fastboot oem rebootRUU gives me the following (but the bootloader isnt locked, which I think I need to do first, no?)
Code:
c:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.065s]
finished. total time: 1.067s
Click to expand...
Click to collapse
nope sorry mate, it's a goner, your phone is fried
time for a new phone, sorry

nkk71 said:
nope sorry mate, it's a goner, your phone is fried
time for a new phone, sorry
Click to expand...
Click to collapse
i locked the bootloader now and got this
Code:
c:\Android>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.157s
and on the screen of the phone it says
Code:
*** tampered ***
*** relocked ***
*** security warning ***
{followed by the rest}
what does that 'security warning' and the error in the relocking of bootloader mean?

herchenm said:
i locked the bootloader now and got this
Code:
c:\Android>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.157s
and on the screen of the phone it says
Code:
*** tampered ***
*** relocked ***
*** security warning ***
{followed by the rest}
what does that 'security warning' and the error in the relocking of bootloader mean?
Click to expand...
Click to collapse
security warning is because you are not on [your] stock version
but it doesn't matter, the phone is fried
i'm really sorry
PS: i'm actually surprised the lock command worked

[Q] Tampered, Unlcoked, S-On Hboot 1.57 - No USB Debug Semi Bricked

Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
I've followed every how-to there is, but all of them require USB debug in some way, I can't get into the phone to get it down, therefore adb doesn't work. at most I have are fastboot commands.
Im at my wits. I just want to get it back to stock, to do that I would need S-off or even just have a RUU that works. This is the RUU:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
I've relocked it prior to update RUU but it didn't make a difference except preventing me to enter recovery for other tasks.
ANY help is appreciated
Here are my fastboot getvar all info:
C:\AndroidSDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXX
(bootloader) imei:XXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.108s
Click to expand...
Click to collapse

PlinXoom said:
Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
I've followed every how-to there is, but all of them require USB debug in some way, I can't get into the phone to get it down, therefore adb doesn't work. at most I have are fastboot commands.
Im at my wits. I just want to get it back to stock, to do that I would need S-off or even just have a RUU that works. This is the RUU:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
I've relocked it prior to update RUU but it didn't make a difference except preventing me to enter recovery for other tasks.
ANY help is appreciated
Here are my fastboot getvar all info:
Click to expand...
Click to collapse
You must flash ARHD using TWRP 2.6.3.3
you can not use older RUU version to restore your phone with S-ON
You can restore your phone back to stock using a nandroid backup of your version and then flash the stock recovery back.
USB debugging is only needed to use ADB when the phone is booted in the OS. Or you can also use ADB from custom recovery even if USB debug is NOT turned on.
So depending what your goal is you should try to either flash TWRP 2.6.3.3 and reflash ARHD or restore your phone using a nandroid backup if the latest dev edition software.

PlinXoom said:
Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
Click to expand...
Click to collapse
alray is correct, you can not flash that RUU because you are S-ON and it is a lower version than your present phone. There is no RUU for your version at the moment only an OTA. Here is the stock firmware for your version. This would give you stock recovery, stock hboot but it may wipe all of your personal data off of the phone. Place the file in your fastboot/adb folder and rename it firmware.zip. Then you would flash it in bootloader/FASTBOOT USB:
Code:
[B][I]fastboot oem lock[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
After the reboot, you can install TWRP and then flash ARHD 81.0.

C:\AndroidSDK\sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.146s
C:\AndroidSDK\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.034s]
finished. total time: 0.034s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.657s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.713s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.653s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.709s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.653s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.710s
C:\AndroidSDK\sdk\platform-tools>
Click to expand...
Click to collapse
I downloaded the file and flashed it, that's what I got.

I went ahead and flashed TWRP 2.6.3.3, that allowed me to have ADB and then I sideloaded the ARHD, now it's working and im setting up.
Question, now that I have the OS back, how should I go about getting S-off and the tampered warning removed. I presume this would save me from loads of trouble down the load. Thanks again in advance.

PlinXoom said:
I went ahead and flashed TWRP 2.6.3.3, that allowed me to have ADB and then I sideloaded the ARHD, now it's working and im setting up.
Question, now that I have the OS back, how should I go about getting S-off and the tampered warning removed. I presume this would save me from loads of trouble down the load. Thanks again in advance.
Click to expand...
Click to collapse
Achieve S-OFF with firewater or sunshine
Download and install this Bootloader Reset Tool

I went ahead and tried with firewater but ran into HTC anti firewater warning. I was told I needed to go back to stock Rom with bulletproof kernel to get it to work then load ARHD after. Being that if I don't intend to change the Rom any time soon, is it worth doing all the swapping around?

PlinXoom said:
I went ahead and tried with firewater but ran into HTC anti firewater warning. I was told I needed to go back to stock Rom with bulletproof kernel to get it to work then load ARHD after. Being that if I don't intend to change the Rom any time soon, is it worth doing all the swapping around?
Click to expand...
Click to collapse
If you develop an issue down the road it is easier to fix with the phone being S-OFF. However, it is a personal choice.

I figured as much, thanks again! :highfive:

[q] htc one m7 *tampereed *relocked* *security warning* help to find ruu h3g_402 cid

Hy guys, my htc one m7 is bricked (hard) no boot,no recovery... i want that my htc return stock for solve the problem but the problem is that i can't find the right RUU for my terminal. My CID is H3G__402. How can resolve this serious problem ?
Thank for eventually answer.
This is status of the terminal
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **********
(bootloader) imei: *********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__402
(bootloader) battery-status: good
(bootloader) battery-voltage: 3963mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
HELP MEE PLEASEE

Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck

R_a_z_v_a_n said:
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
Click to expand...
Click to collapse
hope to solve the problem :crying:

Giuliusss said:
hope to solve the problem :crying:
Click to expand...
Click to collapse
its not hard bricked if you can get into the bootloader, its still fixable, what do you mean no recovery, what happens when you select recovery ?
the only way to get rid of the security warning that you have is to get s-off and to get s-off on your current HBOOT, you need a working rom and will have to pay $25

Seanie280672 said:
its not hard bricked if you can get into the bootloader, its still fixable, what do you mean no recovery, what happens when you select recovery ?
the only way to get rid of the security warning that you have is to get s-off and to get s-off on your current HBOOT, you need a working rom and will have to pay $25
Click to expand...
Click to collapse
I can get into recovery but if reset the system with a factory reset the terminal crashes on a htc quietly brillant, i can't install a new rom because this is an error in a flash a new rom (REMOTE NOT ALLOWED)
C:\Users\Frisone\Desktop\jkj>fastboot flash zip Super_Su.zip
sending 'zip' (1756 KB)...
OKAY [ 0.364s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.386s
C:\Users\Frisone\Desktop\jkj>fastboot flash zip rom1.zip
sending 'zip' (203246 KB)...
OKAY [ 10.527s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 10.558s
So, this is the situation in a recovery
View attachment 3142171
View attachment 3142172
View attachment 3142173
View attachment 3142174
apparently there isn't firmware

Giuliusss said:
I can get into recovery but if reset the system with a factory reset the terminal crashes on a htc quietly brillant, i can't install a new rom because this is an error in a flash a new rom (REMOTE NOT ALLOWED)
C:\Users\Frisone\Desktop\jkj>fastboot flash zip Super_Su.zip
sending 'zip' (1756 KB)...
OKAY [ 0.364s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.386s
C:\Users\Frisone\Desktop\jkj>fastboot flash zip rom1.zip
sending 'zip' (203246 KB)...
OKAY [ 10.527s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 10.558s
So, this is the situation in a recovery
View attachment 3142171
View attachment 3142172
View attachment 3142173
View attachment 3142174
apparently there isn't firmware
Click to expand...
Click to collapse
OS and version main missing is normal for having a custom recovery installed, nothing to worry about.
remote not allowed is because your flashing those zip files the wrong way, they need to be flashed from recovery you cant flash them from fastboot like that.
flash TWRP recovery 2.6.3.3 from here: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
Next download this sense based rom: https://www.androidfilehost.com/?w=files&flid=22071 once downloaded just rename it to rom.zip
Next, enter recovery, at this point I would suggest to do a full wipe then reboot back into recovery for the changes to take full effect, it will say you have no OS installed, just ignore it, it will also ask if you want to install SuperSU, select do not install, the rom you install will most likely already be rooted, then when recovery starts back up, with recovery main screen only showing, put the rom.zip file that you want to flash in the same folder as fastboot and adb on your computer, open a CMD window and then type the below command, make sure your phone plugged into the computer at the same time:
adb push rom.zip /sdcard/
and wait, takes about 5 to 10 mins to push depending on the file size, it will let you know when its done, when it is done, unplug your phone and install the rom, during the install it will ask you if you want to full wipe at the beginning of the aroma installer, select yes to wipe, DO NOT WIPE ANYTHING ONCE THE ROM IS INSTALLED, a flresh clean rom install on a fresh clean slate does not require anything wiping, just restart and let it boot, again it can take 15 to 20mins to boot the first time.
follow these instructions properly, do not skip any steps and you'll be back up and running in 30 mins tops.

Seanie280672 said:
OS and version main missing is normal for having a custom recovery installed, nothing to worry about.
remote not allowed is because your flashing those zip files the wrong way, they need to be flashed from recovery you cant flash them from fastboot like that.
flash TWRP recovery 2.6.3.3 from here:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
Next download this sense based rom: once downloaded just rename it to rom.zip
Next, enter recovery, at this point I would suggest to do a full wipe then reboot back into recovery for the changes to take full effect, it will say you have no OS installed, just ignore it, it will also ask if you want to install SuperSU, select do not install, the rom you install will most likely already be rooted, then when recovery starts back up, with recovery main screen only showing, put the rom.zip file that you want to flash in the same folder as fastboot and adb on your computer, open a CMD window and then type the below command, make sure your phone plugged into the computer at the same time:
adb push rom.zip /sdcard/
and wait, takes about 5 to 10 mins to push depending on the file size, it will let you know when its done, when it is done, unplug your phone and install the rom, during the install it will ask you if you want to full wipe at the beginning of the aroma installer, select yes to wipe, DO NOT WIPE ANYTHING ONCE THE ROM IS INSTALLED, a flresh clean rom install on a fresh clean slate does not require anything wiping, just restart and let it boot, again it can take 15 to 20mins to boot the first time.
follow these instructions properly, do not skip any steps and you'll be back up and running in 30 mins tops.
Click to expand...
Click to collapse
it work !! thank you for all...only two question: but in the future can i flash another different rom ? can i proceed to s-off with firewater with this rom or need a cyanogen mod for firewater ? :angel::angel::laugh:

Giuliusss said:
it work !! thank you for all...only two question: but in the future can i flash another different rom ? can i proceed to s-off with firewater with this rom or need a cyanogen mod for firewater ? :angel::angel::laugh:
Click to expand...
Click to collapse
Yes you need to use that rom to get s-off, CM wont work, Firewater is discontinued, sunshine is the only way to s-off your HBOOT now and that will cost you $25. http://theroot.ninja/
Yes you can change roms at anytime, just follow these instructions again, just using a different rom and also make sure you read the op for the rom incase it requires a different recovery, not all roms will install or boot on TWRP 2.6.3.3 so make sure you read the OP.

htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0