Database Develop

[Q] Downgrading from 4.4. to 4.3

Morning everyone,
I have been reading for days trying to get a handle on downgrading my phone to JB 4.3. I am s-off, unlocked, rooted, with current TWRP installed. I also am using SuperSu. I suspect I am just not using the right combination of programming. My first thought is that I need the correct Hboot to go with the ROM I want. Currently I am on Android 4.4.2 with sense 5.5. Software is 4.18.502.7 CL302626. I have loaded a custom Hboot which removed the developer red text. and have also removed the tampered warning with a bit of help from here. I am quite happy with remaining s-off and unlocked. I am decent with ADB commands. I understand Linux fairly well, and can even use a hex editor in a crude way.
The last 4.3 RUU_exe and RUU_zip would not complete. The EXE stated not compatible. The ZIP failed looking for the Android-info_txt. I looked in the ZIP file thinking it might need modified and did not find the Android-info file at all. Lead me to believe that I may not be hitting the correct file for my use. So, at the risk of asking a repeated question I have finally come here for a push in the right direction.
I have not messed with all of this since I modded my old EVO 4G from Sprint. The new Android system worked well in stock form. I started down this road because of my desire to move back to 4.3
And I did attempt to use the search function but did not find exactly what I want. Appreciate any help I may be able to get.

lonestarmedic said:
My first thought is that I need the correct Hboot to go with the ROM I want.
Click to expand...
Click to collapse
No! you don't have to flash hboot to be able to flash a rom, you can flash a 4.4 Rom even if i.e you are on hboot 1.44.
lonestarmedic said:
Currently I am on Android 4.4.2 with sense 5.5. Software is 4.18.502.7 CL302626. I have loaded a custom Hboot which removed the developer red text and have also removed the tampered warning with a bit of help from here. I am quite happy with remaining s-off
Click to expand...
Click to collapse
I hope so, never turn S-ON with a modded hboot or you will probably brick your phone. Anyway, never S-ON!
lonestarmedic said:
The last 4.3 RUU_exe and RUU_zip would not complete. The EXE stated not compatible.
Click to expand...
Click to collapse
What version of RUU.exe and zip? Please also post the output of fastboot getvar all except IMEI. What was the error code of the ruu.exe and what was the output when attempting to flash the ruu.zip? you were in fastboot ruu mode right? Did you md5 check both the zip and exe?
lonestarmedic said:
The ZIP failed looking for the Android-info_txt. I looked in the ZIP file thinking it might need modified and did not find the Android-info file at all.
Click to expand...
Click to collapse
android-info.txt should be inside ruu.zip, however if you have the correct ruu for your mid/cid you should not have to modify the android-info.txt

Answers
Will do my best to answer.
1) Your example was a newer ROM on an older Hboot. I am going to older ROM on newer Hboot. Any difference.
2) No intention of turning S-on. Understand risks of modified Hboot. I do have stock Hboot if needed.
3) The RUU.exe is RUU_M7_UL_SENSE 5.0_MR_Cingular_US_3.17.502.3_Radio_4A19.3263.13_10.38j.1157.04_release_334235_signed_2
4) The RUU.zip is RUU Zip M7_UL_JB43_Sense50_MR_Cingular_US_3.17.502.3-decrypted
5) I did not copy the prompt screne on the ADB failure. I believe it was a parsing failure 24 on the Android-info.txt
6) Yes, using fastboot mode. Showing Fastboot USB and entering into the screen with the silver HTC logo.
7) I am honestly not sure if I checked both items for md5 sums.
8) I have to copy and paste the get var yet.
Working on the rest.

lonestarmedic said:
Will do my best to answer.
1) Your example was a newer ROM on an older Hboot. I am going to older ROM on newer Hboot. Any difference.
2) No intention of turning S-on. Understand risks of modified Hboot. I do have stock Hboot if needed.
3) The RUU.exe is RUU_M7_UL_SENSE 5.0_MR_Cingular_US_3.17.502.3_Radio_4A19.3263.13_10.38j.1157.04_release_334235_signed_2
4) The RUU.zip is RUU Zip M7_UL_JB43_Sense50_MR_Cingular_US_3.17.502.3-decrypted
5) I did not copy the prompt screne on the ADB failure. I believe it was a parsing failure 24 on the Android-info.txt
6) Yes, using fastboot mode. Showing Fastboot USB and entering into the screen with the silver HTC logo.
7) I am honestly not sure if I checked both items for md5 sums.
8) I have to copy and paste the get var yet.
Working on the rest.
Click to expand...
Click to collapse
1) no
5,7) make sure to md5 check your ruu. Looks like a bad download
3,4,8) still waiting for your getvar

Text files as requested
Getvar results edited out end of serial number and the imei. The meid does come up as all zeros.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34NW(xxxxxxx)
(bootloader) imei: a very private thing
(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: 4123mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Android-info text from the zip file
modelid: PN0712000
cidnum: CWS__001
mainver: 3.17.502.3
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Working on back checking md5 sums
Thanks so far.
JB

lonestarmedic said:
Getvar results edited out end of serial number and the imei. The meid does come up as all zeros.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34NW(xxxxxxx)
(bootloader) imei: a very private thing
(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: 4123mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Android-info text from the zip file
modelid: PN0712000
cidnum: CWS__001
mainver: 3.17.502.3
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Working on back checking md5 sums
Thanks so far.
JB
Click to expand...
Click to collapse
you should try to flash the stock hboot and flash the zip ruu again

Reflashin
alray said:
you should try to flash the stock hboot and flash the zip ruu again
Click to expand...
Click to collapse
I was using the stock Hboot from the OTA via AT&T. I put in the modified one to drop the ugly tampered stuff. Though that might have had something to do with my problem. And tried again with the modified Hboot.
Checked both md5s and good to go there.
JB

Flash timeframe
Is it possible I am too impatient on the flash of the Zip file? Phone sat with no progress for about 5-10 minutes on the silver HTC screen.
JB

Output on oemRUU attempt
Here is what I get when I attempt to use the zip file to flash the phone.
It is the same whether unlocked or relocked.
:\Android\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Android\platform-tools>fastboot flash zip jelly.zip
sending 'zip' (1114992 KB)...
OKAY [ 57.002s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 68.047s

Think I got it fixed
Very busy right now but will report back and explain what I did.
Mainly due to being unfamiliar with different file types and which uses what method for update/load.
JB

Back to 4.3 succsessfully
Ok, long process of learning. Found my problem was with the RUU that I was using. The md5 was ok. It just was not what was needed for using via fastboot.
Do not know what it is, but it has the following inside the zip file:
1) META INF folder
2)system folder
3)boot.img
Sure does not work for fastboot!!! I found a zip on here that had the right file name and was odexed. Downloaded, checked the md5, then unzipped to read the Android-info.txt file. All looked right. Made a backup of phone and loaded it on in.
Succsess!!! Of course I had to put TWRP back in and root the phone.
So, brief sequence of what I did:
1) OTA update from 4.3 to 4.4.2 caused problems with applications
2) Phone in stock form with Hboot 1.56
3) Unlocked phone - HTCdev website used
4) Rooted phone with SuperSU and installed TWRP
5) Played with ROMS and did not like any of them, decided to revert back to 4,3
6) Phone would not S-off with stock ROM using Rumrunner
7) Ended up with the combination of Android Revolution HD and Firewater. Used my UBUNTU Linux to perform S-off.
8) Back-up performed
9) Used zip file and fastboot to load 4.3
10) Now have Hboot 1.56 with 4.3 unlocked, stock Hboot, and S-off.
Thanks for listening to my rantings.
Maybe this will help someone else with an AT&T HTC One.
JB

[Q] Going back to stock for Lollipop update.

Hi, I've read a few threads about going back to stock, but I think the method is not exactly the same right? Like different firmwares etc. So do pardon me for starting this new thread ! I'm currently on ARHD 84.0 , ROM Version 6.09.401.12, S-ON. I'm using the international version if I'm not wrong. My phone's been starting to get frequent hiccups here and there lately, and I've been wanting to update to lollipop, so I've decided to return back to stock and wait for the official lollipop updates without having to S-OFF ( seems quite complicated for me ). May I know how exactly am I suppose to do that ? Thank You !

Boyho said:
Hi, I've read a few threads about going back to stock, but I think the method is not exactly the same right? Like different firmwares etc. So do pardon me for starting this new thread ! I'm currently on ARHD 84.0 , ROM Version 6.09.401.12, S-ON. I'm using the international version if I'm not wrong. My phone's been starting to get frequent hiccups here and there lately, and I've been wanting to update to lollipop, so I've decided to return back to stock and wait for the official lollipop updates without having to S-OFF ( seems quite complicated for me ). May I know how exactly am I suppose to do that ? Thank You !
Click to expand...
Click to collapse
exactly the same as the other threads, just maybe differtent files.
follow "how to flash" the instructions at the top of this page, the file you need is at the bottom 7.19.401.2, 3rd one up, make sure you get the right one: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

Seanie280672 said:
exactly the same as the other threads, just maybe differtent files.
follow "how to flash" the instructions at the top of this page, the file you need is at the bottom 7.19.401.2, 3rd one up, make sure you get the right one: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
Thanks, so I just have to follow the instructions in the link you've posted and download the correct one right? I'm in Singapore so do I still use the one you've suggested or the Asia version?

Boyho said:
Thanks, so I just have to follow the instructions in the link you've posted and download the correct one right? I'm in Singapore so do I still use the one you've suggested or the Asia version?
Click to expand...
Click to collapse
yup, doesnt matter which country your in, you have a WWE european phone, 6.09.401.12 is your current firmware, the 401 part is the key, you next upgarde is 7.19.401.2 which is the file I linked you too.

Just a quick question, do I flash the RUU first or Relock my bootloader first ?

Boyho said:
Just a quick question, do I flash the RUU first or Relock my bootloader first ?
Click to expand...
Click to collapse
if youre s-on, you must relock first to be able to flash the ruu.
Maybe you should post the output of "fastboot getvar all" before proceeding to make sure everything is fine using this RUU.

alray said:
if youre s-on, you must relock first to be able to flash the ruu.
Maybe you should post the output of "fastboot getvar all" before proceeding to make sure everything is fine using this RUU.
Click to expand...
Click to collapse
Help, I used this RUU : HTC_Europe_7.19.401.102 (m7_u edition) MIDN0711000 , accidentally instead of the one he told me. So now i received this error :
c:\mini-sdk>fastboot flash zip RUU.zip
sending 'zip'... (43287 KB) OKAY
sending time = 3.403 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...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 11(s)
My getvar is :
c:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4042mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 47(ms)

Boyho said:
Help, I used this RUU : HTC_Europe_7.19.401.102 (m7_u edition) MID:PN0711000 , accidentally instead of the one he told me. So now i received this error :
c:\mini-sdk>fastboot flash zip RUU.zip
sending 'zip'... (43287 KB) OKAY
sending time = 3.403 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...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 11(s)
My getvar is :
c:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4042mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 47(ms)
Click to expand...
Click to collapse
Even the ruu he told you won't work. Your phone is PN0714000 CID is HTC__044 and your base is .707. You can't flash a .401 RUU on your phone unless you achieve s-off to change MID to PN0710000 and CID to HTC__001.
The only ruu you could possibly use (not tested) is the 6.13.707.7 here: http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_UL/

Boyho said:
Help, I used this RUU : HTC_Europe_7.19.401.102 (m7_u edition) MIDN0711000 , accidentally instead of the one he told me. So now i received this error :
c:\mini-sdk>fastboot flash zip RUU.zip
sending 'zip'... (43287 KB) OKAY
sending time = 3.403 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...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 11(s)
My getvar is :
c:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4042mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 47(ms)
Click to expand...
Click to collapse
the one you tried to flash is the wrong one and not the one I suggested.
The one I suggested you to flash is also the wrong one, you said in your original post you were on 6.09.401, your not, your on 6.13.707.1, lucky for you it failed, there is no RUU available on that page for you at the moment.
Use the RUU that alray above has posted and dont flash anything again until you get the Lollipop update would be my best recommendation.

Seanie280672 said:
the one you tried to flash is the wrong one and the one I suggested you to flash is also the wrong one, you said in your original post you were on 6.09.401, your not, your on 6.13.707.1, lucky for you it failed, there is no RUU available on that page for you at the moment.
Click to expand...
Click to collapse
I thought I was on 6.09.401 since it was stated in my Settings ... I'll try the one the above has suggested first. Currently I'm stuck in RUU mode with my bootloader relocked

alray said:
Even the ruu he told you won't work. Your phone is PN0714000 CID is HTC__044 and your base is .707. You can't flash a .401 RUU on your phone unless you achieve s-off to change MID to PN0710000 and CID to HTC__001.
The only ruu you could possibly use (not tested) is the 6.13.707.7 here: http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_UL/
Click to expand...
Click to collapse
thanks I'll try now

alray said:
Even the ruu he told you won't work. Your phone is PN0714000 CID is HTC__044 and your base is .707. You can't flash a .401 RUU on your phone unless you achieve s-off to change MID to PN0710000 and CID to HTC__001.
The only ruu you could possibly use (not tested) is the 6.13.707.7 here: http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_UL/
Click to expand...
Click to collapse
May I know what's the username and password to download ?

Seanie280672 said:
the one you tried to flash is the wrong one and the one I suggested you to flash is also the wrong one, you said in your original post you were on 6.09.401, your not, your on 6.13.707.1, lucky for you it failed, there is no RUU available on that page for you at the moment.
Use the RUU that alray above has posted and dont flash anything again until you get the Lollipop update would be my best recommendation.
Click to expand...
Click to collapse
But unfortunately Im not 100% sure that ruu will work. Look at the file name: PN07IMG_M7_UL_K443_SENSE60_MR_hTC_Asia_WWE_6.13.707.7_Radio_4T.28.3218.04_10.33E.1718.01L_release_417380_combined_signed.zip.
I think he told you he was on 6.09.401 because he only looked at software version and not at his getvar. arhd 84 is based on 6.09.401 :silly:
---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------
Boyho said:
May I know what's the username and password to download ?
Click to expand...
Click to collapse
There is none you have to make your own account and we can't tell you if the RUU will work since we never tested it.

alray said:
But unfortunately Im not 100% sure that ruu will work. Look at the file name: PN07IMG_M7_UL_K443_SENSE60_MR_hTC_Asia_WWE_6.13.707.7_Radio_4T.28.3218.04_10.33E.1718.01L_release_417380_combined_signed.zip.
I think he told you he was on 6.09.401 because he only looked at software version and not at his getvar. arhd 84 is based on 6.09.401 :silly:
---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------
There is none you have to make your own account and we can't tell you if the RUU will work since we never tested it.
Click to expand...
Click to collapse
Sorry, can I unlock my bootloader again by flashing the unlock token ?

Modern TWRP Backup for CID: TELUS001

Hi everyone,
I have come across a friend's phone which is stuck in a bootloop since the battery died during an update. I am unable to run the Telus RUU (the only one I can find, from the collection thread, and it's very old). The RUU fails and I can not flash the zip from it manually using fastboot either. I can restore the TWRP backup from the collection but then the touch screen doesn't work (the backup must be much older).
So I am hoping someone on here has or can make me a TWRP backup of their latest stock HTC/Telus setup?
I am also going to see if I can get S-OFF and SuperCID so that I can try other RUUs. Thought that finding a backup would be a lot simpler/safer, though.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.661.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4231mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks!

There is a 7.17.661.7 RUU for Telus here. To use this RUU, the phone firmware must be at least 6.xx.661.x and not newer than 7.17.661.7. Read instructions how to flash the RUU in the OP (you must use htc_fastboot to flash it, not the normal fastboot). Post the output of "fastboot getvar all" (remove imei and serialno) if you need more help.

Thanks! I don't have the phone near me at the moment to get the vars however I do know that fw is 5.xx.661.x range

I've added the getvar output. Since it's not my phone I am trying to avoid S-OFF using Sunshine. Didn't think it would be so difficult to find an RUU or TRWP backup

Try the 7.17.661.7 ruu, it might work since the phone is already on hboot 1.57. Otherwise you'll need s-off to either update your firmware and flash this ruu or downgrade your hboot and flash the 4.19.661.8 ruu.
I might be able to provide you a nandroid backup of 5.11.661.8 if I have some spare time. I will need to flash the the 4.19.661.8 ruu on my phone, update it to 5.11.661.8 so I can make a backup and upload it for you. But I won't have the time to do it this week...

Thanks I'll give it a shot. I was hesitant since I heard that jumping more than 1 firmware version could be bad.. but I'll see what happens and let you know.

This firmware thing does not apply to ruu, only apply to firmware update extracted from ota updates . In the worst case, the pre check will fail and nothing will be flashed on the phone

I finally had a chance to try this out and the 7.17.661.7 RUU fails to flash. Guess I'll have to S-OFF.
C:\Users\ryan\Downloads\HTC One M7>htc_fastboot flash zip "C:\Users\ryan\Downloads\HTC One M7\TELUS ROMs\7.17.661.7 (RUU Zip)\PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202_signed.zip"
sending 'zip'... (43286 KB) OKAY
sending time = 2.633 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) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 8(s)

Well if you can s-off this phone it will be indeed possible to flash the ruu after updating the firmware.

M7 soft brick recovery

Hello,
My phone recently soft bricked itself while I was attempting to check a message. The system locked up, then went into a reboot where it hung on the HTC logo. The usual steps of trying a factory reset did not seem to fix the logo hang. The phone was never modified, it was running only stock firmware with S-ON and the boot loader locked. As this is my first attempt at recovering from a soft brick, the learning curve has been steep. At this point I am somewhat stuck as I don't understand why I cannot flash the stock RUU that i have. What I have done:
-unlocked boot loader (1.61.000)
-flashed to TWRP for recovery (3.0.2.0)
-Attempted to use ADB sideload to push RUU files. This failed because ADB only sees the device every few attempts and then sideload commands fail saying "error: closed"
-Attempted to flash RUU as per this post https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
*The RUU that I am trying to flash is the 7.19.401.51 signed version
Here is a getvar readout from my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3833mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I am really confused as to how it soft bricked itself in the first place during normal use and if I am doing something incorrect in flashing it.
C:\mini-sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 3.030 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) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 9(s)

I dont see a reason why it fails but i dont know much about using ruu files. But if you have unlocked your phone and twrp is working you should be able to just restore a Stock twrp backup. You can find them here in the m7 forum, download the one that is matching your device, restart your device into twrp connect it to your computer and copy the twrp backup from your computer into your twrp backup folder on the phone, go in twrp to restore and you should see the backup, select it and slide to start.

All fixed
So I actually managed to fix it last night using the RUU file. I didn't realize that I had to re-lock my boot loader for a signed RUU file to work properly. Once I ran the "fastboot oem lock" command, the file installed normally by running "fastboot oem bootRUU" and then flashing it with "fastboot flash RUU.zip"
I wasn't able to even move files with twrp loaded, my device showed up as an MTP device on my computer, but any file movements gave an error that the device stopped responding.

802w lollipop

Hello
I have the 802w model running MaximusHD rom (4.4)
Anyway I can update to 5.0+?
Thanks

PHOENIX-9 said:
Hello
I have the 802w model running MaximusHD rom (4.4)
Anyway I can update to 5.0+?
Thanks
Click to expand...
Click to collapse
With a RUU? what is your "fastboot getvar all" output?

A custom ROM will be nice to have
I'm not sure what I'm on.. But I know I'm S-on :/
Edit 01
@alray there's my output
i'd prefer a custom rom
but i wouldn't mind a rootable official one
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.14.3509.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.21.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA42RW900149
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4129mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f6d46eca
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Edit 02
so i looked up in your signature and found this RUU
correct me if im wrong.. if not please provide some further instructions of how to flash and root afterwards
thank you

PHOENIX-9 said:
A custom ROM will be nice to have
I'm not sure what I'm on.. But I know I'm S-on :/
Edit 01
@alray there's my output
i'd prefer a custom rom
but i wouldn't mind a rootable official one
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.14.3509.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.21.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA42RW900149
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4129mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f6d46eca
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Edit 02
so i looked up in your signature and found this RUU
correct me if im wrong.. if not please provide some further instructions of how to flash and root afterwards
thank you
Click to expand...
Click to collapse
You can flash the ruu using fastboot:
Code:
fastboot oem reboot RUU
fastboot flash zip ruu.zip
fastboot reboot
(Dont forget to use the fastboot version linked in the ruu collection thread at post #1)
or if you have a sdcard, rename the ruu file to "PN07IMG.zip" and save it at the root of your card and reboot in bootloader mode, use volume up/down and power buttons to flash the ruu.
Don't forget to relock the bootloader before flash the ruu if it's unlocked (requires when s-on)
To root your phone you'll need to re-unlock the bootloader, flash a custom recovery and flash the latest supersu.zip

alray said:
You can flash the ruu using fastboot:
Code:
fastboot oem reboot RUU
fastboot flash zip ruu.zip
fastboot reboot
(Dont forget to use the fastboot version linked in the ruu collection thread at post #1)
or if you have a sdcard, rename the ruu file to "PN07IMG.zip" and save it at the root of your card and reboot in bootloader mode, use volume up/down and power buttons to flash the ruu.
Don't forget to relock the bootloader before flash the ruu if it's unlocked (requires when s-on)
To root your phone you'll need to re-unlock the bootloader, flash a custom recovery and flash the latest supersu.zip
Click to expand...
Click to collapse
Thank you for your help
Will this format my internal storage?
Is this the command for relocking the bootloader "fastboot oem lock" ?
And re-unlocking the bootloader will be using HTC dev?

PHOENIX-9 said:
Thank you for your help
Will this format my internal storage?
Click to expand...
Click to collapse
yes
Is this the command for relocking the bootloader "fastboot oem lock" ?
Click to expand...
Click to collapse
yes

alray said:
yes
yes
Click to expand...
Click to collapse
I've downloaded the file 4 times
Every time it says that the zip is corrupted when I try to extract using WinRAR (I can open it but can't extract it) or when I open it using es file explorer

PHOENIX-9 said:
I've downloaded the file 4 times
Every time it says that the zip is corrupted when I try to extract using WinRAR (I can open it but can't extract it) or when I open it using es file explorer
Click to expand...
Click to collapse
It's an encrypted file, it can't be extracted with winwar. It doesn't need to be extracted...

alray said:
It's an encrypted file, it can't be extracted with winwar. It doesn't need to be extracted...
Click to expand...
Click to collapse
Oh
I usually do it as a precaution
Pausing and resuming usually corrupt zip files
Thank you !

PHOENIX-9 said:
Oh
I usually do it as a precaution
Pausing and resuming usually corrupt zip files
Thank you !
Click to expand...
Click to collapse
md5 checksum is available for that purpose.
md5 of that ruu is 6de185d48c24a296f53a5b1f25f039f9
and it won't flash on a s-on phone if its corrupted

alray said:
md5 checksum is available for that purpose.
md5 of that ruu is 6de185d48c24a296f53a5b1f25f039f9
and it won't flash on a s-on phone if its corrupted
Click to expand...
Click to collapse
i just did my first attempt and it failed
i cant reboot to recovery..system..nothing
just my bootloader with a security warning at the top
im gonna try another one of my downloaded zips
any ideas if that didnt work?
Edit
target reported max download size of 1542111232 bytes
sending 'zip' (1304199 KB)...
OKAY [ 60.604s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 192.961s

PHOENIX-9 said:
i just did my first attempt and it failed
i cant reboot to recovery..system..nothing
just my bootloader with a security warning at the top
im gonna try another one of my downloaded zips
any ideas if that didnt work?
Click to expand...
Click to collapse
What was the error

alray said:
What was the error
Click to expand...
Click to collapse
targetreported max download size of 1542111232 bytes
sending 'zip' (1304199 KB)...
OKAY [ 60.604s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 192.961s

alray said:
What was the error
Click to expand...
Click to collapse
i think i, gonna unlock the bootloader and re-install the ROM

No one has any idea how to deal with this!

PHOENIX-9 said:
No one has any idea how to deal with this!
Click to expand...
Click to collapse
I believe you missed the critical point written in earlier post
(Dont forget to use the fastboot version linked in the ruu collection thread at post #1)​
You need to use htc_fastboot not generic fastboot to flash ruu.zip

ckpv5 said:
I believe you missed the critical point written in earlier post
(Dont forget to use the fastboot version linked in the ruu collection thread at post #1)​
You need to use htc_fastboot not generic fastboot to flash ruu.zip
Click to expand...
Click to collapse
Actually I didn't
I copied my fastboot folder and replaced the fastboot from the given link