FORUMS
Remove All Ads from XDA

[M8QL_UL] Custom Recovery / RUU / Root - HTC One M8S

98 posts
Thanks Meter: 103
 
By El-Conkistador, Member on 21st May 2015, 02:43 PM
Post Reply Email Thread
Quote:

I've changed my device (M8S) for the HTC 10. My old device is own by my girlfriend.

Hi all,

HTC has released a new smartphone for the western region of europe, the HTC One M8S ( m8qlul ) . There is at present no section for this product on XDA . I gather the most information possible right here.

I want to thank CaptainThrowback for his work on the Custom Recovery.

PS : Sorry for my broken English

----------------------------------------------------------------------------------------
#########################################
## NEW RUU AVAILABLE
#########################################

A new RUU are available on the repair site. (Vendor Firmware). If you have an access or files, please upload for add this on my repository. Thanks
> The most important Firmware/RUU to take are in bold..
Quote:

  • 0PKVIMG_M8_QL_UL_L50_SENSE60_H3G_UK_1.07.771.1_Rad [email protected]_15.00_016_F_release_427719_s igned.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_H3G_UK_1.07.771.1_Rad [email protected]_15.00_016_F_release_427719_s igned_Hboot.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_H3G_UK_1.12.771.6_Rad [email protected]_15.00_016_F_release_431742_s igned.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_H3G_UK_1.12.771.10_Ra [email protected]_15.00_016_F_release_450151_ combined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.11.401.2 [email protected]_15.00_016_F_release_4342 97_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.11.401.2 [email protected]_15.00_016_F_release_4383 17_combined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.11.401.2 [email protected]_15.00_016_F_release_4384 71_combined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.11.401.2 [email protected]_15.00_016_F_release_4386 12_combined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_MFG_0.82.997.201_Radi [email protected]_07.00_015_F_test_420314.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_O2_UK_1.07.206.1_Radi [email protected]_15.00_016_F_release_427730_si gned_Hboot.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_O2_UK_1.07.206.1_Radi [email protected]_15.00_016_F_release_428544_co mbined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_O2_UK_1.11.206.10_Rad [email protected]_15.00_016_F_release_449761_c ombined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_Orange_UK_1.11.61.10_ [email protected]_15.00_016_F_release_44994 8_combined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_TMO_AT_1.10.112.11_Ra [email protected]_15.00_016_F_release_451151_ combined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_TMO_DE_1.10.111.1_R_R [email protected]_15.00_016_F_release_429391 _signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_TMO_DE_1.13.111.11_Ra [email protected]_15.00_016_F_release_451505_ combined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_TMO_NL_1.10.114.11_Ra [email protected]_15.00_016_F_release_451153_ combined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_TMO_PL_1.10.118.11_Ra [email protected]_15.00_016_F_release_451152_ combined_signed.zip
  • 0PKVIMG_M[email protected]50311_15.00 _016_F_release_427839_signed.zip
  • 0PKVIMG_M8[email protected]50311_15.00_016_F _release_427667_combined_signed.zip
  • 0PKVIMG_M8_[email protected]50408_15.00_016_ F_release_450238_combined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_Vodafone_UK_1.05.161. [email protected]_15.00_016_F_release_426 598_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_Vodafone_UK_1.05.161. [email protected]_15.00_016_F_release_426 930_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_Vodafone_UK_1.05.161. [email protected]_15.00_016_F_release_427 668_combined_signed.zip
  • 0PKVIMG_M8_QL_UL_L50_SENSE60_Vodafone_UK_1.11.161. [email protected]_15.00_016_F_release_45 0235_combined_signed.zip



If you want participate, press the button : "Click to show content" below. Your phone will reward you and also community !
----------------------------------------------------------------------------------------
#########################################
## RUU/OTA HTC One M8S (M8QL_UL)
#########################################

Warning, you must use the same version of RUU to your system. If version of error the RUU will not install.
- For those who have problems with their phones. Feel free to share your experience

Link for download with my plateform :(Many RUU) http://ruu.lalleman.net/ | If you want make donate / Participate in the acquisition of firmware [Donate-me]
Extract the achive and execute ARUWizard . Attention must be relocker your bootloader before installing this RUU

Quote:

I do not claim* but a small donation to those who can help me to repay the purchase of access to the platform firmware (ir-file.com : If you want to see the average rate).

For informations about this plateform :

  • 12 Month subscription ,150 Gig $60.00 for one year
  • 6 month Subscription,90 Giga $35.00 for 6 months
  • 3 month- 60Gig $25.00 for 3 months
  • Montly subscription-30Giga $15.00 for 30 days
Thank you to donors. As promised and as repeated , repayment of financing is closed. Finally access to firmware was funded collaborative way for all ! And that's what I wanted above all. As promised here all available firmwares . I'll make mirrors you can do same . The files now belong to the community !

Quote:


Special Thanks :
- @tzutzu78 : (09/06/2015) 5$
- @Jackropon : (18/06/2015) 5$
- @gogol-fr : (18/06/2015) 10$
- @Andreas.G : (07/12/2015) 3$
- @mastro7712 : (03/11/2016) 3$
Are you next?

#########################################
----------------------------------------------------------------------------------------
#########################################
## HOW TO USE CUSTOM RECOVERY
#########################################


Files Needed :
- TWRP 2.8.6.0 : http://ruu.lalleman.net/HTC_M8S%28QL....6.0-m8s-qlul/
- The HTC_Fastboot : http://ruu.lalleman.net/HTC_M8S%28QL...ools/Fastboot/
- Stock Extracted Recovery : http://ruu.lalleman.net/HTC_M8S%28QL...TC%20Recovery/ **

** If you have an error for applying a OTA with this stock recovery. Apply an old stock recovery (from the first OTA if your phone is in 1.11.401.1-1 version).
Instruction :
0. Copy the custom recovery or stock recovery into your internal storage.
New method :
1. Use the HTC_Fastboot linked above and flash the recovery :
Code:
htc_fastboot flash recovery {Your_Recovery}
Obselete:
1. On bootloader boot into TWRP custom Recovery :
Code:
fastboot boot twrp-recovery-2.8.6.0-m8s-qlul.img
2. When you're boot into TWRP Custom Recovery make a Full Backup (Optional | But Safe)

3. In Custom Recovery we're able to use ADB command. To flash the Recovery you want use this command :
Code:
adb shell
dd if=/sdcard/{Your_Recovery}.img of=/dev/block/mmcblk0p44
exit
adb reboot-bootloader
4. In bootloader select "Recovery" menu. Your M8S boot into the Recovery (Custom or Stock).


#########################################
----------------------------------------------------------------------------------------
#########################################
## FOR DEVELOPPERS - TWRP
#########################################

If you want to improve recovery :
- Github Device : https://github.com/CaptainThrowback/...evice_htc_m8ql (Thanks to CaptainThrowback)
For rooting device :
This only works if you flashed a custom recovery . Not in boot only.
Problem: When the phone is rooted in changes to the phone are reset on restart .. Strange.

Busybox device :
The phone reboots when installing Busybox through the application. It must be installed through the recovery.

#########################################
----------------------------------------------------------------------------------------
EDIT :
/proc/emmc :
Code:
dev:        size     erasesize name
mmcblk0p1: 00004000  00000200  "board_info"
mmcblk0p2: 00400000  00000200  "pg1fs"
mmcblk0p3: 00100000  00000200  "sbl1"
mmcblk0p4: 00af7c00  00000200  "reserve_1"
mmcblk0p5: 00040000  00000200  "mfg"
mmcblk0p6: 017afc00  00000200  "pg2fs"
mmcblk0p7: 00080000  00000200  "rpm"
mmcblk0p8: 00200000  00000200  "tz"
mmcblk0p9: 00200000  00000200  "hyp"
mmcblk0p10: 00400000  00000200  "hboot"
mmcblk0p11: 00400000  00000200  "tool_diag"
mmcblk0p12: 00500000  00000200  "sp1"
mmcblk0p13: 00008000  00000200  "ddr"
mmcblk0p14: 00500000  00000200  "wcnss"
mmcblk0p15: 00100000  00000200  "rfg_0"
mmcblk0p16: 00100000  00000200  "rfg_1"
mmcblk0p17: 00100000  00000200  "rfg_2"
mmcblk0p18: 00100000  00000200  "rfg_3"
mmcblk0p19: 00100000  00000200  "rfg_4"
mmcblk0p20: 00100000  00000200  "rfg_5"
mmcblk0p21: 00100000  00000200  "rfg_6"
mmcblk0p22: 00100000  00000200  "rfg_7"
mmcblk0p23: 00180000  00000200  "fsg"
mmcblk0p24: 03b00400  00000200  "radio"
mmcblk0p25: 00d08000  00000200  "reserve_2"
mmcblk0p26: 00100000  00000200  "misc"
mmcblk0p27: 00180000  00000200  "modem_st1"
mmcblk0p28: 00180000  00000200  "modem_st2"
mmcblk0p29: 01400000  00000200  "fataldevlog"
mmcblk0p30: 01e00000  00000200  "devlog"
mmcblk0p31: 00040000  00000200  "pdata"
mmcblk0p32: 00004000  00000200  "control"
mmcblk0p33: 00140400  00000200  "local"
mmcblk0p34: 00010000  00000200  "extra"
mmcblk0p35: 00100000  00000200  "cdma_record"
mmcblk0p36: 00000400  00000200  "fsc"
mmcblk0p37: 00002000  00000200  "ssd"
mmcblk0p38: 00080000  00000200  "sensor_hub"
mmcblk0p39: 00500000  00000200  "backup_hboot"
mmcblk0p40: 0007d000  00000200  "frp"
mmcblk0p41: 0016c800  00000200  "reserve"
mmcblk0p42: 10000000  00000200  "cache"
mmcblk0p43: 02000000  00000200  "boot"
mmcblk0p44: 02000000  00000200  "recovery"
mmcblk0p45: 00000000  00000200  "system"
mmcblk0p46: 01900000  00000200  "carrier"
mmcblk0p47: 00a00000  00000200  "battery"
mmcblk0p48: 13100000  00000200  "apppreload"
mmcblk0p49: 03c00000  00000200  "cota"
mmcblk0p50: 68000000  00000200  "userdata"
mmcblk0p51: 01000000  00000200  "absolute"
/proc/mounts
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/memcg cgroup rw,relatime,memory 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/cota /cota ext4 rw,seclabel,nosuid,nodev,noatime,grpid,data=ordered 0 0
/dev/block/bootdevice/by-name/apppreload /preload ext4 rw,seclabel,nosuid,nodev,noatime,grpid,data=ordered 0 0
/dev/block/bootdevice/by-name/devlog /devlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/fataldevlog /fataldevlog ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/carrier /carrier ext4 rw,seclabel,nosuid,nodev,noatime,grpid,data=ordered 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/radio /firmware/radio vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/wcnss /firmware/wcnss vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:65 /mnt/media_rw/ext_sd texfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,umask=0007,allow_utime=0020,codepage=437,iocharset=utf8,min_prealloc_size=64k,max_prealloc_size=60885k,readahead=4M,fail_safe,discard,hidden=show,errors=continue 0 0
/dev/block/vold/179:65 /mnt/secure/asec texfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,umask=0007,allow_utime=0020,codepage=437,iocharset=utf8,min_prealloc_size=64k,max_prealloc_size=60885k,readahead=4M,fail_safe,discard,hidden=show,errors=continue 0 0
/dev/fuse /storage/ext_sd fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/proc/partitions
Code:
major minor  #blocks  name

 179        0   15267840 mmcblk0
 179        1         16 mmcblk0p1
 179        2       4096 mmcblk0p2
 179        3       1024 mmcblk0p3
 179        4      11231 mmcblk0p4
 179        5        256 mmcblk0p5
 179        6      24255 mmcblk0p6
 179        7        512 mmcblk0p7
 179        8       2048 mmcblk0p8
 179        9       2048 mmcblk0p9
 179       10       4096 mmcblk0p10
 179       11       4096 mmcblk0p11
 179       12       5120 mmcblk0p12
 179       13         32 mmcblk0p13
 179       14       5120 mmcblk0p14
 179       15       1024 mmcblk0p15
 179       16       1024 mmcblk0p16
 179       17       1024 mmcblk0p17
 179       18       1024 mmcblk0p18
 179       19       1024 mmcblk0p19
 179       20       1024 mmcblk0p20
 179       21       1024 mmcblk0p21
 179       22       1024 mmcblk0p22
 179       23       1536 mmcblk0p23
 179       24      60417 mmcblk0p24
 179       25      13344 mmcblk0p25
 179       26       1024 mmcblk0p26
 179       27       1536 mmcblk0p27
 179       28       1536 mmcblk0p28
 179       29      20480 mmcblk0p29
 179       30      30720 mmcblk0p30
 179       31        256 mmcblk0p31
 259        0         16 mmcblk0p32
 259        1       1281 mmcblk0p33
 259        2         64 mmcblk0p34
 259        3       1024 mmcblk0p35
 259        4          1 mmcblk0p36
 259        5          8 mmcblk0p37
 259        6        512 mmcblk0p38
 259        7       5120 mmcblk0p39
 259        8        500 mmcblk0p40
 259        9       1458 mmcblk0p41
 259       10     262144 mmcblk0p42
 259       11      32768 mmcblk0p43
 259       12      32768 mmcblk0p44
 259       13    4194304 mmcblk0p45
 259       14      25600 mmcblk0p46
 259       15      10240 mmcblk0p47
 259       16     312320 mmcblk0p48
 259       17      61440 mmcblk0p49
 259       18   10092544 mmcblk0p50
 259       19      16384 mmcblk0p51
 179       32       4096 mmcblk0rpmb
 253        0     104860 zram0
 253        1     104860 zram1
 253        2     104860 zram2
 253        3     104860 zram3
 179       64   62367744 mmcblk1
 179       65   62351360 mmcblk1p1
/cat/cpuinfo
Code:
Processor       : AArch64 Processor rev 1 (aarch64)
processor       : 0
processor       : 1
processor       : 2
processor       : 3
processor       : 4
processor       : 5
processor       : 6
processor       : 7
Features        : fp asimd aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 1

Hardware        : Qualcomm Technologies, Inc MSM8939


Sincerely,
El-Conkistador
The Following 45 Users Say Thank You to El-Conkistador For This Useful Post: [ View ] Gift El-Conkistador Ad-Free
 
 
22nd May 2015, 11:18 AM |#2  
Idlekilla's Avatar
Senior Member
Thanks Meter: 59
 
More
I would really like a recovery for the M8S as well. Been scratching my head over the last few days why none of the recoveries works, until I noticed I have the M8S.
22nd May 2015, 12:28 PM |#3  
El-Conkistador's Avatar
OP Member
Flag Lille
Thanks Meter: 103
 
Donate to Me
More
Quote:
Originally Posted by Idlekilla

I would really like a recovery for the M8S as well. Been scratching my head over the last few days why none of the recoveries works, until I noticed I have the M8S.

Yes M8S is not at all compatible with the recovery of traditional M8 . That is why we must compile a Recovery. For my part , I always encounter compilation errors , it's annoying .
The Following User Says Thank You to El-Conkistador For This Useful Post: [ View ] Gift El-Conkistador Ad-Free
22nd May 2015, 01:44 PM |#4  
Idlekilla's Avatar
Senior Member
Thanks Meter: 59
 
More
Quote:
Originally Posted by El-Conkistador

Yes M8S is not at all compatible with the recovery of traditional M8 . That is why we must compile a Recovery. For my part , I always encounter compilation errors , it's annoying .

I did flash several recoveries after unlocking bootloader (which worked like a charm btw), but now I can't even factory reset.
22nd May 2015, 02:09 PM |#5  
Junior Member
Thanks Meter: 0
 
More
having got my m8s delivered yesterday the first thing i did was unlock the bootloader then try and flash a custom recovery, i have tried so many different ones. The 2 main errors i get are "FAILED remote:32 header error and remote: image error! (bootmagic check fail) i have the original recovery which also says the same but i now have no recovery at all.

The closest i have managed to get is using something called open recovery which atleast part loads

---------- Post added at 01:09 PM ---------- Previous post was at 01:06 PM ----------

Quote:
Originally Posted by Idlekilla

I did flash several recoveries after unlocking bootloader (which worked like a charm btw), but now I can't even factory reset.

have contacted HTC and they say everything should work fine they have no idea why i can't flash the official recovery i told them it didn't seem to have one at all when i got it......
22nd May 2015, 09:36 PM |#6  
Junior Member
Thanks Meter: 2
 
More
I would love to see a recovery too! I'll donate to first working recovery
The Following 2 Users Say Thank You to jordy2811 For This Useful Post: [ View ] Gift jordy2811 Ad-Free
24th May 2015, 12:08 AM |#7  
Idlekilla's Avatar
Senior Member
Thanks Meter: 59
 
More
I would also donate for a recovery for the M8s.

Sent from my HTC One M8s using XDA Free mobile app
The Following User Says Thank You to Idlekilla For This Useful Post: [ View ] Gift Idlekilla Ad-Free
24th May 2015, 12:35 AM |#8  
xunholyx's Avatar
Recognized Contributor
Flag Vancouver
Thanks Meter: 4,798
 
Donate to Me
More
Quote:
Originally Posted by thorgose

having got my m8s delivered yesterday the first thing i did was unlock the bootloader then try and flash a custom recovery, i have tried so many different ones. The 2 main errors i get are "FAILED remote:32 header error and remote: image error! (bootmagic check fail) i have the original recovery which also says the same but i now have no recovery at all.

The closest i have managed to get is using something called open recovery which atleast part loads

---------- Post added at 01:09 PM ---------- Previous post was at 01:06 PM ----------



have contacted HTC and they say everything should work fine they have no idea why i can't flash the official recovery i told them it didn't seem to have one at all when i got it......

It had a recovery when you bought it, they all do. You probably still have one, but you could flash the stock recovery manually to be sure.
In the first post is a link to the recovery.img. Place it into your fastboot folder, hook up to your PC, fastboot flash recovery recovery.img
The Following User Says Thank You to xunholyx For This Useful Post: [ View ] Gift xunholyx Ad-Free
24th May 2015, 01:00 AM |#9  
Idlekilla's Avatar
Senior Member
Thanks Meter: 59
 
More
Quote:
Originally Posted by xunholyx

It had a recovery when you bought it, they all do. You probably still have one, but you could flash the stock recovery manually to be sure.
In the first post is a link to the recovery.img. Place it into your fastboot folder, hook up to your PC, fastboot flash recovery recovery.img

I tried, but got this:

fastboot flash recovery recovery.img
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 9531648 is not a multiple of the
block size 4096
sending sparse 'recovery' (15836 KB)...
error: write_sparse_skip_chunk: don't care size 9531648 is not a multiple of the
block size 4096
error: write_sparse_skip_chunk: don't care size 9531648 is not a multiple of the
block size 4096
OKAY [ 1.829s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.863s
24th May 2015, 01:08 AM |#10  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by xunholyx

It had a recovery when you bought it, they all do. You probably still have one, but you could flash the stock recovery manually to be sure.
In the first post is a link to the recovery.img. Place it into your fastboot folder, hook up to your PC, fastboot flash recovery recovery.img

I told HTC that in the hope they could point me in the direction of an official recovery (i originally thought i had bricked the phone and was hoping to fool them hahaha) , unfortunately you can't seem to flash the official one either as i havbe extracted it from the OTA; i think there could well be some form of bug in the base software as it keeps telling me

"target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 9531648 is not a multiple of the block size 4096
sending sparse 'recovery' (15836 KB)...
error: write_sparse_skip_chunk: don't care size 9531648 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 9531648 is not a multiple of the block size 4096
OKAY [ 1.604s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.607s

this goes for the newest version of twrp which also gives this

target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 669696 is not a multiple of the block size 4096
sending sparse 'recovery' (16380 KB)...
error: write_sparse_skip_chunk: don't care size 669696 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 669696 is not a multiple of the block size 4096
OKAY [ 1.577s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.578s

now what i can flash is a cwm recovery but all it seems to do is try to run but then cuts straight back to fastboot, i see the purple writing at the top "entering recovery mode" then not even a second goes by and it's straight back out again

I have tried flashing an unofficial M9 recovery and that never worked either it just froze up my phone.

According to the guy at HTC he has no idea why we can't flash any recovery at all as far as he is concerned it should work just as the M8 has !

i have tried installing the update zip after restarting the ruu to no avail and have even downloaded the official from htc dev but can't seem to understand what to do with that zip (i thought it was an official ruu but not too sure)

If anyone can point me in the direction of an ruu i would be incredibly grateful
24th May 2015, 03:11 AM |#11  
xunholyx's Avatar
Recognized Contributor
Flag Vancouver
Thanks Meter: 4,798
 
Donate to Me
More
Quote:
Originally Posted by thorgose

I told HTC that in the hope they could point me in the direction of an official recovery (i originally thought i had bricked the phone and was hoping to fool them hahaha) , unfortunately you can't seem to flash the official one either as i havbe extracted it from the OTA; i think there could well be some form of bug in the base software as it keeps telling me

"target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 9531648 is not a multiple of the block size 4096
sending sparse 'recovery' (15836 KB)...
error: write_sparse_skip_chunk: don't care size 9531648 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 9531648 is not a multiple of the block size 4096
OKAY [ 1.604s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.607s

this goes for the newest version of twrp which also gives this

target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 669696 is not a multiple of the block size 4096
sending sparse 'recovery' (16380 KB)...
error: write_sparse_skip_chunk: don't care size 669696 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 669696 is not a multiple of the block size 4096
OKAY [ 1.577s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.578s

now what i can flash is a cwm recovery but all it seems to do is try to run but then cuts straight back to fastboot, i see the purple writing at the top "entering recovery mode" then not even a second goes by and it's straight back out again

I have tried flashing an unofficial M9 recovery and that never worked either it just froze up my phone.

According to the guy at HTC he has no idea why we can't flash any recovery at all as far as he is concerned it should work just as the M8 has !

i have tried installing the update zip after restarting the ruu to no avail and have even downloaded the official from htc dev but can't seem to understand what to do with that zip (i thought it was an official ruu but not too sure)

If anyone can point me in the direction of an ruu i would be incredibly grateful

It's not an RUU, it's kernel source more than likely. RUU is about 1.5gb, kernel source is around 500mb

@LlabTooFeR offers an online RUU flashing service for devices that don't have RUUs out, such as the M8s. but it costs $20.

And yes, it is very strange that the M8s cannot fastboot flash recovery with an unlocked bootloader. Never knew that till now.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes