Database Users

Radio block?

Hi ppl
Can someone tell me or link me.. As to which mmcblk represents radio?
Or if someone can kindly post the output of this command (need to be done after su).. It will be greatly appreciated
adb shell
su
cat /proc/emmc/
Thanks
Sent from my HTC Sensation 4G using xda premium

Code:
# cat /proc/emmc
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 22dffe00 00000200 "system"
mmcblk0p27: 12bffe00 00000200 "cache"
mmcblk0p26: 496ffe00 00000200 "userdata"
mmcblk0p28: 014bfe00 00000200 "devlog"
mmcblk0p29: 00040000 00000200 "pdata"
#
Sent from my HTC Glacier using Tapatalk 2

Sim Unlock. Free!! - CONFIRMED WORKING

CONFIRMED WORKING
No CDMA like Sprint or Verizon. Feel free to test though
EDIT: Sprint See http://forum.xda-developers.com/sprint-one-m9/general/nv-unlocksim-t3314755
Hey guys.
I recently purchased a HTC M9 Sprint with the hopes that I could unlock it. Unfortunately I was not able to
Anyway brought a AT&T version (that arrived yesterday) and started to have a play with it.
First things first:
HTC DEV bootloader unlock
TWRP install
SU
S-Off via Sunshine (optional)
Now for the fun
I dumped all the partitions (except userdata as it was 28GB lol). Then started to work on the Sim Unlock. My attempt via the method that i posted here did not work for me. I then decided to try my luck with a code from Ebay. I got one for US $4 which was pretty good. Took a few hours, but sure enough I received an email with a code. I started a logcat and then entered the SIM Unlock code and to my surprise it WORKED . Nothing interesting in the logcat though
I then dumped all the partitions again (except userdata)
Here is the list BTW:
Code:
dev: size erasesize name
mmcblk0p1: 00004000 00000200 "board_info"
mmcblk0p2: 00400000 00000200 "pg1fs"
mmcblk0p3: 00100000 00000200 "sbl1"
mmcblk0p4: 00100000 00000200 "pmic"
mmcblk0p5: 02800000 00000200 "dummy"
mmcblk0p6: 001f7c00 00000200 "reserve_1"
mmcblk0p7: 00040000 00000200 "mfg"
mmcblk0p8: 017afc00 00000200 "pg2fs"
mmcblk0p9: 00080000 00000200 "rpm"
mmcblk0p10: 00200000 00000200 "tz"
mmcblk0p11: 00018000 00000200 "sdi"
mmcblk0p12: 00200000 00000200 "hyp"
mmcblk0p13: 00100000 00000200 "aboot"
mmcblk0p14: 00a00000 00000200 "tool_diag"
mmcblk0p15: 00a00000 00000200 "sp1"
mmcblk0p16: 00100000 00000200 "ddr"
mmcblk0p17: 00100000 00000200 "rfg_0"
mmcblk0p18: 00100000 00000200 "rfg_1"
mmcblk0p19: 00100000 00000200 "rfg_2"
mmcblk0p20: 00100000 00000200 "rfg_3"
mmcblk0p21: 00100000 00000200 "rfg_4"
mmcblk0p22: 00100000 00000200 "rfg_5"
mmcblk0p23: 00100000 00000200 "rfg_6"
mmcblk0p24: 00100000 00000200 "rfg_7"
mmcblk0p25: 00180000 00000200 "fsg"
mmcblk0p26: 03b00400 00000200 "radio"
mmcblk0p27: 01400000 00000200 "adsp"
mmcblk0p28: 00000400 00000200 "limits"
mmcblk0p29: 004f7c00 00000200 "reserve_2"
mmcblk0p30: 01600000 00000200 "persist"
mmcblk0p31: 00a00000 00000200 "ramdump"
mmcblk0p32: 00100000 00000200 "misc"
mmcblk0p33: 00180000 00000200 "modem_st1"
mmcblk0p34: 00180000 00000200 "modem_st2"
mmcblk0p35: 01400000 00000200 "fataldevlog"
mmcblk0p36: 01e00000 00000200 "devlog"
mmcblk0p37: 00040000 00000200 "pdata"
mmcblk0p38: 00004000 00000200 "control"
mmcblk0p39: 00010000 00000200 "extra"
mmcblk0p40: 00100000 00000200 "cdma_record"
mmcblk0p41: 00000400 00000200 "fsc"
mmcblk0p42: 00002000 00000200 "ssd"
mmcblk0p43: 00080000 00000200 "sensor_hub"
mmcblk0p44: 00020000 00000200 "sec"
mmcblk0p45: 00100000 00000200 "abootbak"
mmcblk0p46: 00002800 00000200 "cir_img"
mmcblk0p47: 00140400 00000200 "local"
mmcblk0p48: 00080000 00000200 "frp"
mmcblk0p49: 00200000 00000200 "cpe"
mmcblk0p50: 01400000 00000200 "carrier"
mmcblk0p51: 00040000 00000200 "skylink"
mmcblk0p52: 00020000 00000200 "rfg_8"
mmcblk0p53: 00020000 00000200 "rfg_9"
mmcblk0p54: 00020000 00000200 "rfg_10"
mmcblk0p55: 00020000 00000200 "rfg_11"
mmcblk0p56: 00020000 00000200 "rfg_12"
mmcblk0p57: 00020000 00000200 "rfg_13"
mmcblk0p58: 00020000 00000200 "rfg_14"
mmcblk0p59: 00020000 00000200 "rfg_15"
mmcblk0p60: 01000000 00000200 "absolute"
mmcblk0p61: 00e07000 00000200 "reserve"
mmcblk0p62: 04000000 00000200 "hosd"
mmcblk0p63: 04000000 00000200 "boot"
mmcblk0p64: 04000000 00000200 "recovery"
mmcblk0p65: 14000000 00000200 "cache"
mmcblk0p66: 18000000 00000200 "system"
mmcblk0p67: e0000000 00000200 "userdata"
mmcblk0p68: 12200000 00000200 "apppreload"
mmcblk0p69: 03c00000 00000200 "cota"
mmcblk0p70: 00a00000 00000200 "battery"
Now for the actual fun. I compared every single partition before and after the SIM Lock trying to find a difference. There were many differences between files as they are not 'static' and used by the system. (This was done from recovery BTW).
I was looking for a small difference such as that of the bootloader lock / unlock which you only have to change a small amount of data.
Something that stood out was mmcblk0p52 which is "rfg_8" and I only noticed this because I had made two dump before Sim Unlocking and it was THE ONLY PAIR OF DUMPS THAT MATCHED.
The files themselves aren't that big so I thought what the hell.
I flashed (dd) the 'before sim unlock' mmcblk0p52 and it was SIM LOCKED again
I then flashed (dd) the after 'after sim unlock' mmcblk0p52 and it was SIM UNLOCKED again
If you could help by getting your mmcblkop52 to me I can then compare and see if this will equal a free SIM UNLOCK for you.
AT&T No longer need Files are the same
T-Mobile No longer need Files are the same
Sprint Partition is empty, all 0's - will need to find another way
Verizon I assume it is the same as Sprint.
Others??
Please use the following code:
Code:
adb shell
su
dd if=/dev/block/bootdevice/by-name/rfg_8 of=/sdcard/rfg_8old
exit
exit
adb pull /sdcard/rfg_8old
Then upload the rfg_8old and link to me.
To Sim unlock your device
Do the above and save it to you computer. Download my rfg_8-Locked.txt and compare the two files.
You can do this using HxD from here http://mh-nexus.de/en/hxd/
Drag both files (locked partitions) into HxD and press Ctrl + K or go to File > Analysis > File-Compare > Compare....
It will prop up 'both files are identical'
If there is a file difference then STOP
If the file is the same then you can do the following:
Please copy and paste one line at a time
[Irfg_8-UnLocked.txt must be in your ADB directory OR manually place on the root of internal SD Card and rename to rfg_8 [/I]
Code:
adb push rfg_8-UnLocked.txt /sdcard/rfg_8new
adb shell
su
dd if=/sdcard/rfg_8new of=/dev/block/bootdevice/by-name/rfg_8
exit
exit
Please use the Poll above and leave a comment
Please don't forget to click the thanks button or donate to me http://forum.xda-developers.com/donatetome.php?u=4428363
This took a lot of time and effort. The (at least) $5 it would have cost you for the unlock code, could be put to better use
Thanks for the support guys
Stifilz
THANKS TO:
@grim489 for dumping the mmcblk0p52 from T-Mobile (which I found was an exact match)
@bigp951 for dumping the mmcblk0p52 from AT&T locked sim (which I found was an exact match)
@bigp951 for dumping the mmcblk0p52 from DEV Edition factory unlocked sim (which I found was empty 0's, probably due to never being locked)
@bigp951 for testing the Unlocked partition on AT&T and confirming it worked
@WildsideUK for confirming that this works while S-On

Interesting. I'll look into this.
Sent From My HTC One (M9)

M9 Sprint
Do you think it will work with my sprint M9?

Here is my mmcblk0p52, I am sim locked to T-Mobile. Haven't got around to trying the international software/firmware with your other unlock thread but managed to get this. :good:

elmy2424 said:
Do you think it will work with my sprint M9?
Click to expand...
Click to collapse
Not at the moment. I have a sprint M9 and have not managed to get it working with this method

grim489 said:
Here is my mmcblk0p52, I am sim locked to T-Mobile. Haven't got around to trying the international software/firmware with your other unlock thread but managed to get this. :good:
Click to expand...
Click to collapse
OMFG. THE FILE IS IDENTICAL TO MY SIM LOCKED PARTITION. FEEL FREE TO USE HxD TO 'FILE COMPARE' THE HEX VALUES YOURSELF. IF YOU ARE KEEN THEN PLEASE FLASH MY UNLOCKED PARTITION. BE VERY CAREFUL WITH THE DD COMMAND!
Obviously reverse the DD command
Do it in recovery or normal and then reboot.
Can you please dump the partition after too. Here is HxD (I love this software)
Drag both files (locked partitions) into HxD and press Ctrl + K or go to File > Analysis > File-Compare > Compare....
It will prop up 'both files are identical'
Thank you @grim489, credits to you

Gotta find somebody's sim to steal and test but it's no problem I'm just doing the simple stuff haha. Let me get back to you in a little bit stifilz, gonna try it out.
Sent from my HTC One M9 using Tapatalk

are you inside US , i think sprint is unlocking their phones for free, just have to call them,

grim489 said:
Gotta find somebody's sim to steal and test but it's no problem I'm just doing the simple stuff haha. Let me get back to you in a little bit stifilz, gonna try it out.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Awaiting anxiously
In the mean time can someone that is Sim Unlocked please dump their mmcblk0p52

Here is mine. AT&T SIM locked. I just added .txt to the end.

stifilz said:
Awaiting anxiously
In the mean time can someone that is Sim Unlocked please dump their mmcblk0p52
Click to expand...
Click to collapse
would the dev edition dump work? I have one of those as well...

bigp951 said:
would the dev edition dump work? I have one of those as well...
Click to expand...
Click to collapse
Yup. That would help check the 'unlock' image

stifilz said:
Yup. That would help check the 'unlock' image
Click to expand...
Click to collapse
Here you go!
dev edition---

I hope this works because I bought an AT&T m9 today for my wife but we are on T-mobile. Only thing is I know nothing about dd commands so would need instructions like in the OP.

bigp951 said:
I hope this works because I bought an AT&T m9 today for my wife but we are on T-mobile. Only thing is I know nothing about dd commands so would need instructions like in the OP.
Click to expand...
Click to collapse
Ok first thing you will need to do is dump the current mmcblk0p52 (same as first OP). Pull this files to computer. Download my mmcblk0p52-rfg_8-Locked.txt (LOCKED VERSION) and compare the two files using HxD or similar.
IF they are the same then you can proceed to flash the my mmcblk0p52-rfg_8-UnLocked.txt(UNLOCKED) file.
Code:
adb push mmcblk0p52-rfg_8-UnLocked /sdcard/mmcblk0p52
adb shell
su
dd if=/sdcard/mmcblk0p52 of=/dev/block/mmcblk0p52
exit
exit
Please proceed at your own risk
Thanks

bigp951 said:
here is mine. At&t sim locked. I just added .txt to the end.
Click to expand...
Click to collapse
exactly the same as mine
bigp951 said:
Here you go!
dev edition---
Click to expand...
Click to collapse
DEV edition is BLANK (file is all zeros) this could make sense as it was never Sim locked and therefore does not need to be unlocked

stifilz said:
Ok first thing you will need to do is dump the current mmcblk0p52 (same as first OP). Pull this files to computer. Download my mmcblk0p52-rfg_8-Locked.txt (LOCKED VERSION) and compare the two files using HxD or similar.
IF they are the same then you can proceed to flash the my mmcblk0p52-rfg_8-UnLocked.txt(UNLOCKED) file.
Code:
adb push mmcblk0p52-rfg_8-UnLocked /sdcard/mmcblk0p52
adb shell
su
dd if=/sdcard/mmcblk0p52 of=/dev/block/mmcblk0p52
exit
exit
Please proceed at your own risk
Thanks
Click to expand...
Click to collapse
I am ready to attempt this but am curious to what my chances are for a hard brick? I will copy and paste your commands
I have a nandroid on my sd card so I should be able to recover from anything minor.
EDIT--strangely enough when I attempted to push the file to the sd card this came back...
failed to copy 'mmcblk0p52-rfg_8-UnLocked' to '/sdcard/mmcblk0p52': Permission d
enied
I will put the file in the sd card manually and proceed from there

bigp951 said:
I am ready to attempt this but am curious to what my chances are for a hard brick? I will copy and paste your commands
I have a nandroid on my sd card so I should be able to recover from anything minor.
Click to expand...
Click to collapse
I am fairly certain that it will be the correct file. I don't have another partition of someone that has Sim Unlocked before (I only have my one). I assume that it is not Unlock Code specific. I have flashed to my Sprint M9 to no avail (this had 0's before like your dev edition). Also no damage to the phone
Hardbrick would be HIGHLY UNLIKELY. I have put my HTC's though the wars and they have always came back to me. As long as you are S-OFF you can recover from almost anything. Copy and paste and double check everything .
Best of luck :good:

bigp951 said:
EDIT--strangely enough when I attempted to push the file to the sd card this came back...
failed to copy 'mmcblk0p52-rfg_8-UnLocked' to '/sdcard/mmcblk0p52': Permission d
enied
I will put the file in the sd card manually and proceed from there
Click to expand...
Click to collapse
mmcblk0p52-rfg_8-UnLocked (note .txt has been removed) will need to be in the folder where your ADB is

IT WORKED!

HTC ONE M9+ Stock Backup, Stock Recovery and OTA Update Collection -- Taiwanese Versi

I just collected the M9+ files and shared them.
Thanks for all on this forum and M9's ,especially @xiaolongzi & @tbalden .
No need to s-off and relock your devices.S-ON is OK.
Use it at your own risk.
I only got the files for TW version and here was my device variable.
CID:HTC__621
MID:0PK711000
Code:
E:\M9pw>htc_fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: zzzzzz...
(bootloader) version-main: 1.84.709.10
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTC__621
all:
finished. total time: 0.005s
htc_fastboot finished. total time: 0.637s
Repack TWRP recovery to backup/restore system image.
Or you could also flash system simply with htc fastboot.
It will elapse long time,not hang.Be patient.
Code:
E:\M9pw>[COLOR="Red"]htc_fastboot flash system M9pw_system_1.08.709.4.img[/COLOR]
htc_fastboot v3.0.8a (2015-04-10)
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.517s]
sending sparse 'system' (779021 KB)...
OKAY [ 73.094s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 20.873s]
sending sparse 'system' (780715 KB)...
OKAY [ 71.325s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 20.986s]
sending sparse 'system' (742840 KB)...
OKAY [ 52.445s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 20.518s]
sending sparse 'system' (773764 KB)...
OKAY [ 54.045s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 20.707s]
sending sparse 'system' (775393 KB)...
OKAY [ 67.296s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 20.849s]
sending sparse 'system' (37096 KB)...
OKAY [ 4.051s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.934s]
finished. total time: 428.716s
htc_fastboot finished. total time: 780.562s
If you wanna apply OTA successfully.
0.Backup your system.
Backup your system.
Backup your system. And then get the ball rolling.....
1.restore stock recovery
2.restore unmodified system image
3.receive OTA and apply it.
4.re-rooted and reflashed Xposed if you would like to use them.
Code:
E:\M9pw>[COLOR="Red"]htc_fastboot flash recovery recovery_verified.img__TW_1.61.709.3[/COLOR]
htc_fastboot v3.0.8a (2015-04-10)
target reported max download size of 800000000 bytes
sending 'recovery' (9710 KB)...
OKAY [ 1.468s]
writing 'recovery'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.205s]
finished. total time: 2.673s
htc_fastboot finished. total time: 5.350s
E:\M9pw>[COLOR="Red"]htc_fastboot flash system system.emmc.win[/COLOR]
htc_fastboot v3.0.8a (2015-04-10)
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.915s]
sending sparse 'system' (778345 KB)...
OKAY [ 55.609s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 20.834s]
sending sparse 'system' (779605 KB)...
OKAY [ 73.650s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 20.995s]
sending sparse 'system' (745409 KB)...
OKAY [ 94.247s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 20.291s]
sending sparse 'system' (771737 KB)...
OKAY [ 66.736s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 20.797s]
sending sparse 'system' (769584 KB)...
OKAY [ 51.970s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 20.733s]
sending sparse 'system' (81928 KB)...
OKAY [ 6.598s]
writing 'system'...
(bootloader) HOSD CL#549681
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.039s]
finished. total time: 456.633s
htc_fastboot finished. total time: 1278.643s
E:\M9pw>fastboot reboot
rebooting...
finished. total time: 0.066s

RUU
http://forum.xda-developers.com/one-m9/one-m9-general/ruu-m9-ruu-file-t3152206
http://forum.xda-developers.com/showpost.php?p=61801034&postcount=8
http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/HIAU_ML_TUHL/
Stock Recovery
http://forum.xda-developers.com/one-m9/one-m9-general/firmware-stock-recoveries-regions-t3120826
Taiwan
recovery_verified.img__TW_1.08.709.4
MD5: d93fb2a3843ad97469db5c87b21d68e8 *recovery_verified.img__TW_1.08.709.4
d98c9906fe60b35d1811897d932d535d recovery_verified.img__TW_1.90.709.3
https://drive.google.com/open?id=0B3hc3jLpl2YxZi1iQTRDWmhRY0E
A2C42813F6212364C91D7B0A2667E3FB recovery_verified.img__TW_2.27.709.1
https://drive.google.com/open?id=0B3hc3jLpl2YxTEkyVWs0dEQ5c0U
63DA5CED55C9811AFD7E7BE0197CC689 recovery_verified.img__TW_2.30.709.1
https://drive.google.com/open?id=0B3hc3jLpl2YxSkE4YVR2M19NRkk
OTA
View attachment FOTA_HIAU_ML_TUHL.txt
Syatem Image Backup
https://drive.google.com/open?id=0B3hc3jLpl2YxYlNuN3RBbmF0SEU
You must unzip the file first and then flash it in download mode,not in recovery.
TWRP unmodify system image backup
M9pw_system_1.08.709.4.zip
2c72d70a9a1ac65bb441d75f1e3659e3 M9pw_system_1.08.709.4.img
https://drive.google.com/open?id=0B3hc3jLpl2YxcHJTRU0yOEpNMGs
M9pw_system_1.90.709.3.zip
4b9f53acd50a1931b27227d728d61de4 system_image.emmc.win
https://drive.google.com/open?id=0B3hc3jLpl2YxVy1Da2txTjhRa2M
M9pw_system_2.27.709.1.zip
adc323ff38b1acfa4dd3b49ea9259c85 system_image.emmc.win
https://drive.google.com/open?id=0B3hc3jLpl2YxRVNyZ0p3UHc1RU0
M9pw_system_2.30.709.1.zip
5f7a0df14ac944155d6a423c04e998d6 system_image.emmc.win
https://drive.google.com/open?id=0B3hc3jLpl2YxT2VWUEpjSEpYVkk

great idea. very nice, lots of work put in to get all these together. thanks!

Sorry if this post is not in the right place but I am new to this forum business, I'm looking for a flashable stock kernel for the HTC One M9. Can anyone help please.. thank you
Sent from my HTC One M9 using XDA Premium HD app

I need，Thank you, my fellow~
J:\HTC M9+\刷機\htc_fastboot_3.0.8>C:\windows\system32\cmd.exe
Microsoft Windows [版本 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
J:\HTC M9+\刷機\htc_fastboot_3.0.8>fastboot flash system M9pw_system_1.84.709.10
.img
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 3.795s]
sending sparse 'system' (769872 KB)...
OKAY [ 27.367s]
writing 'system'...
(bootloader) HOSD CL#573107
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 24.136s]
sending sparse 'system' (767085 KB)...
OKAY [ 28.053s]
writing 'system'...
(bootloader) HOSD CL#573107
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 23.059s]
sending sparse 'system' (766498 KB)...
OKAY [ 28.287s]
writing 'system'...
(bootloader) HOSD CL#573107
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 23.070s]
sending sparse 'system' (771721 KB)...
OKAY [ 28.293s]
writing 'system'...
(bootloader) HOSD CL#573107
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 23.233s]
sending sparse 'system' (779880 KB)...
OKAY [ 28.557s]
writing 'system'...
(bootloader) HOSD CL#573107
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 23.463s]
sending sparse 'system' (93416 KB)...
OKAY [ 5.329s]
writing 'system'...
(bootloader) HOSD CL#573107
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.592s]
finished. total time: 270.264s
Click to expand...
Click to collapse

kano k said:
Sorry if this post is not in the right place but I am new to this forum business, I'm looking for a flashable stock kernel for the HTC One M9. Can anyone help please.. thank you
Sent from my HTC One M9 using XDA Premium HD app
Click to expand...
Click to collapse
Hi
You have the device M9,not M9+.
You should find the files you need in this thread.
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
If you wanna stock kernel file, extract firmware.zip from OTA.zip,and then again extract boot_signed.img from firmware.zip.
That's what you want.
http://forum.xda-developers.com/showpost.php?p=61286824&postcount=3

Hello Guys
I ( and a lot of others out there ) need the stock recovery of Our One ME ( same as M9+ ) but dual sim
I am dying to root my phone but can't as i will lose OTA updates unless i have the stock recovery
Can anybody assist us and extract the stock recovery or know where to get it
and thanks in advance

shouk_1987 said:
Hello Guys
I ( and a lot of others out there ) need the stock recovery of Our One ME ( same as M9+ ) but dual sim
I am dying to root my phone but can't as i will lose OTA updates unless i have the stock recovery
Can anybody assist us and extract the stock recovery or know where to get it
and thanks in advance
Click to expand...
Click to collapse
This is M9pw(One M9+) emmc partitions:
Code:
[email protected]_hiau_ml_tuhl:/ $ cat /proc/emmc
cat /proc/emmc
partno: start_sect nr_sects partition_name
mmcblk0p1: 00000400 00001800 "proinfo"
mmcblk0p2: 00001c00 00002800 "nvram"
mmcblk0p3: 00004400 00005000 "protect1"
mmcblk0p4: 00009400 00005000 "protect2"
mmcblk0p5: 0000e400 00018000 "persist"
mmcblk0p6: 00026400 00000800 "kb"
mmcblk0p7: 00026c00 00000800 "dkb"
mmcblk0p8: 00027400 00000200 "seccfg"
mmcblk0p9: 00027600 00002000 "pg1fs"
mmcblk0p10: 00029600 00006a00 "reserve1"
mmcblk0p11: 00030000 00008000 "pg2fs"
mmcblk0p12: 00038000 00000800 "lk"
mmcblk0p13: 00038800 00003000 "secro"
mmcblk0p14: 0003b800 00000400 "para"
mmcblk0p15: 0003bc00 00004000 "logo"
mmcblk0p16: 0003fc00 00000400 "frp"
mmcblk0p17: 00040000 00010000 "hosd"
mmcblk0p18: 00050000 00000800 "htcsec"
mmcblk0p19: 00050800 00005000 "tool_diag"
mmcblk0p20: 00055800 0000a800 "reserve2"
mmcblk0p21: 00060000 0000a000 "fataldevlog"
mmcblk0p22: 0006a000 0000a000 "devlog"
mmcblk0p23: 00074000 00005000 "expdb"
mmcblk0p24: 00079000 00002800 "tee1"
mmcblk0p25: 0007b800 00002800 "tee2"
mmcblk0p26: 0007e000 00010000 "metadata"
mmcblk0p27: 0008e000 00000800 "lkbackup"
mmcblk0p28: 0008e800 00020000 "otafw"
mmcblk0p29: 000ae800 00000400 "sensor_hub"
mmcblk0p30: 000aec00 00000040 "cir_img"
mmcblk0p31: 000aec40 0000a000 "carrier"
mmcblk0p32: 000b8c40 00000040 "control"
mmcblk0p33: 000b8c80 00005000 "battery"
mmcblk0p34: 000bdc80 00091000 "apppreload"
mmcblk0p35: 0014ec80 0001e000 "cota"
mmcblk0p36: 0016cc80 00000080 "extra"
mmcblk0p37: 0016cd00 00000040 "andinfo"
mmcblk0p38: 0016cd40 000032c0 "reserve"
mmcblk0p39: 00170000 000a0000 "cache"
mmcblk0p40: 00210000 00010000 "boot"
mmcblk0p41: 00220000 00010000 "recovery"
mmcblk0p42: 00230000 00938000 "system"
mmcblk0p43: 00b68000 02ec4000 "userdata"
mmcblk0p44: 03a2c000 00008000 "flashinfo"
[email protected]_hiau_ml_tuhl:/ $
while m9ew (One ME) is
Code:
[email protected]_hima_ace_ml_dtul:/ $ cat /proc/emmc
partno: start_sect nr_sects partition_name
mmcblk0p1: 00000400 00001800 "proinfo"
mmcblk0p2: 00001c00 00002800 "nvram"
mmcblk0p3: 00004400 00005000 "protect1"
mmcblk0p4: 00009400 00005000 "protect2"
mmcblk0p5: 0000e400 00018000 "persist"
mmcblk0p6: 00026400 00000800 "kb"
mmcblk0p7: 00026c00 00000800 "dkb"
mmcblk0p8: 00027400 00000200 "seccfg"
mmcblk0p9: 00027600 00002000 "pg1fs"
mmcblk0p10: 00029600 00006a00 "reserve1"
mmcblk0p11: 00030000 00008000 "pg2fs"
mmcblk0p12: 00038000 00000800 "lk"
mmcblk0p13: 00038800 00003000 "secro"
mmcblk0p14: 0003b800 00000400 "para"
mmcblk0p15: 0003bc00 00004000 "logo"
mmcblk0p16: 0003fc00 00000400 "frp"
mmcblk0p17: 00040000 00010000 "hosd"
mmcblk0p18: 00050000 00000800 "htcsec"
mmcblk0p19: 00050800 00005000 "tool_diag"
mmcblk0p20: 00055800 0000a800 "reserve2"
mmcblk0p21: 00060000 0000a000 "fataldevlog"
mmcblk0p22: 0006a000 0000a000 "devlog"
mmcblk0p23: 00074000 00005000 "expdb"
mmcblk0p24: 00079000 00002800 "tee1"
mmcblk0p25: 0007b800 00002800 "tee2"
mmcblk0p26: 0007e000 00010000 "metadata"
mmcblk0p27: 0008e000 00000800 "lkbackup"
mmcblk0p28: 0008e800 00020000 "otafw"
mmcblk0p29: 000ae800 00000400 "sensor_hub"
mmcblk0p30: 000aec00 00000040 "cir_img"
mmcblk0p31: 000aec40 0000a000 "carrier"
mmcblk0p32: 000b8c40 00000040 "control"
mmcblk0p33: 000b8c80 00005000 "battery"
mmcblk0p34: 000bdc80 00091000 "apppreload"
mmcblk0p35: 0014ec80 0001e000 "cota"
mmcblk0p36: 0016cc80 00000080 "extra"
mmcblk0p37: 0016cd00 00000040 "andinfo"
mmcblk0p38: 0016cd40 000032c0 "reserve"
mmcblk0p39: 00170000 000a0000 "cache"
mmcblk0p40: 00210000 00010000 "boot"
mmcblk0p41: 00220000 00010000 "recovery"
mmcblk0p42: 00230000 00938000 "system"
mmcblk0p43: 00b68000 02ec4000 "userdata"
mmcblk0p44: 03a2c000 00008000 "flashinfo"
So, maybe M9+ and ME could use the same "custom" recovery.
But you must choose the accurate recovery file for the stock one to get OTA.
You could find the one by means of 0PLAIMG_HIMA_ACE_ML_DTUL.

yvtc75 said:
This is M9pw(One M9+) emmc partitions:
Code:
[email protected]_hiau_ml_tuhl:/ $ cat /proc/emmc
cat /proc/emmc
partno: start_sect nr_sects partition_name
mmcblk0p1: 00000400 00001800 "proinfo"
mmcblk0p2: 00001c00 00002800 "nvram"
mmcblk0p3: 00004400 00005000 "protect1"
mmcblk0p4: 00009400 00005000 "protect2"
mmcblk0p5: 0000e400 00018000 "persist"
mmcblk0p6: 00026400 00000800 "kb"
mmcblk0p7: 00026c00 00000800 "dkb"
mmcblk0p8: 00027400 00000200 "seccfg"
mmcblk0p9: 00027600 00002000 "pg1fs"
mmcblk0p10: 00029600 00006a00 "reserve1"
mmcblk0p11: 00030000 00008000 "pg2fs"
mmcblk0p12: 00038000 00000800 "lk"
mmcblk0p13: 00038800 00003000 "secro"
mmcblk0p14: 0003b800 00000400 "para"
mmcblk0p15: 0003bc00 00004000 "logo"
mmcblk0p16: 0003fc00 00000400 "frp"
mmcblk0p17: 00040000 00010000 "hosd"
mmcblk0p18: 00050000 00000800 "htcsec"
mmcblk0p19: 00050800 00005000 "tool_diag"
mmcblk0p20: 00055800 0000a800 "reserve2"
mmcblk0p21: 00060000 0000a000 "fataldevlog"
mmcblk0p22: 0006a000 0000a000 "devlog"
mmcblk0p23: 00074000 00005000 "expdb"
mmcblk0p24: 00079000 00002800 "tee1"
mmcblk0p25: 0007b800 00002800 "tee2"
mmcblk0p26: 0007e000 00010000 "metadata"
mmcblk0p27: 0008e000 00000800 "lkbackup"
mmcblk0p28: 0008e800 00020000 "otafw"
mmcblk0p29: 000ae800 00000400 "sensor_hub"
mmcblk0p30: 000aec00 00000040 "cir_img"
mmcblk0p31: 000aec40 0000a000 "carrier"
mmcblk0p32: 000b8c40 00000040 "control"
mmcblk0p33: 000b8c80 00005000 "battery"
mmcblk0p34: 000bdc80 00091000 "apppreload"
mmcblk0p35: 0014ec80 0001e000 "cota"
mmcblk0p36: 0016cc80 00000080 "extra"
mmcblk0p37: 0016cd00 00000040 "andinfo"
mmcblk0p38: 0016cd40 000032c0 "reserve"
mmcblk0p39: 00170000 000a0000 "cache"
mmcblk0p40: 00210000 00010000 "boot"
mmcblk0p41: 00220000 00010000 "recovery"
mmcblk0p42: 00230000 00938000 "system"
mmcblk0p43: 00b68000 02ec4000 "userdata"
mmcblk0p44: 03a2c000 00008000 "flashinfo"
[email protected]_hiau_ml_tuhl:/ $
while m9ew (One ME) is
Code:
[email protected]_hima_ace_ml_dtul:/ $ cat /proc/emmc
partno: start_sect nr_sects partition_name
mmcblk0p1: 00000400 00001800 "proinfo"
mmcblk0p2: 00001c00 00002800 "nvram"
mmcblk0p3: 00004400 00005000 "protect1"
mmcblk0p4: 00009400 00005000 "protect2"
mmcblk0p5: 0000e400 00018000 "persist"
mmcblk0p6: 00026400 00000800 "kb"
mmcblk0p7: 00026c00 00000800 "dkb"
mmcblk0p8: 00027400 00000200 "seccfg"
mmcblk0p9: 00027600 00002000 "pg1fs"
mmcblk0p10: 00029600 00006a00 "reserve1"
mmcblk0p11: 00030000 00008000 "pg2fs"
mmcblk0p12: 00038000 00000800 "lk"
mmcblk0p13: 00038800 00003000 "secro"
mmcblk0p14: 0003b800 00000400 "para"
mmcblk0p15: 0003bc00 00004000 "logo"
mmcblk0p16: 0003fc00 00000400 "frp"
mmcblk0p17: 00040000 00010000 "hosd"
mmcblk0p18: 00050000 00000800 "htcsec"
mmcblk0p19: 00050800 00005000 "tool_diag"
mmcblk0p20: 00055800 0000a800 "reserve2"
mmcblk0p21: 00060000 0000a000 "fataldevlog"
mmcblk0p22: 0006a000 0000a000 "devlog"
mmcblk0p23: 00074000 00005000 "expdb"
mmcblk0p24: 00079000 00002800 "tee1"
mmcblk0p25: 0007b800 00002800 "tee2"
mmcblk0p26: 0007e000 00010000 "metadata"
mmcblk0p27: 0008e000 00000800 "lkbackup"
mmcblk0p28: 0008e800 00020000 "otafw"
mmcblk0p29: 000ae800 00000400 "sensor_hub"
mmcblk0p30: 000aec00 00000040 "cir_img"
mmcblk0p31: 000aec40 0000a000 "carrier"
mmcblk0p32: 000b8c40 00000040 "control"
mmcblk0p33: 000b8c80 00005000 "battery"
mmcblk0p34: 000bdc80 00091000 "apppreload"
mmcblk0p35: 0014ec80 0001e000 "cota"
mmcblk0p36: 0016cc80 00000080 "extra"
mmcblk0p37: 0016cd00 00000040 "andinfo"
mmcblk0p38: 0016cd40 000032c0 "reserve"
mmcblk0p39: 00170000 000a0000 "cache"
mmcblk0p40: 00210000 00010000 "boot"
mmcblk0p41: 00220000 00010000 "recovery"
mmcblk0p42: 00230000 00938000 "system"
mmcblk0p43: 00b68000 02ec4000 "userdata"
mmcblk0p44: 03a2c000 00008000 "flashinfo"
So, maybe M9+ and ME could use the same "custom" recovery.
But you must choose the accurate recovery file for the stock one to get OTA.
You could find the one by means of 0PLAIMG_HIMA_ACE_ML_DTUL.
Click to expand...
Click to collapse
Thanks mate for your reply
We have been confirmed that TWRP for M9+ works for us but the issue that we need stock recovery such that if an OTA update is available we can restore the untouched system partition and flash stock recovery again
How can we get the stock recovery zip image, that is our main concern
Sent from my HTC One ME dual sim using XDA Free mobile app

shouk_1987 said:
Thanks mate for your reply
We have been confirmed that TWRP for M9+ works for us but the issue that we need stock recovery such that if an OTA update is available we can restore the untouched system partition and flash stock recovery again
How can we get the stock recovery zip image, that is our main concern
Sent from my HTC One ME dual sim using XDA Free mobile app
Click to expand...
Click to collapse
Check this thread for One ME http://forum.xda-developers.com/one-m9/one-m9-general/ruu-htc-one-m9ew-ruus-hboot-zips-t3211628
(smaller HBoot zip contains stock recovery, but that still might be not enough, as backing up untouched system image and restoring it on m9+ didn't really work, no one could get OTA working with TWRP backups on m9+ even with R/O system partition backups restored and stock recoveries flashed!!).
But in that thread you'll find the full RUUs too, hopefully fitting your region. If not, then you'll need S-Off probably and all the fuss, as no-one tested how these firmwares work on different regions models and M9ew one me.
http://forum.xda-developers.com/one-m9/one-m9-general/ruu-htc-one-m9ew-ruus-hboot-zips-t3211628

tbalden said:
Check this thread for One ME http://forum.xda-developers.com/one-m9/one-m9-general/ruu-htc-one-m9ew-ruus-hboot-zips-t3211628
(smaller HBoot zip contains stock recovery, but that still might be not enough, as backing up untouched system image and restoring it on m9+ didn't really work, no one could get OTA working with TWRP backups on m9+ even with R/O system partition backups restored and stock recoveries flashed!!).
But in that thread you'll find the full RUUs too, hopefully fitting your region. If not, then you'll need S-Off probably and all the fuss, as no-one tested how these firmwares work on different regions models and M9ew one me.
http://forum.xda-developers.com/one-m9/one-m9-general/ruu-htc-one-m9ew-ruus-hboot-zips-t3211628
Click to expand...
Click to collapse
Thanks a lot mate
But that's kinda of a bad news
To lose OTA after all this waiting and hustle
I am kinda of noob with htc as this is the 1st device to me with the Taiwanese brand
What is the difference between Full RUU anf normal RUU
Also can you direct me to the threads where it guides me to use the RUU or the hboot and the exact differences between them
Thx a lot mate again
Sent from my HTC One ME dual sim using XDA Free mobile app

i have 1.85.401.6
cid: HTC__J15
what is the proper recovery
Thanks alot
Sent from my HTC One M9PLUS using Tapatalk

mh7 said:
i have 1.85.401.6
cid: HTC__J15
what is the proper recovery
Thanks alot
Sent from my HTC One M9PLUS using Tapatalk
Click to expand...
Click to collapse
If you have an ir-file account , i don't have one, follow the 2nd post to get RUU file from
http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/HIAU_ML_TUHL/
You could extract your recovery file from
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_MR_HTC_Europe_1.85.401.6_Radio_1.1506V24P21.2005.0505_HT[W.T]_release_446584_signed_Hboot.zip
Or wait for others to share European's stock recovery file.
--------edit ---------------
Here you are.
http://forum.xda-developers.com/one-m9/one-m9-general/ruu-htc-one-m9-1-85-401-6-t3218717

Ota 1.08.707.4
Someone please share the OTA 1.08.707.4 file, I'm unable to apply the ota from the phone even my phone is not rooted.

razarahil said:
Someone please share the OTA 1.08.707.4 file, I'm unable to apply the ota from the phone even my phone is not rooted.
Click to expand...
Click to collapse
If your firmware(Hboot) is still 1.08.707.4, try the RUU.
http://forum.xda-developers.com/showpost.php?p=61801034&postcount=8

Did you know where can I find these images for an htc one m9pw CID:HTC__622 MID:0PK711000?

Android M Rom already?

JuanKca said:
Android M Rom already?
Click to expand...
Click to collapse
Nope.
Android M for M9+,ME,M9++ was planed on Q1 2016.
http://llabtoofer.com/2015/12/10/htc-software-updates-plan-q1-q2-2016/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks for you reply, well we'll have to wait until they release the official Rom.

yvtc75 said:
This is M9pw(One M9+) emmc partitions:
Code:
[email protected]_hiau_ml_tuhl:/ $ cat /proc/emmc
cat /proc/emmc
partno: start_sect nr_sects partition_name
mmcblk0p1: 00000400 00001800 "proinfo"
mmcblk0p2: 00001c00 00002800 "nvram"
mmcblk0p3: 00004400 00005000 "protect1"
mmcblk0p4: 00009400 00005000 "protect2"
mmcblk0p5: 0000e400 00018000 "persist"
mmcblk0p6: 00026400 00000800 "kb"
mmcblk0p7: 00026c00 00000800 "dkb"
mmcblk0p8: 00027400 00000200 "seccfg"
mmcblk0p9: 00027600 00002000 "pg1fs"
mmcblk0p10: 00029600 00006a00 "reserve1"
mmcblk0p11: 00030000 00008000 "pg2fs"
mmcblk0p12: 00038000 00000800 "lk"
mmcblk0p13: 00038800 00003000 "secro"
mmcblk0p14: 0003b800 00000400 "para"
mmcblk0p15: 0003bc00 00004000 "logo"
mmcblk0p16: 0003fc00 00000400 "frp"
mmcblk0p17: 00040000 00010000 "hosd"
mmcblk0p18: 00050000 00000800 "htcsec"
mmcblk0p19: 00050800 00005000 "tool_diag"
mmcblk0p20: 00055800 0000a800 "reserve2"
mmcblk0p21: 00060000 0000a000 "fataldevlog"
mmcblk0p22: 0006a000 0000a000 "devlog"
mmcblk0p23: 00074000 00005000 "expdb"
mmcblk0p24: 00079000 00002800 "tee1"
mmcblk0p25: 0007b800 00002800 "tee2"
mmcblk0p26: 0007e000 00010000 "metadata"
mmcblk0p27: 0008e000 00000800 "lkbackup"
mmcblk0p28: 0008e800 00020000 "otafw"
mmcblk0p29: 000ae800 00000400 "sensor_hub"
mmcblk0p30: 000aec00 00000040 "cir_img"
mmcblk0p31: 000aec40 0000a000 "carrier"
mmcblk0p32: 000b8c40 00000040 "control"
mmcblk0p33: 000b8c80 00005000 "battery"
mmcblk0p34: 000bdc80 00091000 "apppreload"
mmcblk0p35: 0014ec80 0001e000 "cota"
mmcblk0p36: 0016cc80 00000080 "extra"
mmcblk0p37: 0016cd00 00000040 "andinfo"
mmcblk0p38: 0016cd40 000032c0 "reserve"
mmcblk0p39: 00170000 000a0000 "cache"
mmcblk0p40: 00210000 00010000 "boot"
mmcblk0p41: 00220000 00010000 "recovery"
mmcblk0p42: 00230000 00938000 "system"
mmcblk0p43: 00b68000 02ec4000 "userdata"
mmcblk0p44: 03a2c000 00008000 "flashinfo"
[email protected]_hiau_ml_tuhl:/ $
while m9ew (One ME) is
Code:
[email protected]_hima_ace_ml_dtul:/ $ cat /proc/emmc
partno: start_sect nr_sects partition_name
mmcblk0p1: 00000400 00001800 "proinfo"
mmcblk0p2: 00001c00 00002800 "nvram"
mmcblk0p3: 00004400 00005000 "protect1"
mmcblk0p4: 00009400 00005000 "protect2"
mmcblk0p5: 0000e400 00018000 "persist"
mmcblk0p6: 00026400 00000800 "kb"
mmcblk0p7: 00026c00 00000800 "dkb"
mmcblk0p8: 00027400 00000200 "seccfg"
mmcblk0p9: 00027600 00002000 "pg1fs"
mmcblk0p10: 00029600 00006a00 "reserve1"
mmcblk0p11: 00030000 00008000 "pg2fs"
mmcblk0p12: 00038000 00000800 "lk"
mmcblk0p13: 00038800 00003000 "secro"
mmcblk0p14: 0003b800 00000400 "para"
mmcblk0p15: 0003bc00 00004000 "logo"
mmcblk0p16: 0003fc00 00000400 "frp"
mmcblk0p17: 00040000 00010000 "hosd"
mmcblk0p18: 00050000 00000800 "htcsec"
mmcblk0p19: 00050800 00005000 "tool_diag"
mmcblk0p20: 00055800 0000a800 "reserve2"
mmcblk0p21: 00060000 0000a000 "fataldevlog"
mmcblk0p22: 0006a000 0000a000 "devlog"
mmcblk0p23: 00074000 00005000 "expdb"
mmcblk0p24: 00079000 00002800 "tee1"
mmcblk0p25: 0007b800 00002800 "tee2"
mmcblk0p26: 0007e000 00010000 "metadata"
mmcblk0p27: 0008e000 00000800 "lkbackup"
mmcblk0p28: 0008e800 00020000 "otafw"
mmcblk0p29: 000ae800 00000400 "sensor_hub"
mmcblk0p30: 000aec00 00000040 "cir_img"
mmcblk0p31: 000aec40 0000a000 "carrier"
mmcblk0p32: 000b8c40 00000040 "control"
mmcblk0p33: 000b8c80 00005000 "battery"
mmcblk0p34: 000bdc80 00091000 "apppreload"
mmcblk0p35: 0014ec80 0001e000 "cota"
mmcblk0p36: 0016cc80 00000080 "extra"
mmcblk0p37: 0016cd00 00000040 "andinfo"
mmcblk0p38: 0016cd40 000032c0 "reserve"
mmcblk0p39: 00170000 000a0000 "cache"
mmcblk0p40: 00210000 00010000 "boot"
mmcblk0p41: 00220000 00010000 "recovery"
mmcblk0p42: 00230000 00938000 "system"
mmcblk0p43: 00b68000 02ec4000 "userdata"
mmcblk0p44: 03a2c000 00008000 "flashinfo"
So, maybe M9+ and ME could use the same "custom" recovery.
But you must choose the accurate recovery file for the stock one to get OTA.
You could find the one by means of 0PLAIMG_HIMA_ACE_ML_DTUL.
Click to expand...
Click to collapse
Sorry guys for resurrecting such an old thread but I'd be glad if someone could at least summarize what these partitions might contain.
Thanks in advance

Sim Unlock Free!!

CONFIRMED WORKING
No CDMA like Sprint or Verizon. Feel free to test though
Sprint See here
Hey guys.
See my work for HTC M9 unlock here http://forum.xda-developers.com/one-m9/general/sim-unlock-method-t3143333
Once again I have done it with a similar method to before.....
Anway, to SIM UNLOCK YOUR 626 PLEASE FOLLOW BELOW
First things first:
HTC DEV bootloader unlock
TWRP install
SU
S-Off via Sunshine (optional)
Now for the fun
I then dumped all the partitions.
Here is the list BTW:
Code:
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"
Something that stood out (just like on the M9) was mmcblk0p36 which is "rfg_8" as the unlock partition on the M9 was also rfg_8.
With the help of @kristid1991 and a remote connection,
I compared the rfg_8 from the 626 and compared it to mine from the M9 and THEY WERE THE SAME.
So I flashed (dd) the 'sim unlock' mmcblk0p36 and it was SIM UNLOCKED again
To Sim unlock your device
Please use the following code:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p36 of=/sdcard/mmcblk0p36old
exit
exit
adb pull /sdcard/mmcblk0p36old
Do the above and save it to you computer. Download my mmcblk0p36-rfg_8-Locked.txt and compare the two files.
You can do this using HxD from here http://mh-nexus.de/en/hxd/
Drag both files (locked partitions) into HxD and press Ctrl + K or go to File > Analysis > File-Compare > Compare....
It will prop up 'both files are identical'
If there is a file difference then STOP
If the file is the same then you can do the following:
Please copy and paste one line at a time
mmcblk0p36-rfg_8-UnLocked.txt must be in your ADB directory OR manually place on the root of internal SD Card and rename to mmcblk0p36new
Code:
adb push mmcblk0p36-rfg_8-UnLocked.txt /sdcard/mmcblk0p36new
adb shell
su
dd if=/sdcard/mmcblk0p36new of=/dev/block/mmcblk0p36
exit
exit
Please use the Poll above and leave a comment
Please don't forget to click the thanks button or donate to me http://forum.xda-developers.com/donatetome.php?u=4428363
This took a lot of time and effort. The (at least) $5 it would have cost you for the unlock code, could be put to better use
Thanks for the support guys
Stifilz
THANKS TO:
@kristid1991 for the remote connection to UNLOCK 626

Missing files??
Sorry but the backups of the mentioned emmc partition are not here i tried the ones from m9 unlock but no dice have you forgot to upload them?
stifilz said:
CONFIRMED WORKING
No CDMA like Sprint or Verizon. Feel free to test though
Sprint See here
Hey guys.
See my work for HTC M9 unlock here http://forum.xda-developers.com/one-m9/general/sim-unlock-method-t3143333
Once again I have done it with a similar method to before.....
Anway, to SIM UNLOCK YOUR 626 PLEASE FOLLOW BELOW
First things first:
HTC DEV bootloader unlock
TWRP install
SU
S-Off via Sunshine (optional)
Now for the fun
I then dumped all the partitions.
Here is the list BTW:
Code:
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"
Something that stood out (just like on the M9) was mmcblk0p36 which is "rfg_8" as the unlock partition on the M9 was also rfg_8.
With the help of @kristid1991 and a remote connection,
I compared the rfg_8 from the 626 and compared it to mine from the M9 and THEY WERE THE SAME.
So I flashed (dd) the 'sim unlock' mmcblk0p36 and it was SIM UNLOCKED again
To Sim unlock your device
Please use the following code:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p36 of=/sdcard/mmcblk0p36old
exit
exit
adb pull /sdcard/mmcblk0p36old
Do the above and save it to you computer. Download my mmcblk0p36-rfg_8-Locked.txt and compare the two files.
You can do this using HxD from here http://mh-nexus.de/en/hxd/
Drag both files (locked partitions) into HxD and press Ctrl + K or go to File > Analysis > File-Compare > Compare....
It will prop up 'both files are identical'
If there is a file difference then STOP
If the file is the same then you can do the following:
Please copy and paste one line at a time
mmcblk0p36-rfg_8-UnLocked.txt must be in your ADB directory OR manually place on the root of internal SD Card and rename to mmcblk0p36new
Code:
adb push mmcblk0p36-rfg_8-UnLocked.txt /sdcard/mmcblk0p36new
adb shell
su
dd if=/sdcard/mmcblk0p36new of=/dev/block/mmcblk0p36
exit
exit
Please use the Poll above and leave a comment
Please don't forget to click the thanks button or donate to me http://forum.xda-developers.com/donatetome.php?u=4428363
This took a lot of time and effort. The (at least) $5 it would have cost you for the unlock code, could be put to better use
Thanks for the support guys
Stifilz
THANKS TO:
@kristid1991 for the remote connection to UNLOCK 626
Click to expand...
Click to collapse

dbstrand24 said:
Sorry but the backups of the mentioned emmc partition are not here i tried the ones from m9 unlock but no dice have you forgot to upload them?
Click to expand...
Click to collapse
Oops, forgot to upload
Edit: uploaded now. Please post results after. Thanks

Fingers crossed!
I have rebooted after wiping cache and dalvic Hope it works
:good::good::good::good:
stifilz said:
Oops, forgot to upload
Edit: uploaded now. Please post results after. Thanks
Click to expand...
Click to collapse
---------- Post added at 12:15 PM ---------- Previous post was at 12:09 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But my variant MAY be different i have a desire 626s from Metro PCS, so silly im trying to unlock it to use on t-mobile and its a MVNO of t-mobile i shouldnt HAVE to unlock...
emmc partitions
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_conf
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_recor
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 "fataldevlo
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"
Tell me if i can add any more info to help out

dbstrand24 said:
I have rebooted after wiping cache and dalvic Hope it works
:good::good::good::good:
---------- Post added at 12:15 PM ---------- Previous post was at 12:09 PM ----------
But my variant MAY be different i have a desire 626s from Metro PCS, so silly im trying to unlock it to use on t-mobile and its a MVNO of t-mobile i shouldnt HAVE to unlock...
emmc partitions
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_conf
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_recor
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 "fataldevlo
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"
Tell me if i can add any more info to help out
Click to expand...
Click to collapse
Dump your 36 partition and upload it

stifilz said:
Oops, forgot to upload
Edit: uploaded now. Please post results after. Thanks
Click to expand...
Click to collapse
It worked fine on my AT&T 626
thank you

clsA said:
It worked fine on my AT&T 626
thank you
Click to expand...
Click to collapse
Here is my partiotion I tried to flash T-Mobile RUU was unsucsessfull file size errors... I also tried to set SuperCID this also failed i assume i need s-off for this?
http://b34st.mooo.com/mmcblk0p36.txt
---------- Post added at 04:18 AM ---------- Previous post was at 04:17 AM ----------
Please vote yes
clsA said:
It worked fine on my AT&T 626
thank you
Click to expand...
Click to collapse

dbstrand24 said:
Here is my partiotion I tried to flash T-Mobile RUU was unsucsessfull file size errors... I also tried to set SuperCID this also failed i assume i need s-off for this?
http://b34st.mooo.com/mmcblk0p36.txt
---------- Post added at 04:18 AM ---------- Previous post was at 04:17 AM ----------
Please vote yes
Click to expand...
Click to collapse
your file is the same as the locked one... did you follow the instructions correctly ?
I don't have s-off and it worked first try.
Also, where is this t-mobile RUU you mentioned I found it here http://www.htc.com/us/support/rom-downloads.html
both T-Mobile/Metro PCS use the same RUU so what was your error ?

Followed to a T i'm honestly no n00b with this stuff been working with cell phones since 2008 and the ruu i downloaded straight from HTC's support site, the file match error i know for a fact is because the CID is incorrect now.
*** I DO Know for a fact that this sim had a CLONED sim in it when i got it, so it may be on a blacklist...***
When i put the cloned sim in i get "4gLTE" symbol just no connectivity
http://www.htc.com/us/support/rom-downloads.html

RUU Errors
I actually couldn't get the RUU package to run properly on windows 7 so i pulled the rom.zip out and tried to manually flash it after t-mobile failed i pretty much gave up, no further testing was done, though i will get back to it again tonight
ALSO the metro and t-mobile RUU are different sizes so clearly not same RUU
clsA said:
your file is the same as the locked one... did you follow the instructions correctly ?
I don't have s-off and it worked first try.
Also, where is this t-mobile RUU you mentioned I found it here http://www.htc.com/us/support/rom-downloads.html
both T-Mobile/Metro PCS use the same RUU so what was your error ?
Click to expand...
Click to collapse

dbstrand24 said:
I actually couldn't get the RUU package to run properly on windows 7 so i pulled the rom.zip out and tried to manually flash it after t-mobile failed i pretty much gave up, no further testing was done, though i will get back to it again tonight
ALSO the metro and t-mobile RUU are different sizes so clearly not same RUU
Click to expand...
Click to collapse
Not sure it's worth it on this phone, but you could use Sunshine and S-Off the phone and use any RUU you want.
changing the CID and MID is very easy on these HTC Phones with S-Off
Back on Topic, the above instructions work fine to unlock this phone.

stifilz said:
CONFIRMED WORKING
No CDMA like Sprint or Verizon. Feel free to test though
Sprint See here
Hey guys.
See my work for HTC M9 unlock here http://forum.xda-developers.com/one-m9/general/sim-unlock-method-t3143333
Once again I have done it with a similar method to before.....
Anway, to SIM UNLOCK YOUR 626 PLEASE FOLLOW BELOW
First things first:
HTC DEV bootloader unlock
TWRP install
SU
S-Off via Sunshine (optional)
Now for the fun
I then dumped all the partitions.
Here is the list BTW:
Code:
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"
Something that stood out (just like on the M9) was mmcblk0p36 which is "rfg_8" as the unlock partition on the M9 was also rfg_8.
With the help of @kristid1991 and a remote connection,
I compared the rfg_8 from the 626 and compared it to mine from the M9 and THEY WERE THE SAME.
So I flashed (dd) the 'sim unlock' mmcblk0p36 and it was SIM UNLOCKED again
To Sim unlock your device
Please use the following code:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p36 of=/sdcard/mmcblk0p36old
exit
exit
adb pull /sdcard/mmcblk0p36old
Do the above and save it to you computer. Download my mmcblk0p36-rfg_8-Locked.txt and compare the two files.
You can do this using HxD from here http://mh-nexus.de/en/hxd/
Drag both files (locked partitions) into HxD and press Ctrl + K or go to File > Analysis > File-Compare > Compare....
It will prop up 'both files are identical'
If there is a file difference then STOP
If the file is the same then you can do the following:
Please copy and paste one line at a time
mmcblk0p36-rfg_8-UnLocked.txt must be in your ADB directory OR manually place on the root of internal SD Card and rename to mmcblk0p36new
Code:
adb push mmcblk0p36-rfg_8-UnLocked.txt /sdcard/mmcblk0p36new
adb shell
su
dd if=/sdcard/mmcblk0p36new of=/dev/block/mmcblk0p36
exit
exit
Please use the Poll above and leave a comment
Please don't forget to click the thanks button or donate to me http://forum.xda-developers.com/donatetome.php?u=4428363
This took a lot of time and effort. The (at least) $5 it would have cost you for the unlock code, could be put to better use
Thanks for the support guys
Stifilz
THANKS TO:
@kristid1991 for the remote connection to UNLOCK 626
Click to expand...
Click to collapse
is this guide works on this model:
http://www.ebay.com/itm/131593194519?_trksid=p2055119.m1438.l2649&ssPageName=STRK:MEBIDX:IT
HTC Desire 626s 5" Android Smartphone works with Virgin Mobile
?
Thanks

@stifilz I'm trying to unlock a Desire 626s MetroPCS variant and got the same results @dbstrand24 did. The locked mmcblk0p36 file was identical to yours. I flashed the unlocked mmcblk0p36, popped in a T-Mobile SIM and still got the "This device can be unlocked" message.

Y.G. said:
@stifilz I'm trying to unlock a Desire 626s MetroPCS variant and got the same results @dbstrand24 did. The locked mmcblk0p36 file was identical to yours. I flashed the unlocked mmcblk0p36, popped in a T-Mobile SIM and still got the "This device can be unlocked" message.
Click to expand...
Click to collapse
Could be something to do with Metro? Is there and unlock app? Like T-Mobile has? Perhaps that is getting in the way? With the M9 unlock it worked fine with T-Mobile device but I'm not sure about Metro...

stifilz said:
Could be something to do with Metro? Is there and unlock app? Like T-Mobile has? Perhaps that is getting in the way? With the M9 unlock it worked fine with T-Mobile device but I'm not sure about Metro...
Click to expand...
Click to collapse
Yeah it has an unlock device app. I ran it after pushing the unlock file and it still said the device was ineligible to be unlocked.

i have this error can anyone help me, i have sdcard inside.
C:\adb>adb shell
[email protected]_a32eul:/ $ su
[email protected]_a32eul:/ # dd if=/dev/block/mmcblk0p36 of=/sdcard/mmcblk0p36old
256+0 records in
256+0 records out
131072 bytes transferred in 0.004 secs (32768000 bytes/sec)
[email protected]_a32eul:/ # exit
[email protected]_a32eul:/ $ exit
C:\adb>adb pull /sdcard/mmcblk0p36old
remote object '/sdcard/mmcblk0p36old' does not exist
C:\adb>adb push mmcblk0p36-rfg_8-UnLocked.txt /sdcard/mmcblk0p36new
1066 KB/s (131072 bytes in 0.120s)
C:\adb>adb shell
[email protected]_a32eul:/ $ su
[email protected]_a32eul:/ # dd if=/sdcard/mmcblk0p36new of=/dev/block/mmcblk0p36
dd: /sdcard/mmcblk0p36new: No such file or directory
1|[email protected]_a32eul:/ # exit
1|[email protected]_a32eul:/ $ exit
---------- Post added at 12:33 PM ---------- Previous post was at 12:24 PM ----------
ok working great and unlock, change /sdcard to /sdcard2. check logs.
C:\adb>adb shell
[email protected]_a32eul:/ $ su
[email protected]_a32eul:/ # dd if=/dev/block/mmcblk0p36 of=/sdcard2/mmcblk0p36old
256+0 records in
256+0 records out
131072 bytes transferred in 0.070 secs (1872457 bytes/sec)
[email protected]_a32eul:/ # exit
[email protected]_a32eul:/ $ exit
C:\adb>adb pull /sdcard2/mmcblk0p36old
2560 KB/s (131072 bytes in 0.050s)
C:\adb>adb push mmcblk0p36-rfg_8-UnLocked.txt /sdcard2/mmcblk0p36new
41 KB/s (131072 bytes in 3.097s)
C:\adb>adb shell
[email protected]_a32eul:/ $ su
[email protected]_a32eul:/ # dd if=/sdcard/mmcblk0p36new of=/dev/block/mmcblk0p36
dd: /sdcard/mmcblk0p36new: No such file or directory
1|[email protected]_a32eul:/ # dd if=/sdcard2/mmcblk0p36new of=/dev/block/mmcblk0p36
256+0 records in
256+0 records out
131072 bytes transferred in 0.149 secs (879677 bytes/sec)
[email protected]_a32eul:/ # exit
[email protected]_a32eul:/ $ exit

is it method work for HTC Desire 626S T-Mobile ?
anyone tested ?

Gsm UK said:
is it method work for HTC Desire 626S T-Mobile ?
anyone tested ?
Click to expand...
Click to collapse
You tell us. M9 was the same for T-Mobile

how u get s-off on 626 ... i cant find anywhere

Only two thing's are required, anything else is optional such as twrp recovery.
1. Bootloader Unlocked
2. Rooted

HTC 10 Verizon Turning on Radio..

hey guys...
i need working device modem parts for my device.. when i try to call emergency it says Turning on radio.. can u pls send me modem parts..?
i need these parts;
mmcblk0p29 ( fsg)
mmcblk0p30 (radio)
mmcblk0p39 (modemst1)
mmcblk0p40 (modemst2)
mmcblk0p64 (cradio)
Code:
mmcblk0p1: 00004000 00000200 "board_info"
mmcblk0p2: 00040000 00000200 "mfg"
mmcblk0p3: 00400000 00000200 "pg1fs"
mmcblk0p4: 017afc00 00000200 "pg2fs"
mmcblk0p5: 00200000 00000200 "xbl"
mmcblk0p6: 00200000 00000200 "tz"
mmcblk0p7: 00080000 00000200 "rpm"
mmcblk0p8: 00080000 00000200 "pmic"
mmcblk0p9: 00080000 00000200 "hyp"
mmcblk0p10: 00400000 00000200 "aboot"
mmcblk0p11: 04000000 00000200 "hosd"
mmcblk0p12: 00a00000 00000200 "tool_diag"
mmcblk0p13: 00000400 00000200 "devinfo"
mmcblk0p14: 00020000 00000200 "devcfg"
mmcblk0p15: 00020000 00000200 "lksecapp"
mmcblk0p16: 00040000 00000200 "cmnlib32"
mmcblk0p17: 00040000 00000200 "cmnlib64"
mmcblk0p18: 00040000 00000200 "apdp"
mmcblk0p19: 00040000 00000200 "msadp"
mmcblk0p20: 00000400 00000200 "dpo"
mmcblk0p21: 00a00000 00000200 "sp1"
mmcblk0p22: 00100000 00000200 "ddr"
mmcblk0p23: 00000400 00000200 "cdt"
mmcblk0p24: 00100000 00000200 "rfg_0"
mmcblk0p25: 00100000 00000200 "rfg_1"
mmcblk0p26: 00100000 00000200 "rfg_2"
mmcblk0p27: 00100000 00000200 "rfg_3"
mmcblk0p28: 00100000 00000200 "rfg_4"
mmcblk0p29: 00200000 00000200 "fsg"
mmcblk0p30: 04600000 00000200 "radio"
mmcblk0p31: 01400000 00000200 "adsp"
mmcblk0p32: 00200000 00000200 "fp"
mmcblk0p33: 00a00000 00000200 "slpi"
mmcblk0p34: 02000000 00000200 "mdtp"
mmcblk0p35: 00100000 00000200 "dip"
mmcblk0p36: 00200000 00000200 "venus"
mmcblk0p37: 00447400 00000200 "reserve1"
mmcblk0p38: 00100000 00000200 "misc"
mmcblk0p39: 00200000 00000200 "modemst1"
mmcblk0p40: 00200000 00000200 "modemst2"
mmcblk0p41: 01400000 00000200 "fataldevlog"
mmcblk0p42: 01e00000 00000200 "devlog"
mmcblk0p43: 00140400 00000200 "local"
mmcblk0p44: 00010000 00000200 "extra"
mmcblk0p45: 00000400 00000200 "fsc"
mmcblk0p46: 00100000 00000200 "rfg_8"
mmcblk0p47: 00002000 00000200 "ssd"
mmcblk0p48: 02000000 00000200 "persist"
mmcblk0p49: 00020000 00000200 "sec"
mmcblk0p50: 00080000 00000200 "frp"
mmcblk0p51: 00a00000 00000200 "ramdump"
mmcblk0p52: 00000400 00000200 "skylink"
mmcblk0p53: 02d00000 00000200 "carrier"
mmcblk0p54: 00080000 00000200 "keystore"
mmcblk0p55: 00080000 00000200 "keymaster"
mmcblk0p56: 00100000 00000200 "mota"
mmcblk0p57: 01000000 00000200 "dsp"
mmcblk0p58: 00d0d400 00000200 "reserve2"
mmcblk0p59: 04000000 00000200 "boot"
mmcblk0p60: 04000000 00000200 "recovery"
mmcblk0p61: 0e000000 00000200 "cache"
mmcblk0p62: 0d000000 00000200 "system"
mmcblk0p63: fe000000 00000200 "userdata"
mmcblk0p64: 04000000 00000200 "cradio"
mmcblk0p65: 00500000 00000200 "apppreload"
mmcblk0p66: 03c00000 00000200 "cota"
mmcblk0p67: 01000000 00000200 "vzw_quality"
mmcblk0p68: 01000000 00000200 "vzw_logger"
[email protected]_pmewl:/ #

t-mobile_mda said:
hey guys...
i need working device modem parts for my device.. when i try to call emergency it says Turning on radio.. can u pls send me modem parts..?
i need these parts;
mmcblk0p29 ( fsg)
mmcblk0p30 (radio)
mmcblk0p39 (modemst1)
mmcblk0p40 (modemst2)
mmcblk0p64 (cradio)
Code:
mmcblk0p1: 00004000 00000200 "board_info"
mmcblk0p2: 00040000 00000200 "mfg"
mmcblk0p3: 00400000 00000200 "pg1fs"
mmcblk0p4: 017afc00 00000200 "pg2fs"
mmcblk0p5: 00200000 00000200 "xbl"
mmcblk0p6: 00200000 00000200 "tz"
mmcblk0p7: 00080000 00000200 "rpm"
mmcblk0p8: 00080000 00000200 "pmic"
mmcblk0p9: 00080000 00000200 "hyp"
mmcblk0p10: 00400000 00000200 "aboot"
mmcblk0p11: 04000000 00000200 "hosd"
mmcblk0p12: 00a00000 00000200 "tool_diag"
mmcblk0p13: 00000400 00000200 "devinfo"
mmcblk0p14: 00020000 00000200 "devcfg"
mmcblk0p15: 00020000 00000200 "lksecapp"
mmcblk0p16: 00040000 00000200 "cmnlib32"
mmcblk0p17: 00040000 00000200 "cmnlib64"
mmcblk0p18: 00040000 00000200 "apdp"
mmcblk0p19: 00040000 00000200 "msadp"
mmcblk0p20: 00000400 00000200 "dpo"
mmcblk0p21: 00a00000 00000200 "sp1"
mmcblk0p22: 00100000 00000200 "ddr"
mmcblk0p23: 00000400 00000200 "cdt"
mmcblk0p24: 00100000 00000200 "rfg_0"
mmcblk0p25: 00100000 00000200 "rfg_1"
mmcblk0p26: 00100000 00000200 "rfg_2"
mmcblk0p27: 00100000 00000200 "rfg_3"
mmcblk0p28: 00100000 00000200 "rfg_4"
mmcblk0p29: 00200000 00000200 "fsg"
mmcblk0p30: 04600000 00000200 "radio"
mmcblk0p31: 01400000 00000200 "adsp"
mmcblk0p32: 00200000 00000200 "fp"
mmcblk0p33: 00a00000 00000200 "slpi"
mmcblk0p34: 02000000 00000200 "mdtp"
mmcblk0p35: 00100000 00000200 "dip"
mmcblk0p36: 00200000 00000200 "venus"
mmcblk0p37: 00447400 00000200 "reserve1"
mmcblk0p38: 00100000 00000200 "misc"
mmcblk0p39: 00200000 00000200 "modemst1"
mmcblk0p40: 00200000 00000200 "modemst2"
mmcblk0p41: 01400000 00000200 "fataldevlog"
mmcblk0p42: 01e00000 00000200 "devlog"
mmcblk0p43: 00140400 00000200 "local"
mmcblk0p44: 00010000 00000200 "extra"
mmcblk0p45: 00000400 00000200 "fsc"
mmcblk0p46: 00100000 00000200 "rfg_8"
mmcblk0p47: 00002000 00000200 "ssd"
mmcblk0p48: 02000000 00000200 "persist"
mmcblk0p49: 00020000 00000200 "sec"
mmcblk0p50: 00080000 00000200 "frp"
mmcblk0p51: 00a00000 00000200 "ramdump"
mmcblk0p52: 00000400 00000200 "skylink"
mmcblk0p53: 02d00000 00000200 "carrier"
mmcblk0p54: 00080000 00000200 "keystore"
mmcblk0p55: 00080000 00000200 "keymaster"
mmcblk0p56: 00100000 00000200 "mota"
mmcblk0p57: 01000000 00000200 "dsp"
mmcblk0p58: 00d0d400 00000200 "reserve2"
mmcblk0p59: 04000000 00000200 "boot"
mmcblk0p60: 04000000 00000200 "recovery"
mmcblk0p61: 0e000000 00000200 "cache"
mmcblk0p62: 0d000000 00000200 "system"
mmcblk0p63: fe000000 00000200 "userdata"
mmcblk0p64: 04000000 00000200 "cradio"
mmcblk0p65: 00500000 00000200 "apppreload"
mmcblk0p66: 03c00000 00000200 "cota"
mmcblk0p67: 01000000 00000200 "vzw_quality"
mmcblk0p68: 01000000 00000200 "vzw_logger"
[email protected]_pmewl:/ #
Click to expand...
Click to collapse
hey guys..
anyone has any idea..?

You tried just flashing the appropriate radio ?

Tallywacker said:
You tried just flashing the appropriate radio ?
Click to expand...
Click to collapse
yes i had..
device was dissambly, pb was the antennas..after connecting the antennas everything was oki..
thanx..