Database Develop

[Q] Can't Access Storage - Partition & Format?

I used the Vivid Toolkit for Noobs and unlocked the bootloader, flashed the recovery to CWM, flashed the kernel using the .IMG kernel file in Virtuous Inquisition v4.0.2.1, rooted, copied Virtuous Inquisition over to the phone, went to recovery, and...
wipe data/factory reset
wipe cache partition
install zip from sdcard
Virtuous Inquisition installed and I am using it now. However, if I go to SETTINGS > STORAGE something happens to where the phone goes back to the Home Screen and displays...
"Unfortunately, Settings has stopped."
I can press OK to close that message, but something isn't right.
If I enable USB Storage and look on my computer, I only have 8.82 GBs of storage? I realize some is locked by Android, but I would think I would be allowed more than 8.82 GBs.
I would like to repartition then reformat the phone and reinstall Virtuous Inquisition v4.0.2.1. What is the best and easiest way for a noob to do this?

Yeah something isn't right...
d:\Root\Data>adb shell
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Can't have overlapping partitions.
(parted)

(parted) quit
quit
quit
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 17 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 17 49 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 49 4094 32367 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 4094 1923584 15355920 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 4095 4096 16 5a Unknown
/dev/block/mmcblk0p6 4097 4129 256 73 Unknown
/dev/block/mmcblk0p7 4129 6684 20442+ 5b Unknown
/dev/block/mmcblk0p8 6684 6716 256 5c Unknown
/dev/block/mmcblk0p9 6716 6844 1024 45 Unknown
/dev/block/mmcblk0p10 6844 6876 256 47 Unknown
/dev/block/mmcblk0p11 6876 7132 2048 46 Unknown
/dev/block/mmcblk0p12 7132 7260 1024 4c Unknown
/dev/block/mmcblk0p13 7260 7264 32 39 Unknown
/dev/block/mmcblk0p14 7264 8032 6144 34 Unknown
/dev/block/mmcblk0p15 8032 8160 1024 36 Unknown
/dev/block/mmcblk0p16 8161 8192 256 76 Unknown
/dev/block/mmcblk0p17 8193 13313 40960 77 Unknown
/dev/block/mmcblk0p18 13313 18433 40960 77 Unknown
/dev/block/mmcblk0p19 18433 19457 8191 74 Unknown
/dev/block/mmcblk0p20 19457 20480 8190+ 74 Unknown
/dev/block/mmcblk0p21 20481 24576 32768 7a Unknown
/dev/block/mmcblk0p22 24577 26625 16384 48 Unknown
/dev/block/mmcblk0p23 26625 28672 16383 71 Unknown
/dev/block/mmcblk0p24 28673 30720 16381+ 76 Unknown
/dev/block/mmcblk0p25 30720 31232 4096 4a Unknown
/dev/block/mmcblk0p26 31232 31744 4096 4b Unknown
/dev/block/mmcblk0p27 31744 32256 4096 59 Unknown
/dev/block/mmcblk0p28 32257 32768 4096 5a Unknown
/dev/block/mmcblk0p29 32769 163840 1048575+ 83 Linux
/dev/block/mmcblk0p30 163841 167902 32489+ 19 Unknown
/dev/block/mmcblk0p31 167902 167902 4 88 Unknown
/dev/block/mmcblk0p32 167902 167934 256 23 Unknown
/dev/block/mmcblk0p33 167934 167936 16 89 Unknown
/dev/block/mmcblk0p34 167937 692224 4194303+ 83 Linux
/dev/block/mmcblk0p35 692225 729088 294911+ 83 Linux
/dev/block/mmcblk0p36 729089 1887744 9269248 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p37 1887745 1887753 64 90 Unknown
/dev/block/mmcblk0p38 4095 4096 16 5a Unknown
/dev/block/mmcblk0p39 4097 4129 256 73 Unknown
/dev/block/mmcblk0p40 4129 6684 20442+ 5b Unknown
/dev/block/mmcblk0p41 6684 6716 256 5c Unknown
/dev/block/mmcblk0p42 6716 6844 1024 45 Unknown
/dev/block/mmcblk0p43 6844 6876 256 47 Unknown
/dev/block/mmcblk0p44 6876 7132 2048 46 Unknown
/dev/block/mmcblk0p45 7132 7260 1024 4c Unknown
/dev/block/mmcblk0p46 7260 7264 32 39 Unknown
/dev/block/mmcblk0p47 7264 8032 6144 34 Unknown
/dev/block/mmcblk0p48 8032 8160 1024 36 Unknown
/dev/block/mmcblk0p49 8161 8192 256 76 Unknown
/dev/block/mmcblk0p50 8193 13313 40960 77 Unknown
/dev/block/mmcblk0p51 13313 18433 40960 77 Unknown
/dev/block/mmcblk0p52 18433 19457 8191 74 Unknown
/dev/block/mmcblk0p53 19457 20480 8190+ 74 Unknown
/dev/block/mmcblk0p54 20481 24576 32768 7a Unknown
/dev/block/mmcblk0p55 24577 26625 16384 48 Unknown
/dev/block/mmcblk0p56 26625 28672 16383 71 Unknown
/dev/block/mmcblk0p57 28673 30720 16381+ 76 Unknown
/dev/block/mmcblk0p58 30720 31232 4096 4a Unknown
/dev/block/mmcblk0p59 31232 31744 4096 4b Unknown
/dev/block/mmcblk0p60 31744 32256 4096 59 Unknown
Partition table entries are not in disk order
~ #

[Q] How do I edit/restore the mmcblk0 partition.

I have used esfdisk and fdisk and determined my boot loops are caused by a corrupted partition: mmcblk0. The size is incorrect, 30539776 and should be 30535680. As a result other partitions are overlapped, e.i: e2fsck:
* Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
* e2fsck: Superblock invalid, trying backup blocks...
2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p24
The size of all other partitions are correct but maligned. I believe if I can correct partition mmcblk0, the others will not overlap. Does anyone have the savvy to show me how? I've tried sdparted with no success. Thanks

davidrol said:
I have used esfdisk and fdisk and determined my boot loops are caused by a corrupted partition: mmcblk0. The size is incorrect, 30539776 and should be 30535680. As a result other partitions are overlapped, e.i: e2fsck:
* Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
* e2fsck: Superblock invalid, trying backup blocks...
2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p24
The size of all other partitions are correct but maligned. I believe if I can correct partition mmcblk0, the others will not overlap. Does anyone have the savvy to show me how? I've tried sdparted with no success. Thanks
Click to expand...
Click to collapse
I think you need to be s-off in order to edit mmcblk artitions. If you are s-off you can push the partition with dd comand in fastboot but but you need non corrupted one

Seems logical. I've been trying to gain S-OFF for days, but on my mac, adb recognizes the device as offline, using various roms. I'm going to use a pc today and attempt to apply firewater or rumrunner. I suppose getting an uncorrupted partition wouldn't be difficult if I could get one donated here. Otherwise, a disk editor (sdparted) might also work.
Thanks for your interest.

davidrol said:
Seems logical. I've been trying to gain S-OFF for days, but on my mac, adb recognizes the device as offline, using various roms. I'm going to use a pc today and attempt to apply firewater or rumrunner. I suppose getting an uncorrupted partition wouldn't be difficult if I could get one donated here. Otherwise, a disk editor (sdparted) might also work.
Thanks for your interest.
Click to expand...
Click to collapse
I could send you my partition, that's the least of your priblems. I had corrupted mmcblk09 and it took me around 1 minute to flash a good one with dd. But I'm s-off

Yes you can! Ican probably install it using sdparted without gaining s-off. If you could provide the mmcblk0, I'll at least have that to work with. I've installed mmcblk0p27 using sdparted with success. Thanks!
Here's the code from user harshdev in another forum: while in custom recovery:
Code:
adb push mmcblk0p19_repaired.img /tmp/
adb shell dd if=/tmp/mmcblk0p19_repaired.img of=/dev/block/mmcblk0p19
adb reboot bootloader

@donkeykong1
Here's my fdisk readout on mmcblk0. How does this compare to yours:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 3817472.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: deleting partitions after 60
Command (m for help): u
Changing display/entry units to sectors
Command (m for help): p
Disk /dev/block/mmcblk0: 31.2 GB, 31272730624 bytes
1 heads, 16 sectors/track, 3817472 cylinders, total 61079552 sectors
Units = sectors of 1 * 512 = 512 bytes
isk /dev/block/mmcblk0: 31.2 GB, 31272730624 bytes
1 heads, 16 sectors/track, 3817472 cylinders, total 61079552 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 256 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 257 768 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 769 262110 130671 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 262111 61079550 30408720 5 Extended ------------------------------> should be 1mb
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 262112 262143 16 5a Unknown
/dev/block/mmcblk0p6 262145 262656 256 73 Unknown
/dev/block/mmcblk0p7 262658 293812 15577+ 5b Unknown
/dev/block/mmcblk0p8 293814 294325 256 5c Unknown
/dev/block/mmcblk0p9 294327 296374 1024 45 Unknown
/dev/block/mmcblk0p10 296376 296887 256 47 Unknown
/dev/block/mmcblk0p11 296889 300984 2048 46 Unknown
/dev/block/mmcblk0p12 300986 305146 2080+ 4c Unknown
/dev/block/mmcblk0p13 305148 315387 5120 34 Unknown
/dev/block/mmcblk0p14 315389 317436 1024 36 Unknown
/dev/block/mmcblk0p15 317438 319485 1024 0 Empty
/dev/block/mmcblk0p16 319487 442368 61441 50 Unknown
/dev/block/mmcblk0p17 442370 458750 8190+ 74 Unknown
/dev/block/mmcblk0p18 458752 524287 32768 0 Empty
/dev/block/mmcblk0p19 524289 526333 1022+ 76 Unknown
/dev/block/mmcblk0p20 526335 534526 4096 4a Unknown
/dev/block/mmcblk0p21 534528 542719 4096 4b Unknown
/dev/block/mmcblk0p22 542721 583680 20480 19 Unknown
/dev/block/mmcblk0p23 583682 583689 4 0 Empty
/dev/block/mmcblk0p24 583691 584202 256 23 Unknown
/dev/block/mmcblk0p25 584204 584235 16 0 Empty
/dev/block/mmcblk0p26 584237 586797 1280+ 0 Empty
/dev/block/mmcblk0p27 586799 586926 64 0 Empty
/dev/block/mmcblk0p28 586928 588975 1024 0 Empty
/dev/block/mmcblk0p29 588977 786431 98727+ 0 Empty
/dev/block/mmcblk0p30 786433 894973 54270+ 0 Empty
/dev/block/mmcblk0p31 894975 1048575 76800+ 77 Unknown
/dev/block/mmcblk0p32 1048577 1245182 98303 0 Empty
/dev/block/mmcblk0p33 1245184 1277951 16384 48 Unknown
/dev/block/mmcblk0p34 1277953 1310719 16383+ 71 Unknown
/dev/block/mmcblk0p35 1310721 5111806 1900543 83 Linux
/dev/block/mmcblk0p36 5111808 6422526 655359+ 83 Linux
/dev/block/mmcblk0p37 6422528 60948479 27262976 83 Linux

No luck editing the size of mmcblk0p4. Edits won't stay and reverts back.
Anyone know how to do this?

davidrol said:
No luck editing the size of mmcblk0p4. Edits won't stay and reverts back.
Anyone know how to do this?
Click to expand...
Click to collapse
I'm pretty sure you won't be able to change your partition layout without S-OFF, but aren't you jumping the gun a little? (and potentially bricking your device completely!!)
Why don't you first explain what the problem is.
BTW, on the m7_u/ul the only EXT partitions are
/dev/block/mmcblk0p35 /system
/dev/block/mmcblk0p36 /cache
/dev/block/mmcblk0p37 /data
so you can only use e2fsck on these partitions, all the others are RAW partitions.
please post a
1) "fastboot getvar all" (excluding IMEI and s/n)
2) what custom recovery (and version) you are using (cause looks like you're on CWM, and you should probably be using TWRP)
3) what ROM are you using/want to use
4) what is the problem

Right! I need to gain s-off for this to stick. The device was soft bricked when I acquired it and is unable to run sense and cm10.1 without boot looping. I have gained a only slight improvements. I've installed an original/compatible RUU sense and it boot loops like the others. Only cm11 (aosb_kk_1.3.6_m7) runs but with crippled resources, i.e., no gps, no phone radio, no google sync or location sync, widget won't stay after reboot, etc, etc. The version main: is not shown, the imei or phone hardversion is not present in phone info. I'm using the latest TWRP.
There are overlapping partitions in 1,2,3 and 4. I had hoped that parted would repair this, but returns the error: You can't have overlapping partitions.
Partition 1 does not end on cylinder boundary
Partition 1: sector 0 greater than maximum 16
Partition 2 does not end on cylinder boundary
Partition 2: sector 0 greater than maximum 16
Partition 3 does not end on cylinder boundary
Partition 3: sector 0 greater than maximum 16
Partition 5: sector 0 greater than maximum 16
Partition 6: sector 0 greater than maximum 16
Partition 7: sector 0 greater than maximum 16
Partition 8: sector 0 greater than maximum 16
Partition 9: sector 0 greater than maximum 16
Partition 10: sector 0 greater than maximum 16
Partition 11: sector 0 greater than maximum 16
Partition 12: sector 0 greater than maximum 16
Partition 13: sector 0 greater than maximum 16
Partition 14: sector 0 greater than maximum 16
Partition 16: sector 0 greater than maximum 16
Partition 17: sector 0 greater than maximum 16
Partition 19: sector 0 greater than maximum 16
Partition 20: sector 0 greater than maximum 16
Partition 21: sector 0 greater than maximum 16
Partition 22: sector 0 greater than maximum 16
Partition 24: sector 0 greater than maximum 16
Partition 31: sector 0 greater than maximum 16
Partition 33: sector 0 greater than maximum 16
Partition 34: sector 0 greater than maximum 16
Partition 35: sector 0 greater than maximum 16
Partition 36: sector 0 greater than maximum 16
Partition 37: sector 0 greater than maximum 16
Partition 38: sector 0 greater than maximum 16
Warning: partition 5 overlaps partition 38
Partition 39: sector 0 greater than maximum 16
Warning: partition 6 overlaps partition 39
Partition 40: sector 0 greater than maximum 16
Warning: partition 7 overlaps partition 40
Partition 41: sector 0 greater than maximum 16
Warning: partition 8 overlaps partition 41
Partition 42: sector 0 greater than maximum 16
Warning: partition 9 overlaps partition 42
Partition 43: sector 0 greater than maximum 16
Warning: partition 10 overlaps partition 43
Partition 44: sector 0 greater than maximum 16
Warning: partition 11 overlaps partition 44
Partition 45: sector 0 greater than maximum 16
Warning: partition 12 overlaps partition 45
Partition 46: sector 0 greater than maximum 16
Warning: partition 13 overlaps partition 46
Partition 47: sector 0 greater than maximum 16
Warning: partition 14 overlaps partition 47
Partition 49: sector 0 greater than maximum 16
Warning: partition 16 overlaps partition 49
Partition 50: sector 0 greater than maximum 16
Warning: partition 17 overlaps partition 50
Partition 52: sector 0 greater than maximum 16
Warning: partition 19 overlaps partition 52
Partition 53: sector 0 greater than maximum 16
Warning: partition 20 overlaps partition 53
Partition 54: sector 0 greater than maximum 16
Warning: partition 21 overlaps partition 54
Partition 55: sector 0 greater than maximum 16
Warning: partition 22 overlaps partition 55
Partition 57: sector 0 greater than maximum 16
Warning: partition 24 overlaps partition 57
~ # cat /proc/partitions
major minor #blocks name
179 0 30539776 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
These are stock values:
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1 sbl1
179 2 256 mmcblk0p2 sbl2
179 3 130671 mmcblk0p3 pg1fs
179 4 1 mmcblk0p4 ?
179 5 16 mmcblk0p5 board_info
I've managed to recover mmcblk0p4 since my previous posts. Here's my getvar:
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4A.19.3263.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: XXXXXXXXXX
INFOimei: XXXXXXXXXXXX
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4323mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-2da61e5e88
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Thanks for your reply. Admittedly, I'm no dev and I sometimes get lost trying to wrap my head around all this!

davidrol said:
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4A.19.3263.13
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOproduct: m7_ul
INFOmodelid: PN0712000
INFOcidnum: CWS__001
Click to expand...
Click to collapse
well, i haven't run parted/gparted/etc. too risky, way too easy to fully brick your device, but i can tell you that the Start/End/Size/Id of all your partitions are exactly the same as mine, except p4, which was due to the overall size difference (but which didn't affect all the other partitions!!!)
Have you tried this ruu: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe

Have to agree with nkk71 here. You have a normal AT&T phone, it should be easy to RUU back to stock from your current settings.
relock bootloader
fastboot oem lock
Run the 3.17.502.3 RUU and you should be all set

Installing an RUU didn't solve restoring all partitions, only a small portion. The upper (1-5) is where the overlap occurred and RUU's dont' effect those partitions, at all. I deleted mmcblk0p4, because it was way too large and should be 1MB. After, a few restarts and 3 attempts at gaining s-off with firewater, the phone now functions correctly! I have tested and confirm a working GPS, phone radio recognizing sim, google sync, etc, etc. The imei and broadband version show correctly in phone info. I cant explain or fully understand why it's fully working. I will examine the partitions again and post the results.
BTW, I haven't tried installing a sense rom (current Android Revolution) to check for the constant boot loops I was getting.
Next step would be to sim unlock and test phone reception and signal strength.
I thank you all for your assistance.

davidrol said:
Installing an RUU didn't solve restoring all partitions, only a small portion. The upper (1-5) is where the overlap occurred and RUU's dont' effect those partitions, at all. I deleted mmcblk0p4, because it was way too large and should be 1MB. After, a few restarts and 3 attempts at gaining s-off with firewater, the phone now functions correctly! I have tested and confirm a working GPS, phone radio recognizing sim, google sync, etc, etc. The imei and broadband version show correctly in phone info. I cant explain or fully understand why it's fully working. I will examine the partitions again and post the results.
BTW, I haven't tried installing a sense rom (current Android Revolution) to check for the constant boot loops I was getting.
Next step would be to sim unlock and test phone reception and signal strength.
I thank you all for your assistance.
Click to expand...
Click to collapse
hmm, interesting, I've never seen that done before, but just for info:
fdisk -ul
Code:
...
/dev/block/mmcblk0p4 262111 61071358 30404624 5 Extended
...
the rest are exactly like the ones you posted earlier.
but if you actually "dd" the partition, you'll get a 1KB (not MB) file, which starting ot offset 0x200 (ie 1 block) shows the HTC-BOARD-INFO from p5
so seems p4 is only 1 block plus some kind of container for the rest of the partitions.
Anyway, very glad that worked out for :good:
PS: and you were able to change the partition layout with S-ON.... didn't / don't think that's possible

[Q] Why do I have 39 partitions?

I've been blundering through the world of rooting for a few days, stumbling around in the dark. Many of the steps I've taken I didn't fully understand at the time, but I've come a long way towards understanding.
My getvar dump should answer most basic questions:
Code:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 1.00.20.0315
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: ############
imei: ###############
meid: ##############
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4319mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
I just flashed "RUU Zip M7_WLS_JB_50_Sprint_1.29.651.10_RUU_decrypted.zip"
Ok, here's my problem. My phone has 39 partitions instead of 37. I think this happened when I flashed "Sprint_HTC_One_m7wls_4.06.651.4_RUU" but I'm not sure about the timing. I went S-OFF and flashed to an older firmware, hoping that would clear up the issue, but it remains as before.
Code:
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 256 mmcblk0p29 skylink [NEW]
179 30 25600 mmcblk0p30 carrier [NEW]
179 31 72870 mmcblk0p31 reserve [SMALLER]
179 32 54270 mmcblk0p32 reserve_2
179 33 76800 mmcblk0p33 radio
179 34 98303 mmcblk0p34 reserve_3
179 35 16384 mmcblk0p35 boot
179 36 16383 mmcblk0p36 recovery
179 37 1900543 mmcblk0p37 system
179 38 655359 mmcblk0p38 cache
179 39 27262976 mmcblk0p39 userdata
Because of this, TWRP incorrectly mounts the system partition to /data and fails to mount /cache and /system. When I modify /etc/fstab to reflect my partitions, it works. Until I try to restore from a backup or install a custom ROM. Then it somehow manages to remount something by the old scheme and fails. The device boots and runs fine, but anything to do with recovery is broken.
If anyone knows what's going on or how I can coerce TWRP to use my new partitions, it would mean a lot to me. Thanks.

terrabite3 said:
I've been blundering through the world of rooting for a few days, stumbling around in the dark. Many of the steps I've taken I didn't fully understand at the time, but I've come a long way towards understanding.
My getvar dump should answer most basic questions:
Code:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 1.00.20.0315
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: ############
imei: ###############
meid: ##############
[/HIDE][B][COLOR="Red"]product: m7_wls[/COLOR][/B]
platform: HBOOT-8064
[B][COLOR="Red"]modelid: PN0720000
cidnum: SPCS_001[/COLOR][/B]
[HIDE]battery-status: good
battery-voltage: 4319mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
I just flashed "RUU Zip M7_WLS_JB_50_Sprint_1.29.651.10_RUU_decrypted.zip"
Ok, here's my problem. My phone has 39 partitions instead of 37. I think this happened when I flashed "Sprint_HTC_One_m7wls_4.06.651.4_RUU" but I'm not sure about the timing. I went S-OFF and flashed to an older firmware, hoping that would clear up the issue, but it remains as before.
Code:
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 256 mmcblk0p29 skylink [NEW]
179 30 25600 mmcblk0p30 carrier [NEW]
179 31 72870 mmcblk0p31 reserve [SMALLER]
179 32 54270 mmcblk0p32 reserve_2
179 33 76800 mmcblk0p33 radio
179 34 98303 mmcblk0p34 reserve_3
179 35 16384 mmcblk0p35 boot
179 36 16383 mmcblk0p36 recovery
179 37 1900543 mmcblk0p37 system
179 38 655359 mmcblk0p38 cache
179 39 27262976 mmcblk0p39 userdata
Because of this, TWRP incorrectly mounts the system partition to /data and fails to mount /cache and /system. When I modify /etc/fstab to reflect my partitions, it works. Until I try to restore from a backup or install a custom ROM. Then it somehow manages to remount something by the old scheme and fails. The device boots and runs fine, but anything to do with recovery is broken.
If anyone knows what's going on or how I can coerce TWRP to use my new partitions, it would mean a lot to me. Thanks.
Click to expand...
Click to collapse
It's because you have a Sprint phone. The partition table is correct for Sprint (which is different from the M7_U/UL), you need to use TWRP for M7_WLS
http://techerrata.com/browse/twrp2/m7wls

Ahhhh! Thank you! The only question that remains is how I switched from the RIGHT one to the WRONG one at some point.

terrabite3 said:
Ahhhh! Thank you! The only question that remains is how I switched from the RIGHT one to the WRONG one at some point.
Click to expand...
Click to collapse
you took a left turn somewhere
make sure you stick with recoveries/kernels/ROMs mean for Sprint.... due to the different partition table, unless you are 100% sure "it's" Sprint compatible (m7_wls), then don't flash it.

[INFO][DEV][DISCUSSION] All in one Androidone discussion thread for development

hi friends
Today i got my hands on Spice Dream Uno android one handset.
here is what i found for that device.
May be this info is common to all other android one devices that is why i am posting it in this section.
1. build.prop
Code:
#
# PRODUCT_OEM_PROPERTIES
#
import /oem/oem.prop ro.product.device
import /oem/oem.prop ro.product.name
import /oem/oem.prop ro.product.manufacturer
import /oem/oem.prop ro.product.model
import /oem/oem.prop ro.product.locale.language
import /oem/oem.prop ro.product.locale.region
import /oem/oem.prop ro.config.ringtone
import /oem/oem.prop ro.config.notification_sound
import /oem/oem.prop ro.config.alarm_alert
import /oem/oem.prop ro.config.wallpaper
import /oem/oem.prop ro.config.wallpaper_component
import /oem/oem.prop ro.oem.*
import /oem/oem.prop oem.*
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KPW53
ro.build.display.id=KPW53
ro.build.version.incremental=1379542
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Fri Aug 22 22:49:18 UTC 2014
ro.build.date.utc=1408747758
ro.build.type=user
ro.build.user=android-build
ro.build.host=wpds12.hot.corp.google.com
ro.build.tags=release-keys
ro.product.brand=google
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=mt6582
# ro.build.product is obsolete; use ro.product.device
ro.build.product=sprout
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=sprout-user 4.4.4 KPW53 1379542 release-keys
ro.build.thumbprint=4.4.4/KPW53/1379542:user/release-keys
ro.build.characteristics=default
# end build properties
#
# from device/mediatek/sprout/sprout/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.sf.lcd_density=240
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=128m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
ro.kernel.zio=38,108,105,16
#ro.kernel.qemu=1
#ro.kernel.qemu.gles=0
ro.boot.selinux=disable
# Disable dirty region for Mali
debug.hwui.render_dirty_regions=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=Titania.ogg
ro.config.notification_sound=Tethys.ogg
ro.config.alarm_alert=Oxygen.ogg
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.carrier=unknown
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.gms
ro.setupwizard.enterprise_mode=1
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=128m
ro.mediatek.chip_ver=S01
ro.mediatek.version.release=ALPS.W10.24.p0
ro.mediatek.platform=MT6582
ro.mediatek.version.sdk=1
ro.telephony.sim.count=2
persist.radio.default.sim=0
persist.radio.multisim.config=dsds
ro.telephony.default_network=0,1
persist.gemini.sim_num=2
ro.gemini.smart_3g_switch=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.mtk.wcn.combo.chipid=-1
drm.service.enabled=true
fmradio.driver.enable=0
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
ril.radiooff.poweroffMD=0
dalvik.vm.heapstartsize=8m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.mediatek.version.branch=KK.AOSP
keyguard.no_require_sim=true
ro.facelock.black_timeout=400
ro.facelock.det_timeout=1500
ro.facelock.rec_timeout=2500
ro.facelock.lively_timeout=2500
ro.facelock.est_max_time=600
ro.facelock.use_intro_anim=false
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
2.Partition layout
Code:
adb shell
Code:
127|[email protected]_sprout:/ $ cat proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 256 mmcblk0p5
179 6 384 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 6144 mmcblk0p9
179 10 512 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 65536 mmcblk0p12
179 13 16768 mmcblk0p13
179 14 1024000 mmcblk0p14
179 15 131072 mmcblk0p15
179 16 2416640 mmcblk0p16
179 17 32768 mmcblk0p17
179 18 65024 mmcblk0p18
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 7782400 mmcblk1
179 97 7781376 mmcblk1p1
and
Code:
[email protected]_sprout:/ $ ls -l /dev/block/platform/mtk-msdc.0/by-name
lrwxrwxrwx root root 2010-01-01 05:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2010-01-01 05:30 bootloader -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2010-01-01 05:30 cache -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2010-01-01 05:30 expdb -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2010-01-01 05:30 gen -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2010-01-01 05:30 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2010-01-01 05:30 metadata -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2010-01-01 05:30 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2010-01-01 05:30 oem -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2010-01-01 05:30 para -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2010-01-01 05:30 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2010-01-01 05:30 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2010-01-01 05:30 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2010-01-01 05:30 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2010-01-01 05:30 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2010-01-01 05:30 secro -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2010-01-01 05:30 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2010-01-01 05:30 userdata -> /dev/block/mmcblk0p16
3.Mount points
Code:
adb shell
Code:
[email protected]_sprout:/ $ cat proc/mounts
rootfs / rootfs ro,seclabel,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
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/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/oem /oem ext4 ro,context=u:object_r:oemfs:s0,nosuid,nodev,relatime,data=ordered 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:97 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
4.fastboot
yes this device has fastboot.
Unlocking bootloader via fastboot
***reboot into fastboot mode
2ways
a] switch off the phone>>press volume up + power at same time>>boot menu should appear>>go to fastboot menu with volume up and then select by pressing volume down.
OR
b]connect phone to PC(i use linux i dont need to install any drivers or adb or fastboot packages).>>enable usb debugging mode (developer options)>>adb reboot bootloader
this will boot into fastboot directly.
***connect phone to the PC
***open terminal>>fastboot oem unlock>>press volume down to select fastboot again>>fastboot format cache>>fastboot format userdata>>fastboot reboot
now you have unloicked bootloader.
5. Recovery
when
adb reboot recovery
Click to expand...
Click to collapse
given >>it boot into recovery screen where only some chinese picture of recovery is present.
On chinese recovery screen, if you press volume up and power button you will get apply zip from sideload and sdcard.
6.there is no valid fstab present at the root
7. init rc files are seem to be hidden out or symlinked somewhere else.
if you try to open them they open as only a blank text file.
8. Build version in build.prop is KPW53.
i dont know which version of kitkat is that.
9. baseband version
WR8.W1412.MD.WG.GMP.SP.W14.26.P3,2014/08/15 11.39
10. KERNEL version
3.4.67 [email protected]#1 Wed Aug 20 14:13:29 PDT 2014
11. SELINUX is disabled in build.prop
13. SAR value is 0.641 W/Kg (1g)
14. oem.prop for spice dream uno mi-498
Code:
ro.product.device=Mi-498_sprout
ro.product.name=Mi-498
ro.product.manufacturer=Spice
ro.product.model=Spice Mi-498
ro.product.locale.language=en
ro.product.locale.region=IN
ro.config.wallpaper=/oem/media/Default.jpg
15. partition layout proc/dumchar type(this does not exist on our phone but this info may be useful to create scatter file for sp flash tool)
Code:
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00001800 "proinfo"
emmc_p2: 00001c00 00002800 "nvram"
emmc_p3: 00004400 00005000 "protect1"
emmc_p4: 00009400 00005000 "protect2"
emmc_p5: 0000e400 00000200 "seccfg"
emmc_p6: 0000e600 00000300 "bootloader"
emmc_p7: 0000e900 00005000 "boot"
emmc_p8: 00013900 00005000 "recovery"
emmc_p9: 00018900 00003000 "secro"
emmc_p10: 0001b900 00000400 "para"
emmc_p11: 0001bd00 00004000 "logo"
emmc_p12: 0001fd00 00020000 "oem"
emmc_p13: 0003fd00 00008300 "expdb"
emmc_p14: 00048000 001f4000 "system"
emmc_p15: 0023c000 00040000 "cache"
emmc_p16: 0027c000 0049c000 "userdata"
emmc_p17: 00718000 00010000 "metadata"
emmc_p18: 00728000 0001fc00 "gen"
16. more info for the android one partitions and bootloader and preloader methods
Code:
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:gen: 3f80000
(bootloader) partition-type:gen: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:userdata: 93800000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 8000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 3e800000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: 1060000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:oem: 4000000
(bootloader) partition-type:oem: ext4
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: a00000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: a00000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:bootloader: 60000
(bootloader) partition-type:bootloader: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) version-baseband: MOLY
(bootloader) kernel: lk
(bootloader) product: sprout
(bootloader) version-preloader: 0.1.02
(bootloader) version-bootloader: 0.5.17
17. how to access preloader
The preloader does exist and can be accessed.
Remove and replace the battery and keep the volume down button with the phone connected to activate it.
thanks to @joshuab227

reserved1

@k2wl
Can you send me output of
Code:
cat /proc/cmdline
Also check if you have adb access in the Chinese recovery.

varun.chitre15 said:
@k2wl
Can you send me output of
Code:
cat /proc/cmdline
Also check if you have adb access in the Chinese recovery.
Click to expand...
Click to collapse
cat proc/cmdline
Click to expand...
Click to collapse
permission denied.
and there is no adb access in chinese recovery

k2wl said:
permission denied.
and there is no adb access in chinese recovery
Click to expand...
Click to collapse
Hmm... and none of the exploits look to be working, Google has patched them all. Even if I had the command line I could have build up a recovery which could have opened all these barriers.
The factory images just like the Nexus line are likely to be posted by Google soon.

Is any reason adb not being available in recovery?
varun.chitre15 said:
Hmm... and none of the exploits look to be working, Google has patched them all. Even if I had the command line I could have build up a recovery which could have opened all these barriers.
The factory images just like the Nexus line are likely to be posted by Google soon.
Click to expand...
Click to collapse

varun.chitre15 said:
Hmm... and none of the exploits look to be working, Google has patched them all. Even if I had the command line I could have build up a recovery which could have opened all these barriers.
The factory images just like the Nexus line are likely to be posted by Google soon.
Click to expand...
Click to collapse
oh you need that for recovery build.
then here it is
console=tty0 console=ttyMT3,921600n1 root=/dev/ram vmalloc=496M slub_max_order=0 slub_debug=O androidboot.hardware=sprout
Click to expand...
Click to collapse
hope this helps!!

k2wl said:
oh you need that for recovery build.
then here it is
hope this helps!!
Click to expand...
Click to collapse
Try flashing this new recovery
https://s.basketbuild.com/filedl/devs?dev=varun.chitre15&dl=varun.chitre15/A1/recovery.img
fastboot flash recovery path/to/recovery.img
Check if it boots.
P.s: You will lose that Chinese recovery after this, it isn't of any use anyway.

varun.chitre15 said:
Try flashing this new recovery
https://s.basketbuild.com/filedl/devs?dev=varun.chitre15&dl=varun.chitre15/A1/recovery.img
fastboot flash recovery path/to/recovery.img
Check if it boots.
P.s: You will lose that Chinese recovery after this, it isn't of any use anyway.
Click to expand...
Click to collapse
recovery doesnt boot.
it stays on spice logo
saying recovery mode in the bottom and after a while it shows oem unlock and phone reboots.

k2wl said:
recovery doesnt boot.
it stays on spice logo
saying recovery mode in the bottom and after a while it shows oem unlock and phone reboots.
Click to expand...
Click to collapse
I have uploaded a new image at the same link. Check with that.

varun.chitre15 said:
I have uploaded a new image at the same link. Check with that.
Click to expand...
Click to collapse
this recovery does not boot.
spice mobile screen with recovery mode for 1 min. then spice screen with oem unlocked for 10-15 sec then phone reboots.

k2wl said:
this recovery does not boot.
spice mobile screen with recovery mode for 1 min. then spice screen with oem unlocked for 10-15 sec then phone reboots.
Click to expand...
Click to collapse
OK I have ordered the Micromax variant, will be able to experiment myself after that.

guys try this to gain root http://www.mgyun.com/en/getvroot

varunrocks17 said:
guys try this to gain root http://www.mgyun.com/en/getvroot
Click to expand...
Click to collapse
man it doesnt work. plz stop posting it on every android 1 thread. the phones have same everything internal.

can upload a backup of the system and boot?

walkman-star said:
can upload a backup of the system and boot?
Click to expand...
Click to collapse
no root access till now so no boot.img
but system dump can be taken.

System dump
Find system dump here http://dropjar.com/#YazLGa6
k2wl said:
no root access till now so no boot.img
but system dump can be taken.
Click to expand...
Click to collapse

sheldroid said:
Find system dump here
Click to expand...
Click to collapse
boot.img can upload ?

No root available so can't take boot image
Sent from my Spice Mi-498

k2wl said:
no root access till now...
Click to expand...
Click to collapse
So there are no exploits reported to working as of now?
How about towelroot? (BTW I've seen many devices with kernel build date greater than JUN 2014 and towelroot working) If it doesn't work, you can try to play with modstrings.

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

I've changed my device (M8S) for the HTC 10. My old device is own by my girlfriend.
Click to expand...
Click to collapse
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..
0P[email protected]50311_15.00_016_F_release_427719_signed.zip
0P[email protected]50311_15.00_016_F_release_427719_signed_Hboot.zip
0P[email protected]50408_15.00_016_F_release_431742_signed.zip
0PK[email protected]50408_15.00_016_F_release_450151_combined_signed.zip
0PKVIM[email protected]50408_15.00_016_F_release_434297_signed.zip
0PKVIM[email protected]50408_15.00_016_F_release_438317_combined_signed.zip
0PKVIM[email protected]50408_15.00_016_F_release_438471_combined_signed.zip
0PKVIM[email protected]50408_15.00_016_F_release_438612_combined_signed.zip
0PKVIMG[email protected]50408_15.00_016_F_release_450409_combined_signed.zip
0[email protected]50128_07.00_015_F_test_420314.zip
0[email protected]50311_15.00_016_F_release_427730_signed_Hboot.zip
0[email protected]50311_15.00_016_F_release_428544_combined_signed.zip
0P[email protected]50408_15.00_016_F_release_449761_combined_signed.zip
0PKVI[email protected]50408_15.00_016_F_release_449948_combined_signed.zip
0PK[email protected]50408_15.00_016_F_release_451151_combined_signed.zip
0PKV[email protected]50408_15.00_016_F_release_429391_signed.zip
0PK[email protected]50408_15.00_016_F_release_451505_combined_signed.zip
0PK[email protected]50408_15.00_016_F_release_451153_combined_signed.zip
0PK[email protected]50408_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[email protected]50311_15.00_016_F_release_426598_signed.zip
0PKVIMG[email protected]50311_15.00_016_F_release_426930_signed.zip
0PKVIMG[email protected]50311_15.00_016_F_release_427668_combined_signed.zip
0PKVIMG_[email protected]50408_15.00_016_F_release_450235_combined_signed.zip
Click to expand...
Click to collapse
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
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 !
Click to expand...
Click to collapse
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?
Click to expand...
Click to collapse
#########################################
----------------------------------------------------------------------------------------
#########################################
## HOW TO USE CUSTOM RECOVERY
#########################################
Files Needed :
- TWRP 2.8.6.0 : http://ruu.lalleman.net/HTC_M8S(QL_UL)/Recovery/twrp-recovery-2.8.6.0-m8s-qlul/
- The HTC_Fastboot : http://ruu.lalleman.net/HTC_M8S(QL_UL)/Tools/Fastboot/
- Stock Extracted Recovery : http://ruu.lalleman.net/HTC_M8S(QL_UL)/Recovery/HTC Recovery/ **
** 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/android_device_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

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.

Idlekilla said:
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.
Click to expand...
Click to collapse
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 .

El-Conkistador said:
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 .
Click to expand...
Click to collapse
I did flash several recoveries after unlocking bootloader (which worked like a charm btw), but now I can't even factory reset.

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 :crying:
---------- Post added at 01:09 PM ---------- Previous post was at 01:06 PM ----------
Idlekilla said:
I did flash several recoveries after unlocking bootloader (which worked like a charm btw), but now I can't even factory reset.
Click to expand...
Click to collapse
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......

I would love to see a recovery too! I'll donate to first working recovery

I would also donate for a recovery for the M8s.
Sent from my HTC One M8s using XDA Free mobile app

thorgose said:
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 :crying:
---------- 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......
Click to expand...
Click to collapse
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

xunholyx said:
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
Click to expand...
Click to collapse
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

xunholyx said:
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
Click to expand...
Click to collapse
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

thorgose said:
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
Click to expand...
Click to collapse
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.

flash to original recovery worked
I made the same error and tried to flash TWRP and CWM for the M8 on to my M8S before I realised that this is a different 'phone. As a consequence, I managed to lose the original recovery and also the ability to factory wipe the phone.
Thanks to the OP, I was able to flash the recovery that he provided and all is working now. My phone is unlocked (HTCdev) and is provided by vodafone UK (cid VODAP001).
Now patiently waiting for someone to create a custom recovery...

ragg987 said:
I made the same error and tried to flash TWRP and CWM for the M8 on to my M8S before I realised that this is a different 'phone. As a consequence, I managed to lose the original recovery and also the ability to factory wipe the phone.
Thanks to the OP, I was able to flash the recovery that he provided and all is working now. My phone is unlocked (HTCdev) and is provided by vodafone UK (cid VODAP001).
Now patiently waiting for someone to create a custom recovery...
Click to expand...
Click to collapse
I'm glad I could help by sharing the file OTA update . Now with the support of the XDA community, we will see if a custom recovery is coming soon.

ragg987 said:
I made the same error and tried to flash TWRP and CWM for the M8 on to my M8S before I realised that this is a different 'phone. As a consequence, I managed to lose the original recovery and also the ability to factory wipe the phone.
Thanks to the OP, I was able to flash the recovery that he provided and all is working now. My phone is unlocked (HTCdev) and is provided by vodafone UK (cid VODAP001).
Now patiently waiting for someone to create a custom recovery...
Click to expand...
Click to collapse
How did you flash it? I only get an error when I try.
Sent from my HTC One M8s using XDA Free mobile app

Using the latest platform-tools from Google and Win 8.1 x64 - in case it matters. USB cable to my PC, then
adb reboot-bootloader
fastboot flash recovery <the recovery file.img>
fastboot erase cache

ragg987 said:
Using the latest platform-tools from Google and Win 8.1 x64 - in case it matters. USB cable to my PC, then
adb reboot-bootloader
fastboot flash recovery <the recovery file.img>
fastboot erase cache
Click to expand...
Click to collapse
I get same error as earlier. Installed the latest platform tools (on Win7 x64), but get 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.826s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.845s
Why does this happen?

Idlekilla said:
I get same error as earlier. Installed the latest platform tools (on Win7 x64), but get 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.826s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.845s
Why does this happen?
Click to expand...
Click to collapse
i think you might have to relock your bootloader.
fastboot oem lock

xunholyx said:
i think you might have to relock your bootloader.
fastboot oem lock
Click to expand...
Click to collapse
Did that, but now I get this:
[...]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail))
finished. total time: 2.896s
I'm stumped. Tried booting into RUU also, but to no avail. Main problem is that some apps doesn't work anymore.
Ordered an M8 and got an M8s - but I don't know if I can blame someone else. ^^

Idlekilla said:
Ordered an M8 and got an M8s - but I don't know if I can blame someone else. ^^
Click to expand...
Click to collapse
Can you not return it as not what you ordered?

ragg987 said:
Can you not return it as not what you ordered?
Click to expand...
Click to collapse
Probably, but I can't factory reset, and I believe there will be e few eyebrows raised when they get back a phone that's been tampered with.
Is there a way to factory reset when booting into RUU?