I'm trying to flash Stock RUU.
Now i have access only to Fastboot.
This the error log when i tried to flash RUU.zip
Code:
sending 'zip'... (50277 KB) OKAY
sending time = 3.213 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
FAILED (status read failed (Too many links))
Execution time is 10(s)
Device Info:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
svprm said:
I'm trying to flash Stock RUU.
Now i have access only to Fastboot.
This the error log when i tried to flash RUU.zip
Code:
sending 'zip'... (50277 KB) OKAY
sending time = 3.213 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
FAILED (status read failed (Too many links))
Execution time is 10(s)
Device Info:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
And what ruu version are you trying to flash?
7.21.707.121 LP 5.0.2 Sense 6
Indian version
svprm said:
7.21.707.121 LP 5.0.2 Sense 6
Indian version
Click to expand...
Click to collapse
Your firmware is too old to flash a 7.xx.xxx.xx RUU. To flash it you must be at least on a 6.xx.xxx.x firmware with hboot 1.57
alray said:
Your firmware is too old to flash a 7.xx.xxx.xx RUU. To flash it you must be at least on a 6.xx.xxx.x firmware with hboot 1.57
Click to expand...
Click to collapse
I tried to flash Stock Reset Rom
6.13.707.106 KK 4.4.3 Sense 6
From this thread:
http://forum.xda-developers.com/showthread.php?t=2778404
It stopped at Signature Verify Failed.
svprm said:
I tried to flash Stock Reset Rom
6.13.707.106 KK 4.4.3 Sense 6
From this thread:
http://forum.xda-developers.com/showthread.php?t=2778404
It stopped at Signature Verify Failed.
Click to expand...
Click to collapse
Signature Verify Failed? So you are trying to flash a rom using fastboot if I understand correctly? A rom must be flashed using a custom recovery. Only RUU/Firmware are flashed using fastboot. If you flash a ruu, it must be done using fastboot (in ruu mode) with a locked bootloader (because your phone is s-on). If flashing a rom, like the stock reset rom, it mus tbe done from twrp recovery with an unlocked bootloader.
alray said:
Signature Verify Failed? So you are trying to flash a rom using fastboot if I understand correctly? A rom must be flashed using a custom recovery. Only RUU/Firmware are flashed using fastboot. If you flash a ruu, it must be done using fastboot (in ruu mode) with a locked bootloader (because your phone is s-on). If flashing a rom, like the stock reset rom, it mus tbe done from twrp recovery with an unlocked bootloader.
Click to expand...
Click to collapse
When i try to flash files from TWRP recovery,it showing an error:
Unable to mount cache.
To solve this problem,i want to get back to Stock.
svprm said:
When i try to flash files from TWRP recovery,it showing an error:
Unable to mount cache.
To solve this problem,i want to get back to Stock.
Click to expand...
Click to collapse
Go in twrp recovery, select the "wipe" menu then select "Format Data" and type "Yes" to confirm. Once formatted, reboot twrp then push the reset rom to your phone storage, select "install" and flash the reset rom.
alray said:
Go in twrp recovery, select the "wipe" menu then select "Format Data" and type "Yes" to confirm. Once formatted, reboot twrp then push the reset rom to your phone storage, select "install" and flash the reset rom.
Click to expand...
Click to collapse
I tried all the ways i can not mount any partition on recovery system,data,cache.
Don't know why?
Again i tried to flash RUU.zip.
So i tried to lock the device again:
It showing following error:
Code:
... (bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
Execution time is 1(s)
Related
TWRP 2.6.3.3 is installed, adb is working. Funny enough, adb stops working with TWRP 2.7.
..adb sideload of Android_Revolution_HD-One_53.0 seems to work, go through the install questions, but never gets past HTC logo on reboot.
...flashed boot.img from HD-53 after sideload just in case, no change
...did factory reset in twrp, as well as wiping cache in twrp.. no change
..tried relocking bootloader and flashing RUU zip for Telus001, but failed with error, FAILED (remote: 12 signature verify fail)
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 12345
(bootloader) imei: 12345
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4268mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s
At a bit of a loss... but it doesn't seem dead just yet....
romansj said:
TWRP 2.6.3.3 is installed, adb is working. Funny enough, adb stops working with TWRP 2.7.
..adb sideload of Android_Revolution_HD-One_53.0 seems to work, go through the install questions, but never gets past HTC logo on reboot.
...flashed boot.img from HD-53 after sideload just in case, no change
...did factory reset in twrp, as well as wiping cache in twrp.. no change
..tried relocking bootloader and flashing RUU zip for Telus001, but failed with error, FAILED (remote: 12 signature verify fail)
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 12345
(bootloader) imei: 12345
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4268mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s
At a bit of a loss... but it doesn't seem dead just yet....
Click to expand...
Click to collapse
Did you md5 checked both your recovery and your rom before flashing?
Btw, you need a locked or relocked bootloader to flash a ruu with S-ON... Thats why you got the signature fail.
alray said:
Did you md5 checked both your recovery and your rom before flashing?
Btw, you need a locked or relocked bootloader to flash a ruu with S-ON... Thats why you got the signature fail.
Click to expand...
Click to collapse
Didn't do md5 check, but twrp 2.6.3.3 comes up as expected, and AD-53 installs as expected.
The bootloader was relocked for the RUU zip install.. I thought I read somewhere that it was because there is no OS present, or something.
romansj said:
Didn't do md5 check, but twrp 2.6.3.3 comes up as expected, and AD-53 installs as expected.
The bootloader was relocked for the RUU zip install.. I thought I read somewhere that it was because there is no OS present, or something.
Click to expand...
Click to collapse
what ruu are you trying to flash?
alray said:
what ruu are you trying to flash?
Click to expand...
Click to collapse
RUU Zip M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted
romansj said:
RUU Zip M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted
Click to expand...
Click to collapse
you are S-ON, you can't use decrypted RUU! With s-on you can only use SIGNED ruu
http://androidruu.com/getdownload.p...09_10.26.1718.01L_release_351500_signed_2.exe
alray said:
you are S-ON, you can't use decrypted RUU! With s-on you can only use SIGNED ruu
Click to expand...
Click to collapse
Thanks, I'll give that a shot once it finishes downloading. I was coming to the same conclusion but was stuck on trying to figure out why sideloading wasn't working. I guess the firmware is corrupt or some such? First time messing with an HTC and the world of RUUs
Will report back..
alray said:
you are S-ON, you can't use decrypted RUU! With s-on you can only use SIGNED ruu
]
Click to expand...
Click to collapse
Fails with error 155... Here's the relevent log:
htc_fastboot -s serial getvar boot-mode</CMD>
Execution time is 3(ms)boot-mode: RUU</OUT>
htc_fastboot -s serial erase cache</CMD>
Execution time is 60(ms)erasing 'cache'... OKAY</OUT>
Try to read image count from android-info.txt in rom.zip
The rom is encrypted, read the header instead.
[getImageCount] Large and signed rom
getImageCount, nHR: 18
htc_fastboot -s serial -d flash zip C:\Users\rhino\AppData\Local\Temp\{8B222E2D-DAB9-49ED-9B39-D1FC22F745A1}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
sending 'zip'... (42406 KB) OKAY</OUT>
=====Sending zip OK=====
writing 'zip'... (bootloader) adopting the signature contained in this image...</OUT>
(bootloader) signature checking...</OUT>
(bootloader) rom parsing start ...</OUT>
(bootloader) rom parsing finish ...</OUT>
(bootloader) zip header checking...</OUT>
(bootloader) zip info parsing...</OUT>
(bootloader) Read zipped android_info fail</OUT>
Execution time is 10382(ms)</OUT>
FAILED (status read failed (Too many links))</OUT>
Hello,
I need help with my HTC One M7 UL. After an OTA Update my phone started to bootloop. It has never been Rooted, its S-ON and I just unlocked the bootloader to try to fix it, didnt work though. Ive searched everywhere and I can not find a solution.
My getvar all:
(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.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:xxx
(bootloader) imei:xx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(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
Ive tryed to flash PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip but I only get an error:
sending 'zip'... (43286 KB) OKAY
sending time = 2.782 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 9(s)
Is it because im S-ON? Is it even possible to S-OFF it when I cant boot the Phone into the OS?
Help would be really apreciated
xtremtuner said:
Hello,
I need help with my HTC One M7 UL. After an OTA Update my phone started to bootloop. It has never been Rooted, its S-ON and I just unlocked the bootloader to try to fix it, didnt work though. Ive searched everywhere and I can not find a solution.
My getvar all:
(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.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(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
Ive tryed to flash PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip but I only get an error:
sending 'zip'... (43286 KB) OKAY
sending time = 2.782 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 9(s)
Is it because im S-ON? Is it even possible to S-OFF it when I cant boot the Phone into the OS?
Help would be really apreciated
Click to expand...
Click to collapse
relock your bootloader to flash a ruu. Also remove your IMEI/SN from your above post.
Thanks for the quick reply, removed imei and SN. But I have already tryed to flash with locked bootloader, it did not work
xtremtuner said:
Thanks for the quick reply, removed imei and SN. But I have already tryed to flash with locked bootloader, it did not work
Click to expand...
Click to collapse
can you post a screenshot of your command prompt please
alray said:
can you post a screenshot of your command prompt please
Click to expand...
Click to collapse
Sure:
xtremtuner said:
Sure:
Click to expand...
Click to collapse
Your phone must be booted in ruu mode to flash a ruu
you must use htc_fastboot.exe to flash a ruu, not fastboot.exe
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
htc_fastboot reboot
alray said:
Your phone must be booted in ruu mode to flash a ruu
you must use htc_fastboot.exe to flash a ruu, not fastboot.exe
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
htc_fastboot reboot
Click to expand...
Click to collapse
That worked, thank you!!! :laugh:
Need some very urgent help with getting 100% stock on the htc one m7. So far I have managed to unlock the bootloader and its showing S-ON and RELOCKED just under TAMPERED. Now I trying to RUU.img by using this command fastboot flash zip ruu.zip while in fastboot but the following error comes up: could not allocate 1688576026 bytes, error: cannot load 'ruu.zip'. Why is this error coming up? I am pretty sure I have the right RUU for my phone as it was suggested to me by someone on xda here.
Am i low on internal storage is that the reason why RUU is not going through? What is the possible fix. I am stuck on the black and white logo HTC screen with no OS installed or recovery. I think I might have a recovery saved in the internal storage but I cannot enter recovery mode either.
Any replies would be appreciated.
singh_harman said:
Need some very urgent help with getting 100% stock on the htc one m7. So far I have managed to unlock the bootloader and its showing S-ON and RELOCKED just under TAMPERED. Now I trying to RUU.img by using this command fastboot flash zip ruu.zip while in fastboot but the following error comes up: could not allocate 1688576026 bytes, error: cannot load 'ruu.zip'. Why is this error coming up? I am pretty sure I have the right RUU for my phone as it was suggested to me by someone on xda here.
Am i low on internal storage is that the reason why RUU is not going through? What is the possible fix. I am stuck on the black and white logo HTC screen with no OS installed or recovery. I think I might have a recovery saved in the internal storage but I cannot enter recovery mode either.
Any replies would be appreciated.
Click to expand...
Click to collapse
Please post output of fastboot getvar all, so someone can suggest a solution.
mb_guy said:
Please post output of fastboot getvar all, so someone can suggest a solution.
Click to expand...
Click to collapse
The following is the output of fastboot getvar all.
(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.22
(bootloader) version-misc: PVT SHIP S-ON
(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: 3943mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
singh_harman said:
The following is the output of fastboot getvar all.
(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.22
(bootloader) version-misc: PVT SHIP S-ON
(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: 3943mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
Click to expand...
Click to collapse
Are you using htc-fastboot when flashing, link is in flash instructions here http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
mb_guy said:
Are you using htc-fastboot when flashing, link is in flash instructions here http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
Yes I just downloaded the htc fastboot and its sort of working now but not completely. I realized I was using the normal fastboot.exe before.
However. The flash of ruu.zip goes fine until to the point it says "Please flush again immediately", for "hboot-preupdate" response, restart the same procedure for device number ..............
sending 'zip'.... (50280 KB) stuck here forever.
What is going wrong? How to fix from here on.
fastboot flash zip ruu.zip
sending 'zip'... (50280 KB) OKAY
sending time = 3.165 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 ...
sending 'zip'... (50280 KB)
singh_harman said:
fastboot flash zip ruu.zip
sending 'zip'... (50280 KB) OKAY
sending time = 3.165 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 ...
sending 'zip'... (50280 KB)
Click to expand...
Click to collapse
I would just try agin. If still failing try another cable or usb port. Also be sure you have the latest adb drivers.
Thanks, I managed to get it working. I tried a few times one after the other and in the end it was done.
I have used the Guru reset from HTC 1 Guru to reset my HTC One M7 on Three (Hutchinson 3G) UK with version 7.19.771.1.
Like some others I have had the problem of a boot loop when getting the Android 4.3 OTA after 2 minor updates which worked fine.
I have learned that this happened because my firmware is higher than the firmware of the OTA.
I was able to get out of the boot loop fine by flashing TWRP recovery and restoring to my TWRP backup of CyanogenMod, but I still want to go back to stock Sense.
I can't S-OFF as Sunshine is the only tool for HBOOT 1.61 and that won't work on CyanogenMod as it says that I need to be using stock. Also, I don't have the money to pay for it anyway.
So I'm wondering if anyone knows how I can get to stock Sense with all updates applied.
I was wondering if I could do a Guru reset again without performing updates, and then use a RUU of a more recent version to get to updated stock. I thought this may work because the version of the RUU would be higher than that of the current software.
Or would I get something from the HTC Dev Center downloads? Etc
Or is there another way?
Thanks for reading!
(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.771.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3786mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Zannxdaaccount said:
I have used the Guru reset from HTC 1 Guru to reset my HTC One M7 on Three (Hutchinson 3G) UK with version 7.19.771.1.
Like some others I have had the problem of a boot loop when getting the Android 4.3 OTA after 2 minor updates which worked fine.
I have learned that this happened because my firmware is higher than the firmware of the OTA.
I was able to get out of the boot loop fine by flashing TWRP recovery and restoring to my TWRP backup of CyanogenMod, but I still want to go back to stock Sense.
I can't S-OFF as Sunshine is the only tool for HBOOT 1.61 and that won't work on CyanogenMod as it says that I need to be using stock. Also, I don't have the money to pay for it anyway.
So I'm wondering if anyone knows how I can get to stock Sense with all updates applied.
I was wondering if I could do a Guru reset again without performing updates, and then use a RUU of a more recent version to get to updated stock. I thought this may work because the version of the RUU would be higher than that of the current software.
Or would I get something from the HTC Dev Center downloads? Etc
Or is there another way?
Thanks for reading!
(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.771.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3786mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95916177934542817
Here's a RUU for you. It should work just fine
Poslano sa mog HTC One koristeći Tapatalk
donkeykong1 said:
Here's a RUU for you. It should work just fine
Click to expand...
Click to collapse
Thank you - so I flash this using TWRP then flash stock recovery using fastboot?
Zannxdaaccount said:
Thank you - so I flash this using TWRP then flash stock recovery using fastboot?
Click to expand...
Click to collapse
You flash it via fastboot in RUU mode. First command you need is "fasboot oem rebootRUU" That will boot your phone in bootloader mode ( black screen with silver HTC logo ). Then "fastboot flash zip (name of the zip).zip. You might want to rename that zip to something simple like "firmware" to avoid mistakes when writing in fastboot. And one mote note - you need htc fasboot to flash this, not the regular fastboot
Poslano sa mog HTC One koristeći Tapatalk
donkeykong1 said:
You flash it via fastboot in RUU mode. First command you need is "fasboot oem rebootRUU" That will boot your phone in bootloader mode ( black screen with silver HTC logo ). Then "fastboot flash zip (name of the zip).zip. You might want to rename that zip to something simple like "firmware" to avoid mistakes when writing in fastboot. And one mote note - you need htc fasboot to flash this, not the regular fastboot
Poslano sa mog HTC One koristeći Tapatalk
Click to expand...
Click to collapse
What is HTC fastboot and how do I get that?
https://www.androidfilehost.com/?w=...f812d4f8d7d551183257032e28f6937dd8bb61c6af2ca
donkeykong1 said:
https://www.androidfilehost.com/?w=...f812d4f8d7d551183257032e28f6937dd8bb61c6af2ca
Click to expand...
Click to collapse
C:\Users\\Desktop\AndroidSDKSlim\android-sdk-windows\platform-tools>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
Zannxdaaccount said:
C:\Users\\Desktop\AndroidSDKSlim\android-sdk-windows\platform-tools>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
Put the fastboot.exe file in your regular fastboot folder. That should fix it. I forgot to write that, sorry
donkeykong1 said:
Put the fastboot.exe file in your regular fastboot folder. That should fix it. I forgot to write that, sorry
Click to expand...
Click to collapse
I had already done that. So there is the normal fastboot.exe that was already in there, and the htcfastboot.exe.
Zannxdaaccount said:
I had already done that. So there is the normal fastboot.exe that was already in there, and the htcfastboot.exe.
Click to expand...
Click to collapse
Try with "htc_fastboot flash zip..."
donkeykong1 said:
Try with "htc_fastboot flash zip..."
Click to expand...
Click to collapse
Alright, now on the command prompt it's saying flash zip complete but on my phone I've got the HTC silver logo with the green progress bar at about 80%, not moving by the looks of it?
Zannxdaaccount said:
Alright, now on the command prompt it's saying flash zip complete but on my phone I've got the HTC silver logo with the green progress bar at about 80%, not moving by the looks of it?
Click to expand...
Click to collapse
That's the way it should be. Now "htc_fastboot reboot" and wait till it finishes upgrading apps. Then set up, and enjoy
donkeykong1 said:
That's the way it should be. Now "htc_fastboot reboot" and wait till it finishes upgrading apps. Then set up, and enjoy
Click to expand...
Click to collapse
It's setting up apps now. Thank you very much!!
Zannxdaaccount said:
It's setting up apps now. Thank you very much!!
Click to expand...
Click to collapse
No problem mate. Glad I could help
Hi,
I have exactly the same issue, needing the same RUU. But the one linked to on android forums is corrupt. fastboot says it can't find the image title and if I open it in in WinRAR it fails the integrity test. I downloaded it three times and FC'd them. They are identicle but all corrupt. Is there another version out there or can you share one you've used? Thanks.
gunholio77 said:
Hi,
I have exactly the same issue, needing the same RUU. But the one linked to on android forums is corrupt. fastboot says it can't find the image title and if I open it in in WinRAR it fails the integrity test. I downloaded it three times and FC'd them. They are identicle but all corrupt. Is there another version out there or can you share one you've used? Thanks.
Click to expand...
Click to collapse
Don't try to extract a RUU zip, it will get corrupted because it's encrypted. Just download the zip, put it in your fastboot folder, and flash via fastboot with your phone in RUU mode
donkeykong1 said:
Don't try to extract a RUU zip, it will get corrupted because it's encrypted. Just download the zip, put it in your fastboot folder, and flash via fastboot with your phone in RUU mode
Click to expand...
Click to collapse
When I try to fastboot it I get an error
h ttp://imgur . com/a/cm8YL
I can't post images until I've posted more posts...
---------- Post added at 07:17 PM ---------- Previous post was at 06:58 PM ----------
I've tried that many things I forgot what I was meaning to show you. This is the error I get
C:\adbLink>htc_fastboot.exe flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420805_signed_.zip
sending 'zip'... (43287 KB) OKAY
sending time = 3.203 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)
My info is
C:\adbLink>htcfastboot2.exe getvar all
(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.771.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 69(ms)
C:\adbLink>htc_fastboot.exe flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.1_Rad io_4T.35.3218.16_10.33Q.1718.01L_release_420805_si gned_.zip
sending 'zip'... (43287 KB) OKAY
sending time = 3.203 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)
Click to expand...
Click to collapse
gunholio77 said:
My info is
C:\adbLink>htcfastboot2.exe getvar all
(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.771.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 69(ms)
Click to expand...
Click to collapse
Your version-main is 7.19.771.21 so you need a RUU same or newer than that number. 7.19.771.1 will not work (its older). Unless you want to edit your version-main number from the /misc partition, the simplest is to flash the 7.19.771.21 RUU.
You can download it from here: https://www.androidfilehost.com/?fid=24052804347763965
There are some problems today on androidfilehost.com so if you have some issues downloading the file, try later :good:
I get the same failed message with that ruu - I've put cyangenmod back on for now, so I have a working phone. But I will return to this an get it working
Really appreciate your help with this - Thanks
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.