Database Develop

[Q] Unsuccessfuly unroot - Main Version is older!

I have serious trouble.
I tried unroot my phone but when I tried to install original ROM, I got message about fail. I rebooted the phone into recovery and restored nand backup.
I tried newer ROM. This rans longer, updated HBOOT from 1.09 to 1.13 and removed root (now I have S-ON) but then I got error "Main Version is older!" Now I can boot only info boorloader. When I use ROM in file PG32IMG.zip I got error message again.
Can anybody help me? I don't need S-OFF but I need working phone
HTC Incredible S, previous ROM was CyanogenMod 7.1 nightly, HBOOT was 1.09 but now is 1.13.
Then I try use alpharev I have no connection to phone. Driver manager says that device is working properly but then I got message that it was not recognized.
I really need drivers to connect phone un fastboot and made S-OFF again or install stock ROM (this rather). How I can recognize the right ROM?
Thanks!
P.S. I looked into forum but all solutions are for dirrerent phones

Your going to have to remove your sd card and load it into your computer with another device and replace the pg32img.zip file with another Rom.... I think.

itsbeertimenow said:
Your going to have to remove your sd card and load it into your computer with another device and replace the pg32img.zip file with another Rom.... I think.
Click to expand...
Click to collapse
I tried this but I don't know which ROM is correct for me. I tried three ROMs and every ends with error or with no message but also no effect

I want to help dude but I've never heard of this. Are you flashing a froyo or gingerbread Rom?

libb said:
I have serious trouble.
I tried unroot my phone but when I tried to install original ROM, I got message about fail. I rebooted the phone into recovery and restored nand backup.
I tried newer ROM. This rans longer, updated HBOOT from 1.09 to 1.13 and removed root (now I have S-ON) but then I got error "Main Version is older!" Now I can boot only info boorloader. When I use ROM in file PG32IMG.zip I got error message again.
Can anybody help me? I don't need S-OFF but I need working phone
HTC Incredible S, previous ROM was CyanogenMod 7.1 nightly, HBOOT was 1.09 but now is 1.13.
Then I try use alpharev I have no connection to phone. Driver manager says that device is working properly but then I got message that it was not recognized.
I really need drivers to connect phone un fastboot and made S-OFF again or install stock ROM (this rather). How I can recognize the right ROM?
Thanks!
P.S. I looked into forum but all solutions are for dirrerent phones
Click to expand...
Click to collapse
dude are you stuck at security warning bootloader???
Sent from my HTC Incredible S using xda premium

santhoshpirate said:
dude are you stuck at security warning bootloader???
Click to expand...
Click to collapse
Yes
I can run fastboot and bootloader. But I cannot connect to phone from Windows.

itsbeertimenow said:
I want to help dude but I've never heard of this. Are you flashing a froyo or gingerbread Rom?
Click to expand...
Click to collapse
I flashed Gingerbread.
I tried this ROMS in this order:
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.0225_2_NV_VZW1.92_release_181303_signed.exe (cleared CM7.1 but not recovery)
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe (cleared recovery and S-OFF, Error message)
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe (nothing, load, check then nothing - try to flash from card)

libb said:
Yes
I can run fastboot and bootloader. But I cannot connect to phone from Windows.
Click to expand...
Click to collapse
read the post carefully!
http://forum.xda-developers.com/showpost.php?p=18706124&postcount=6

santhoshpirate said:
read the post carefully!
http://forum.xda-developers.com/showpost.php?p=18706124&postcount=6
Click to expand...
Click to collapse
I read it twice.
Now I can connect via fastboot.exe but I have problem with versions.
Whe I try flash ROM, I got this:
Code:
sending 'zip' (293453 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
or this
Code:
sending 'zip' (262360 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
fastboot getvar all returns:
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.13.0000
INFOversion-baseband: 3805.06.03.03_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.32.1010.1
INFOserialno: HT12WTD01939
INFOimei: 355301040865167
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4010mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
I desperated because I flashed before latest radio and I'm afraid that the mainver is too high. Can you please advice me which ROM I could use?
On display I see:
*** Security Warning ***
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3805.06.03.03_M
eMMC-boot
Apt 1 2011, 18:34:39

use "fast boot getvar all" to get the mainver is. And than go to "h ttp://goo-inside.me/ruu/vivo" to download a new PG32IMG.zip
Delete the space between h and t.
---------- Post added at 10:01 AM ---------- Previous post was at 09:55 AM ----------
1.go to "goo-inside.me/ruu/vivo/full" and download "PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip"
2.Flash it
3.revolutionary S-OFF
4.use adb and misc_version to write a new version that you are pending to flash.
5.reboot to Bootloader
6.Make a cup of coffee
7.OK

keroro430 said:
download "PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip"
2.Flash it
Click to expand...
Click to collapse
Code:
c:\SDK_15\platform-tools>fastboot flash zip PG32IMG_Vivo_Gingerbread_S_KT_KR_2.3
2.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip
sending 'zip' (262360 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
What could be wrong?
P.S. I have removed SIM and also microSD card, i't ok?

When I flash it via RUU, I got:
Code:
c:\SDK_15\platform-tools>fastboot reboot
rebooting...
c:\SDK_15\platform-tools>fastboot erase cache
erasing 'cache'... OKAY
c:\SDK_15\platform-tools>fastboot oem rebootRUU
... OKAY
c:\SDK_15\platform-tools>fastboot flash zip PG32IMG_Vivo_Gingerbread_S_KT_KR_2.3
2.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip
sending 'zip' (262360 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)

Okay this is really old and from the evo xda threads but check it out it describes unbricking evo phones that were bricked by installing old ruu's. I'm not saying to follow this at all but it might lead you to try a different method of flashing I dunno
h ttp://forum.xda-developers.com/showthread.php?t=654119
Your going to have to mess around til you get it. Just don't let your battery get too low. Also make sure the radio isn't in the packaged zip your flashing, its not vital.

Create a goldcard, and copy the PG32IMG.zip to the root of sdcard(goldcard),enter the hboot and flash it.

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] return to stock now trapped in bootloader

after successfully getting S-ON and Locked i have TAMPERED on boot loader and unable to boot the device, always restart into bootloader and if i try recovery to flash anything i get the green circle with two green arrows then the red rectangle with ! mark in the middle
and since i'm on S-ON now i can't flash custom recovery to restart my process
the ROM was stock/rooted before i reach this step though

I managed to reach recovery after the red rectangle by pressing both volume bottons and power
now what are my options to get into the device to flash the OTA or latest RUU to return to stock?

I have downloaded Aroma Guru reset file earlier but when trying to flash it using fastboot i get this:
Code:
sudo ./platform-tools/fastboot flash zip update.zip
target reported max download size of 1508216832 bytes
sending 'zip' (1076864 KB)...
OKAY [ 39.790s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 109.946s
where can i find a functional signed (correct signature) by HTC update.zip ?

What country are you in? and what Carrier?

MicShadow said:
What country are you in? and what Carrier?
Click to expand...
Click to collapse
Zain - Kuwait (Middle east version is what i need i believe but anything works for now)

MicShadow said:
What country are you in? and what Carrier?
Click to expand...
Click to collapse
I meant any RUU that works would do the job for me, any advise?

Can someone please help me update my firmware? need help with an error

I wanted tot post in the RUU post in the android development thread, but I wasn't allowed to...
I'm running Viper 6.2 on my htc one m7 with twrp 2.6.3 and I'm trying to update to the latest firmware so I can use viper 7.1. I'm trying to update tot he odified firmware, but don't mind if I have to do the full firmware. I just want the radios and functionality there and don't ind if I have to reflash twrp recovery.
I go through the instructions but I keep getting this error no matter what I try:
C:\Users\msing_000\Documents\HTC One Files\RED HTC ONE Root>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.048s]
finished. total time: 0.050s
C:\Users\msing_000\Documents\HTC One Files\RED HTC ONE Root>fastboot flash zip firmware.zip
sending 'zip' (44873 KB)...
OKAY [ 2.763s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 3.019s
C:\Users\msing_000\Documents\HTC One Files\RED HTC ONE Root>fastboot flash zip firmware.zip
sending 'zip' (44873 KB)...
OKAY [ 2.763s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 3.018s
C:\Users\msing_000\Documents\HTC One Files\RED HTC ONE Root>fastboot reboot
rebooting...
finished. total time: 0.042s
C:\Users\msing_000\Documents\HTC One Files\RED HTC ONE Root>
Click to expand...
Click to collapse
Can someone please help me through this?

Are you s-off?
Modified firmware = s-off

yes I am s-off

msingh95 said:
yes I am s-off
Click to expand...
Click to collapse
Could be a bad download.
Try a different USB port...USB 2 work best.
Try a different PC.

BD619 said:
Could be a bad download.
Try a different USB port...USB 2 work best.
Try a different PC.
Click to expand...
Click to collapse
So I checked again and I was wrong, I'm not S-Off...that was my other HTC ONE, I thought I'd done the same to this one.
But Now I'm having problems...I want to do a firmware update to fix Viper 7.0.1 issues with data/connectivity but it's still not letting me.
Will I be able to flash the updated firmware in the full version with S-On?
I've being running RumRunner all day on different computers and different usb ports...still no luck

msingh95 said:
So I checked again and I was wrong, I'm not S-Off...that was my other HTC ONE, I thought I'd done the same to this one.
But Now I'm having problems...I want to do a firmware update to fix Viper 7.0.1 issues with data/connectivity but it's still not letting me.
Will I be able to flash the updated firmware in the full version with S-On?
I've being running RumRunner all day on different computers and different usb ports...still no luck
Click to expand...
Click to collapse
Try Firewater for s-off.
Yes you can flash the Full Firmware while s-on but you will have to re-lock your bootloader to do so which means unlocking again and wiping your phone.

BD619 said:
Try Firewater for s-off.
Yes you can flash the Full Firmware while s-on but you will have to re-lock your bootloader to do so which means unlocking again and wiping your phone.
Click to expand...
Click to collapse
I tried firewater, but I don't understand how to push it to my phone...can I have some detailed help? the firewater page didn't help me much...

msingh95 said:
I tried firewater, but I don't understand how to push it to my phone...can I have some detailed help? the firewater page didn't help me much...
Click to expand...
Click to collapse
Put the firewater file in your adb/fastboot/platform tools folder, open a cmd window then copy and paste the commands on the firewater site.

BD619 said:
Put the firewater file in your adb/fastboot/platform tools folder, open a cmd window then copy and paste the commands on the firewater site.
Click to expand...
Click to collapse
everything worked out, got it all working, thanks!

[Q] No Red Text Firmware 7.17.1540.7 Solved

Has anyone done a no red text version of the firmware for 7.17.1540.7? This is from the current dev edition release of lollipop. At this point I can't seem to find it if someone has done one already.

I have done one, but not tested it yet. If you want to test it, go ahead but I'm not responsible if this brick your phone.
If you want to test it, report if its working fine, then I'll upload it to my thread and give you credit for testing it. You can compare the origianl hboot with this one with an hex editing tool to double check if you want.
Edit:
7.17.1540.7 no red text hboot available here: http://forum.xda-developers.com/htc-one/general/stock-rom-reset-developer-edition-t2915170

Thanks! I tested and it works. I did verify it against my copy of the clean hboot here and it checked out and based on instruction I saw elsewhere looked fine so I took a try. Here is the zip pack I used. It only updates the hboot (I've seen others doing a full pack) so it is best run on top after already having firmware 7.17.1540.7.
Please note it may appear to get stuck at about 75%. As long as it says OKAY at the end and does not indicate it failed then it should be ok to reboot. It got stuck for me on my screen so I had to fastboot reboot-bootloader after. From my understanding that last 25% is actually the reboot stage which doesn't happen automatically so here you do get a chance to check the result before rebooting manually.
For those that do download from this post...
If it says FAILED at the end DO NOT reboot the device. Instead try to flash again or flash a stock hboot. If you reboot at this point there is a very high chance it will not boot and become a lightweight doorstop. Let's not have that happen ok?
Trial run (serial is censored):
Code:
C:\Users\User\Desktop>fastboot flash zip 7.17.1540.7_no_red.zip
target reported max download size of 1514139648 bytes
sending 'zip' (603 KB)...
OKAY [ 0.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.211s]
finished. total time: 2.461s
C:\Users\User\Desktop>fastboot devices
HT42CW000000 fastboot
C:\Users\User\Desktop>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.038s

signes or unsigned firmware?
Hi,
I'm sorry for the noob question but what's the difference of a signed and unsigned firmware?

shinji257 said:
Thanks! I tested and it works. I did verify it against my copy of the clean hboot here and it checked out and based on instruction I saw elsewhere looked fine so I took a try. Here is the zip pack I used. It only updates the hboot (I've seen others doing a full pack) so it is best run on top after already having firmware 7.17.1540.7.
Please note it may appear to get stuck at about 75%. As long as it says OKAY at the end and does not indicate it failed then it should be ok to reboot. It got stuck for me on my screen so I had to fastboot reboot-bootloader after. From my understanding that last 25% is actually the reboot stage which doesn't happen automatically so here you do get a chance to check the result before rebooting manually.
For those that do download from this post...
If it says FAILED at the end DO NOT reboot the device. Instead try to flash again or flash a stock hboot. If you reboot at this point there is a very high chance it will not boot and become a lightweight doorstop. Let's not have that happen ok?
Trial run (serial is censored):
Click to expand...
Click to collapse
Thanks for reporting, will remove the file from this thread and post it I'm my collection thread and also in a firmware.zip

RucaNebas said:
Hi,
I'm sorry for the noob question but what's the difference of a signed and unsigned firmware?
Click to expand...
Click to collapse
Signed firmware is official HTC firmware signed with their private (encrypted) key. S-ON phones can only flash signed firmware. Firmware to flash must be the same version or newer (higher) than whats already running on the phone and bootloader must be locked/relocked.
S-OFF phone can flash unsigned firmware package, like this one, with a modded bootloader (hboot), no matters what the version is can be done with an locked/unlocked/relocked bootloader.