Root [AT&T] RUU & OTA Questions

[sharksfan7]

My One is S-OFF & rooted w/ TWRP recovery. Still running the stock ROM but have edited some system files and deleted some system apps. So the 4.4.2 OTA won't install. I've read that I can install the 4.3 RUU then the OTA and just flash TWRP & SuperSU again and I'd be good to go. But I have a few questions before I do so.

I used Firewater to S-OFF. With the temproot method, I didn't unlock the bootloader through HTCDev first but it was unlocked when Firewater was done doing its voodoo. If I run the RUU and the OTA will the bootloader be replaced with a locked version? If so, are there any issues with unlocking it again through HTCDev? I've read a few posts stating that HTC no longer supports unlocking the bootloader on AT&T devices (not sure if that's accurate, though). Being S-OFF, do I even need to worry about unlocking the bootloader? With the Inspire, I was S-OFF for a couple of years before I upgraded to an unlockable bootloader. But I never really used fastboot commands to flash any of the stuff I did with that. It seems with the One, most stuff is done through fastboot. Will I still be able to run all the fastboot commands that I would need if the bootloader is locked?

If after updating I decide for some reason to go back to 4.3 and restore a nandroid, will the firmware updgrades from the OTA remain? If they do, are there any compatibility issues when using newer firmware with the older ROM? (I'm still not entirely clear on what constitutes "firmware".)

Thanks for reading my ridiculously long post. Always appreciate the help as I try to figure out all this stuff.

 

[clsA]

My One is S-OFF & rooted w/ TWRP recovery. Still running the stock ROM but have edited some system files and deleted some system apps. So the 4.4.2 OTA won't install. I've read that I can install the 4.3 RUU then the OTA and just flash TWRP & SuperSU again and I'd be good to go. But I have a few questions before I do so.

I used Firewater to S-OFF. With the temproot method, I didn't unlock the bootloader through HTCDev first but it was unlocked when Firewater was done doing its voodoo. If I run the RUU and the OTA will the bootloader be replaced with a locked version? If so, are there any issues with unlocking it again through HTCDev? I've read a few posts stating that HTC no longer supports unlocking the bootloader on AT&T devices (not sure if that's accurate, though). Being S-OFF, do I even need to worry about unlocking the bootloader? With the Inspire, I was S-OFF for a couple of years before I upgraded to an unlockable bootloader. But I never really used fastboot commands to flash any of the stuff I did with that. It seems with the One, most stuff is done through fastboot. Will I still be able to run all the fastboot commands that I would need if the bootloader is locked?

If after updating I decide for some reason to go back to 4.3 and restore a nandroid, will the firmware updgrades from the OTA remain? If they do, are there any compatibility issues when using newer firmware with the older ROM? (I'm still not entirely clear on what constitutes "firmware".)

Thanks for reading my ridiculously long post. Always appreciate the help as I try to figure out all this stuff.

Your s-off so the bootloader lock is not needed
just flash the RUU.zip found here
RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted - HTC1Guru
Take the OTA update
reflash recovery TWRP 2.6.3.3 from here > Techerrata Downloads - Browsing m7

enter recovery and choose yes to root on exit
setup and enjoy your new phone.

Be aware that the RUU.zip I posted will totally wipe you phone ... if this is not what you want you can edit the RUU.zip by deleting all the dzdata files before flashing and your sdcard should remain untouched (I still backup to PC first just in case)

 

[scotty85]

My One is S-OFF & rooted w/ TWRP recovery. Still running the stock ROM but have edited some system files and deleted some system apps. So the 4.4.2 OTA won't install. I've read that I can install the 4.3 RUU then the OTA and just flash TWRP & SuperSU again and I'd be good to go. But I have a few questions before I do so.

I used Firewater to S-OFF. With the temproot method, I didn't unlock the bootloader through HTCDev first but it was unlocked when Firewater was done doing its voodoo. If I run the RUU and the OTA will the bootloader be replaced with a locked version? If so, are there any issues with unlocking it again through HTCDev? I've read a few posts stating that HTC no longer supports unlocking the bootloader on AT&T devices (not sure if that's accurate, though). Being S-OFF, do I even need to worry about unlocking the bootloader? With the Inspire, I was S-OFF for a couple of years before I upgraded to an unlockable bootloader. But I never really used fastboot commands to flash any of the stuff I did with that. It seems with the One, most stuff is done through fastboot. Will I still be able to run all the fastboot commands that I would need if the bootloader is locked?

If after updating I decide for some reason to go back to 4.3 and restore a nandroid, will the firmware updgrades from the OTA remain? If they do, are there any compatibility issues when using newer firmware with the older ROM? (I'm still not entirely clear on what constitutes "firmware".)

Thanks for reading my ridiculously long post. Always appreciate the help as I try to figure out all this stuff.

Hmm ill try and not miss anything

1)no,the ruu will not change what I refer to as your "lock status" with s off you can ruu while unlocked,and you still will be after

2)now that you're s off,you don't need to fool with htcdev(and shoulnt) if you need to lock or unlock,you can use a recovery tool made by crushalot,or use a couple simple adb commands(my recomendation). I hadn't heard about att closing the bootloader door,but while were on the subject,let's make sure we understand that any such action is att's doing,not HTC's

3)just like your inspire,you don't need to be unlocked at all. Recovery and anything else can be installed as a zip file in ruu mode with a locked bootloader. Being unlocked is a personal preference,not a requirement

4)if you nandroid back to 4.3,the newer firmware will remain. In this case,that should not cause any issue.

5)firmware is basically software that controls hardware. Things like the bootloader,radio,touch panel,and a few other bits are firmware. Software are what make up the rom(kernel aka boot and system) and recovery.

Hope that helps clear it up

 

[sharksfan7]

Your s-off so the bootloader lock is not needed
just flash the RUU.zip found here
RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted - HTC1Guru
Take the OTA update
reflash recovery TWRP 2.6.3.3 from here > Techerrata Downloads - Browsing m7

enter recovery and choose yes to root on exit
setup and enjoy your new phone.

Be aware that the RUU.zip I posted will totally wipe you phone ... if this is not what you want you can edit the RUU.zip by deleting all the dzdata files before flashing and your sdcard should remain untouched (I still backup to PC first just in case)

Thanks, clsA! It was one of your posts on xda that set me on this road to enlightenment. Appreciate you providing the steps to follow.

....

Hope that helps clear it up

Can always count on Scotty to come through in the clutch. As they say, "The Devil is in the details" and these were exactly the details I needed. Thanks again.

As for flashing things in RUU mode, do I just

fastboot oem rebootRUU

and then run the fastboot commands as I normally would from fastboot mode? Or are there different commands to use in RUU mode? Guess I need to track down an RUU mode tutorial.

 

[scotty85]

As for flashing things in RUU mode, do I just

fastboot oem rebootRUU

and then run the fastboot commands as I normally would from fastboot mode? Or are there different commands to use in RUU mode? Guess I need to track down an RUU mode tutorial.

first of all the files you use must be the same type you used to flash from the sd card. i.e. a recovery image(or whatever firmware youre flashing) and an android info text document. let me know if you have trouble finding the recovery you want packed up this way. or just pack them up yourself,youll do it just like you did for your inspire.

you then put the file into your adb/fastboot folder,and flash it in the following manner:

Spoiler

if youre working with a booted,operational phone,you can flsh the file in the following manner:

-open a cmd window

-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )

-place the zip file you want to flash into adb/fastboot directory

-enable usb debug,disable fastboot,plug in phone

-check for connectivity
adb devices (should return serial number)

-boot to fastboot
adb reboot bootloader

-check for connectivity again
fastboot devices

-flash the file
fastboot erase cache

fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)

fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)

*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish

-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)

-reboot back to the OS
fastbooot reboot

you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices

 

[clsA]

Thanks, clsA! It was one of your posts on xda that set me on this road to enlightenment. Appreciate you providing the steps to follow.



Can always count on Scotty to come through in the clutch. As they say, "The Devil is in the details" and these were exactly the details I needed. Thanks again.

As for flashing things in RUU mode, do I just

fastboot oem rebootRUU

and then run the fastboot commands as I normally would from fastboot mode? Or are there different commands to use in RUU mode? Guess I need to track down an RUU mode tutorial.

The RUU flashing instructions were on the htc1guru's site very easy to follow

 

[sharksfan7]

first of all the files you use must be the same type you used to flash from the sd card. i.e. a recovery image(or whatever firmware youre flashing) and an android info text document. let me know if you have trouble finding the recovery you want packed up this way. or just pack them up yourself,youll do it just like you did for your inspire.

Okay. That seems pretty straight forward. There are still some things about this that I'm curious about, but I'll tackle those when the need arises. Whenever something has come up that I need to do, someone usually has already posted a how-to.

Thanks guys.

 

[sharksfan7]

I posted some questions on a thread over on xda but my stuff always seems to get buried unanswered over there. So I'll ask here & I'm sure you guys will set me straight.

I never got around to RUU'ing back to stock 4.3 to take the OTA like I asked about originally. Now with the 4.4 Sense 5.5 RUU available some confusion has crept in again regarding what can/can't be used with all the different security & lock states. If I'm S-OFF w/ unlocked bootloader, can I run the ruu.exe? Or am I better off waiting for a decrypted ruu.zip?

As far as I understand it, I believe I can pretty much run anything w/ S-OFF and it's up to me to make sure that what I run is compatible with my device, lest I risk bricking it. Is that an accurate assessment? Are there any avenues to restore that cannot or should not be used while S-OFF? Are there any that would require relocking the bootloader while S-OFF?

Also, I believe the appropriate RUU for my AT&T One (CWS__001/PN0712000) is RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe. What does the "MR" refer to? I can pretty much decipher all the other bits except the "MR". I noticed that with the earlier RUU versions, some have the "MR" & some do not. Oh, and if that isn't the correct ruu for my device, can you point me to the one that is?

As always, thanks.

 

[scotty85]

I posted some questions on a thread over on xda but my stuff always seems to get buried unanswered over there. So I'll ask here & I'm sure you guys will set me straight.

I never got around to RUU'ing back to stock 4.3 to take the OTA like I asked about originally. Now with the 4.4 Sense 5.5 RUU available some confusion has crept in again regarding what can/can't be used with all the different security & lock states. If I'm S-OFF w/ unlocked bootloader, can I run the ruu.exe? Or am I better off waiting for a decrypted ruu.zip?

As far as I understand it, I believe I can pretty much run anything w/ S-OFF and it's up to me to make sure that what I run is compatible with my device, lest I risk bricking it. Is that an accurate assessment? Are there any avenues to restore that cannot or should not be used while S-OFF? Are there any that would require relocking the bootloader while S-OFF?

Also, I believe the appropriate RUU for my AT&T One (CWS__001/PN0712000) is RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe. What does the "MR" refer to? I can pretty much decipher all the other bits except the "MR". I noticed that with the earlier RUU versions, some have the "MR" & some do not. Oh, and if that isn't the correct ruu for my device, can you point me to the one that is?

As always, thanks.

You are correct,you are free to run the ruu.exe while s off and unlocked. Being s off removes almost all the security checks:
-lock status
-main version
-bootloader version
-HTC signiture

The only things the phone pays attention to while s off is the cid and mid. Changing the cid to supercid(11111111) eliminates the the cid and mid checks,making it a true statement that the phone will flash literally anything however,rest assured that leaving your stock cid and mid does offer some protection against accidentally flashing an incorrect ruu.

As far as the decrypted vs the official signed ruu,you can use either. The biggest advantage to using the decrypted ruu would be if you wanted your custom recovery to remain in place,you could delete the stock image from the decrypted version. If you wanted to be 100% stock,then the decrypted ruu offers no advantage. Going back to stock,the signed ruu may be a better choice,as you can be 100% certain that all the firmware and images HTC intended are present.

That is a correct att ruu,you should be fine to run it. The MR stands for "maintenance release"

Hope that clears it up

 

[clsA]

I posted some questions on a thread over on xda but my stuff always seems to get buried unanswered over there. So I'll ask here & I'm sure you guys will set me straight.

I never got around to RUU'ing back to stock 4.3 to take the OTA like I asked about originally. Now with the 4.4 Sense 5.5 RUU available some confusion has crept in again regarding what can/can't be used with all the different security & lock states. If I'm S-OFF w/ unlocked bootloader, can I run the ruu.exe? Or am I better off waiting for a decrypted ruu.zip?

As far as I understand it, I believe I can pretty much run anything w/ S-OFF and it's up to me to make sure that what I run is compatible with my device, lest I risk bricking it. Is that an accurate assessment? Are there any avenues to restore that cannot or should not be used while S-OFF? Are there any that would require relocking the bootloader while S-OFF?

Also, I believe the appropriate RUU for my AT&T One (CWS__001/PN0712000) is RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe. What does the "MR" refer to? I can pretty much decipher all the other bits except the "MR". I noticed that with the earlier RUU versions, some have the "MR" & some do not. Oh, and if that isn't the correct ruu for my device, can you point me to the one that is?

As always, thanks.

You are correct,you are free to run the ruu.exe while s off and unlocked. Being s off removes almost all the security checks:
-lock status
-main version
-bootloader version
-HTC signiture

The only things the phone pays attention to while s off is the cid and mid. Changing the cid to supercid(11111111) eliminates the the cid and mid checks,making it a true statement that the phone will flash literally anything however,rest assured that leaving your stock cid and mid does offer some protection against accidentally flashing an incorrect ruu.

As far as the decrypted vs the official signed ruu,you can use either. The biggest advantage to using the decrypted ruu would be if you wanted your custom recovery to remain in place,you could delete the stock image from the decrypted version. If you wanted to be 100% stock,then the decrypted ruu offers no advantage. Going back to stock,the signed ruu may be a better choice,as you can be 100% certain that all the firmware and images HTC intended are present.

That is a correct att ruu,you should be fine to run it. The MR stands for "maintenance release"

Hope that clears it up

I have the Full Decrypted RUU stashed right here
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip | by clsA for One

Enjoy !!

 

[LoyalServant]

I posted some questions on a thread over on xda but my stuff always seems to get buried unanswered over there. So I'll ask here & I'm sure you guys will set me straight.

This.

I am getting too old to keep up with the XDA noise so that's why if I have to ask for help or advice I come here.... the noise level is a lot lower and the mods won't tolerate the bashing that exists everywhere else.

It's a good thing some of those kids on other forums are not mine.

So yeah I guess I am an AF fanboy... it's the people not the name

 

[sharksfan7]

I have the Full Decrypted RUU stashed right here
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip | by clsA for One

Enjoy !!

Well I finally decided I was going to take the time today to update my phone to KK using the decrypted RUU clsA offered, with a couple modifications. Got a FAILED error when I flashed it. Luckily it wasn't a fatal error. I'm hoping you guys can help me sort out what I did wrong.

Here's what I did.

Downloaded file & verified md5. Since I recently flashed the dark bootloader (HBOOT 1.54) from GPE, I figured I would remove the hboot.img from the ruu as well as the recovery.img to retain TWRP. My understanding was that with the decrypted ruu I could do this. I opened the zip with 7zip & deleted both images. I then renamed the zip to "ruu.zip", just for convenience.

From command window:

O:\Android\HTC_One\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [  0.047s]
finished. total time: 0.063s

O:\Android\HTC_One\RUU>fastboot flash zip ruu.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (0 KB)...
OKAY [  0.156s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.359s

I knew that when flashing an ruu to expect an error the first time and that I just needed to run the command again. So I did. Same error. (I realize now that's not the error to expect.)

Now I got worried. Did some searching and found that with the "32 header error", the process stopped before anything on the phone was touched and that it was safe to reboot. So I "fastboot reboot" & held my breath until the phone fully booted. When I regained consciousness, I found that my phone was up & running fine.

So what happened? Was deleting the img's from the zip the wrong thing to do? I guess I can just flash the full decrypted zip and then just flash HBOOT & TWRP again separately. But isn't that the benefit of the decrypted RUU; to be able to remove particular img's before flashing? And if I'm going to run the full RUU, I might as well just run the signed one, right?

 

[scotty85]

Typically you get that error if there is not an android info text document present,or it is some how corrupt/missing info.

Nothing you did was wrong

You might look in the zip and make sure the text document is present. If so,paste its contents here for us.

 

[clsA]

Well I finally decided I was going to take the time today to update my phone to KK using the decrypted RUU clsA offered, with a couple modifications. Got a FAILED error when I flashed it. Luckily it wasn't a fatal error. I'm hoping you guys can help me sort out what I did wrong.

Here's what I did.

Downloaded file & verified md5. Since I recently flashed the dark bootloader (HBOOT 1.54) from GPE, I figured I would remove the hboot.img from the ruu as well as the recovery.img to retain TWRP. My understanding was that with the decrypted ruu I could do this. I opened the zip with 7zip & deleted both images. I then renamed the zip to "ruu.zip", just for convenience.

From command window:

O:\Android\HTC_One\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [  0.047s]
finished. total time: 0.063s

O:\Android\HTC_One\RUU>fastboot flash zip ruu.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (0 KB)...
OKAY [  0.156s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.359s

I knew that when flashing an ruu to expect an error the first time and that I just needed to run the command again. So I did. Same error. (I realize now that's not the error to expect.)

Now I got worried. Did some searching and found that with the "32 header error", the process stopped before anything on the phone was touched and that it was safe to reboot. So I "fastboot reboot" & held my breath until the phone fully booted. When I regained consciousness, I found that my phone was up & running fine.

So what happened? Was deleting the img's from the zip the wrong thing to do? I guess I can just flash the full decrypted zip and then just flash HBOOT & TWRP again separately. But isn't that the benefit of the decrypted RUU; to be able to remove particular img's before flashing? And if I'm going to run the full RUU, I might as well just run the signed one, right?

Sorry you had a problem with the file .. I have flashed it without errors so i don't know what happened

here's the contins of the Android-info.txt

Spoiler

modelid: PN0711000
modelid: PN0713000
modelid: PN0712000
modelid: PN0714000
modelid: PN0710000
modelid: PN071****
cidnum: 11111111
cidnum: HTC__***
cidnum: CWS__001
cidnum: H3G__***
cidnum: O2___***
cidnum: ORANG***
cidnum: TELNZ001
cidnum: OPTUS001
cidnum: T-MOB***
cidnum: TELST001
cidnum: VODAP***
cidnum: BM___001
cidnum: BS_US001
cidnum: GLOBA001
cidnum: ROGER001
cidnum: TELUS001
cidnum: TIM__***
mainver: 4.18.502.7
btype:1
aareport:1
DelCache:1
hbootpreupdate:3

and here's the zip

 

[sharksfan7]

Typically you get that error if there is not an android info text document present,or it is some how corrupt/missing info.

Nothing you did was wrong

You might look in the zip and make sure the text document is present. If so,paste its contents here for us.

android-info.txt is in the zip.

modelid: PN0711000
modelid: PN0713000
modelid: PN0712000
modelid: PN0714000
modelid: PN0710000
modelid: PN071****
cidnum: 11111111
cidnum: HTC__***
cidnum: CWS__001
cidnum: H3G__***
cidnum: O2___***
cidnum: ORANG***
cidnum: TELNZ001
cidnum: OPTUS001
cidnum: T-MOB***
cidnum: TELST001
cidnum: VODAP***
cidnum: BM___001
cidnum: BS_US001
cidnum: GLOBA001
cidnum: ROGER001
cidnum: TELUS001
cidnum: TIM__*** 
mainver: 4.18.502.7
btype:1
aareport:1
DelCache:1
hbootpreupdate:3

Both my MID & CID are listed (PN0712000/CWS__001).

I'm suspecting that the zip may have been corrupted when I deleted the img's. It seemed to take a long time to delete each image, a couple of minutes per image. Would it be better to extract all the files in the zip, delete the hboot.img & recovery.img, then re-package the rest? I'm kinda reluctant to go that route b/c I'm just risking something getting corrupted somewhere along the way, and it may not be so forgiving if the flash fails.

 

[scotty85]

hmm that should not have corrupted the zip.

clsa,did you do the decrypting? have you ever flashed it with the gpe bootloader?

im thinking maybe the gpe bootloader does not understant the ruu.

have you tried flashing the original version? doing so should let the hboot pre-update to the one required.

if that fails,you might have to flash back to a sense bootloader before flashing the zip

 

[sharksfan7]

hmm that should not have corrupted the zip.

clsa,did you do the decrypting? have you ever flashed it with the gpe bootloader?

im thinking maybe the gpe bootloader does not understant the ruu.

have you tried flashing the original version? doing so should let the hboot pre-update to the one required.

if that fails,you might have to flash back to a sense bootloader before flashing the zip

When you say "flashing the original version", are you referring to the original decrypted RUU or the original HBOOT? Either way, I have not. I wanted to get a clearer picture of what happened here before I tried again.

As for flashing back to a Sense bootloader, I'll try that if flashing the full RUU doesn't work. And I may try running the RUU.exe as well, before flashing just HBOOT. Kinda want to limit flashing HBOOT.

I was just looking at the android-info.txt and it has "hbootpreupdate:3". When I fastboot getvar all, it lists "(bootloader) hbootpreupdate: 11". Not sure if the different number makes a difference here. Just something that I noticed. Do those numbers need to match in order for the flash to work?

 

[scotty85]

No,the hboot preupdate numbers will not need to match. Did you have any luck flashing the ruus?

 

[sharksfan7]

No,the hboot preupdate numbers will not need to match. Did you have any luck flashing the ruus?

Haven't had a chance yet. Need to set aside a couple of hours so I can get it all set up again. I might try to get to it tonight. I'll post back with an update when I do. Thanks for your help.

 

[sharksfan7]

Well I tried flashing the full decrypted RUU and got the same failure as before. After debating with myself for a while on what I should try next, I decided to flash a Sense HBOOT like Scotty suggested and then try to reflash the RUU. I was a bit concerned because if the full RUU that contains the proper HBOOT wouldn't flash, maybe a zip with just the HBOOT.img won't flash either. But I figured I need to just give it a try.

I downloaded the ATT_OTA.4.18.502.7.firmware.zip & extracted the HBOOT.img & the android-info.txt. I edited the mainver: to 3.17.502.3 since I leaving all the other firmware the same. Zipped those two files & flashed w/o a problem. I then attempted to flash the full decrypted RUU. Again I got the same error.

O:\Android\HTC_One\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [  0.047s]
finished. total time: 0.047s

O:\Android\HTC_One\RUU>fastboot flash zip RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4
.18.502.7_decrypted.ROM.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (0 KB)...
OKAY [  0.156s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.344s

O:\Android\HTC_One\RUU>

So now what? I figure I'll download the official signed RUU and try to run that. But I'm having a hell of a time downloading files from the HTC1guru site. All the files I've tried to download end prematurely. I don't know what the issue is with that, if it's on my end or the server. Anyone got another source where I can download RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R1 0_Radio_4T.24.3218.09_10.26.1718.01L_release_35656 5_signed_2.exe?

 

[clsA]

Well I tried flashing the full decrypted RUU and got the same failure as before. After debating with myself for a while on what I should try next, I decided to flash a Sense HBOOT like Scotty suggested and then try to reflash the RUU. I was a bit concerned because if the full RUU that contains the proper HBOOT wouldn't flash, maybe a zip with just the HBOOT.img won't flash either. But I figured I need to just give it a try.

I downloaded the ATT_OTA.4.18.502.7.firmware.zip & extracted the HBOOT.img & the android-info.txt. I edited the mainver: to 3.17.502.3 since I leaving all the other firmware the same. Zipped those two files & flashed w/o a problem. I then attempted to flash the full decrypted RUU. Again I got the same error.

O:\Android\HTC_One\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [  0.047s]
finished. total time: 0.047s

O:\Android\HTC_One\RUU>fastboot flash zip RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4
.18.502.7_decrypted.ROM.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (0 KB)...
OKAY [  0.156s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.344s

O:\Android\HTC_One\RUU>

So now what? I figure I'll download the official signed RUU and try to run that. But I'm having a hell of a time downloading files from the HTC1guru site. All the files I've tried to download end prematurely. I don't know what the issue is with that, if it's on my end or the server. Anyone got another source where I can download RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R1 0_Radio_4T.24.3218.09_10.26.1718.01L_release_35656 5_signed_2.exe?

here you go
AndroidRUU | The #1 source for Android RUU files

 

[scotty85]

Well I tried flashing the full decrypted RUU and got the same failure as before. After debating with myself for a while on what I should try next, I decided to flash a Sense HBOOT like Scotty suggested and then try to reflash the RUU. I was a bit concerned because if the full RUU that contains the proper HBOOT wouldn't flash, maybe a zip with just the HBOOT.img won't flash either. But I figured I need to just give it a try.

I downloaded the ATT_OTA.4.18.502.7.firmware.zip & extracted the HBOOT.img & the android-info.txt. I edited the mainver: to 3.17.502.3 since I leaving all the other firmware the same. Zipped those two files & flashed w/o a problem. I then attempted to flash the full decrypted RUU. Again I got the same error.

O:\Android\HTC_One\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [  0.047s]
finished. total time: 0.047s

O:\Android\HTC_One\RUU>fastboot flash zip RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4
.18.502.7_decrypted.ROM.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (0 KB)...
OKAY [  0.156s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.344s

O:\Android\HTC_One\RUU>

So now what? I figure I'll download the official signed RUU and try to run that. But I'm having a hell of a time downloading files from the HTC1guru site. All the files I've tried to download end prematurely. I don't know what the issue is with that, if it's on my end or the server. Anyone got another source where I can download RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R1 0_Radio_4T.24.3218.09_10.26.1718.01L_release_35656 5_signed_2.exe?

so you have checked md5s,correct? bad download can defiantely give you the header error

when you flashed the ruus,the hboot onscreen was the sense hboot,correct? if the dark bootloader was still present,that could have been the issue(even tho the other one flashed,you werent using it). if thats the case,try again after rebooting to botloader and verifying its the white one.

last and not lease,you are in ruu mode when flashing,yes? you should be flashing like this:

Spoiler

if youre working with a booted,operational phone,you can flsh the file in the following manner:

-open a cmd window

-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )

-place the zip file you want to flash into adb/fastboot directory

-enable usb debug,disable fastboot,plug in phone

-check for connectivity
adb devices (should return serial number)

-boot to fastboot
adb reboot bootloader

-check for connectivity again
fastboot devices

-flash the file
fastboot erase cache

fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)

fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)

*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish

-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)

-reboot back to the OS
fastbooot reboot

you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices

edit:
as an afterthot,you could always swap out the android info text in one of the decrypted ruus for the one in your hboot zip,since you did flash that successfully.

 

[sharksfan7]

so you have checked md5s,correct? bad download can defiantely give you the header error

Yes. I'm meticulous at checking md5s. I check it after downloading as well as right before flashing every time.

when you flashed the ruus,the hboot onscreen was the sense hboot,correct? if the dark bootloader was still present,that could have been the issue(even tho the other one flashed,you werent using it). if thats the case,try again after rebooting to botloader and verifying its the white one.

I was in the white bootloader. After I flashed it, I fastboot reboot-bootloader. It booted to the white bootloader and I saw that it was HBOOT 1.56. I then proceeded with flashing the RUU.zip.

last and not lease,you are in ruu mode when flashing,yes? you should be flashing like this:

Spoiler

if youre working with a booted,operational phone,you can flsh the file in the following manner:

-open a cmd window

-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )

-place the zip file you want to flash into adb/fastboot directory

-enable usb debug,disable fastboot,plug in phone

-check for connectivity
adb devices (should return serial number)

-boot to fastboot
adb reboot bootloader

-check for connectivity again
fastboot devices

-flash the file
fastboot erase cache

fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)

fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)

*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish

-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)

-reboot back to the OS
fastbooot reboot

you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices

Yes. Definitely in RUU mode. Black screen w/ silver HTC. However, looking through your steps, I didn't fastboot erase cache before going into RUU mode. Could that cause the problem?

edit:
as an afterthot,you could always swap out the android info text in one of the decrypted ruus for the one in your hboot zip,since you did flash that successfully.

I actually thought of doing that but wasn't sure if I should. I don't know what each line of that text is for so wasn't sure if they could just be swapped out like that, in case there was a particular line that was specific for the RUU package. I'm probably over thinking this though. I tend to do that. This will most likely be the next thing I try. I'll try it using the decrypted RUU w/ the HBOOT & recovery images removed. That's the original goal in all of this.

In case that still doesn't work, I'm downloading the official RUU from AndroidRUU.com that cslA linked to above. I'll most likely extract the rom.zip first and flash it manually. I just wish there was md5 for that rom.zip that I could check against.

Not sure when I'll be able to find time to do this. NHL playoffs start tonight so my nights will be spent firmly planted in a barcalounger acting like a face-painting fool in various states of inebriation. :cheers:Not a good state to be flashing things. But I'll post an update once I am able.

 

[clsA]

Yes. I'm meticulous at checking md5s. I check it after downloading as well as right before flashing every time.



I was in the white bootloader. After I flashed it, I fastboot reboot-bootloader. It booted to the white bootloader and I saw that it was HBOOT 1.56. I then proceeded with flashing the RUU.zip.



Yes. Definitely in RUU mode. Black screen w/ silver HTC. However, looking through your steps, I didn't fastboot erase cache before going into RUU mode. Could that cause the problem?



I actually thought of doing that but wasn't sure if I should. I don't know what each line of that text is for so wasn't sure if they could just be swapped out like that, in case there was a particular line that was specific for the RUU package. I'm probably over thinking this though. I tend to do that. This will most likely be the next thing I try. I'll try it using the decrypted RUU w/ the HBOOT & recovery images removed. That's the original goal in all of this.

In case that still doesn't work, I'm downloading the official RUU from AndroidRUU.com that cslA linked to above. I'll most likely extract the rom.zip first and flash it manually. I just wish there was md5 for that rom.zip that I could check against.

Not sure when I'll be able to find time to do this. NHL playoffs start tonight so my nights will be spent firmly planted in a barcalounger acting like a face-painting fool in various states of inebriation. :cheers:Not a good state to be flashing things. But I'll post an update once I am able.

I know it sounds strange but extracting the rom.zip for that RUU will not work ... it gives some size mismatch error. But the decrypted one works .. i have flashed it 3 times on different phones (plus it's had over 100 downloads with no complaints)

 

[sharksfan7]

I know it sounds strange but extracting the rom.zip for that RUU will not work ... it gives some size mismatch error. But the decrypted one works .. i have flashed it 3 times on different phones (plus it's had over 100 downloads with no complaints)

Okay. Good to know. Is that true for all RUUs or just this particular one? Because there's a thread on xda on how to do this for the M7. Is that process no longer valid?

Not sure why I'm having such issues with the decrypted one. I'll try downloading it again, even though the md5 of the one I already have does match. If comes to it, I'll just run the exe. If that doesn't work, I don't know what the hell to do.

Fortunately, I don't have any issues with the phone as it is. And I can always just flash a custom ROM and a firmware package. At least, I'm assuming I can. Haven't tried yet. Maybe I'll run into issues there too. God, I hope not.