Database Develop

ICS ROM bricked my Raider, has old hboot, unlocked, how to relock getting error

I have a soft-bricked Raider that I dont know the history of and looks like it was updated to a ICS ROM with out updating the hboot, it has hboot 1.83.0014 and unlocked, a getver all shows the version-main to be 1.65.666.3 so I google that up and found this ICS image...
OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip
http://forum.xda-developers.com/showthread.php?t=1498003
So it appear I need to lock my bootloader and update the hboot.
When I run oem lock this is what I get.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Unknown error))
finished. total time: 0.022s
I let it sit for 15 minutes but no change.
what do I need to do to get my bootloader relocked?

That's relocked. Reboot into hboot.
Sent from an HTC Vivid via XDA Premium

I have do.e fastboot OEM lock 5 or more times on this phone and it says *** locked *** when I reboot into hboot

http://forum.xda-developers.com/showthread.php?t=1421760
Maybe you can try this tool to wipe your device. I have no idea if it will work. It's worth reading up on though.

Tx I will check that when I get home

MORE BAD NEWS
I yanked zom.zip out of the RUU for my Raider.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.197s]
finished. total time: 0.199s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 1.184s]
finished. total time: 1.186s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip c:\
junk\zom.zip
sending 'zip' (420878 KB)...
OKAY [ 39.172s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 40.786s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
so ends up the EMMC chip has bad sectors and this is a problem with this phone. I ended up on freenode at #htc-holiday and had a good chat with IOMonster, so I will try to return the phone to HTC 866.449.8358 and if not I will do the following.
by the way fastboot boot recovery-beta2.img did get me into recovery -- strange no one pointed that out to me...
The above error is how I found out the EMMC chip has write errors.
I will try to remember to come back and post what happens when I call HTC tomorrow.

bobmutch2 said:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 1.184s]
finished. total time: 1.186s
Click to expand...
Click to collapse
Did you solved it? I have a same problem [SD/EMMC]Error status=0x400008.

[q] help plzz fast....

NEED HELP PLZZ
I was trying to change the MID,CID with this guide http://forum.xda-developers.com/showthread.php?t=2322820 and now i'm stuck on the last step with my HTC One on with that gray screen and whenn i try to flash the RUU from this guide http://htc-one.wonderhowto.com/how-to/convert-any-htc-one-into-stock-google-play-edition-with-bootloader-recovery-ota-updates-0148068/ i get this:
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'

Did you do this:
fastboot oem rebootRUU.
fastboot flash zip filename
fastboot flash zip filename (second time) ?

SaHiLzZ said:
Did you do this:
fastboot oem rebootRUU.
fastboot flash zip filename
fastboot flash zip filename (second time) ?
Click to expand...
Click to collapse
when i use : fastboot oem reboot RUU the screen gose black and nothing hapens :/

Post a fastboot getvar all output

SaHiLzZ said:
Post a fastboot getvar all output
Click to expand...
Click to collapse
so i manage to get my HTC running again but couldn't install tha RUU:
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'
C:\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.046s]
finished. total time: 0.046s
C:\sdk\platform-tools>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip
sending 'zip' (467625 KB)...
OKAY [ 22.085s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 23.430s
C:\sdk\platform-tools>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip
< waiting for device >
target reported max download size of 1526722560 bytes
sending 'zip' (467625 KB)...
OKAY [ 23.033s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 23.450s

The error is obviously MID. Fix it!

SaHiLzZ said:
The error is obviously MID. Fix it!
Click to expand...
Click to collapse
i fixed the MID isue and now sows an other error -.-
C:\sdk\platform-tools>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip
target reported max download size of 1526722560 bytes
sending 'zip' (467625 KB)...
OKAY [ 23.207s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 23.242s

You didn't do rebootruu

sahilzz said:
you didn't do rebootruu
Click to expand...
Click to collapse
omg works perfect now i have htc one google play edition thanks a lot :ddddd

[Q] bricked?

hey i may have messed up my nexus 6 already. unlocked the bootloader, rooted it with no problem. downloaded the twrp from play store and installed. got an install error. i looked online for someone having the issue and they said they got error and booted into recovery and it was working. i did the same. once in recovery i did a hard reset just to see if it was working, it worked. after that i hit fix permissions. and then phone would never boot. i was a little drunk so i went into recovery again, and wiped but this time i checked system. not smart i know, but what can i say. now phone boots upto google screen with unlock icon? what do i do?

Reflash factory imagine

Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

El Daddy said:
Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.

uncfan44 said:
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.
Click to expand...
Click to collapse
Sometimes you have to install the drivers on your computer again while your phone is connected and in the boot loader.
Also, if you don't have your environment variables set up correctly, you'll have to open the command prompt from the same folder in which fastboot.exe lies. As well as putting the image files in that folder.
Sent from my Nexus 5 using Tapatalk

and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.

uncfan44 said:
and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.
Click to expand...
Click to collapse
Make sure you have fastboot selected in bootloader and try this tool to make sure fastboot is installed in your machine properly.
http://forum.xda-developers.com/showthread.php?t=2588979

ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!

uncfan44 said:
ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!
Click to expand...
Click to collapse
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!

Make sure you have the newest fastboot and flash everything manually. If you don't have the newest fastboot it'll throw errors.

12MaNy said:
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!
Click to expand...
Click to collapse
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>

uncfan44 said:
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>
Click to expand...
Click to collapse
You have the latest fastboot installed? Also the system image from Google was extracted to platform tools? And lastly did u check md5 of original download?
Definitely not something wrong with the commands your using.

yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.

uncfan44 said:
yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.
Click to expand...
Click to collapse
I know im a little late but you can just use wugfresh nexus toolkit and flash back to stock.

[HELP REQUEST] Carrier signal problem on my HTC

Hello XDA, hoping everyone is doing great..
Unfortunately i am not doing so great my HTC has become a pain in the a**! lol
When i first got my HTC it was working great signal was strong and everything was working flawlessly.
I decided to get my device S-off, rooted and change the rom to cm 12.1 i was able to do it fine, i Also have twrp 3 too.
This is the info of my phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT358W908664
(bootloader) imei: Hidden
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4135mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The carrier was working fine until later on i decided to install Viperone i was able to install it fine and it was working fine when it booted. i did notice that for some reason now my device is back to S-on and has hboot 1.61 which prevents me to get s-off and change the CID because for some reason i'm getting a T-Mobile CID now
Code:
cidnum: T-MOB010
When i rebooted the phone it won't detect the sim card at all when i check the IMEI it displays unknown, same thing with the baseband but if when i do
Code:
fastboot getvar
i see my IMEI there but when the phone is booted when i do *#06# i get unknown. I don't know what went wrong and i am out of ideas.
By the way i not longer on Viperone i changed to a Google version and the same thing happened. First boot i got signal and after reboot no sim card detect it
Is there a way to get it to stock without having to do S-off, iv'e seen a couple of posts but none of the links are working.
I can't flash RUU since i am on 1.61 and can't get it s-off.
Could this be a radio or firmware issue? Or what can be causing this? Or how can i get it back to stock fully without having to s-off if that is possible.
I would really appreciate some help, Thank you very much

jisgore said:
Hello XDA, hoping everyone is doing great..
Unfortunately i am not doing so great my HTC has become a pain in the a**! lol
When i first got my HTC it was working great signal was strong and everything was working flawlessly.
I decided to get my device S-off, rooted and change the rom to cm 12.1 i was able to do it fine, i Also have twrp 3 too.
This is the info of my phone:
The carrier was working fine until later on i decided to install Viperone i was able to install it fine and it was working fine when it booted. i did notice that for some reason now my device is back to S-on and has hboot 1.61 which prevents me to get s-off and change the CID because for some reason i'm getting a T-Mobile CID now
When i rebooted the phone it won't detect the sim card at all when i check the IMEI it displays unknown, same thing with the baseband but if when i do i see my IMEI there but when the phone is booted when i do *#06# i get unknown. I don't know what went wrong and i am out of ideas.
By the way i not longer on Viperone i changed to a Google version and the same thing happened. First boot i got signal and after reboot no sim card detect it
Is there a way to get it to stock without having to do S-off, iv'e seen a couple of posts but none of the links are working.
I can't flash RUU since i am on 1.61 and can't get it s-off.
Could this be a radio or firmware issue? Or what can be causing this? Or how can i get it back to stock fully without having to s-off if that is possible.
I would really appreciate some help, Thank you very much
Click to expand...
Click to collapse
1st, if your phone is back to s-on it's because you did the command to turn it back s-on. It can't change by itself "for some reasons" like youv said. Same thing for the CID.
Anyway you don't need s-off to flash a RUU. Flash the 7.18.531.2 ruu (see the ruu collection thread in the general section). The ruu and instructions how to flash are at post #1 and you'll probably have to follow the guide at the end of post #2 to write the correct version-main before flashing the ruu.
If you still have the same issue after successfuly flashing the RUU then it's an hardware problem, most likely with the baseband processor.
Sent from my HTC One using XDA Labs

alray said:
1st, if your phone is back to s-on it's because you did the command to turn it back s-on. It can't change by itself "for some reasons" like youv said. Same thing for the CID.
Anyway you don't need s-off to flash a RUU. Flash the 7.18.531.2 ruu (see the ruu collection thread in the general section). The ruu and instructions how to flash are at post #1 and you'll probably have to follow the guide at the end of post #2 to write the correct version-main before flashing the ruu.
If you still have the same issue after successfuly flashing the RUU then it's an hardware problem, most likely with the baseband processor.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Thank you for the brief response alray. I did find that RUU on HTC website im downloading. I will test it and get back to you. Thanks again

i have same problem , have same H-boot , try update RUU , Ota not fix problem , change radio baseband get same error , first boot have signal and working fine no longer phone hang and signal lose after reboot , baseband unknow i dont know what worng .

after trying many times i can't get the RUU to install correctly i have only been able to find the .exe from the htc website. I have tried using the ones on HTC1Guru it installs but then when booting it seems is going to work and loads up but them restarts and i get softbricked and i have to flash recovery again,
EDIT: I found the RUU trying again

Can't flash the ruu:
Code:
:\Program Files (x86)\Android\android-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.164s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fasboot oem rebootRUU
'fasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
< waiting for any device >
...
(bootloader) Start Verify: 3
OKAY [ 0.093s]
finished. total time: 0.094s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
sending sparse 'zip' 1/2 (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
OKAY [ 58.548s]
writing 'zip' 1/2...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 218.295s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 3.334s]
finished. total time: 3.335s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
sending sparse 'zip' 1/2 (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
OKAY [ 58.552s]
writing 'zip' 1/2...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 523.855s

jisgore said:
Can't flash the ruu:
Code:
:\Program Files (x86)\Android\android-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.164s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fasboot oem rebootRUU
'fasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
< waiting for any device >
...
(bootloader) Start Verify: 3
OKAY [ 0.093s]
finished. total time: 0.094s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
sending sparse 'zip' 1/2 (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
OKAY [ 58.548s]
writing 'zip' 1/2...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 218.295s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 3.334s]
finished. total time: 3.335s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
sending sparse 'zip' 1/2 (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 94273929 is not a multiple of the block size 4096
OKAY [ 58.552s]
writing 'zip' 1/2...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 523.855s
Click to expand...
Click to collapse
are you using htc_fastboot.exe or the regular fastboot.exe? You must use htc's version of fastboot to flash newer RUU like explained in the ruu thread.

I was using the fastboot from android SDK. I have one I downloaded from HTC website. Do I have to rename it to htc_fastboot ?

jisgore said:
I was using the fastboot from android SDK. I have one I downloaded from HTC website. Do I have to rename it to htc_fastboot ?
Click to expand...
Click to collapse
the name of the file itself doesn't matters just make sure you are using the same name in the command window.

Ok, i am trying again now with the HTC fastboot

I downloaded the ruu.exe from HTC now it go as far as step 4/6 and then i get "Error [132]: Signature error" .
Before i tried this i noticed that when i did "fastboot getvar all" on this part was blank before (version-main: ) and now is showing (version-main: 7.18.531.2) I'm am going to try this method now instead http://forum.xda-developers.com/showthread.php?t=2497614

After succesfully installing the RUU i still have the same problem. Well basically the same but now i get the carrier popping up but it says no service. Will it make a difference if i SuperCID?

jisgore said:
After succesfully installing the RUU i still have the same problem. Well basically the same but now i get the carrier popping up but it says no service. Will it make a difference if i SuperCID?
Click to expand...
Click to collapse
Supercid? CID doesn't affect carrier signal, its only used to determine which versions of ota updates your phone will receive.

stuck on white logo htc (not bootloop)

tried a lot of custom roms, ruu, flashing by fastboot i've the same problem, i can see the lockscreen, bar but when i unlock phone all i can see is this logo htc, exact same like in bootloop, dont know what should i do, any ideas?

jeffseid6 said:
tried a lot of custom roms, ruu, flashing by fastboot i've the same problem, i can see the lockscreen, bar but when i unlock phone all i can see is this logo htc, exact same like in bootloop, dont know what should i do, any ideas?
Click to expand...
Click to collapse
I didn't want to leave this unanswered and was hoping someone would have ideas. If you've successfully run the RUU and the phone reboots but still has problems, then I'm not sure what else to do. Resetting to stock via the RUU should fix all software issues AFAIK.

I'm running into similar issues trying to put the phone back to stock. I've tried RUU and just about everything else. Nothing I do works. Anyone have any suggestions?

Htc one A9 firmware flashing problem
htc one a9 (model: 2PQ9100) see the error below i'm facing please help me i am very upset
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1166400000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 617001178 is not a multiple of the block size 4096
sending sparse 'zip' (1139061 KB)...
error: write_sparse_skip_chunk: don't care size 617001178 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 617001178 is not a multiple of the block size 4096
OKAY [ 53.554s]
writing 'zip'...
(bootloader) HOSD CL#853511
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_z
(bootloader) EOonp
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 91.572s