Database Develop

[Q] HTC One relocked after firmware updated now soft-bricked and unable to unlock!

Help!
I recently installed the 4.06.1540.3.zip firmware onto my HTC One in preparation to install Android Revolution HD 41. After installing the firmware, I have been unable to unlock the relocked bootloader. I am able to send commands via fastboot and can successfully send the unlock code but nothing shows up on the phone. I currently have no working OS on the phone and only have stock recovery, it seems, and obviously can't send over a custom recovery until I'm unlocked which I can't do =(.
Please help, I have no phone!

Why did you lock it?
Sent from my HTC One using Tapatalk

xcrazydx said:
Why did you lock it?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Mike's directions for updating firmware required a re lock.
How to flash?
(bootloader needs to be relocked)
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Click to expand...
Click to collapse

Whaines said:
Mike's directions for updating firmware required a re lock.
Click to expand...
Click to collapse
If u r s_off ..u dont need to relock bootloader mike clearly stated tht in his post read properly before u even proceed
Sent from my HTC One using xda app-developers app

vaibhav satam said:
If u r s_off ..u dont need to relock bootloader mike clearly stated tht in his post read properly before u even proceed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yup. I am and was s-on and followed directions. So why can't I unlock again?

Whaines said:
Yup. I am and was s-on and followed directions. So why can't I unlock again?
Click to expand...
Click to collapse
Unlock boot loader using HTC Dev instructions again?
Sent from my HTC One using xda app-developers app

you will need a new unlock bin file from HTC

Jcc1dls said:
you will need a new unlock bin file from HTC
Click to expand...
Click to collapse
Yes, and I've received one (and then kept trying and got about 30 more). I can flash it just fine but the screen on my phone never pops up to accept the unlock. This is my issue. There is no error message on the flash. It just doesn't show up and I can't accept the unlock.

Whaines said:
Yes, and I've received one (and then kept trying and got about 30 more). I can flash it just fine but the screen on my phone never pops up to accept the unlock. This is my issue. There is no error message on the flash. It just doesn't show up and I can't accept the unlock.
Click to expand...
Click to collapse
S-On, right? :crying:
1- was that a signed firmware package
2- did the update go all the way (ie you flashed it twice in a row, first one came back with "flush again immediately" and you did)
3- you confirmed everything was updated by checking your "fastboot getvar all"
4- bootloader also shows the correct firmware
if yes to above, try a factory reset in bootloader and/or stock recovery, then try a new unlock token, and hope it works.

nkk71 said:
S-On, right? :crying:
1- was that a signed firmware package
2- did the update go all the way (ie you flashed it twice in a row, first one came back with "flush again immediately" and you did)
3- you confirmed everything was updated by checking your "fastboot getvar all"
4- bootloader also shows the correct firmware
if yes to above, try a factory reset in bootloader and/or stock recovery, then try a new unlock token, and hope it works.
Click to expand...
Click to collapse
Yes, S-ON since getting S-OFF on hboot 1.5 is a pain.
I'm almost certain it was a signed firmware otherwise it wouldn't have even be able to have been flashed.
The firmware update was successful, after flashing twice. I can successfully flash that firmware and ..1540.2
Getvar shows the new firmware, as does the bootloader.
Here's the getvar:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4283mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I just don't understand why I can't get the popup on my phone. That's what I get for trying to do it the right way, I guess =(.
I'd like to at least get stock back on the phone so I can have a working phone but I can't find an RUU that will work, my firmware is too new for any that I've found. =(

Should have done s-off. No point in modding without it.
Sent from my HTC One using Tapatalk

No unlock acknowledgment
I had the same issue with my first HTC One, it was a tmobile version. I ended up having to RUU whick alligned the firmware, hboot, rom, and recovery to the same versions. Boot and go through the setup. shut down. reboot. shutdown. boot into fastboot. create a new user with HTC, submit your token. Reboot your PC. Send the bin file to the device. unlock. powerdown. flash recovery. powerdown. enter recovery. powerdown and accept the install of SU. boot into the stock ROM. powerdown. You should be set to go.

Jcc1dls said:
I had the same issue with my first HTC One, it was a tmobile version. I ended up having to RUU whick alligned the firmware, hboot, rom, and recovery to the same versions. Boot and go through the setup. shut down. reboot. shutdown. boot into fastboot. create a new user with HTC, submit your token. Reboot your PC. Send the bin file to the device. unlock. powerdown. flash recovery. powerdown. enter recovery. powerdown and accept the install of SU. boot into the stock ROM. powerdown. You should be set to go.
Click to expand...
Click to collapse
I can't find an RUU for 4.06.1540.X though. =( I believe that will fix my problem but the solution is not out there.
xcrazydx said:
Should have done s-off. No point in modding without it.
Click to expand...
Click to collapse
At the time I modded there was no solution for S-OFF for 1.5+.

As for now, the only thing I seem to be able to successfully flash via RUU are the two 4.06 firmwares from @mike1986. Unfortunately, it's just firmware and not a full RUU so I can't boot into anything but the bootloader. Any hints on where I can find a stock rom that it will let me install via fastboot since I don't have a custom recovery?

Run a ruu exe
Sent from my HTC One using Tapatalk

xcrazydx said:
Run a ruu exe
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (1103159 KB)...
OKAY [ 36.684s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 148.740s
=/ Can't seem to find one that passes the signature verification.

Whaines said:
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (1103159 KB)...
OKAY [ 36.684s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 148.740s
=/ Can't seem to find one that passes the signature verification.
Click to expand...
Click to collapse
Your CID is still CWS__001.
Get the AT&T RUU from HTC and run it. Then start the bootloader unlock process all over.
Once you've got a working phone, then attempt to s-off using rumrunner with a live CD/USB of a Linux distribution.
Sent from my HTC One using xda app-developers app

ilal2ielli said:
Your CID is still CWS__001.
Get the AT&T RUU from HTC and run it. Then start the bootloader unlock process all over.
Once you've got a working phone, then attempt to s-off using rumrunner with a live CD/USB of a Linux distribution.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I really appreciate all the help, but there either is no AT&T RUU that will run with the firmware on my phone (afaik you can't go backward when you're S-ON), or it's not where I'm able to find it on the internet. I've looked here and htc1guru.com.

Whaines said:
I really appreciate all the help, but there either is no AT&T RUU that will run with the firmware on my phone (afaik you can't go backward when you're S-ON), or it's not where I'm able to find it on the internet. I've looked here and htc1guru.com.
Click to expand...
Click to collapse
That might be the case then...
I ran this RUU:
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
I used it go return to stock for a warranty exchange and had the 3.62.401.1 firmware at the time, but I was s-off.
Hopefully someone knows a way to get a ROM back on the phone so that you can get the bootloader unlocked.
Sent from my HTC One using xda app-developers app

[Q] Can't S-ON?

After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!

Jikstah said:
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Click to expand...
Click to collapse
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082

nkk71 said:
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
I thank you immensely.

Jikstah said:
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Click to expand...
Click to collapse
Luckily the signature check kept you away from a brick, had you been able to S-On with a modded hboot, then you would have had a brick.
Jikstah said:
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
Click to expand...
Click to collapse
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.

nkk71 said:
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
Click to expand...
Click to collapse
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Surely I'm close?! Thanks again.

Jikstah said:
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
Surely I'm close?! Thanks again.
Click to expand...
Click to collapse
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)

nkk71 said:
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
Click to expand...
Click to collapse
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?

Jikstah said:
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Click to expand...
Click to collapse
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.

nkk71 said:
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
Click to expand...
Click to collapse
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.

Jikstah said:
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Click to expand...
Click to collapse
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware

nkk71 said:
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
Click to expand...
Click to collapse
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.

Jikstah said:
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Click to expand...
Click to collapse
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe

nkk71 said:
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
Click to expand...
Click to collapse
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.

Jikstah said:
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Click to expand...
Click to collapse
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.

nkk71 said:
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
Click to expand...
Click to collapse
Gosh, you are too good. This is definitely the big break.
But nope, freakin' adb decides to bail on me and my device can no longer be detected. WTF?! What have I done to deserve such trouble.. -_-

[SOLVED] Reverting back to stock with RUU - Error 158 Image Error

Hi!
So I have a problem with my M7 and I need to return it to stock so that I can send it back to HTC for repair. I have downloaded the "RUU M7 UL K44 SENSE55 MR O2 UK 4.20.206.16 Radio 4A.23.3263.28 10.38r.1157.04L Release 353143 Signed 2" from here (multiple times to check if I had a corrupted download or something like that).
Every time I run the RUU it reboots it to the black HTC screen then gives me the error message
Code:
ERROR [158]: IMAGE ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
My bootloader is Unlocked (though I have tried it with Relocked). I first tried with SuperCId then I did
Code:
fastboot oem writecid O2___001
(that's 3 underscores - I think that is right!) to put it back to the O2 UK cid and I get the same error. Below is what
Code:
fastboot getvar all
returns.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.063s
I'm almost certain that this is the correct RUU I should be using.
Can anybody help or tell me why it's going wrong? Thanks in advance!

One thing I forgot to mention - I have previously flashed an RUU zip file from here when I had super cid to unbrick my device. Might that have something to do with it?

HapticThreek said:
One thing I forgot to mention - I have previously flashed an RUU zip file from here when I had super cid to unbrick my device. Might that have something to do with it?
Click to expand...
Click to collapse
Your version main says your on a 401 ruu, your trying to run a 206 ruu, I would change the cid back to HTC__001 and run the 401.ruu personally.
158 error specifies wrong ruu

Seanie280672 said:
Your version main says your on a 401 ruu, your trying to run a 206 ruu, I would change the cid back to HTC__001 and run the 401.ruu personally.
158 error specifies wrong ruu
Click to expand...
Click to collapse
That sounds like it's because I flashed the wrong RUU before then. I thought with super cid I should be able to flash any RUU?
Do you know if there's any way to get my version main back to 206 (which I'm fairly sure it was before I flashed the first ruu), or to get the O2 UK ruu to reflash the version main?
The reason I ask is because the phone has already been sent to HTC for repair once so they would probably know what software was on it when it was returned to me.
Thanks
EDIT: the cid was always O2___001 before I got supercid to unbrick phone. I have used this RUU previously on this phone successfully.

HapticThreek said:
That sounds like it's because I flashed the wrong RUU before then. I thought with super cid I should be able to flash any RUU?
Do you know if there's any way to get my version main back to 206 (which I'm fairly sure it was before I flashed the first ruu), or to get the O2 UK ruu to reflash the version main?
The reason I ask is because the phone has already been sent to HTC for repair once so they would probably know what software was on it when it was returned to me.
Thanks
EDIT: the cid was always O2___001 before I got supercid to unbrick phone. I have used this RUU previously on this phone successfully.
Click to expand...
Click to collapse
You could try setting super cid first, run the O2 ruu and after its finished then set the phone to the O2 cid, or, you could pull the firmware zip from the ruu, force flash that and then run the ruu.

Seanie280672 said:
You could try setting super cid first, run the O2 ruu and after its finished then set the phone to the O2 cid, or, you could pull the firmware zip from the ruu, force flash that and then run the ruu.
Click to expand...
Click to collapse
Thanks, I'll give the second one a shot first. Will the firmware.zip be in the temp folder/rom.zip?

HapticThreek said:
Thanks, I'll give the second one a shot first. Will the firmware.zip be in the temp folder/rom.zip?
Click to expand...
Click to collapse
Yes, when you run the ruu it unpacks itself to a temp folder on your pc, right before you accept the license agreement, find the temp.folder and pull the firmware.zip from the Rom

Seanie280672 said:
Yes, when you run the ruu it unpacks itself to a temp folder on your pc, right before you accept the license agreement, find the temp.folder and pull the firmware.zip from the Rom
Click to expand...
Click to collapse
When I go to extract the rom.zip file I get the message that the archive is corrupt and that CRC data failed in dzdata_32g.img and dzdata_64g.img.
I have tried this on multiple downloads which I have verified the md5 hashes. Using winrar to extract - should I be using something else?
EDIT - quick search tells me its because its encrypted - will look for decrypting solutions

HapticThreek said:
When I go to extract the rom.zip file I get the message that the archive is corrupt and that CRC data failed in dzdata_32g.img and dzdata_64g.img.
I have tried this on multiple downloads which I have verified the md5 hashes. Using winrar to extract - should I be using something else?
EDIT - quick search tells me its because its encrypted - will look for decrypting solutions
Click to expand...
Click to collapse
Yeah, sorry for the slow reply, its because its encrypted, try this
http://forum.xda-developers.com/showthread.php?t=2084470

Seanie280672 said:
Yeah, sorry for the slow reply, its because its encrypted, try this
http://forum.xda-developers.com/showthread.php?t=2084470
Click to expand...
Click to collapse
Hi, thanks very much. So I have extracted the rom.zip, for some reason it split it into 5 zip files. Unfortunately for me none of these zips contained the firmware.zip file you spoke about (or any other zip file).
I think what happened is it extracted what was in the zips too. One of the extracted zips contained the following files:
adsp.img
android-info.txt
cir.img
hboot_signedbyaa.img
pg2fs_spcustom.img
radio.img
ramdisk.img
rcdata.img
recovery_signed.img
rpm.img
sbl1-1.img
sbl1-2.img
sbl1-3.img
sbl2.img
sbl3.img
splash1.nb0
tp_SYN3202.img
tz.img
Am I right in thinking this is the firmware zip file? ( I hope! lol )

HapticThreek said:
Hi, thanks very much. So I have extracted the rom.zip, for some reason it split it into 5 zip files. Unfortunately for me none of these zips contained the firmware.zip file you spoke about (or any other zip file).
I think what happened is it extracted what was in the zips too. One of the extracted zips contained the following files:
adsp.img
android-info.txt
cir.img
hboot_signedbyaa.img
pg2fs_spcustom.img
radio.img
ramdisk.img
rcdata.img
recovery_signed.img
rpm.img
sbl1-1.img
sbl1-2.img
sbl1-3.img
sbl2.img
sbl3.img
splash1.nb0
tp_SYN3202.img
tz.img
Am I right in thinking this is the firmware zip file? ( I hope! lol )
Click to expand...
Click to collapse
Yup that's firmware.zip, all the system files etc, just zip those files back up into one zip, name it firmware.zip and flash it, don't forget to flash it twice, make sure on the 2nd time it says successful at the end, if it says anything else do not restart your phone, it will brick, you will need to find another firmware to flash whilst the phone is still in RUU mode.
see here: http://trjlive.com/guide-install-firmware-htc-one-m7/

Seanie280672 said:
Yup that's firmware.zip, all the system files etc, just zip those files back up into one zip, name it firmware.zip and flash it, don't forget to flash it twice, make sure on the 2nd time it says successful at the end, if it says anything else do not restart your phone, it will brick, you will need to find another firmware to flash whilst the phone is still in RUU mode.
see here: http://trjlive.com/guide-install-firmware-htc-one-m7/
Click to expand...
Click to collapse
Hi, so I did that and followed the guide, unfortunately hasn't worked. get the following when I run fastboot flash zip firmware.zip:
Code:
sending 'zip' (41218 KB)...
OKAY [ 3.118s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 3.396s
Does it need to be re-encrypted or something?
EDIT - actually think the firmware.zip is already encrypted still. trying to see if I can decrypt it.
trying to unzip it gives me "invalid compressed data to inflate" error
EDIT 2 - seems like I'm getting the same issue as this dude http://forum.xda-developers.com/showpost.php?p=49519579&postcount=155. Will look for a different way to decrypt rom.zip

Seanie280672 said:
Yup that's firmware.zip, all the system files etc, just zip those files back up into one zip, name it firmware.zip and flash it, don't forget to flash it twice, make sure on the 2nd time it says successful at the end, if it says anything else do not restart your phone, it will brick, you will need to find another firmware to flash whilst the phone is still in RUU mode.
see here: http://trjlive.com/guide-install-firmware-htc-one-m7/
Click to expand...
Click to collapse
So managed to decrypt properly and flash. Woohoo!
Here is the new output for fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3830mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-44d68d6b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.064s
Version main now has the 206 in it so hopefully when I get to try the RUU again tomorrow it works, fingers crossed and thanks for all your input so far, you've been really helpful!
EDIT - should have waited til tomorrow to flash this firmware - touch screen is non functional now! bah. Hopefully ruu works tomorrow!

SOLVED
Well, the RUU worked this time and I now have a fully stock phone to return.
Thanks for all your help and pointing me in the right directions. Will hit the thanks button on your posts!

[Q] Stuck at RUU Bootloader

I believe I have bricked my device. I'm s-off on the latest firmware and radios and was running the latest insertcoin sense 7 rom when I tried to run the LP RUU to get it back to stock and it failed. Keeps giving me error code 152, which means it thinks something is wrong with the image. It has left me stuck on the RUU bootloader screen with no means of getting back to the main bootloader. I still have fastboot commands, but cannot manually flash the newest firmware or rom.zip from this thread. The RUU I have is also from this thread. I have tried it several times, tried relocking the bootloader even though I am s-off, still didnt work, and I am completely stuck on the bootloader. Now it seems that I can't flash anything because I've relocked the bootloader? I've tried fresh downloads of everything, and also have the HTC drivers installed with HTC sync uninstalled. Does anyone have any suggestions or ideas? I have been working on phones for years and never had a problem running an RUU until today. Any help is greatly appreciated, and I'll buy you a beer if you can fix it
Please ask questions if I'm not clear enough, I can clarify if needed.
Here are a few of the outputs I'm getting:
C:\adb>fastboot flash zip rom.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 116912852 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 116912852 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 116912852 is not a multiple of t
he block size 4096
OKAY [ 64.235s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 64.450s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4215mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s

Have you tried running it as .exe?

BD619 said:
Have you tried running it as .exe?
Click to expand...
Click to collapse
Yes, that's what caused all of this to begin with. The .exe RUU failed with Error 152. I've tried the previous KK RUU as well, to no avail.
Edit: The failure is with the partition update. everything passes, and then the partition fails and it hangs after it tries to update system.

goliath714 said:
Yes, that's what caused all of this to begin with. The .exe RUU failed with Error 152. I've tried the previous KK RUU as well, to no avail.
Click to expand...
Click to collapse
When you run the exe from you PC when it fails does it give you a Recover option in the RUU screen?

BD619 said:
When you run the exe from you PC when it fails does it give you a Recover option in the RUU screen?
Click to expand...
Click to collapse
Yes, and I've followed all those steps as well. It does the same thing each time; says it has recovered successfully, I go to continue the RUU process, and it fails again and gives me the chance to recover, and this repeats no matter how many times I try.

goliath714 said:
Yes, and I've followed all those steps as well. It does the same thing each time; says it has recovered successfully, I go to continue the RUU process, and it fails again and gives me the chance to recover, and this repeats no matter how many times I try.
Click to expand...
Click to collapse
After you recover don't restart the RUU.
Try from the beginning from a different USB port USB2 work best.

BD619 said:
After you recover don't restart the RUU.
Try from the beginning from a different USB port USB2 work best.
Click to expand...
Click to collapse
Tried that as well. Tried both USB 2 and 3, running as administrator and normally, same Error 152 each time. Tried recovering and not recovering as well. My PC is running Windows 7 Pro.
Could the fact that I relocked it have anything to do with it?

goliath714 said:
Tried that as well. Tried both USB 2 and 3, running as administrator and normally, same Error 152 each time. Tried recovering and not recovering as well. My PC is running Windows 7 Pro.
Could the fact that I relocked it have anything to do with it?
Click to expand...
Click to collapse
Being re-locked shouldn't matter since you are s-off.
My only other suggestions are...
Different cable
Different PC.

BD619 said:
Being re-locked shouldn't matter since you are s-off.
My only other suggestions are...
Different cable
Different PC.
Click to expand...
Click to collapse
BD could it be because he's relocked and doesn't have a eng . bootloader be the problem, just throwing this out there.

Aldo101t said:
BD could it be because he's relocked and doesn't have a eng . bootloader be the problem, just throwing this out there.
Click to expand...
Click to collapse
I don't think so...I had him try everything I can think of and he's still having problems.

BD619 said:
I don't think so...I had him try everything I can think of and he's still having problems.
Click to expand...
Click to collapse
yeah, it's weird that's for sure. well thought maybe I could help, thanks

BD619 said:
I don't think so...I had him try everything I can think of and he's still having problems.
Click to expand...
Click to collapse
I took it to the Sprint store and they couldn't even flash the image. Not that it's any different than the one I was using, but they replaced it for free since I've had it less than a year. Chalk one up for the home team!
Sent from my One M7 using XDA Free mobile app

Failing to Flash / Locate RUU on M7

Hey Guys -
This morning I've spent some time trying to convert my HTC One M7 from AT&T to T-Mobile (both USA) so that I may use a new T-Mobile SIM I have. I already had S-Off, so it looked like a fairly simple process. Unfortunatly, I've hit a roadblock and after searching cannot find the solution. I believe the biggest issue is due to htc1guru.com being down which I do not know if due to the DOS attack in Atlanta or not - Anyways - below is what I've done so far, where i hit the error, and current status of the phone...
Phone's Original State
I should have run a getvar for this first, but copied all info from a pic I took before starting of the bootloader screen
HTC One M7 flashed with ViperOne 9.0.0 on AT&T USA (GSM)
- M7_UL PVT SHIP S-OFF RH
- S-Off / Rooted
- CID: CWS__001
- HBOOT: 1.61.0000
- RADIO: 4M.32.3218.06
- OpenDSP: v35.120.274.0718
- OS: 7.23.502.1
Steps I Followed to Convert Carrier to T-Mobile
I found and used this guide mostly as it seemed to do exactly what I was trying to do
1. Changed CID to "T-MOB010"
2. Flashed "MID_Change_1.01.zip" via TWRP and choose to install Model ID "PN0713000" - Rebooted
3. Skipped step for re-locking bootloader
4. htc1guru.com was offline so had to find RUU elsewhere. So, I finally found and downloaded "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed.exe" from androidruu.com.
5. Executed above EXE, went to %temp%, and copied "rom.zip" out to my adb folder
6. Ran "adb reboot bootloader" then "fastboot oem rebootRUU" to get to silver HTC logo
7. Executed "fastboot flash zip rom.zip" which failed with below error. I tried re-running the string, but got the same results
Current Error
When executing step #7 above
Code:
C:\adb>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1037365 KB)...
OKAY [ 41.799s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 47.542s
Current Phone Status
Below are the current settings for my M7 which I just pulled via "fastboot getvar all" before posting...
Code:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT35ZW914588
(bootloader) imei: 354439051018051
(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: 3864mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 4.782s
The Issue? / Overall
I'm pretty sure that the error is due to the rom.zip not being what I need to flash. I've found plenty of links for the rom/ruu that should work for my situation, but they are all on htc1guru.com. If I power on the phone in it's current state with the (new / never used) T-Mobile SIM in, I am prompted to enter an 8 digit PIN which I assume I would need to call T-Mobile for and activate first. Based on what I'm trying to do, the error, and the above data; what do I need to do? If it is in fact an incorrect rom/ruu file, does anyone have a link to it on another site or can tell me which specific one I need to look for?
Thanks for your help!!!

Try the link on OP for latest Ruu it may help. http://forum.xda-developers.com/showthread.php?p=59353567

Toqeer said:
Try the link on OP for latest Ruu it may help. http://forum.xda-developers.com/showthread.php?p=59353567
Click to expand...
Click to collapse
Thanks - downloading now. So this is obviously an installable one. Do you suggest I try to install it via the EXE / built-in installer, extract the rom.zip and apply using steps above, or does it even matter? I don't care if I loose any data on the phone.
Thanks!

bzowk said:
Hey Guys -
This morning I've spent some time trying to convert my HTC One M7 from AT&T to T-Mobile (both USA) so that I may use a new T-Mobile SIM I have.
Click to expand...
Click to collapse
Converting your phone from AT&T to T-Mobile USA version won't make it work with a T-Mobile SIM card. You have to SIM-Unlock your phone. Even if you flash a T-MOB ruu, your phone will still be locked to AT&T and ask you for an unlock code.

alray said:
Converting your phone from AT&T to T-Mobile USA version won't make it work with a T-Mobile SIM card. You have to SIM-Unlock your phone. Even if you flash a T-MOB ruu, your phone will still be locked to AT&T and ask you for an unlock code.
Click to expand...
Click to collapse
Well crap. What's the process for in the guide I posted a link to in my original post, then? What more do I need to do in order to SIM-Unlock it?

bzowk said:
Thanks - downloading now. So this is obviously an installable one. Do you suggest I try to install it via the EXE / built-in installer, extract the rom.zip and apply using steps above, or does it even matter? I don't care if I loose any data on the phone.
Thanks!
Click to expand...
Click to collapse
Install it via EXE auto installer put your phone in fastboot mode and simply run .exe file on PC.

bzowk said:
Well crap. What's the process for in the guide I posted a link to in my original post, then? What more do I need to do in order to SIM-Unlock it?
Click to expand...
Click to collapse
You don't need to do anything from that guide, you just need to sim-unlock your phone. Its done with an unlock code you can purchase online, sometimes you can get the unlock code for free from the original carrier (at&t in your case). Insert a foreign sim card, boot your phone, it will then ask you to enter the code and once done your phone will be able to work on any network (as long as the frequencies are compatible).
Btw that guide should be named "how to brand/de-brand your M7" and not "How to Get Your HTC One M7 Ready for a Different Mobile Carrier". That guide will obviously not make your phone ready to be used on another carrier if its not telling you to remove the sim-lock... I guess the author was using a carrier unlocked M7 hence why he forgot to tell about sim-unlock in his guide...