[Q] HTC One (M7) can't flash recovery | "target reported max download size.."

Search This thread
Jun 10, 2014
10
0
Melbourne
[Q] HTC One (M7) can't flash recovery | "target reported max download size.."

Hey guys,

I'm not sure if I have soft bricked it or not, but I can't flash a recovery .img or a .zip file onto the device. I am trying to return to stock, I have a stock ROM that I downloaded from HTC1Guru.

I have tried fastboot method (with and without erasing cache) to no success, adb doesn't recognise it, even tried to rename the recovery image to recovery.img, doesn't work

fastboot getvar all:

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3853mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0


The bootloader information is this;

*** TAMPERED ***
*** UNLOCKED ***

M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB

This is the response I get with fastboot methods;

target reported max download size of 1496092672 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.287s]
writing 'recovery'...
OKAY [ 0.726s]
finished. total time: 2.016s

Help! How can I fix this issue and get it back to stock? Thanks in advance for the help.
 
Last edited:

bored_stupid

Senior Member
Jul 10, 2011
669
188
Hereford
Hey guys,

I'm not sure if I have soft bricked it or not, but I can't flash a recovery .img or a .zip file onto the device. I am trying to return to stock, I have a stock ROM that I downloaded from HTC1Guru.

I have tried fastboot method (with and without erasing cache) to no success, adb doesn't recognise it, even tried to rename the recovery image to recovery.img, doesn't work

The bootloader information is this;

*** TAMPERED ***
*** UNLOCKED ***

M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB

This is the response I get with fastboot methods;

target reported max download size of 1496092672 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.287s]
writing 'recovery'...
OKAY [ 0.726s]
finished. total time: 2.016s

Help! How can I fix this issue and get it back to stock? Thanks in advance for the help.

Post a fastboot getvar all, ( minus imei & serial no) + links to recovery

Sent from my HTC One using Xparent Skyblue Tapatalk 2
 
Jun 10, 2014
10
0
Melbourne
Post a fastboot getvar all, ( minus imei & serial no) + links to recovery

Sent from my HTC One using Xparent Skyblue Tapatalk 2

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3853mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Guru Stock Reset: htc1guru.com/dld/guru_reset_m7_2-24-841-1-zip
 

bored_stupid

Senior Member
Jul 10, 2011
669
188
Hereford
Download this one openrecovery-twrp-2.6.3.3-m7.img

http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img

Put the recovery in your adb/fastboot folder and connect your phone to the PC
Reboot to bootloader, the press shift/right mouse button and open command window here.

type fastboot devices
if a serial no is displayed type

fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img

fastboot erase cache

fastboot reboot-bootloader

enter recovery
 
Jun 10, 2014
10
0
Melbourne
235

Download this one openrecovery-twrp-2.6.3.3-m7.img

http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img

Put the recovery in your adb/fastboot folder and connect your phone to the PC
Reboot to bootloader, the press shift/right mouse button and open command window here.

type fastboot devices
if a serial no is displayed type

fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img

fastboot erase cache

fastboot reboot-bootloader

enter recovery

I have tried that recovery verison as well, since I know it works on the device. I get the same results
 

SaHiLzZ

Senior Member
Jan 19, 2011
2,000
516
This is the response I get with fastboot methods;

target reported max download size of 1496092672 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.287s]
writing 'recovery'...
OKAY [ 0.726s]
finished. total time: 2.016s


Help! How can I fix this issue and get it back to stock? Thanks in advance for the help.

I dont see a problem here... What is the problem ?
 

SaHiLzZ

Senior Member
Jan 19, 2011
2,000
516
I have tried that yes, same issue...

Next step will be to post the output of your fastboot getvar all (remove IMEI) and get a stock recovery and flash, and then try to get in the recovery.

If still not working, then get the firmware.zip matching your device's current main version, and flash it in RUU mode with a locked bootloader
 
Jun 10, 2014
10
0
Melbourne
Next step will be to post the output of your fastboot getvar all (remove IMEI) and get a stock recovery and flash, and then try to get in the recovery.

If still not working, then get the firmware.zip matching your device's current main version, and flash it in RUU mode with a locked bootloader

I have posted a getvar

I have also tried to flash an RUU with limited success, it failed due to s-on, I have tried to get s-off, but ADB is not seeing the device.