And again Help Needed. - One (M7) Q&A, Help & Troubleshooting

Hello Guys,
Sorry to bother again but I think I messed up bad, I accidently did this some how,(attached file) can you help me with it ?

todorov.drago1 said:
Hello Guys,
Sorry to bother again but I think I messed up bad, I accidently did this some how,(attached file) can you help me with it ?
Click to expand...
Click to collapse
That used to happen to me with some versions of TWRP. Which one do you have?

donkeykong1 said:
That used to happen to me with some versions of TWRP. Which one do you have?
Click to expand...
Click to collapse
TWRP v2.8.7.0.. is it because of that, that I cannot flash the RUU.zip from fastboot ?
When I try to flash it a second time it just stays there for 2 hours and nothing.

todorov.drago1 said:
TWRP v2.8.7.0.. is it because of that, that I cannot flash the RUU.zip from fastboot ?
When I try to flash it a second time it just stays there for 2 hours and nothing.
Click to expand...
Click to collapse
2.8.7.0 works fine for me. Can you go to bootloader menu and do factory reset from there? Then go to recovery and try again

donkeykong1 said:
2.8.7.0 works fine for me. Can you go to bootloader menu and do factory reset from there? Then go to recovery and try again
Click to expand...
Click to collapse
When I try to do this, it gives me this /attached file/, and then after some second It reboots.
Keep in mind that I don't have installed OS on that phone.

todorov.drago1 said:
When I try to do this, it gives me this /attached file/, and then after some second It reboots.
Keep in mind that I don't have installed OS on that phone.
Click to expand...
Click to collapse
Why not just flash the RUU that @alray mentioned in your other thread. I think your initial flash problem was because you didn't use htc-fastboot. The download link is in the "How to flash" instructions for the Lolipop ruu collection in the general thread.

mb_guy said:
Why not just flash the RUU that @alray mentioned in your other thread. I think your initial flash problem was because you didn't use htc-fastboot. The download link is in the "How to flash" instructions for the Lolipop ruu collection in the general thread.
Click to expand...
Click to collapse
Yeah, I did that and this was outcome:
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 41(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 2.867 secs
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
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device SH39JW901074...
^C
C:\Users\Drago Todorov\Downloads\fastboot-win>
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 35(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 34(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB)
And it stays like this forever (2hours) and nothing. That's why I asked for your help.

todorov.drago1 said:
When I try to do this, it gives me this /attached file/, and then after some second It reboots.
Keep in mind that I don't have installed OS on that phone.
Click to expand...
Click to collapse
That's recovery. I ment bootloader. Press power+vol down, and you will get in bootloader menu. From there make a factory reset

todorov.drago1 said:
Yeah, I did that and this was outcome:
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 41(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 2.867 secs
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
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device SH39JW901074...
^C
C:\Users\Drago Todorov\Downloads\fastboot-win>
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 35(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 34(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB)
And it stays like this forever (2hours) and nothing. That's why I asked for your help.
Click to expand...
Click to collapse
I think when others have seen this @alray and others suggest it could be adb drivers (make sure you have most current) and tray another usb cable and \or port. I know it worked the first time, sort of as it usully restarts automatically. But worth a try.

donkeykong1 said:
That's recovery. I ment bootloader. Press power+vol down, and you will get in bootloader menu. From there make a factory reset
Click to expand...
Click to collapse
Well, when I go to the bootloader and press factory reset I sends me to the recovery. I think that was normal. Is it not ?

mb_guy said:
I think when others have seen this @alray and others suggest it could be adb drivers (make sure you have most current) and tray another usb cable and \or port. I know it worked the first time, sort of as it usully restarts automatically. But worth a try.
Click to expand...
Click to collapse
I'll try with a different usb cable and different port, and ill get back to you. Thanks for the help fellas.

todorov.drago1 said:
Yeah, I did that and this was outcome:
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 41(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 2.867 secs
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
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device SH39JW901074...
^C
C:\Users\Drago Todorov\Downloads\fastboot-win>
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 35(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 34(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB)
And it stays like this forever (2hours) and nothing. That's why I asked for your help.
Click to expand...
Click to collapse
Wait just a moment. I didn't see this post of yours. When fastboot prompts you to "flush image again immediately" what steps exactly do you do? Please describe it in your own words. I think I know what the problem is [emoji6]

todorov.drago1 said:
I'll try with a different usb cable and different port, and ill get back to you. Thanks for the help fellas.
Click to expand...
Click to collapse
Do you have HTCsync installed on your pc? If so uninstall it. Leaving only the HTC drivers installed. Reboot your pc and flash the RUU again.
HTCsync can cause ruu's to stall like that :good:
Sent from my SM-T230 using Tapatalk

donkeykong1 said:
Wait just a moment. I didn't see this post of yours. When fastboot prompts you to "flush image again immediately" what steps exactly do you do? Please describe it in your own words. I think I know what the problem is [emoji6]
Click to expand...
Click to collapse
Thanks mate for the help, i flashed it correctly. I just switched the usb's and it went on with the install.
And now can i ask you somethink else, after the install my phone says there is no IMEI num and doesnt exept my sim card can this be fix or is it hardware problem, it worked before tho?

todorov.drago1 said:
Thanks mate for the help, i flashed it correctly. I just switched the usb's and it went on with the install.
And now can i ask you somethink else, after the install my phone says there is no IMEI num and doesnt exept my sim card can this be fix or is it hardware problem, it worked before tho?
Click to expand...
Click to collapse
Sorry mate, I really can't help you with that. I never encountered that issue, so everything I say would be guessing, and potenetial fixes might ruin your phone. Sorry again [emoji20]

donkeykong1 said:
Sorry mate, I really can't help you with that. I never encountered that issue, so everything I say would be guessing, and potenetial fixes might ruin your phone. Sorry again [emoji20]
Click to expand...
Click to collapse
Nah Dude you did alot for me for it im am thankful alot. ill just have to take it to a GSM service to fix it then :angel:

todorov.drago1 said:
Nah Dude you did alot for me for it im am thankful alot. ill just have to take it to a GSM service to fix it then :angel:
Click to expand...
Click to collapse
Check your baseband as well. Unknown IMEI and baseband is a known issue. Unfortunately if flashing the ruu doesn't help its most probably a hardware problem. ?
Sent from my HTC One using Tapatalk

?
I'm trying to flash recovery.img with fastboot and it is downloaded, but when it starts to write
it says Failed (remote not allowed.) Any hints? Thanks

halloj said:
I'm trying to flash recovery.img with fastboot and it is downloaded, but when it starts to write
it says Failed (remote not allowed.) Any hints? Thanks
Click to expand...
Click to collapse
Is your bootloader unlocked?

Related

Error : 43, while restoring RUU from zip

Hi All,
I am trying to get my phone back to stock and trying to flash RUU zip via fastboot, however i am getting the below error, could you please help me understand what the error means :
Code:
D:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>fastboot flash zip rom.
zip
sending 'zip' (1029979 KB)...
OKAY [ 59.742s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 186.470s
Thanks a lot
Could anyone please help me with this?
It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off
gunnyman said:
It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off
Click to expand...
Click to collapse
well so i guess there is no way currently to go back to stock with 1.544 hboot. I checked the RUU has my model id but i am s-on , so i guess i have nothing left but to sulk
gunnyman said:
It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off
Click to expand...
Click to collapse
Do you know if there is anyway for me to go 100% stock with a 4.1.2 RUU , when i am on 4.2.2 with 1.544 hboot with s-on?
No not possible.

Am I screwed?

I just spent way too much time trying to figure this out. Today the mic on my one shat the bed, so I was attempting to return to stock to get a replacement. I am running the 1.31 software and foolishly tried to run back to 1.29. I am relocked, I have access to fastboot but nothing pass security verification. I've tried recoveries, my unlock time bin, and anything else I could throw at it. Nothing works. I always get the FAILED message. I am S ON, and security warning at the header of my boot loader screen. I can't get it to be recognized be adb either. Man would I love some advice to get past this. Please.
Sent from my Nexus 7 using xda app-developers app
Your good don't worry. Download a recovery from the dev section. Rename it something easy like recovery.img and place it in the same folder as your ADB (if you don't have ADB keep reading down to the bottom then come back and flash your recovery). Open a command prompt on your computer and cd to your adb dir. Connect phone in fastboot to computer and type fastboot flash recovery recovery.img (or whatever you named it. Then from recovery follow the guide for 1.31 RUU which I will link below.
Now to RUU follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
You will see this message (failed) ignore it and flash the RUU anyway.
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.007263 seconds, 1.6KB/s
~ # ←[6n
To make your life easy you will need drivers for your phone the best are the universal naked drivers for HTC One
http://forum.xda-developers.com/showthread.php?t=2263822
If installed, uninstall HTC sync, and disable any anti virus or firewalls including Windows firewall. You will also need to download ADB if you don't have it minimal ADB is great
http://forum.xda-developers.com/showthread.php?p=42407269
It was lots of fun typing all of this on my phone.
Sent from my HTCONE using xda app-developers app
I can't get anything including recovery to flash. It all says Failed. Here's a pic of ,e trying to fastboot flash TWRP.
Sent from my Nexus 7 using xda app-developers app
ajd88 said:
I can't get anything including recovery to flash. It all says Failed. Here's a pic of ,e trying to fastboot flash TWRP.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Check PM
I think I got it. I had to re unlock the boot loader with a new token. I was trying to unlock with my old bin file. Thank you for helping me out much appreciated. Wasted way to many hours on this.
Sent from my Nexus 7 using xda app-developers app
Hit me up if you need anything else
ajd88 said:
I think I got it. I had to re unlock the boot loader with a new token. I was trying to unlock with my old bin file. Thank you for helping me out much appreciated. Wasted way to many hours on this.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
No worries, hope you get it sorted.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
It was lots of fun typing all of this on my phone.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I bet it was!! I wouldn't have tried that. More power to ya!! You are PRO!
Still getting
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
Im not stuck like I was I can get into recovery and boot, but everytime I try to Ruu I get this crap. I am Soff and have oem relocked everytime before attempting RUU. This sucks.
ajd88 said:
Still getting
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
Im not stuck like I was I can get into recovery and boot, but everytime I try to Ruu I get this crap. I am Soff and have oem relocked everytime before attempting RUU. This sucks.
Click to expand...
Click to collapse
Every time I got that message it was due to a bad or wrong choice in RUU files. I would try fastboot flashing this RUU.zip. Hopefully that will work for you. I have written up all the steps to follow that work for most people here. You are already past the tricky part.
Good luck.
MrFixit007 said:
Every time I got that message it was due to a bad or wrong choice in RUU files. I would try fastboot flashing this RUU.zip. Hopefully that will work for you. I have written up all the steps to follow that work for most people here. You are already past the tricky part.
Good luck.
Click to expand...
Click to collapse
That Zip file got me a little farther, still stuck though.
sending 'zip' (1029700 KB)...
OKAY [ 48.045s]
writing 'zip'...
(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) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(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: 54.880s
Are you running the RUU from your PC?
bigdaddy619 said:
Are you running the RUU from your PC?
Click to expand...
Click to collapse
Yes I am. Running windows 8. I have never had issues before doing stuff like this. I'm stumped.
Edit: Think I'm good now.
ajd88 said:
That Zip file got me a little farther, still stuck though.
sending 'zip' (1029700 KB)...
OKAY [ 48.045s]
writing 'zip'...
(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) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(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: 54.880s
Click to expand...
Click to collapse
When you get the please flush message you IMMEDIATELY run the exact same command again!!
Everything will work fine after that.
MrFixit007 said:
When you get the please flush message you IMMEDIATELY run the exact same command again!!
Everything will work fine after that.[/
Your right thats what I did. All good now. Thank you.
Click to expand...
Click to collapse

[solved] How to get back on stock?

Hello everybody,
I'm a victim of the infamous purple tint camera bug so I'm planning get my phone fixed and thus need to get back on stock. I'm currently S-OFF and relocked bootloader. My phone's original CID is O2___102 (German O2 HTC One) but right now its on super CID (11111111). My hboot is 1.44 and my radio 4a.13.3231.27. As of right now there is a 4.2.2 custom rom running on the phone. I tried to go back to stock using this RUU ruu_m7_u_jb_50_htc_europe_1-29-401-2_r_radio_4a-14-3250-13_10-33-1150-01_release_311663_signed_2_4-exe but it always gives me that annoying 155 image error. Does anybody know a way for me to return to stock? All answers are kindly appreciated! :fingers-crossed:
fearless! said:
Hello everybody,
I'm a victim of the infamous purple tint camera bug so I'm planning get my phone fixed and thus need to get back on stock. I'm currently S-OFF and relocked bootloader. My phone's original CID is O2___102 (German O2 HTC One) but right now its on super CID (11111111). My hboot is 1.44 and my radio 4a.13.3231.27. As of right now there is a 4.2.2 custom rom running on the phone. I tried to go back to stock using this RUU ruu_m7_u_jb_50_htc_europe_1-29-401-2_r_radio_4a-14-3250-13_10-33-1150-01_release_311663_signed_2_4-exe but it always gives me that annoying 155 image error. Does anybody know a way for me to return to stock? All answers are kindly appreciated! :fingers-crossed:
Click to expand...
Click to collapse
You can follow the link in my signature on returning to stock. The reason you were not able to run that RUU is your MID or CID needs to change to match the RUU. Take a look at this crushalot's site for the .401 RUU.
Thanks a lot for the reply. My CID is on 11111111, shouldnt I be able to flash every RUU? So basically I should change my CID to HTC__102 and then flash RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1 ?
fearless! said:
Thanks a lot for the reply. My CID is on 11111111, shouldnt I be able to flash every RUU? So basically I should change my CID to HTC__102 and then flash RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1 ?
Click to expand...
Click to collapse
Try this RUU it is stock for your phone. You can try it with superCID, if it fails just change CID to O2___102.
I've tried to flash the RUU with both super CID and O2___102 but it did not work. It failed with a 158 error.
fearless! said:
I've tried to flash the RUU with both super CID and O2___102 but it did not work. It failed with a 158 error.
Click to expand...
Click to collapse
if you're comfortable following my guide, you'll need to use CWM method. Here are all the files you'd need: http://forum.xda-developers.com/showpost.php?p=54857652&postcount=1068
Many thanks for your tips. Im trying to do the CWM nAndroid method but when Im trying to flash the RUU.zip, I get the following error:
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (XXXXXXXXX)...
Is something wrong with my bootloader?
PS: If it's of any interest, here is my getvar all output:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
fearless! said:
Many thanks for your tips. Im trying to do the CWM nAndroid method but when Im trying to flash the RUU.zip, I get the following error:
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (XXXXXXXXX)...
Is something wrong with my bootloader?
Click to expand...
Click to collapse
You need to follow instructions. When you run a RUU, you have to run the same command twice. Here are the instructions out of nkk71's guide.
In bootloader/FASTBOOT USB, flash it:
Code:
[B][I]fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip[/I][/B] <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
[B][I]fastboot reboot-bootloader[/I][/B]
majmoz said:
You need to follow instructions. When you run a RUU, you have to run the same command twice. Here are the instructions out of nkk71's guide.
In bootloader/FASTBOOT USB, flash it:
Code:
[B][I]fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip[/I][/B] <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
[B][I]fastboot reboot-bootloader[/I][/B]
Click to expand...
Click to collapse
Im not able to put in the command twice. After the first time it just gets stuck.
For the record, here is what my cmd looks like:
finished sending zip
OKAY
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (XXX)...
< waiting for device >
starts sending zip again...
gets stuck
I think the problem is that fastboot shouldnt "restart the same procedure" on its own, so I can type in the command again right?
fearless! said:
Im not able to put in the command twice. After the first time it just gets stuck.
For the record, here is what my cmd looks like:
finished sending zip
OKAY
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (XXX)...
< waiting for device >
starts sending zip again...
gets stuck
I think the problem is that fastboot shouldnt "restart the same procedure" on its own, so I can type in the command again right?
Click to expand...
Click to collapse
You are correct, it should not start its self. Let me do some quick checking and I will get back to you.
majmoz said:
You are correct, it should not start its self. Let me do some quick checking and I will get back to you.
Click to expand...
Click to collapse
Thank you a lot, Sir!
fearless! said:
Thank you a lot, Sir!
Click to expand...
Click to collapse
This is the only thing I could find. Let's reboot the phone and try the steps again.
Code:
fastboot reboot-bootloader
Code:
fastboot devices
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip ruu.zip
Code:
[B][I]fastboot flash zip ruu.zip[/I][/B] <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
Code:
fastboot reboot-bootloader
Arrrgh tried it again and same results..I don't know what's wrong with my phone..
fearless! said:
Arrrgh tried it again and same results..I don't know what's wrong with my phone..
Click to expand...
Click to collapse
It may not be your phone, are you running Win 8 or 8.1? If so, they don't recognize hboot 1.44, so you will need to use Win 7 or Ubuntu on USB FAQ Q#5.
I was running windows 7 but your advice was aiming at the right direction. I changed PCs to another Windows 7 PC and now the flashing seems to be working! Thanks for your help so far and Im gonna keep you updated if everything else went well
Next problem: after flashing the ruu and changing the CID back the adb pushing doesnt seem to work for me. It tells me that all the files have been copied but cwm wont find any files to restore. So Im guessing that the copying didnt work. Tried it in normal storage mode too but Im getting an error kessage while trying to copy the bigger files (900 and 400mb) . Any advice on how to solve this?
fearless! said:
Next problem: after flashing the ruu and changing the CID back the adb pushing doesnt seem to work for me. It tells me that all the files have been copied but cwm wont find any files to restore. So Im guessing that the copying didnt work. Tried it in normal storage mode too but Im getting an error kessage while trying to copy the bigger files (900 and 400mb) . Any advice on how to solve this?
Click to expand...
Click to collapse
are you pushing to the right location? can you copy/paste your command prompt output
if you look at post #8 in my guide, you'll have a visual walkthrough of what kind of output to expect.
nkk71 said:
are you pushing to the right location? can you copy/paste your command prompt output
if you look at post #8 in my guide, you'll have a visual walkthrough of what kind of output to expect.
Click to expand...
Click to collapse
I did manage to get the files on my phone (over simple USB and put it in sdcard/clockworkmod/backup). But now CWM does not recognize the backup (another test backup that i put into the same folder is being recognized). When I tried to push the files before my cmd output looked just like the output in your guide. Ill try to push the files again and post the output here.
Here is my output:
c:\mini-sdk>adb push 2013-03-11.17.58.27 /data/media/clockworkmod/backup/2013-03
-11.17.58.27
push: 2013-03-11.17.58.27/system.ext4.tar.b -> /data/media/clockworkmod/backup/2
013-03-11.17.58.27/system.ext4.tar.b
push: 2013-03-11.17.58.27/system.ext4.tar.a -> /data/media/clockworkmod/backup/2
013-03-11.17.58.27/system.ext4.tar.a
push: 2013-03-11.17.58.27/system.ext4.tar -> /data/media/clockworkmod/backup/201
3-03-11.17.58.27/system.ext4.tar
push: 2013-03-11.17.58.27/recovery.img -> /data/media/clockworkmod/backup/2013-0
3-11.17.58.27/recovery.img
push: 2013-03-11.17.58.27/nandroid.md5 -> /data/media/clockworkmod/backup/2013-0
3-11.17.58.27/nandroid.md5
push: 2013-03-11.17.58.27/data.ext4.tar.a -> /data/media/clockworkmod/backup/201
3-03-11.17.58.27/data.ext4.tar.a
push: 2013-03-11.17.58.27/data.ext4.tar -> /data/media/clockworkmod/backup/2013-
03-11.17.58.27/data.ext4.tar
push: 2013-03-11.17.58.27/cache.ext4.tar.a -> /data/media/clockworkmod/backup/20
13-03-11.17.58.27/cache.ext4.tar.a
push: 2013-03-11.17.58.27/cache.ext4.tar -> /data/media/clockworkmod/backup/2013
-03-11.17.58.27/cache.ext4.tar
push: 2013-03-11.17.58.27/boot.img -> /data/media/clockworkmod/backup/2013-03-11
.17.58.27/boot.img
10 files pushed. 0 files skipped.
2670 KB/s (1532716986 bytes in 560.567s)
CWM says: No file found

[Q] Soft-bricked Phone Issue

Hello all,
I am having trouble trying to restore my AT&T HTC One M7 back to being functional again. The phone was soft-bricked "somehow" by my ex-wife and have been trying to restore it for the past few months. I have done alot of searching and tried many options but nothing is working so far.
The phone had never been rooted and has no custom roms on it. After it was soft-bricked, I was able to get it unlocked at one point, but stupidly enough I followed some wrong advice on how to proceed from there and relocked the phone. Now I cannot unlock it again in order to try to put TWRP or recovery on the phone to get it working again.
So far I have tried the following approaches to this issue:
1)I tried going through the HTC dev site steps to get a unlock code, but nothing happens on the phone screen even after getting a successful notice in CMD screen. (I tried both the original code and getting a new code)
2)Every time I try to flash it on there also I get signature failures in CMD and nothing happens on the phone.
3)I also tried running a stock RUU app, but after the process beings the final update, I get a usb cable error saying it is unplugged when it is not.
Thanks in advance for any suggestions.
To me that sounds like it might be a corrupt boot loader. You could also try to gain s-off and flash a recovery that way. Rumrunner works well: http://rumrunner.us
If you can s-off it then you can flash an hboot image which should fix the issue. Just go to the hboot section on the rumrunner website. Then install TWRP etc....
Your bootloader needs to be locked in order to run the RUU. Boot to bootloader screen and make sure you are in Fastboot. If on Windows, ensure you have adb installed correctly. Open command prompt on Windows with phone connected and type 'Fastboot relock oem'. This should relock the bootloader. From there, you need to make sure you have the correct RUU for your firmware, boot the phone to the main bootloader screen and run the RUU. Let me know if you need more details.
MarkBell said:
Your bootloader needs to be locked in order to run the RUU. Boot to bootloader screen and make sure you are in Fastboot. If on Windows, ensure you have adb installed correctly. Open command prompt on Windows with phone connected and type 'Fastboot relock oem'. This should relock the bootloader. From there, you need to make sure you have the correct RUU for your firmware, boot the phone to the main bootloader screen and run the RUU. Let me know if you need more details.
Click to expand...
Click to collapse
Thanks for sticking around and helping others
The correct command to lock the bootloader is fastboot oem lock. but he says he can't unlock his bootloader so I doubt that's the problem.
@Squirrelsquisher what is the software version on the phone
3.xx.502.x / 4.xx.502.x / 5.xx.502.x ?
you can use a fastboot command to get the info
fastboot getvar all
you can post the result here or just give me your version number as you have AT&T I already know you MID and CID
I love Xda, and plan to become more involved. My thinking is he is likely flashing the wrong RUU. If there is a mistake to be made, I've made it.
---------- Post added at 07:47 PM ---------- Previous post was at 07:37 PM ----------
And sorry about screwing up that Fastboot command. Lol. Posting too early in the day I guess. Lol. It is indeed Fastboot oem lock. I skimmed over the fact he can't unlock the bootloader. Sorry.
clsA said:
Thanks for sticking around and helping others
The correct command to lock the bootloader is fastboot oem lock. but he says he can't unlock his bootloader so I doubt that's the problem.
@Squirrelsquisher what is the software version on the phone
3.xx.502.x / 4.xx.502.x / 5.xx.502.x ?
you can use a fastboot command to get the info
fastboot getvar all
you can post the result here or just give me your version number as you have AT&T I already know you MID and CID
Click to expand...
Click to collapse
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Squirrelsquisher said:
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Click to expand...
Click to collapse
Try using a different USB cable. Make sure it's not one of those cheap ones from ebay. I've had issues with those before. Use your stock usb cord if you can. Let me know if you try that and it still doesn't work. Also try a different USB port on your computer. For some reason, port 2 tends to work best for most people is what I've read.
Squirrelsquisher said:
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Click to expand...
Click to collapse
You can flash just the firmware zip
It's on my android file host
I'll post the link when I get to my PC
MarkBell said:
Try using a different USB cable. Make sure it's not one of those cheap ones from ebay. I've had issues with those before. Use your stock usb cord if you can. Let me know if you try that and it still doesn't work. Also try a different USB port on your computer. For some reason, port 2 tends to work best for most people is what I've read.
Click to expand...
Click to collapse
I tried again using different USB ports and different cables with the same error result. Both cables that I used are stock HTC One cables that came with this problem phone and my newer M8 version.
The RUU I have been trying 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
Did you have sense 5.5 or had you upgraded to Sense 6 before? If you upgraded look for the RUU made for your software version with Sense 6. You may also try a newer RUU version. Just don't try an older one.
MarkBell said:
Did you have sense 5.5 or had you upgraded to Sense 6 before? If you upgraded look for the RUU made for your software version with Sense 6. You may also try a newer RUU version. Just don't try an older one.
Click to expand...
Click to collapse
I didn't get any version errors during the update and I have not seen any RUU out there with sense 6 that doesn't require S-off.
Have you tried the first one on this list? http://forum.xda-developers.com/showthread.php?t=2428276
---------- Post added at 03:19 AM ---------- Previous post was at 03:15 AM ----------
Also. Make sure you check the MD5 of everything you download. I've heard of people downloading corrupted RUUs using Google Chrome. Try another browser. Any other one besides the one you have been using and check the MD5.
Squirrelsquisher said:
I didn't get any version errors during the update and I have not seen any RUU out there with sense 6 that doesn't require S-off.
Click to expand...
Click to collapse
MarkBell said:
Have you tried the first one on this list? http://forum.xda-developers.com/showthread.php?t=2428276
---------- Post added at 03:19 AM ---------- Previous post was at 03:15 AM ----------
Also. Make sure you check the MD5 of everything you download. I've heard of people downloading corrupted RUUs using Google Chrome. Try another browser. Any other one besides the one you have been using and check the MD5.
Click to expand...
Click to collapse
He said in both post #6 and #9 that that is the RUU he's trying
Here's the firmware from the OTA try flashing it then the RUU
http://www.androidfilehost.com/?fid=23329332407580581
I meant that download specifically thinking along the lines of a bad file/download. clsA is very good and I recommend following any advice he gives.
clsA said:
He said in both post #6 and #9 that that is the RUU he's trying
Here's the firmware from the OTA try flashing it then the RUU
Could you be a little more specific on the steps involved in that? Because I tried straight flashing that file and it said it could not load.
Click to expand...
Click to collapse
Squirrelsquisher said:
Could you be a little more specific on the steps involved in that? Because I tried straight flashing that file and it said it could not load.
Click to expand...
Click to collapse
In these situations, it's usually best to always post a "fastboot getvar all" excluding IMEI, possibly a screenshot of bootloader, and a copy/paste of your command prompt output.
the way to flash firmware is:
fastboot oem rebootRUU
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip <- yes twice!!, first will say failed flush again, second one should report success
fastboot reboot-bootloader
nkk71 said:
In these situations, it's usually best to always post a "fastboot getvar all" excluding IMEI, possibly a screenshot of bootloader, and a copy/paste of your command prompt output.
the way to flash firmware is:
fastboot oem rebootRUU
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip <- yes twice!!, first will say failed flush again, second one should report success
fastboot reboot-bootloader
Click to expand...
Click to collapse
I attached a screenshot of the getvar results before attempting those steps you posted.
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Squirrelsquisher said:
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Click to expand...
Click to collapse
getvar looks ok (well, more or less), what says "it failed"?
example of a copy/paste of a command prompt output:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
[B][COLOR="Red"]FAILED (remote: 90 hboot pre-update! please flush image again immediately)[/COLOR][/B]
finished. total time: 43.118s
^^ as expected "flush again"
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
< waiting for device >
sending 'zip' (1033216 KB)...
OKAY [ 41.912s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
......
......
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
[B](bootloader) ...... Successful
OKAY [200.187s]
finished. total time: 242.101s[/B]
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.037s
---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------
Squirrelsquisher said:
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Click to expand...
Click to collapse
oh crap, just saw your screenshot
are you using a USB3 port?
nkk71 said:
getvar looks ok (well, more or less), what says "it failed"?
example of a copy/paste of a command prompt output:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
[B][COLOR="Red"]FAILED (remote: 90 hboot pre-update! please flush image again immediately)[/COLOR][/B]
finished. total time: 43.118s
^^ as expected "flush again"
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
< waiting for device >
sending 'zip' (1033216 KB)...
OKAY [ 41.912s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
......
......
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
[B](bootloader) ...... Successful
OKAY [200.187s]
finished. total time: 242.101s[/B]
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.037s
---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------
oh crap, just saw your screenshot
are you using a USB3 port?
Click to expand...
Click to collapse
My PC does not have USB3 ports, only USB2. I don't see how the speed of the transfer would affect the process though?

My device isn't working, rebooting PLZ Help!!!

Dear all,
My friend's phone is always rebooting and isn't working, even, I have tried to enter recovery no use, even, I have tried to install custom recovery no use.
I have downloaded many firmwares and it's not working, even the Original HTC ROMs can't update the phone with Signature Error, I read many forum threads but, the information isn't clear for me and didn't find a direct steps to follow, I really appreciate your help,
The device is showing
********** TAMPERED ********
********** RELOCKED ********
M7_UL IVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO -4T.29.3218.08
OpenDSP-v32.120.274.0909
OS-6.09.401.5
wMMC-boot 2048MB
I got the fastboot getvar all for your reference.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXX
(bootloader) imei: xxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4299mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.087s
Click to expand...
Click to collapse
Thanks in advance
magcp said:
Dear all,
My friend's phone is always rebooting and isn't working, even, I have tried to enter recovery no use, even, I have tried to install custom recovery no use.
I have downloaded many firmwares and it's not working, even the Original HTC ROMs can't update the phone with Signature Error, I read many forum threads but, the information isn't clear for me and didn't find a direct steps to follow, I really appreciate your help,
The device is showing
********** TAMPERED ********
********** RELOCKED ********
M7_UL IVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO -4T.29.3218.08
OpenDSP-v32.120.274.0909
OS-6.09.401.5
wMMC-boot 2048MB
I got the fastboot getvar all for your reference.
Thanks in advance
Click to expand...
Click to collapse
You can unlock the bootloader, flash twrp 2.8.5.0 and restore this backup: https://www.androidfilehost.com/?fid=23622183712472331 then flash back the stock 6.09.401.5 recovery.
Or
Keep the bootloader relocked and flash the 7.19.401.2 RUU: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
btw remove your imei and serialno from your post above.
Hi, Thank you so much, I'll try both methods and I'll let you know,
PS: I have removed the IMEI, thanks for letting me know.
Kind regards,
alray said:
You can unlock the bootloader, flash twrp 2.8.5.0 and restore this backup: https://www.androidfilehost.com/?fid=23622183712472331 then flash back the stock 6.09.401.5 recovery.
Or
Keep the bootloader relocked and flash the 7.19.401.2 RUU: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
btw remove your imei and serialno from your post above.
Click to expand...
Click to collapse
alray said:
You can unlock the bootloader, flash twrp 2.8.5.0 and restore this backup: https://www.androidfilehost.com/?fid=23622183712472331 then flash back the stock 6.09.401.5 recovery.
Or
Keep the bootloader relocked and flash the 7.19.401.2 RUU: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
btw remove your imei and serialno from your post above.
Click to expand...
Click to collapse
Hi, I have tried to flash the lolipop ruu, and it gave me this error (using htc_fastboot):
sending 'zip'... (43283 KB) OKAY
sending time = 3.511 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 9(s)
Plus, I can't unlock the bootloader it is still stating relocked
magcp said:
Hi, I have tried to flash the lolipop ruu, and it gave me this error (using htc_fastboot):
sending 'zip'... (43283 KB) OKAY
sending time = 3.511 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 9(s)
Plus, I can't unlock the bootloader it is still stating relocked
Click to expand...
Click to collapse
is your phone booted in ruu mode?
alray said:
is your phone booted in ruu mode?
Click to expand...
Click to collapse
Yes, it is
magcp said:
Hi, I have tried to flash the lolipop ruu, and it gave me this error (using htc_fastboot):
sending 'zip'... (43283 KB) OKAY
sending time = 3.511 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 9(s)
Plus, I can't unlock the bootloader it is still stating relocked
Click to expand...
Click to collapse
magcp said:
Yes, it is
Click to expand...
Click to collapse
43283 kb only? Its 42 Mb only, you are either not flashing the right file or the file is corrupted. The 7.19.401.2 ruu is 1.56 Gb so fastboot should report:
Code:
sending 'zip'... [B][COLOR="Red"](1637620 KB)[/COLOR][/B] OKAY.
alray said:
43283 kb only? Its 42 Mb only, you are either not flashing the right file or the file is corrupted. The 7.19.401.2 ruu is 1.56 Gb so fastboot should report:
Code:
sending 'zip'... [B][COLOR="Red"](1637620 KB)[/COLOR][/B] OKAY.
Click to expand...
Click to collapse
Hi, Thanks for your reply, I really don't know, I can confirm that the file is 1.56 GB on Disk, I can't open it with WinRar or Zip7 but, I downloaded this file twice, I'll try again in few hours and I'll let you know, by the way, I have flashed the 5.1 on my Nexus 6 and it was sending the file in chunks but, I don't know about HTC,
Thanks again
magcp said:
Hi, Thanks for your reply, I really don't know, I can confirm that the file is 1.56 GB on Disk, I can't open it with WinRar or Zip7 but, I downloaded this file twice, I'll try again in few hours and I'll let you know, by the way, I have flashed the 5.1 on my Nexus 6 and it was sending the file in chunks but, I don't know about HTC,
Thanks again
Click to expand...
Click to collapse
By the way, I have tried the EXE file and it gave me Signature error as well, so, I guess it's not corrupted zip file.
Any ideas???
I don't know why it is not accepting to unlock the phone, I tried it many times, and it's "RELOCKED"
Thanks
magcp said:
By the way, I have tried the EXE file and it gave me Signature error as well, so, I guess it's not corrupted zip file.
Any ideas???
I don't know why it is not accepting to unlock the phone, I tried it many times, and it's "RELOCKED"
Thanks
Click to expand...
Click to collapse
whats wrong when trying to unlock the bootloader?
alray said:
whats wrong when trying to unlock the bootloader?
Click to expand...
Click to collapse
I don't know, I execute this command and I got this results:
C:\...\Downloads>fastboot flash unlocktoken "Unlock_code (1).bin"
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.013s]
finished. total time: 0.157s
Click to expand...
Click to collapse
Then, I choose YES then POWER, the phone restarts but nothing happens, it CAN NOT enter RECOVERY just white screen saying "Entering Recovery..." then after a while a black screen appears and stays there, then, I press VOL Down + POWER to enter fastboot. and "RELOCKED" message is there.
Thanks
magcp said:
I don't know, I execute this command and I got this results:
Then, I choose YES then POWER, the phone restarts but nothing happens, it CAN NOT enter RECOVERY just white screen saying "Entering Recovery..." then after a while a black screen appears and stays there, then, I press VOL Down + POWER to enter fastboot. and "RELOCKED" message is there.
Thanks
Click to expand...
Click to collapse
looks like your bootloader was relocked with a custom recovery. You can't unlock the bootloader if a custom recovery is installed and you can't boot to your custom recovery if the bootloader is relocked. You will have to reflash the stock firmware.
download the firmware from here: https://www.androidfilehost.com/?fid=23622183712460395
Code:
fastboot oem rebootRUU
fastboot flash zip 6.09.401.5_signed_firmware.zip
fastboot flash zip 6.09.401.5_signed_firmware.zip
fastboot reboot-bootloader
then get a new unlock_code.bin
Code:
fastboot oem get_identifier_token
submit the token to htcdev.com/bootloader and wait for your unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
alray said:
looks like your bootloader was relocked with a custom recovery. You can't unlock the bootloader if a custom recovery is installed and you can't boot to your custom recovery if the bootloader is relocked. You will have to reflash the stock firmware.
download the firmware from here: https://www.androidfilehost.com/?fid=23622183712460395
Code:
fastboot oem rebootRUU
fastboot flash zip 6.09.401.5_signed_firmware.zip
fastboot flash zip 6.09.401.5_signed_firmware.zip
fastboot reboot-bootloader
then get a new unlock_code.bin
Code:
fastboot oem get_identifier_token
submit the token to htcdev.com/bootloader and wait for your unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
When trying to flash the zip it said:
Code:
sending 'zip' (44368 KB)...
OKAY [ 3.349s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.281s
magcp said:
When trying to flash the zip it said:
Code:
sending 'zip' (44368 KB)...
OKAY [ 3.349s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.281s
Click to expand...
Click to collapse
can you post a complete screenshot of your command prompt please?
Here you are,
htc_fastboot.exe
is the same as
fastboot.exe
but, I was just checking
Thanks
magcp said:
Here you are,
htc_fastboot.exe
is the same as
fastboot.exe
but, I was just checking
Thanks
Click to expand...
Click to collapse
you must reboot in ruu mode before flashing the zip:
Code:
fastboot oem rebootRUU
Phone will reboot to a black screen with silver HTC logo
alray said:
you must reboot in ruu mode before flashing the zip:
Code:
fastboot oem rebootRUU
Phone will reboot to a black screen with silver HTC logo
Click to expand...
Click to collapse
I did already,
magcp said:
I did already,
Click to expand...
Click to collapse
Well its very strange, with s-on and relocked bootloader you should be able to flash this firmware. Don't know why the signature verification is failing. Try with this one: https://www.androidfilehost.com/?fid=23622183712462447
or this one: https://www.androidfilehost.com/?fid=23622183712459334
You can also try to extract the firmware.zip from this ota: https://www.androidfilehost.com/?fid=23622183712458585 and flash it
and always make sure your MD5 match before flashing.
alray said:
Well its very strange, with s-on and relocked bootloader you should be able to flash this firmware. Don't know why the signature verification is failing. Try with this one: https://www.androidfilehost.com/?fid=23622183712462447
or this one: https://www.androidfilehost.com/?fid=23622183712459334
You can also try to extract the firmware.zip from this ota: https://www.androidfilehost.com/?fid=23622183712458585 and flash it
and always make sure your MD5 match before flashing.
Click to expand...
Click to collapse
I have verified the first two and tried and still, signature error, is there something wrong with the bootloader?? can I flash another bootloader?
alray said:
Well its very strange, with s-on and relocked bootloader you should be able to flash this firmware. Don't know why the signature verification is failing. Try with this one: https://www.androidfilehost.com/?fid=23622183712462447
or this one: https://www.androidfilehost.com/?fid=23622183712459334
You can also try to extract the firmware.zip from this ota: https://www.androidfilehost.com/?fid=23622183712458585 and flash it
and always make sure your MD5 match before flashing.
Click to expand...
Click to collapse
I have downloaded the OTA and after verifying, I extracted the firmware.zip and flash it, and still Signature Error
Code:
C:\Users\MAG\Downloads>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.035s]
finished. total time: 0.036s
C:\Users\MAG\Downloads>fastboot flash zip firmware.zip
sending 'zip' (44368 KB)...
OKAY [ 3.255s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.187s

Categories

Resources