Database Develop

[INFO]Partition List HTC ONE M8 / RAW DUMP SCRIPT

Hello Everyone,
I needed the partition read-out of the M8 and thought i can as well leave it here for you as a reference.
I might also extend this to a custom firmware section if no one else takes the job before (see my M7 stuff) once i got the phone.
Well anyhow, here's the list, it's not complete yet, i will further it with the names of the corresponding RUU images for who might find it helpful (should i get device and RUU's rather soon. If not this will be abandoned )
[EDIT]
IF you guys want to dump your brand spanking new M8 as a raw full dump (not sure a restore later works out but better have this, right? ) you can run this batch script, it will pull all partitions EXCEPT userdata (the "sdcard") first to SD and then to PC.
Run the EXE (its a self extracting WinRAR5 archive - i SWEAR its not evil! Its not gonna steal your pizza!
Its just a simple batch for now, the exe will only extract it to C:\Android\com. Then you can double click the batch script and it will attempt to pull the first 46 partitions as RAW material.
Its not really meant as a backup solution for average Joe, its more like giving you an easy method to create a (nearly) full dump of a (nearly) virgin device so there's a way back to (nearly) original state when we get S-OFF (a restore of this will never work with S-ON).
And its probably more a handy script for those of you who do the developing part here. You will know how to adjust the script so it runs wherever and does whatever, you may just use it as a repository of dd pull commands. Save you some typing
M8-Dumper (47 Partitions GSM model)
[EDIT]
Code:
echo. "HTC One / M8 FULL DUMP Script"
echo. ================================
echo.
echo. Warning: the DUMP on M8 can use many Gigabytes free
echo. space on the SDcard! Please make sure that you have
echo. at least 50% free space on your card.
echo. Since SDCard is now part of the /data Partition, i
echo. will not dump /data (around 10 GB) either.
echo. You also absoutely need to get a modified Boot.img
echo. with Insecure ADB added from somewhere or else this
echo. will NOT work!
....
This means: you need to Unlock, flash Custom Recovery, Root, flash Unsecure kernel before you can work with this script. So, Recovery, Boot and System will already be modified when dumping. The other 40+ partitions will be original.
Handy links:
@Guich's Stock Recovery Thread
@Mr Hofs Stock Backup Thread

Nice work, Sneaky, and yes, looking forward to you working your magic on M8 firmware! Waiting on my M8 Dev edition, should ship in a week or so. Really happy to see you here mate, cheers!

Not quite there yet. Still looking for cash or free devices
Could become June before I'll be able to buy it. We shall see.
«--=|[Mobile Viper bite]|=--»

Thanks for the Partition Table! I'll be using this in my toolkit!

Hey sneaky, good to see you here too. Will get my m8 tomorrow.
Verstuurd vanaf mijn HTC One met Tapatalk

Snah001 said:
Hey sneaky, good to see you here too. Will get my m8 tomorrow.
Verstuurd vanaf mijn HTC One met Tapatalk
Click to expand...
Click to collapse
Yeah! Nice to hear that... Seems like virtually every dev with a name around here gets it. Gonna be a mad and exciting year.
Called my carrier today, they have it on pre-order as well now. I can have it for about 400 and keep the M7. So I'll sell that and get the M8 for about 100 quid including excellent two year service.
Thinking about it,I actually haven't paid that little for a good phone in a while
Expect me here within the month.
SixthSenseSuxx... visually... time for venom theming...

@Sneakyghost :
hi mate,
any news how to remove the red warning ?
remeber on M7 that I used yours excellents mods ...
tks bro

jonata said:
@Sneakyghost :
hi mate,
any news how to remove the red warning ?
remeber on M7 that I used yours excellents mods ...
tks bro
Click to expand...
Click to collapse
Not until S-Off iirc.

S-OFF first. Before that, no firmware packs whatsoever. Sorry.
SixthSenseSuxx... visually... time for venom theming...

Could be soon.
http://forum.xda-developers.com/showthread.php?t=2706553

@Sneakyghost s-off is here! Time to get up and start making those amazing FUUs and ZIPs!
Will be getting my m8 within the month (hopefully)
Sent from my iPod touch using Tapatalk

n1234d said:
@Sneakyghost s-off is here! Time to get up and start making those amazing FUUs and ZIPs!
Will be getting my m8 within the month (hopefully)
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
https://twitter.com/Sneakygh0st/status/452941752186712065
Seen and retweeted it 25 minutes after they tweeted. While being half asleep in the middle of the night.
It's my birthday too soon. I'm going shopping then. Thank God some really nice people here already helped finance it a bit. Got about 10% now. That means I'll stick to what I said: I'll have it within the month (April).
[EDIT]
It's gonna be here Friday.
Some good people helped me out a bit, thank you guys.
Will start working here once I've achieved S-OFF. Hope I'm not gonna run into the fails many others have been seeing with firewater.

Sneakyghost said:
https://twitter.com/Sneakygh0st/status/452941752186712065
Seen and retweeted it 25 minutes after they tweeted. While being half asleep in the middle of the night.
It's my birthday too soon. I'm going shopping then. Thank God some really nice people here already helped finance it a bit. Got about 10% now. That means I'll stick to what I said: I'll have it within the month (April).
[EDIT]
It's gonna be here Friday.
Some good people helped me out a bit, thank you guys.
Will start working here once I've achieved S-OFF. Hope I'm not gonna run into the fails many others have been seeing with firewater.
Click to expand...
Click to collapse
Happy Birthday !!!!!!!!!
when have time, and party is over ...
no red warning ?
tks bro and again HAPPY BIRTHDAY

here you go
Verison M8 with ARHD on it:
dev: size erasesize name
mmcblk0p1: 00100000 00000200 "sbl1"
mmcblk0p2: 076f7c00 00000200 "pg1fs"
mmcblk0p3: 00004000 00000200 "board_info
mmcblk0p4: 00800000 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "sbl1_updat
mmcblk0p8: 00040000 00000200 "rpm"
mmcblk0p9: 00200000 00000200 "tz"
mmcblk0p10: 00008000 00000200 "sdi"
mmcblk0p11: 00400000 00000200 "hboot"
mmcblk0p12: 00500000 00000200 "sp1"
mmcblk0p13: 00100000 00000200 "wifi"
mmcblk0p14: 00008000 00000200 "ddr"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p17: 00500000 00000200 "wcnss"
mmcblk0p18: 00800000 00000200 "radio_con
mmcblk0p19: 00180000 00000200 "fsg"
mmcblk0p20: 04b00400 00000200 "radio"
mmcblk0p21: 00400000 00000200 "tool_diag
mmcblk0p22: 03200000 00000200 "custdata"
mmcblk0p23: 00effc00 00000200 "reserve_2
mmcblk0p24: 00100000 00000200 "misc"
mmcblk0p25: 00180000 00000200 "modem_st1
mmcblk0p26: 00180000 00000200 "modem_st2
mmcblk0p27: 01400000 00000200 "fataldevl
mmcblk0p28: 00001000 00000200 "debug_con
mmcblk0p29: 00040000 00000200 "pdata"
mmcblk0p30: 00004000 00000200 "control"
mmcblk0p31: 00140400 00000200 "local"
mmcblk0p32: 00010000 00000200 "extra"
mmcblk0p33: 00100000 00000200 "cdma_reco
mmcblk0p34: 00000400 00000200 "fsc"
mmcblk0p35: 00002000 00000200 "ssd"
mmcblk0p36: 00040000 00000200 "skylink"
mmcblk0p37: 01900000 00000200 "carrier"
mmcblk0p38: 00040000 00000200 "sensor_hu
mmcblk0p39: 01e00000 00000200 "devlog"
mmcblk0p40: 00002800 00000200 "cir_img"
mmcblk0p41: 01000000 00000200 "vzw_quali
mmcblk0p42: 01de6000 00000200 "reserve"
mmcblk0p43: 01000000 00000200 "boot"
mmcblk0p44: 01800000 00000200 "recovery"
mmcblk0p45: 05800000 00000200 "reserve_3
mmcblk0p46: a8000000 00000200 "system"
mmcblk0p47: 40000000 00000200 "cache"
mmcblk0p48: 30000000 00000200 "userdata"

jonata said:
Happy Birthday !!!!!!!!!
when have time, and party is over ...
no red warning ?
tks bro and again HAPPY BIRTHDAY
Click to expand...
Click to collapse
You have S-OFF?
I suggest you find yourself a copy of UltraEdit (buy it, its good!) and then head over to my M7 Firmware thread and look up how to edit your hboot yourself. If you stick EXACTLY to my instructions, its not dangerous. If you mess up, it is.
Like i said, i am NOT going to provide hboots i have not tested myself. Because with this file, there are two options only: either it works 100% or it bricks your device. Any error kills it. I am not going to modify it and let others test it. I would feel very bad. Sorry.
If you don't want to do that yourself, you will have to wait until my phone is here (hopefully friday) and then i can start working on it (if i manage to S-OFF it).

Verizon:
Partition Table:
Code:
D:\>adb shell cat /proc/emmc
dev: size erasesize name
mmcblk0p1: 00100000 00000200 "sbl1"
mmcblk0p2: 076f7c00 00000200 "pg1fs"
mmcblk0p3: 00004000 00000200 "board_info"
mmcblk0p4: 00800000 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "sbl1_update"
mmcblk0p8: 00040000 00000200 "rpm"
mmcblk0p9: 00200000 00000200 "tz"
mmcblk0p10: 00008000 00000200 "sdi"
mmcblk0p11: 00400000 00000200 "hboot"
mmcblk0p12: 00500000 00000200 "sp1"
mmcblk0p13: 00100000 00000200 "wifi"
mmcblk0p14: 00008000 00000200 "ddr"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p17: 00500000 00000200 "wcnss"
mmcblk0p18: 00800000 00000200 "radio_config"
mmcblk0p19: 00180000 00000200 "fsg"
mmcblk0p20: 04b00400 00000200 "radio"
mmcblk0p21: 00400000 00000200 "tool_diag"
mmcblk0p22: 03200000 00000200 "custdata"
mmcblk0p23: 00effc00 00000200 "reserve_2"
mmcblk0p24: 00100000 00000200 "misc"
mmcblk0p25: 00180000 00000200 "modem_st1"
mmcblk0p26: 00180000 00000200 "modem_st2"
mmcblk0p27: 01400000 00000200 "fataldevlog"
mmcblk0p28: 00001000 00000200 "debug_config"
mmcblk0p29: 00040000 00000200 "pdata"
mmcblk0p30: 00004000 00000200 "control"
mmcblk0p31: 00140400 00000200 "local"
mmcblk0p32: 00010000 00000200 "extra"
mmcblk0p33: 00100000 00000200 "cdma_record"
mmcblk0p34: 00000400 00000200 "fsc"
mmcblk0p35: 00002000 00000200 "ssd"
mmcblk0p36: 00040000 00000200 "skylink"
mmcblk0p37: 01900000 00000200 "carrier"
mmcblk0p38: 00040000 00000200 "sensor_hub"
mmcblk0p39: 01e00000 00000200 "devlog"
mmcblk0p40: 00002800 00000200 "cir_img"
mmcblk0p41: 01000000 00000200 "vzw_quality"
mmcblk0p42: 01de6000 00000200 "reserve"
mmcblk0p43: 01000000 00000200 "boot"
mmcblk0p44: 01800000 00000200 "recovery"
mmcblk0p45: 05800000 00000200 "reserve_3"
mmcblk0p46: a8000000 00000200 "system"
mmcblk0p47: 40000000 00000200 "cache"
mmcblk0p48: 30000000 00000200 "userdata"
Mount:
Code:
D:\HTC One>adb shell
[email protected]_m8wl:/ $ mount
mount
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
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/mmcblk0p46 /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p47 /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p39 /devlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p27 /fataldevlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/radio /firmware/radio vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/adsp /firmware/adsp vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/wcnss /firmware/wcnss vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p22 /custdata ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 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:129 /mnt/media_rw/ext_sd texfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,umask=0007,allow_utime=0020,nls=utf8,min_prealloc_size=64k,readahead=4M,fail_safe,discard,errors=continue 0 0
/dev/block/vold/179:129 /mnt/secure/asec texfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,umask=0007,allow_utime=0020,nls=utf8,min_prealloc_size=64k,readahead=4M,fail_safe,discard,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
[email protected]_m8wl:/ $

Sneakyghost said:
You have S-OFF?
I suggest you find yourself a copy of UltraEdit (buy it, its good!) and then head over to my M7 Firmware thread and look up how to edit your hboot yourself. If you stick EXACTLY to my instructions, its not dangerous. If you mess up, it is.
Like i said, i am NOT going to provide hboots i have not tested myself. Because with this file, there are two options only: either it works 100% or it bricks your device. Any error kills it. I am not going to modify it and let others test it. I would feel very bad. Sorry.
If you don't want to do that yourself, you will have to wait until my phone is here (hopefully friday) and then i can start working on it (if i manage to S-OFF it).
Click to expand...
Click to collapse
thanks for reply and again AUGURI
I'm a little bit afraid, and have a lot of time to await
so, next friday, next week ... when you receive your M8 and got S-OFF
I await you
Thanks again

Sneaky partions from my HTC__001https://www.dropbox.com/s/zypbska37jh8xgm/partitions.txt
Sent from my HTC One_M8 using xda app-developers app

Sneakyghost said:
You have S-OFF?
I suggest you find yourself a copy of UltraEdit (buy it, its good!) and then head over to my M7 Firmware thread and look up how to edit your hboot yourself. If you stick EXACTLY to my instructions, its not dangerous. If you mess up, it is.
Like i said, i am NOT going to provide hboots i have not tested myself. Because with this file, there are two options only: either it works 100% or it bricks your device. Any error kills it. I am not going to modify it and let others test it. I would feel very bad. Sorry.
If you don't want to do that yourself, you will have to wait until my phone is here (hopefully friday) and then i can start working on it (if i manage to S-OFF it).
Click to expand...
Click to collapse
Hi Sneaky.
I removed the red text myself, remembered when we did this together on the M7 in the very beginning.
When you want I can send you my orig.hboot and the altered one (3.16) by PM so you can use it. Oh and of course it works

Snah001 said:
Hi Sneaky.
I removed the red text myself, remembered when we did this together on the M7 in the very beginning.
When you want I can send you my orig.hboot and the altered one (3.16) by PM so you can use it. Oh and of course it works
Click to expand...
Click to collapse
:highfive:

[TOOL][WIP/RECOVERY]TWRP 2.7.0.x[OFFMODE CHARGING FIX]

This is a WIP(work in progress)..built from latest source(maintained)..this is untested since none of you wants to help..used the latest OTA images for some parts of the recovery(built it with dependency mode)
Grab the image here
for both S-ON and S-OFF:
- Grab the recovery image..
- Setup Fastboot tools and drivers..
- Reboot phone to Bootloader mode(pressing Volume down while powering it on and pressing on Bootloader option)
- Run command prompt on your fastboot directory by Holding Shift(keyboard) and pressing right click on your mouse..choose open command window here..
- Issue commands:
Code:
fastboot erase cache
- Then after finishing the previous command..
Code:
fastboot flash recovery [COLOR="Red"][I]image.image[/I][/COLOR]
note: where image.image is the filename of the recovery image you have downloaded..
- Reboot bootloader and try to enter recovery..and give yourself a HUG..if all goes well you will be greeted by the Teamwin screen and will enter the menu shortly..
Kindly test and give feedback.. if you like it a Thanks cannot be as harmful as it seems..it will keep me motivated to work things out for FREE..
Credits:
DeesTroy(TWRP), Flyhalf205(device tree), Omni git, tropical_cactus(tester), moonchy(tester), migascalp(tester) and to those who donated my biggest Thanks!!
XDA:DevDB Information
TWRP for Butterfly S, Tool/Utility for the HTC Butterfly S
Contributors
kairi_zeroblade
Version Information
Status: Testing
Created 2014-10-18
Last Updated 2014-10-18

Installed on my 901S and it does not work. Wanting to get into recovery the phone will restart.:crying:
We hope you manage to fix the problem charging the phone is off.
For the moment, thanks!

fiorello said:
Installed on my 901S and it does not work. Wanting to get into recovery the phone will restart.:crying:
We hope you manage to fix the problem charging the phone is off.
For the moment, thanks!
Click to expand...
Click to collapse
they removed the offmode charging on kitkat..even on the HTC One,,if you want offmode charging downgrade your bootloader..can you dump me a last_kmsg and a recovery log from /cache/recovery.log or sumthin..
edit:
here's a new image..can you try this??this is still using your own stock recovery image..dl here

kairi_zeroblade said:
they removed the offmode charging on kitkat..even on the HTC One,,if you want offmode charging downgrade your bootloader..can you dump me a last_kmsg and a recovery log from /cache/recovery.log or sumthin..
edit:
here's a new image..can you try this??this is still using your own stock recovery image..dl here
Click to expand...
Click to collapse
Thanks. Will try when I get my damn phone back from the service centre. After chasing everyday, it's finally repaired. Can I give your kernel a try?

Not even the new image works. Advice concerning the same: the phone will restart.

fiorello said:
Not even the new image works. Advice concerning the same: the phone will restart.
Click to expand...
Click to collapse
logs please..i dont know if the recovery of 901s even differs from the 901e..build is successful and no issues..

The file /cache/recovery.log is not created because the recovery will not start

fiorello said:
The file /cache/recovery.log is not created because the recovery will not start
Click to expand...
Click to collapse
last_kmsg will be created..i need to know where it is having issues..

I am attaching the file that I last_kmsg taken immediately after the restart of the phone

fiorello said:
I am attaching the file that I last_kmsg taken immediately after the restart of the phone
Click to expand...
Click to collapse
it cannot mount the partition thats why it restarts..can you do on a terminal for me a cat /proc/emmc command??so i can check the partitions..

kairi_zeroblade said:
it cannot mount the partition thats why it restarts..can you do on a terminal for me a cat /proc/emmc command??so i can check the partitions..
Click to expand...
Click to collapse
Here's one from my phone, running the system:
Code:
dev: size erasesize name
mmcblk0p20: 000ffa00 00000200 "misc"
mmcblk0p37: 00fffe00 00000200 "recovery"
mmcblk0p36: 01000000 00000200 "boot"
mmcblk0p38: 8bfffc00 00000200 "system"
mmcblk0p27: 00140200 00000200 "local"
mmcblk0p39: 17fffe00 00000200 "cache"
mmcblk0p40: 2d0000000 00000200 "userdata"
mmcblk0p23: 01400000 00000200 "devlog"
mmcblk0p25: 00040000 00000200 "pdata"
mmcblk0p28: 00010000 00000200 "extra"
mmcblk0p34: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p21: 00400000 00000200 "modem_st1"
mmcblk0p22: 00400000 00000200 "modem_st2"
mmcblk0p30: 00040000 00000200 "skylink"
mmcblk0p31: 01900000 00000200 "carrier"
mmcblk0p29: 00100000 00000200 "cdma_record"
mmcblk0p19: 01bffe00 00000200 "reserve_1"
mmcblk0p33: 034ffa00 00000200 "reserve_2"
mmcblk0p35: 05fffc00 00000200 "reserve_3"
mmcblk0p32: 04729a00 00000200 "reserve"
mmcblk0p26: 00004000 00000200 "control"

Result for cat / proc / EMMC attachment

ok so this is the fstab for twrp that its trying to mount..
Code:
# Android fstab file.
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p36
/cache ext4 /dev/block/mmcblk0p39
/data ext4 /dev/block/mmcblk0p40
/recovery emmc /dev/block/mmcblk0p37
/system ext4 /dev/block/mmcblk0p38
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
so everything seems to match..will rebuild in just a while..
edit: new image here..took me around 8 minutes to rebuild..lolz..kindly test and give feedback

To me it does not work: the phone is restarted.

fiorello said:
To me it does not work: the phone is restarted.
Click to expand...
Click to collapse
what recovery are you using recently??

TWRP 2.7.0.0 with SELinux support

fiorello said:
TWRP 2.7.0.0 with SELinux support
Click to expand...
Click to collapse
ok..am doing a rebuild now i think i got the fix..(wink*)
edit: here a new test build

:good: Now the phone easily fits into recovery, and also the problem of charging the phone is off it seems to work well. Now I want to try to do a backup and then a restore. I'll know in a few minutes.
For the moment, thank you very much.:fingers-crossed:
---------- Post added at 03:34 PM ---------- Previous post was at 03:30 PM ----------
Immediately an error: Unable to mount '/ cache'

fiorello said:
:good: Now the phone easily fits into recovery, and also the problem of charging the phone is off it seems to work well. Now I want to try to do a backup and then a restore. I'll know in a few minutes.
For the moment, thank you very much.:fingers-crossed:
Click to expand...
Click to collapse
hit the thanks button..i knew it..it was chickening me out..nonetheless will update this in a few days time..
dump me a recovery log this time..so i can double check..
edit: can you wipe cache and see if it mounts on next reboot?

I did a wipe cache and now it works. I do a backup and a restore and let you know.
---------- Post added at 04:08 PM ---------- Previous post was at 03:50 PM ----------
:good: Backup and Restore completed successfully!!!!

New update virgin mobile

New Update for our phones. Anyone know about this update m Download link for the update. mediafirecom/?ll6h862125c4l5o

Here's info on it
https://community.sprint.com/baw/thread/180988
I would like to know how to install it with a custom recovery.

Me too. I just told it to install and it downloaded, restarted into recovery and didn't do anything.

jmdarling said:
Me too. I just told it to install and it downloaded, restarted into recovery and didn't do anything.
Click to expand...
Click to collapse
need stock recovery

jmdarling said:
Me too. I just told it to install and it downloaded, restarted into recovery and didn't do anything.
Click to expand...
Click to collapse
Same here.

HTC Download Link:
http://dl3.htc.com/application/RUU_..._NV_SPCS_1.08_003_release_403624_signed_2.exe

Confirmed working ...
on Virgin Mobile
jdmedeiros said:
HTC Download Link:
http://dl3.htc.com/application/RUU_..._NV_SPCS_1.08_003_release_403624_signed_2.exe
Click to expand...
Click to collapse

LarryBoyG said:
on Virgin Mobile
Click to expand...
Click to collapse
Error 155!!!!
How to fix it?
Need help

Try making sure HTC sync is closed all the way.

Won't running this RUU wipe our phone?

LarryBoyG said:
Try making sure HTC sync is closed all the way.
Click to expand...
Click to collapse
Security fail!
Maybe need S-OFF?

Igor2906 said:
Security fail!
Maybe need S-OFF?
Click to expand...
Click to collapse
It worked for me on virgin mobile but I got the same error as you on boost. Weird.

jdmedeiros said:
HTC Download Link:
http://dl3.htc.com/application/RUU_..._NV_SPCS_1.08_003_release_403624_signed_2.exe
Click to expand...
Click to collapse
I need this new update for my htc because i have bootloop but its give me 132 error,i think my phone is no virgin..(dont know how to check it) so there is other RUU file what is working on boost/sprint or idk what namr other...?

yeah, im getting the same error.
has anyone found a solution?

All Sprint RUU info in one place
The update: http://dl3.htc.com/application/RUU_..._NV_SPCS_1.08_003_release_403624_signed_2.exe (within which you have rom.zip)
The key file: http://goo.gl/MXyoel
The HBoot file: http://goo.gl/tec0Ph
The Boot image file: http://goo.gl/PHQqjp
The Radio image file: http://goo.gl/Axs0rK
If someone could do the same for a GSM version, like Cricket or Telus, would be great!

jdmedeiros said:
The update: http://dl3.htc.com/application/RUU_..._NV_SPCS_1.08_003_release_403624_signed_2.exe (within which you have rom.zip)
The key file: http://goo.gl/MXyoel
The HBoot file: http://goo.gl/tec0Ph
The Boot image file: http://goo.gl/PHQqjp
The Radio image file: http://goo.gl/Axs0rK
If someone could do the same for a GSM version, like Cricket or Telus, would be great!
Click to expand...
Click to collapse
I'm on cricket and still no update [emoji53]

Any chance you could extract and post your HBoot file and radio.img file? I would appreciate it.
Surj138 said:
I'm on cricket and still no update [emoji53]
Click to expand...
Click to collapse

jdmedeiros said:
Any chance you could extract and post your HBoot file and radio.img file? I would appreciate it.
Click to expand...
Click to collapse
Hi,
Maybe if you post a method (guide) for extracting the HBoot file and the radio.img file, someone will be able to follow your guide and post these two files.
Just a suggestion...

Just a suggestion? You should bang my head with it until I do it... coming up in 1 minute!
moh19814 said:
Hi,
Maybe if you post a method (guide) for extracting the HBoot file and the radio.img file, someone will be able to follow your guide and post these two files.
Just a suggestion...
Click to expand...
Click to collapse
---------- Post added at 02:06 PM ---------- Previous post was at 02:01 PM ----------
Better late than never... I have been asking people to send me the HBoot file and Radio file from Cricket or Telus, but I have failed to detail how this should be done. moh19814 called me out on this and in good time he did. Here it is:
adb shell
su
mkdir /mnt/media_rw/ext_sd/firm_backup/
cd /mnt/media_rw/ext_sd/firm_backup/
cat /proc/emmc
Now, look at the listing (mine is at the bottom of this post) and find the blocks associated with what we want. In my case they were 11, 18 and 20. Continue, but double check before pressing ENTER...
dd if=/dev/block/mmcblk0p11 of=/mnt/media_rw/ext_sd/firm_backup/hboot
dd if=/dev/block/mmcblk0p18 of=/mnt/media_rw/ext_sd/firm_backup/radio_config
dd if=/dev/block/mmcblk0p20 of=/mnt/media_rw/ext_sd/firm_backup/radio
dd if=/dev/block/mmcblk0p25 of=/mnt/media_rw/ext_sd/firm_backup/modem_st1
dd if=/dev/block/mmcblk0p26 of=/mnt/media_rw/ext_sd/firm_backup/modem_st2
ls -l
exit
exit
At this point I looked at my sdcard on Windows but I did not see the firm_backup folder. I properly ejected the phone, removed the usb cable from the computer, connected the phone again and the folder was there and within the folder there was the three files.
[email protected]_a11chl:/mnt/media_rw/ext_sd/firm_backup # cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p1: 00100000 00000200 "sbl1"
mmcblk0p2: 02000000 00000200 "pg1fs"
mmcblk0p3: 00004000 00000200 "board_info"
mmcblk0p4: 00ef7c00 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "sbl1_update"
mmcblk0p8: 00040000 00000200 "rpm"
mmcblk0p9: 00200000 00000200 "tz"
mmcblk0p10: 00008000 00000200 "sdi"
mmcblk0p11: 00400000 00000200 "hboot"
mmcblk0p12: 00500000 00000200 "sp1"
mmcblk0p13: 00100000 00000200 "wifi"
mmcblk0p14: 00008000 00000200 "ddr"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p17: 00500000 00000200 "wcnss"
mmcblk0p18: 00800000 00000200 "radio_config"
mmcblk0p19: 00180000 00000200 "fsg"
mmcblk0p20: 04b00400 00000200 "radio"
mmcblk0p21: 00400000 00000200 "tool_diag"
mmcblk0p22: 00a00000 00000200 "custdata"
mmcblk0p23: 006ffc00 00000200 "reserve_2"
mmcblk0p24: 00100000 00000200 "misc"
mmcblk0p25: 00180000 00000200 "modem_st1"
mmcblk0p26: 00180000 00000200 "modem_st2"
mmcblk0p27: 01400000 00000200 "fataldevlog"
mmcblk0p28: 00001000 00000200 "debug_config"
mmcblk0p29: 00040000 00000200 "pdata"
mmcblk0p30: 00004000 00000200 "control"
mmcblk0p31: 00140400 00000200 "local"
mmcblk0p32: 00010000 00000200 "extra"
mmcblk0p33: 00100000 00000200 "cdma_record"
mmcblk0p34: 00000400 00000200 "fsc"
mmcblk0p35: 00002000 00000200 "ssd"
mmcblk0p36: 00040000 00000200 "skylink"
mmcblk0p37: 01900000 00000200 "carrier"
mmcblk0p38: 01e00000 00000200 "devlog"
mmcblk0p39: 00e28800 00000200 "reserve"
mmcblk0p40: 01000000 00000200 "boot"
mmcblk0p41: 01000000 00000200 "recovery"
mmcblk0p42: 06c00000 00000200 "cache"
mmcblk0p43: 80000000 00000200 "system"
mmcblk0p44: 48000000 00000200 "userdata"
[email protected]_a11chl:/mnt/media_rw/ext_sd/firm_backup #

Purple flashing light
Hi, in a review for the HTC DESIRE 510 i saw a purple flashing light next to front camera, the review was on a boost us model,
Just curious about this flashing light.... due to the fact i dont have this light on my desire 510.

[Q] unable to mount + internal storage 0mb + stuck in hboot

Background :
Rooted phone and installed Cyanogen rom, then installed PackMan rom then HTC Google Edition rom. Everything was working perfect for a year.
The phone was always in protective silicon case and didn't give me any problems.
Problem :
Without installing any new application or change any settings or anything other then normal daily use. One day, out of the blue (didnt fell or anything), the screen wouldn’t turn on, but the screen touch buttons at bottom would lite up.
Did hard reset but then it kept getting stuck or screen again and again, the screen wouldn’t turn on, kept doing more and more and more hard resets. Sometimes after hard reset it would get to the “slide to unlock” screen and once i would unlock it would get stuck, so more hard resets.
Then after the 10th ~ hard reset it seemed to rollback on its own to the factory rom without my apps and contacts. But still get stuck and more hard resets. After the 13th ~ hard reset it got stuck on the green HTC logo with white background.
TWRP shows E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount internal storage
and Internal Storage 0MB
Current status:
Booting directly to hboot menu and nothing else.
Fastboot is working
ADB and ADB Shell is working
Booting into TWRP command : fastboot boot openrecovery-twrp-2.8.3.0-m7.img
Booting into philz command : fastboot boot philz_touch_6.15.4-m7ul.img
I’m not able to get to the RUU mode (black screen with silver HTC logo) !
flashing recovery twrp and then selecting recovery at the hboot menu will not get into twrp. only
fastboot boot openrecovery-twrp-2.8.3.0-m7.img
will get me into twrp
Version :
Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.00000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 4 2013, 14:29:10:-1
Device Screenshots :
From TWRP and philpz
the forum will not let me post outside url image links. you can see the images in the word document i've uploaded
Solution attempts:
TWRP “Restore from backup” failed. And now there are no backups.
Was able to copy zip rom but wasn’t able to install it (cannot mount errors)
I’m not able to get to the RUU mode (black screen with silver HTC logo)
found many posts in many forms and youtube videos but wasn't able to fix
output of 'fastboot getvar all' :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.631.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT367W913960
(bootloader) imei: 354439051186122
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4270mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.044s
“fastboot oem lock” output :
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.244s
“fastboot oem rebootRUU” reboots back to hboot menu.
I’m not able to get to the RUU mode (black screen with silver HTC logo) !
Getting ADB to respond :
“adb devices” command output :
List of devices attached
HT***numbers**** sideload
“adb shell“ command output:
error: closed
the forum will not let me post outside url image links. you can see the images in the word document i've uploaded
Then
“adb shell“ command output:
~ # ←[6n
Which is good!
according to htcdev.com/bootloader/rom_flashing_guide#flashing_from_device
“cd /proc/” command output :
cd /proc/
~ # ←[6ncd /proc/
“cat emmc/” command output
cat emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
/proc # ←[6n
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p33
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p33
12968+0 records in
12968+0 records out
6639616 bytes (6.3MB) copied, 2.222748 seconds, 2.8MB/s
/proc # ←[6nreboot
Ouput of command “adb shell dmesg > dmesg_log1.txt” is attached
Important to notice in the dmesg :
<3>[ 15.868743] EXT4-fs (mmcblk0p37): VFS: Can't find ext4 filesystem
<3>[ 16.723510] EXT4-fs (mmcblk0p36): VFS: Can't find ext4 filesystem
this is the closest posts I could find :
http://forum.xda-developers.com/showthread.php?t=2300511
http://forum.xda-developers.com/htc-one/help/0-mb-internal-storage-t2993567
I am completely lost and miss my HTC. any advise?

shariksharik said:
TWRP shows E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount internal storage
and Internal Storage 0MB
Click to expand...
Click to collapse
Corrupted data partition? Boot twrp 2.6.3.3 go in wipe --> format data --> then reboot the recovery and see if your Internal storage is showing the correct size instead of 0MB. If yes push and flash a rom.
What version of ADB and HTC drivers that you are using?
What is very strange is that you can't boot in ruu mode and that you can't flash the recovery. Just in case, have you erased cache and rebooted the bootloader after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Im starting to think your phone is having an hardware problem. Would explain why it bootlooped and that your bootloader looks bricked.
Where is parition p25? It should be listed when you do "cat proc/emmc"
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
mmcblk0p25 ???
Click to expand...
Click to collapse

first of all thank you for your quick response.
I will try to answer everything you wrote in the best accuracy and details i can.
Boot twrp 2.6.3.3 go in wipe --> format data --> then reboot the recovery and see if your Internal storage is showing the correct size instead of 0MB.
Click to expand...
Click to collapse
i did this
Code:
fastboot boot openrecovery-twrp-2.6.3.3-m7.img
it loaded twrp
i did "wipe ->format data" results attached.
then i did reboot , it got me back to the hboot menu
to enter twrp i again
Code:
fastboot boot openrecovery-twrp-2.6.3.3-m7.img
and internal storage still 0MB
and the output is :
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
What version of ADB and HTC drivers that you are using?
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.31
how do I know what version of HTC drivers i am using? according to the Device Manager there is "HTC MTP Device" under "Portable Devices" node its version is 1.0.0.20. is this what you meant? btw there is a small yellow warning triangle on that "HTC MTP Device". not sure if it should be like that.
have you erased cache and rebooted the bootloader after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
where can i get recovery.img ? do you mean recovery.img is openrecovery-twrp-2.6.3.3-m7.img ? can you give me more input on this ?
Where is parition p25? It should be listed when you do "cat proc/emmc"
Click to expand...
Click to collapse
i noticed that i can use adb only with openrecovery-twrp-2.8.3.0-m7.img and not with 2.6.3.3
i ran
Code:
cat emmc
again and confirmed p25 is not there. to be fair if you look here "htcdev.com/bootloader/rom_flashing_guide#flashing_from_device" also dont have p25, my output is exactly as the one in that link.

i did "wipe ->format data" results attached.
Click to expand...
Click to collapse
forgot to attach the result. now attached

Sadly probably a bad EMMC. This means it is able to mouth the drive, and the ability to only boot TWRP 2.8.3.0 (pushes it self to the memory completely b4 running, uses no Storage space) and not older versions (which don't) only reaffirms that sad reality. The fact that you can't boot to recovery from HBOOT reaffirms it again, as HBOOT mounts system and then finds the recovery partition to boot by looking in the mount area symlinks on the system partition, which in your case, doesn't exist.
The other possibility is a corrupted partition map, but that would most likely require JTAG recovery, which you can google, bit is ridiculously hard.
Another possibility is using a debrick image and pushing it through QCOM download mode, but I'm unsure of how to get to QCOM mode on the M7 (maybe try googling it?)
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
Ok. Wait I failed to read the cat prof output, huh, so the eMMC is mounting, must be a faulty partition map. Use ext4unpacker to check and see if that recovery IMG you made is legit, or broken, if its a legit IMG, then that could help us out [emoji14]
---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------
Hmmm. May have figured it out. If you accidentally used a recovery meant for a slightly different m7, wiping data could have wiped a low level boot loader partition instead...

thank you for replying .
npjohnson said:
Use ext4unpacker to check and see if that recovery IMG you made is legit, or broken, if its a legit IMG, then that could help us out
Click to expand...
Click to collapse
what recovery IMG that I made? i didnt make any recovery.
can you give me more details about ext4unpacker . i found this http://forum.xda-developers.com/showthread.php?t=2294909 , will this help me?
npjohnson said:
Hmmm. May have figured it out. If you accidentally used a recovery meant for a slightly different m7, wiping data could have wiped a low level boot loader partition instead...
Click to expand...
Click to collapse
yes it is possible i did flash something that was not meant exactly for my m7....

My bad, you made a boot image with Dd=. Could you use the same method to dump your system and recovery partitions?
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
And then just google how to extract a system.IMG. it will probably require ext4unpacker.

npjohnson said:
My bad, you made a boot image with Dd=.
Click to expand...
Click to collapse
you are correct, i did try to put a boot.img that i found online but i am not sure its 100% for my device version, it was a "hail marry" attempt.
npjohnson said:
Could you use the same method to dump your system and recovery partitions?
And then just google how to extract a system.IMG. it will probably require ext4unpacker.
Click to expand...
Click to collapse
i'm sorry i am somewhat a noob in linux and the core stuff like adb and fastboot, i learned what i could from other posts and tutorials. i didn't understand what you meant, if i will dump system.img and recovery.img partitions why would i need to extract them afterwords ?

i've been writing back and forth with HTC, i gave them all this info and they gave me a zip (1.1GB) to flash.
PN07IMG_M7_UL_JB43_SENSE50_MR_Rogers_WWE_3.22.631.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336568_signed_2.zip
however, after i've downloaded the zip, if i try to open it with winzip it will say "Error: central directory not found" , this tells me that it might be corrupted download, so i downloaded it again and again and again, using chrome, using explorer, it keeps saying the same. i've also opened it in winrar and it does show me the content. inside i can see :
boot_signed.img (6.5 MB)
recovery_signed.img (12 MB)
system.img (1,879 MB)
and other files.
but i can't seem to extract them.
any advise?

why not?
I do not understand what is the use of packing the opened in ext4_unpacker .img file into .ext4 file and extracting it with ext2explore afterwards!?!
It is just simple way to extract [Alt+E] all bunch right away from ext4_unpacker window:
My Question is:
if there is the same easy way for Windows OS to compile the extracted system folder back to .img file AND make the system.new.dat file for Lollipop ROM ?

Nar4 said:
I do not understand what is the use of packing the opened in ext4_unpacker .img file into .ext4 file and extracting it with ext2explore afterwards!?!
It is just simple way to extract [Alt+E] all bunch right away from ext4_unpacker window:
My Question is:
if there is the same easy way for Windows OS to compile the extracted system folder back to .img file AND make the system.new.dat file for Lollipop ROM ?
Click to expand...
Click to collapse
im sorry for asking, how is this related to the thread?

Same problem on my OnePlus ONe
@shariksharik, Do you get any resolution for the same?

I'm here for same problems, anyone solved it?

[Q] HTC Desire 626s - Need Root/Recovery

Hey everyone!
I am trying to get root access to my HTC Desire 626s.
I have been able to unlock it via HTCDev site.
At this point I believe I need to get root access.. I have tried the one click option Kingroot which was unsuccessful.. It always stops at 16-17%....
I believe I can obtain root access by flashing a CWM recovery which would have to be built for the 626s..
I am not sure if builder.clockworkmod.com is still functional?
Is anyone able to build a CWM recovery for this device? If so what would I need to provide?
Any help or responses would be much appreciated!
EDIT: Dump from /proc/emmc
130|[email protected]_a32eul:/ $ cat /proc/emmc
dev: size erasesize name
mmcblk0p1: 00004000 00000200 "board_info"
mmcblk0p2: 00400000 00000200 "pg1fs"
mmcblk0p3: 00100000 00000200 "sbl1"
mmcblk0p4: 01af7c00 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "rpm"
mmcblk0p8: 00200000 00000200 "tz"
mmcblk0p9: 00400000 00000200 "aboot"
mmcblk0p10: 00a00000 00000200 "sp1"
mmcblk0p11: 00008000 00000200 "ddr"
mmcblk0p12: 00100000 00000200 "rfg_0"
mmcblk0p13: 00100000 00000200 "rfg_1"
mmcblk0p14: 00100000 00000200 "rfg_2"
mmcblk0p15: 00100000 00000200 "rfg_3"
mmcblk0p16: 00100000 00000200 "rfg_4"
mmcblk0p17: 00100000 00000200 "rfg_5"
mmcblk0p18: 00100000 00000200 "rfg_6"
mmcblk0p19: 00100000 00000200 "rfg_7"
mmcblk0p20: 00180000 00000200 "fsg"
mmcblk0p21: 03b00400 00000200 "radio"
mmcblk0p22: 00a00000 00000200 "tool_diag"
mmcblk0p23: 00500000 00000200 "wcnss"
mmcblk0p24: 00000400 00000200 "limits"
mmcblk0p25: 00447c00 00000200 "reserve_2"
mmcblk0p26: 00100000 00000200 "misc"
mmcblk0p27: 00001000 00000200 "debug_config"
mmcblk0p28: 00180000 00000200 "modem_st1"
mmcblk0p29: 00180000 00000200 "modem_st2"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p31: 01600000 00000200 "persist"
mmcblk0p32: 00004000 00000200 "sec"
mmcblk0p33: 00100000 00000200 "cdma_record"
mmcblk0p34: 00000400 00000200 "fsc"
mmcblk0p35: 00002000 00000200 "ssd"
mmcblk0p36: 00020000 00000200 "rfg_8"
mmcblk0p37: 00020000 00000200 "rfg_9"
mmcblk0p38: 00020000 00000200 "rfg_10"
mmcblk0p39: 00020000 00000200 "rfg_11"
mmcblk0p40: 00020000 00000200 "rfg_12"
mmcblk0p41: 00020000 00000200 "rfg_13"
mmcblk0p42: 00020000 00000200 "rfg_14"
mmcblk0p43: 00020000 00000200 "rfg_15"
mmcblk0p44: 00004000 00000200 "control"
mmcblk0p45: 00010000 00000200 "extra"
mmcblk0p46: 00140400 00000200 "local"
mmcblk0p47: 00040000 00000200 "skylink"
mmcblk0p48: 02800000 00000200 "carrier"
mmcblk0p49: 00080000 00000200 "frp"
mmcblk0p50: 01400000 00000200 "fataldevlog"
mmcblk0p51: 01e00000 00000200 "devlog"
mmcblk0p52: 00a00000 00000200 "ramdump"
mmcblk0p53: 00a00000 00000200 "battery"
mmcblk0p54: 01000000 00000200 "absolute"
mmcblk0p55: 023a4800 00000200 "reserve"
mmcblk0p56: 03000000 00000200 "hosd"
mmcblk0p57: 02000000 00000200 "boot"
mmcblk0p58: 02000000 00000200 "recovery"
mmcblk0p59: 10000000 00000200 "cache"
mmcblk0p60: a0000000 00000200 "system"
mmcblk0p61: 12000000 00000200 "apppreload"
mmcblk0p62: 02800000 00000200 "cota"
mmcblk0p63: f0000000 00000200 "userdata"
When attempting to dd the recovery block I get an error since I don't have permission.
dd if=/dev/block/mmcblk0p58 of=/sdcard2/recovery.img

Was this the app or pc version of kingroot that failed?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

Anyone able to root this yet ?

http://forum.xda-developers.com/showthread.php?t=3181038 I made a thread got the stock recovery
Sent from my LGMS345 using Tapatalk

Just picked up this phone, awaiting a way to root, kingroot and kingoroot do not work. Cricket 626S. Already ran htcdev on it, need recovery to install supersu.

Update on Root?
I was hesitant to buy a new phone from MetroPCS lineup given that I was aware a root would not be available. This phone is great but has so much more capability. Not writing to SD card is crazy. You can trasnfer files on a PC between internal storage and SD. Anyway enough said. Does anyone have any updates on a root?

i found a thread with the stock recovery, i do not understand how to create a custom recovery ive gone over it over and over. i also tried the clockworkmod builder but it doesnt seem to be working i just get 404 errors. here is the link to the thread its the op. hopefully some one can make a custom recovery
http://forum.xda-developers.com/general/xda-assist/htc-desire-626s-cwm-build-t3181038

I'm also interested in this. I spent most of my time trying to extract the stock recovery from the RUU (which you can download from HTC's website, then extract using instructions here on XDA. It's basically starting the exe, then going to your temp directory). Some of the files can be extracted, but I think the others are encrypted. I've read that HTC started doing this a while back.
If the above link really is a copy of the stock recovery (and I'm curious to know how this was obtained), then we may be able to build CWM following these instructions- http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
Or maybe we also need the boot.img. I can't remember if this was one of the files I was able to extract from the RUU. Either way, there's some process by which we should be able to create a custom recovery.
Once we have something built and want to test it, you can try to boot your phone into the recovery without actually flashing it by running
Code:
fastboot boot recovery.img
. See these links- https://aubykhan.wordpress.com/2013/07/21/android-tip-boot-into-twrp-or-cwm-recovery-without-flashing/ http://androidforums.com/threads/stock-recovery-partition-image-backup.612148/ http://optionkey.blogspot.com/2013/12/backing-up-your-android-phones-stock.html
I'm kinda busy the next few weeks, but I definitely want to work on this when I get the chance some time. This is about the extent of what I know at this point. Have at it.

i tried that one, wont boot with fastboot boot cmd, says its a incomplete boot image

Here's something else worth looking into -https://twitter.com/srsroot/status/639544040489357312?s=09 which links to http://www.srsroot.com
If that doesn't work, it appears we can modify the boot.img file to gain root adb. I found it here http://androidforums.com/threads/htc-desire-626s-root.946455/ with more detailed instructions here http://android.stackexchange.com/questions/28653/obtaining-root-by-modifying-default-propro-secure
Again, I'll try this sometime, but I'll be pretty busy for a while.

k, ill take a looksie
edit: problem with this is, we need boot.img, but we can only get that with root xd

I might have that file. HTC posts their RUU files on their developer website. There are instructions floating around here showing how to extract them. It didn't have recovery, but it might have had boot.img. I just got to work, but I'll check when I get home.
Edit: Just check on TeamViewer. I've got a boot_signed.img file. We might be in business.

k man, that root kit doesnt work either im afraid
tried a few times
but is there a safe way to test the bootimg? can we boot that like we do recovery?

Perhaps you could boot it through fastboot, but I'm not finding any mention of it online. I'll probably give it a shot. Whenever I get to make it, I'll flash it on my device. Even if it's bad, we ought to be able to boot into fastboot and reflash the stock boot image. If that even fails, we have an RUU from HTC that should completely restore everything. And if THAT fails, then I wouldn't mind helping myself to the new Nexus 5X

lolol, i see how it is xD
here is hoping that it goes bad huh?

I tried modding the boot.img file I pulled from the RUU. I flashed it, and my phone booted fine, but didn't seem to have any root access via adb or terminal. I tried "adb root", but apparently you need a modded version of the adbd binary per this page- http://bclary.com/blog/2014/04/14/splitting-and-packing-android-boot-images/. I followed these instructions http://forum.xda-developers.com/showthread.php?t=2593581 and included an insecure adbd, but this made my phone go into a bootloop.
I was able to reflash the stock boot.img (from the RUU) after each time with no troubles. So, no bricks, but no root yet either. I notice that my device still has "s-on". Haven't been an HTC guy before, but I think that needs to be "s-off". I'll try again some other time.
Just to be thorough (in case anyone else wants to try), these tools helped to unpack the boot.img file - http://forum.xda-developers.com/showthread.php?t=1494036

i been a htc user for a few years now, and although i always got s-off before, im almost 100% certain that for gaining root its not needed.
unlocking bootloader should be enough, if we can get a custom recovery on it that is...

It may be worth investigating other ways of modifying the boot.img to give us root access over adb, but it seems that we need a version of adbd that won't cause a bootloop. I should mention that whenever I used the modified adbd binary (which always made it bootloop), I got a red warning/copyright message really quickly. It said something like "this HTC development something is property of HTC". I never got that message when I only modified default.prop.
A custom recovery would be the best option for sure. There's a post on XDA University about making CWM for a new device, and this method needs the boot.img (unlike the other method, which needs the recovery.img we don't have apparently). Reading the instructions, I'm not entirely sure it works for devices CM doesn't support, since it makes mention of the device codename, but I'm hopeful. Since I know for a fact we have a working stock boot.img (my phone is using it to boot now, lol), this looks like a good option.
---------- Post added at 08:57 AM ---------- Previous post was at 08:57 AM ----------
It may be worth investigating other ways of modifying the boot.img to give us root access over adb, but it seems that we need a version of adbd that won't cause a bootloop. I should mention that whenever I used the modified adbd binary (which always made it bootloop), I got a red warning/copyright message really quickly. It said something like "this HTC development something is property of HTC". I never got that message when I only modified default.prop.
A custom recovery would be the best option for sure. There's a post on XDA University about making CWM for a new device, and this method needs the boot.img (unlike the other method, which needs the recovery.img we don't have apparently). Reading the instructions, I'm not entirely sure it works for devices CM doesn't support, since it makes mention of the device codename, but I'm hopeful. Since I know for a fact we have a working stock boot.img (my phone is using it to boot now, lol), this looks like a good option.

well, we could always try TWRP recovery, if CWM doesnt work
Edit, thanx to another member here, i got files from a RUU, for the 626s, dont think that changes much, that "S"
anyway, in it i got boot, aboot, recovery etc, do you think we can do stuff with it?

From my understanding you need to set Selinux to permissive for an insecure boot.img to work on lollipop. I am unaware on how to do this but I believe we need to wait for HTC to post the Kernel source on HTCdev in order to do this.