Database Develop

[Q] Flashing Hboot - Answered!

I see that most CM7's require the new hboot. I have flashed, pushed, fastbooted, just about anything you can do with ADB and am quite comfortable with it but i can't find anywhere the instructions on just "how to" flash the new hboot to the N1. Is it as easy as placing the zip on the sd and flashing through recovery or is there more to it? I even tried looking in the Wiki and it showed the newest hboot but not how to flash. Thanks in advance!!

I thought it was possible to flash from recovery but after some digging around i'm not so sure now. Best to check with somebody who has done this

I flashed new hboot using cw recovery just this morning. No worries.

Thanks for the reply!

fastboot flash hboot whatever_hboot_you_want.img

Hi, am trying to flash my HBOOT, downloaded d6096cac5e9f.signed-hboot-0.35.0017.zip and currently trying to flash but getting this error:
Code:
$ ./fastboot flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
The phone is unlocked and fastboot can see the device, any ideas?

braingravyuk said:
Hi, am trying to flash my HBOOT, downloaded d6096cac5e9f.signed-hboot-0.35.0017.zip and currently trying to flash but getting this error:
Code:
$ ./fastboot flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
The phone is unlocked and fastboot can see the device, any ideas?
Click to expand...
Click to collapse
I think what they are saying is you can flash that .zip through clockwork and not worry about fastboot. Try that and let me know if that works for you.

just disable verification check and then flash. worked for me

Just in the process of rooting the phone... just rooted it and about to install RA recovery.. guess I'll flash it through that

Just tried to flash in RA Recovery got the following:
Code:
Install:d6096cac5e9f.signed.hboot-0.35.0017.zip?
Press Trackball to confirm,
any other key to abort.
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:No signature (8 files)
E: Verification failed
Zip verification failed!
Zip isn't signed correctly!
Installation aborted.
Surely if the thing is signed then there shouldn't be a problem with the signature?

Check the md5 on the file...
Sent from my Nexus One using XDA App

Hi,
the md5sum is coming back with:
Code:
b0669d79f3ace07fdd3e1c03d88d2c68 d6096cac5e9f.signed-hboot-0.35.0017.zip

tah318 said:
just disable verification check and then flash. worked for me
Click to expand...
Click to collapse
Try this in AR recovery and see if you can flash then.

In AR recovery main menu select flash zip, then in that menu under "select zip" is toggle verification. Select that once and you will get a warning that unsinged zip can corrupt. then you can choose "select zip" and flash the hboot zip from the sd card.

Jack_R1 said:
fastboot flash hboot whatever_hboot_you_want.img
Click to expand...
Click to collapse
I don't think that's correct. It should be: fastboot flash misc whatever_hboot_you_want.img
Sent from my Nexus One using XDA App

braingravyuk said:
Hi,
the md5sum is coming back with:
Code:
b0669d79f3ace07fdd3e1c03d88d2c68 d6096cac5e9f.signed-hboot-0.35.0017.zip
Click to expand...
Click to collapse
Thanks for the tip, just wondering if anyone can confirm the md5sum, there isn't one shown on the sticky for kernels and radios.
Cheers

braingravyuk said:
Thanks for the tip, just wondering if anyone can confirm the md5sum
Click to expand...
Click to collapse
That's the correct value. Note that the d6096cac5e9f is the prefix of the sha1 checksum.

efrant said:
I don't think that's correct. It should be: fastboot flash misc whatever_hboot_you_want.img
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Im 100% sure its fastboot flash hboot whicheverhboot.img
your way may or may not work but this way does

deleted...

Why isn't the RUU restoring the recovery partition/image?

I have an HTC One developer edition (64GB), and I've flash Clockwork Recovery to it.
However, when I relock the bootloader and install the RUU, it doesn't overwrite the recovery partition.
What can I be doing wrong?
I've tried fooling around with the "HTC Fast boot" (in the Sense menu, not the sdk fastboot) but I can't seem to figure out what I'm doing wrong...

sofakng said:
I have an HTC One developer edition (64GB), and I've flash Clockwork Recovery to it.
However, when I relock the bootloader and install the RUU, it doesn't overwrite the recovery partition.
What can I be doing wrong?
I've tried fooling around with the "HTC Fast boot" (in the Sense menu, not the sdk fastboot) but I can't seem to figure out what I'm doing wrong...
Click to expand...
Click to collapse
actually what are you trying to achieve?

Well, mostly I'm just trying to learn more about how Android works. I was able to restore the RUU before and it even removed the tampered boot loader warning but now my RUU doesn't seem to restore everything. It's very inconsistent so that's why I'm trying to figure out exactly how this works and what I might be doing differently.
Maybe I have to clear the (dalvik) cache before running the RUU?

sofakng said:
Well, mostly I'm just trying to learn more about how Android works. I was able to restore the RUU before and it even removed the tampered boot loader warning but now my RUU doesn't seem to restore everything. It's very inconsistent so that's why I'm trying to figure out exactly how this works and what I might be doing differently.
Maybe I have to clear the (dalvik) cache before running the RUU?
Click to expand...
Click to collapse
it shouldn't be needed, you only need to lock your bootloader and then run the RUU and that will bring everything to stock

matt95 said:
it shouldn't be needed, you only need to lock your bootloader and then run the RUU and that will bring everything to stock
Click to expand...
Click to collapse
Ok, something is wrong then...
My boot loader says relocked and tampered but after running the RUU, recovery doesn't work (it just reboots if I try to enter recovery and shows the developer warning before rebooting)...

sofakng said:
Ok, something is wrong then...
My boot loader says relocked and tampered but after running the RUU, recovery doesn't work (it just reboots if I try to enter recovery and shows the developer warning before rebooting)...
Click to expand...
Click to collapse
it worked in your case the stock recovery always gives that symbol there's nothing wrong with it

Maybe I'm not explaining it properly, but for example, I JUST relocked my bootloader and ran the RUU.
It restored successfully.
However, if I boot into the bootloader and then recovery, it boots into clockwork recovery! That means the RUU didn't overwrite my recovery partition...
Shouldn't the RUU restore the stock recovery?!

sofakng said:
Maybe I'm not explaining it properly, but for example, I JUST relocked my bootloader and ran the RUU.
It restored successfully.
However, if I boot into the bootloader and then recovery, it boots into clockwork recovery! That means the RUU didn't overwrite my recovery partition...
Shouldn't the RUU restore the stock recovery?!
Click to expand...
Click to collapse
Try getting the .zip one and do a fastboot version. Works for me.
tozfeekum said:
I'm trying to return my HTC developer edition back to stock
and I am running the RUU via terminal:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip.
I've tried running it immediately as suggested in other threads but that hasn't worked.
Does anyone know what's going on here:
ending 'zip' (1004418 KB)...
OKAY [ 34.434s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 165.173s
EDIT:
I got this working by running fastboot erase cache
Click to expand...
Click to collapse
I'm not sure if you're also experiencing the recovery partition missing, like in my thread.
http://forum.xda-developers.com/showthread.php?t=2267008

Hmmmm, maybe that's my problem?
I've just flashed the ZIP, and everything looked like it worked fine... (I received the "please flush image" message and I re-ran the flash and it then completely successfully)
However, when I select [Recovery] from HBOOT, the screen flashes for a second, and then it returns to the HBOOT again. It does seem like the recovery partition is missing...?
Here is my fastboot log: http://pastebin.com/KQJjE78a
EDIT: When I unlocked my bootloader (fastboot flash unlocktoken), and then tried to enter recovery, it went back into clockwork recovery!!
The RUU/ZIP is absolutely, positively, not overwriting my recovery... (which is also why the bootloader still says "tampered" as well, because the entire stock image is not being 100% restored)

I have the same exact problem with my one dev edition.Hope someone can figure this out
Sent from my HTC One using xda premium

Glad to see I'm not the only one!
I've decrypted the RUU ZIP file and extracted the signed recovery.img, but I think decrypting the ZIP changes the checksum so when I try to flash it to the bootloader it says the signature failed.
I've been trying all kinds of things and I have gotten it to work (and the tampered warning was removed), but I have no idea what combination of commands/images I used to get it working...
Hopefully somebody can help us

sofakng said:
Glad to see I'm not the only one!
I've decrypted the RUU ZIP file and extracted the signed recovery.img, but I think decrypting the ZIP changes the checksum so when I try to flash it to the bootloader it says the signature failed.
I've been trying all kinds of things and I have gotten it to work (and the tampered warning was removed), but I have no idea what combination of commands/images I used to get it working...
Hopefully somebody can help us
Click to expand...
Click to collapse
you succeeded in installing the recovery then?

matt95 said:
you succeeded in installing the recovery then?
Click to expand...
Click to collapse
Yes, a few days ago it worked but now it's not working any more and I'm not sure what combination of events occured when it did work...

sofakng said:
Yes, a few days ago it worked but now it's not working any more and I'm not sure what combination of events occured when it did work...
Click to expand...
Click to collapse
the stock one i mean..? where did you get it? from a nandroid backup or from the RUU itself?

The only way I have fixed this is flashing stock recovery from one of Mike's post ...but I think it's from the at&t model ...not sure if that makes a difference but I do get it working then
Sent from my HTC One using xda premium

martyotaku said:
The only way I have fixed this is flashing stock recovery from one of Mike's post ...but I think it's from the at&t model ...not sure if that makes a difference but I do get it working then
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmmm, so there is a signed recovery image floating around somewhere? Any idea which post has it?
I've also been able to successfully get mine restored but it seems like it worked by some random chance.
Here's what I think I did differently:
* Turned off phone for five minutes
* Unplugged USB cable until I entered fastboot
I have no idea if that's why the RUU finally worked but I'd love to know for sure in case I need to perform this in the future.

sofakng said:
Hmmm, so there is a signed recovery image floating around somewhere? Any idea which post has it?
I've also been able to successfully get mine restored but it seems like it worked by some random chance.
Here's what I think I did differently:
* Turned off phone for five minutes
* Unplugged USB cable until I entered fastboot
I have no idea if that's why the RUU finally worked but I'd love to know for sure in case I need to perform this in the future.
Click to expand...
Click to collapse
Did you do the fastboot erase cache?
The way I got it back to stock recovery was doing this.
When I had CWM, I attempted to fastboot a different recovery using this.
http://forum.xda-developers.com/showthread.php?t=2158763&highlight=recovery+img
It installed but it never worked as the phone could not enter. Then I just fastboot the factory zip and it some how overriden the faulty recovery and it worked.

I'm not home now and hate using this app lol I'll post it when I get home ...but it's from dev mikes post
edit here is what i used from this link http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html

Trouble flashing 4.3 radio

I basically get
writing 'zip'...
bootlader zip header checking
bootloader zip info parsing..
bootloader read zipped android_info fail
FAILEd remove: 24 parsing android-info fail
finished. total tim: 2.465s
any ideas?

Are you flashing it from recovery?

bigdaddy619 said:
Are you flashing it from recovery?
Click to expand...
Click to collapse
fastboot

PaulB007 said:
fastboot
Click to expand...
Click to collapse
Also, when pushing through fastboot with the firmware update the hboot updates but I get the remote 90 error issue. It doesnt seem to want to update the radio, so I wonder how much of the firmware even pushed to my device..

If it's a zip from the Radio thread just flash it from recovery

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?

Can't flash firmware, cant RUU

unlocked
s-on
Can't RUU, FUU, or flash via FASTBOOT.
Trying to flash latest 3.30 firmware from this thread
http://forum.xda-developers.com/showthread.php?t=2729173
trying to flash "3.30.651.2 Full Firmware from OTA (fastboot flashable)"
on my non HK device. Tried from various roms, including latest insert coin, and my original stock backup.
Installed htc sync to make sure drivers are correct, unintalled htc sync so it doesn't interfere.
firewater failed s-off.
unually says unknown error of some sort but nothing specific in any flashing methods.
any ideas helpfull.
Sprint_HTC_One_M8_3.30.651.2_RUU failed as well.
flashing firmware with adb/fastboot
sending 'zip' (51931 KB)...
OKAY [ 2.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.427s
RUU says error 155, download correct ruu and try agin...

You have to re-lock your bootloader

BD619 said:
You have to re-lock your bootloader
Click to expand...
Click to collapse
can i do that while s-on?

badname said:
can i do that while s-on?
Click to expand...
Click to collapse
Yes
fastboot oem lock

BD619 said:
Yes
fastboot oem lock
Click to expand...
Click to collapse
said some errors but says relocked now, firmware update failed with
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.464s
had a communication error with RUU, restarting things, trying again

I had a similar problem, so I bought a MicroSD card and trying flashing the RUU that way and it worked on the first try.

RUU went through. Now maybe by some chance firewater will work...

badname said:
RUU went through. Now maybe by some chance firewater will work...
Click to expand...
Click to collapse
Most likely it won't and you'll need to use the Sunshine exploit.

Firewater won't work. If you look at my thread from a couple days ago I had the exact same issues. Ruu in fastboot, unlock bootloader, install twrp 281, and run sunshine.
Sent from my HTC One_M8 using XDA Free mobile app