[how to] change your MID without an eng bootloader

Search This thread

scotty1223

Inactive Recognized Contributor
Jan 3, 2011
2,813
3,055
READ THIIS!
*this thread is for m8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.

_____________________________________________________________________________________________________________________

this thread is for the folks who wish tochage their MID in order to fully convert a device and recieve OTA updates. the method described here is not the only way to skin the cat,but as long as your careful the risk is very minimal, its quick and easy and doesnt require any hboot downgrades,eng hboot install,data loss,or having to run an ruu.

please note that s-off is required!

credits:
-beaups for schooling me on the echo command protocol
-kdj67f for dumping partitions from his java card s-offed phone
-davehasninjas for dumping rumrunner s offed partitions
-andybones for testing on a vzw device
*i dont have m8 yet. if you want to test,ill add you to the credits.

standard disclaimer: use this information at your own risk. it has been tested,but copying the command incorrectly could have consequences. if you melt your phone into a smoldering little pile of aluminum goo, its not my fault.


IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)


-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:

cd c:\miniadb_m7

your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)

-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:

adb devices

if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.

if you get your serial number back,then enter this command:
adb reboot bootloader

this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.

now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.

if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot

and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine

failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)

failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above

note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities

-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window

-fastboot with phone in fastboot,enter:
fastboot devices in cmd window

in either case,a properly connected phone with working drivers installed should report back the phones serial number.

this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]

c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx    device


c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx    fastboot

c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...

finished. total time: 0.037s

c:\miniadb_m7>


2)change your MID
warning: *do not try and type the command. please copy and paste it

-AT&T, unlocked, developer MID:
enter the following:

adb shell

su (if needed to get a # prompt)

Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)

exit

adb reboot bootloader

fastboot getvar mid (or getvar all)

verify 0P6B12000 for modelid

fastboot reboot

________________________________________________________________________________________
-google play MID:
enter the following:

adb shell

su (if needed to get a # prompt)

Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x37\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)

exit

adb reboot bootloader

fastboot getvar mid (or getvar all)

verify 0P6B17000 for modelid

fastboot reboot


________________________________________________________________________________________
-t mobile MID:
enter the following:

adb shell

su (if needed to get a # prompt)

Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)

exit

adb reboot bootloader

fastboot getvar mid (or getvar all)

verify 0P6B13000 for modelid

fastboot reboot

________________________________________________________________________________________
-HTC_Europe MID:
enter the following:

adb shell

su (if needed to get a # prompt)

Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)

exit

adb reboot bootloader

fastboot getvar mid (or getvar all)

verify 0P6B10000 for modelid

fastboot reboot

________________________________________________________________________________________



your command window should look like this:
Code:
c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ # [COLOR="Red"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR]
00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384                          <
17+0 records in
17+0 records out
17 bytes transferred in 0.009 secs (1888 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit

c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000  [COLOR="Blue"]<-looky[/COLOR]
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.092s

c:\miniadb_m7>[COLOR="Red"]fastboot reboot[/COLOR]
rebooting...
(bootloader) hbootpreupdate: 11

finished. total time: 7.288s

some other useful links:
remove tampered banner: http://forum.xda-developers.com/showthread.php?t=2708565
change lock status flag(lock/unlock bootloader): http://forum.xda-developers.com/showthread.php?t=2708571
 
Last edited:

scotty1223

Inactive Recognized Contributor
Jan 3, 2011
2,813
3,055
other MIDs

Rogers MID
0P6B16000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x36\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
*thanks @craig0r
___________________________________________________________________________________________

wind(canada) MID
0P6B13000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
___________________________________________________________________________________________

verizon MID
0P6B20000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or sprint device to this in attempts to use it on vzw and convert to a vzw device(or vice versa)
___________________________________________________________________________________________

sprint MID
0P6B70000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or vzw device to this in attempts to use it on sprint and convert to a sprint device(or vice versa).
___________________________________________________________________________________________

0P6B11000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
___________________________________________________________________________________________

europe m8 dual sim MID
0P6B64000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x36\x00\x34\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
*thanks @EddyOS

warning! provided by request. i would strongly advise against attempting to convert single sim m8 to dual sim,or vise versa
___________________________________________________________________________________________
 
Last edited:

craig0r

Senior Member
Sep 24, 2008
1,141
77
Toronto
Sorry if this is a dumb question, but I want to be clear before I try this sort of thing out.

Am I to understand that the developer edition, Google Play edition, and AT&T version all have the same MID?

Sent from my HTC One using XDA Premium HD app
 

scotty1223

Inactive Recognized Contributor
Jan 3, 2011
2,813
3,055
Sorry if this is a dumb question, but I want to be clear before I try this sort of thing out.

Am I to understand that the developer edition, Google Play edition, and AT&T version all have the same MID?

Sent from my HTC One using XDA Premium HD app

We have recently learned gpe is different.
 
Last edited:
  • Like
Reactions: TheEarman

scotty1223

Inactive Recognized Contributor
Jan 3, 2011
2,813
3,055
cool.let me know what the mid is, if its same ill add that to the OP,and if its different,ill list the command to go back to that if needed in the second post.
 
  • Like
Reactions: yourunlikegus

dachat

Member
May 1, 2012
21
1
Manchester
Change MID for HTC One M8 EE UK

I am s-off and rooted, will this work for M8
(I see all comments are from M7)
Should I change my CID from ORANG001 to supercid?
What benefits can I get? Will this remove the EE simlock?
Advice welcome please

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.00
(bootloader) version-baseband: 1.14.213315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.61.17
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
 

Gja88

Senior Member
Oct 6, 2010
448
28
I know this thread is about mid but whats the cid for the unlocked version? I was told before that it was htc__001 and that its mid was the european version on this thread, but i see the mid is different on here. Either way I changed both my cid to htc__001 and the mid on here for unlocked devices since im trying to change my t-mobile version to unlocked. Am i go to go to flash the correct firmware? I'm s-off as well
 

scotty1223

Inactive Recognized Contributor
Jan 3, 2011
2,813
3,055
I am s-off and rooted, will this work for M8 yes. (you are in m8 general)
(I see all comments are from M7)
Should I change my CID from ORANG001 to supercid? i dont know,should you? what do you want to achieve?
What benefits can I get? first thing said in the first post. if you dont fit that scenario you dont need to change your nid. Will this remove the EE simlock? no
Advice welcome please

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.00
(bootloader) version-baseband: 1.14.213315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.61.17
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

I know this thread is about mid but whats the cid for the unlocked version? I was told before that it was htc__001 and that its mid was the european version on this thread, but i see the mid is different on here. Either way I changed both my cid to htc__001 and the mid on here for unlocked devices since im trying to change my t-mobile version to unlocked. Am i go to go to flash the correct firmware? I'm s-off as well

not sure what the cid is for the unlocked version. maybe @yourunlikegus can provide that info.

if youve changed your cid/mid to htc europe,you can now run an unbranded(x.xx.401.x) ruu if one exists,to complete the conversion.

if the unlocked cid is not HTC__001 and does not match your mid,you cannot ruu and OTAs will not happen.
 

dachat

Member
May 1, 2012
21
1
Manchester
Change from ORANG001 to HTC_001

I am hoping to change my device to enable it to have the unlocked Europe stock rom getting stock ota's
Is this possible and how should I set about it?
I have S-off rooted ul_M8 Originally on EE
Running Android Revolution HD 5.0
 

dave.michael

Member
Jan 24, 2010
27
4
New York
I know it specifies Windows 7 and older but just looking to confirm. This can't be done with a Mac, can it? I have adb running on it, but in the shell, the super user command isn't recognized.
 

scotty1223

Inactive Recognized Contributor
Jan 3, 2011
2,813
3,055
I am hoping to change my device to enable it to have the unlocked Europe stock rom getting stock ota's
Is this possible and how should I set about it?
I have S-off rooted ul_M8 Originally on EE
Running Android Revolution HD 5.0

-change cid
-change mid
-run a release keys ruu for the build you want to run





I know it specifies Windows 7 and older but just looking to confirm. This can't be done with a Mac, can it? I have adb running on it, but in the shell, the super user command isn't recognized.

Yes it can be done on a Mac,but you're on your own getting adb/fastboot working. I've zero Mac experience


Sent from my HTC PG09410 using Tapatalk 2
 

Top Liked Posts

  • There are no posts matching your filters.
  • 64
    READ THIIS!
    *this thread is for m8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.

    _____________________________________________________________________________________________________________________

    this thread is for the folks who wish tochage their MID in order to fully convert a device and recieve OTA updates. the method described here is not the only way to skin the cat,but as long as your careful the risk is very minimal, its quick and easy and doesnt require any hboot downgrades,eng hboot install,data loss,or having to run an ruu.

    please note that s-off is required!

    credits:
    -beaups for schooling me on the echo command protocol
    -kdj67f for dumping partitions from his java card s-offed phone
    -davehasninjas for dumping rumrunner s offed partitions
    -andybones for testing on a vzw device
    *i dont have m8 yet. if you want to test,ill add you to the credits.

    standard disclaimer: use this information at your own risk. it has been tested,but copying the command incorrectly could have consequences. if you melt your phone into a smoldering little pile of aluminum goo, its not my fault.


    IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
    1)set up adb(windows 7 and older)


    -download this file
    -install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
    -unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
    -open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
    -change to your miniadb_m7 directory. type the following at the prompt in your cmd window:

    cd c:\miniadb_m7

    your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)

    -now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
    -make sure your phone is being recognized- type:

    adb devices

    if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.

    if you get your serial number back,then enter this command:
    adb reboot bootloader

    this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.

    now enter:
    fastboot devices
    again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.

    if you get your serial number back,you can enter the following to boot back to the phones OS:
    fastboot reboot

    and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
    troubleshooting connectivity issues:
    -try a reboot of the PC
    -try different usb cables and ports
    -dont use a usb hub
    -dont use usb 3.0
    -make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
    -windows 8 has been known to have issues. try a windows 7 or older machine

    failing the above,
    -i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)

    failing that,try manually updating the drivers in the following manner:
    -put the phone in fastboot mode(select fastboot from the hboot menu)
    -open device manager on the PC
    -plug in phone,watch for it to pop up in device manager.
    -update drivers with device manager,pointing the wizard to the extracted
    driver download folder from above

    note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
    -open cmd window. change to directory containing adb/fastboot utilities

    -adb with the phone in the booted OS,usb debug enabled,enter:
    adb devices in a cmd window

    -fastboot with phone in fastboot,enter:
    fastboot devices in cmd window

    in either case,a properly connected phone with working drivers installed should report back the phones serial number.

    this process,in your cmd window,should look something like this:
    Code:
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    
    C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
    
    c:\miniadb_m7>adb devices
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    List of devices attached
    FAxxxxxxxxxx    device
    
    
    c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
    
    c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
    FAxxxxxxxxxx    fastboot
    
    c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
    rebooting...
    
    finished. total time: 0.037s
    
    c:\miniadb_m7>


    2)change your MID
    warning: *do not try and type the command. please copy and paste it

    -AT&T, unlocked, developer MID:
    enter the following:

    adb shell

    su (if needed to get a # prompt)

    Code:
    [B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
    (the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)

    exit

    adb reboot bootloader

    fastboot getvar mid (or getvar all)

    verify 0P6B12000 for modelid

    fastboot reboot

    ________________________________________________________________________________________
    -google play MID:
    enter the following:

    adb shell

    su (if needed to get a # prompt)

    Code:
    [B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x37\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
    (the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)

    exit

    adb reboot bootloader

    fastboot getvar mid (or getvar all)

    verify 0P6B17000 for modelid

    fastboot reboot


    ________________________________________________________________________________________
    -t mobile MID:
    enter the following:

    adb shell

    su (if needed to get a # prompt)

    Code:
    [B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
    (the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)

    exit

    adb reboot bootloader

    fastboot getvar mid (or getvar all)

    verify 0P6B13000 for modelid

    fastboot reboot

    ________________________________________________________________________________________
    -HTC_Europe MID:
    enter the following:

    adb shell

    su (if needed to get a # prompt)

    Code:
    [B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
    (the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)

    exit

    adb reboot bootloader

    fastboot getvar mid (or getvar all)

    verify 0P6B10000 for modelid

    fastboot reboot

    ________________________________________________________________________________________



    your command window should look like this:
    Code:
    c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
    [email protected]:/ # [COLOR="Red"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x
    30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR]
    00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384                          <
    17+0 records in
    17+0 records out
    17 bytes transferred in 0.009 secs (1888 bytes/sec)
    [email protected]:/ # [COLOR="red"]exit[/COLOR]
    exit
    
    c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
    
    c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
    (bootloader) version: 0.5
    (bootloader) version-bootloader: 1.44.0000
    (bootloader) version-baseband: 4A.17.3250.20
    (bootloader) version-cpld: None
    (bootloader) version-microp: None
    (bootloader) version-main: 1.27.531.8
    (bootloader) version-misc: PVT SHIP S-OFF
    (bootloader) serialno: HTxxxxxxxxxx
    (bootloader) imei: xxxxxxxxxxxxxxx
    (bootloader) meid: 00000000000000
    (bootloader) product: m7_ul
    (bootloader) platform: HBOOT-8064
    (bootloader) modelid: PN0731000  [COLOR="Blue"]<-looky[/COLOR]
    (bootloader) cidnum: 11111111
    (bootloader) battery-status: good
    (bootloader) battery-voltage: 4175mV
    (bootloader) partition-layout: Generic
    (bootloader) security: off
    (bootloader) build-mode: SHIP
    (bootloader) boot-mode: FASTBOOT
    (bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
    getvar:all FAILED (unknown status code)
    finished. total time: 0.092s
    
    c:\miniadb_m7>[COLOR="Red"]fastboot reboot[/COLOR]
    rebooting...
    (bootloader) hbootpreupdate: 11
    
    finished. total time: 7.288s

    some other useful links:
    remove tampered banner: http://forum.xda-developers.com/showthread.php?t=2708565
    change lock status flag(lock/unlock bootloader): http://forum.xda-developers.com/showthread.php?t=2708571
    19
    other MIDs

    Rogers MID
    0P6B16000
    Code:
    echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x36\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
    *thanks @craig0r
    ___________________________________________________________________________________________

    wind(canada) MID
    0P6B13000
    Code:
    echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
    ___________________________________________________________________________________________

    verizon MID
    0P6B20000
    Code:
    echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
    warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or sprint device to this in attempts to use it on vzw and convert to a vzw device(or vice versa)
    ___________________________________________________________________________________________

    sprint MID
    0P6B70000
    Code:
    echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
    warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or vzw device to this in attempts to use it on sprint and convert to a sprint device(or vice versa).
    ___________________________________________________________________________________________

    0P6B11000
    Code:
    echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
    ___________________________________________________________________________________________

    europe m8 dual sim MID
    0P6B64000
    Code:
    echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x36\x00\x34\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
    *thanks @EddyOS

    warning! provided by request. i would strongly advise against attempting to convert single sim m8 to dual sim,or vise versa
    ___________________________________________________________________________________________
    7
    echo command for indian M8 0P6B65000

    Code:
    echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x36\x00\x35\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
    4
    right....[Dehr...I text quicker than I think]

    but he's still got fastboot huh?

    Sent from my HTC6525LVW using Tapatalk

    it appears so. however,p5 bricks with dna were only recoverable via jtag so i dont have alot of hope. that fact that the phone still responds at all makes it worth exploring. were now discussing it here: http://forum.xda-developers.com/showthread.php?p=52595696 in efforts to not stray to far off topic in this thread.

    I was wondering how you get the numbers:

    Code:
    \x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30
    ?

    Is there a specific way to 'translate' any MID so it can be used with the instructions in the OP? Btw I would like to change back my MID to:

    Code:
    0P6B11000

    0P6B11000 works out to:
    Code:
    echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384

    theres not any trick to the numbers. 30=0,31=1 and so on. 41=A,42=B and so on. its important to keep the 00s,wich are a . in the hex editor. the mid is kept in the partition in a somewhat stange fasion,and it you cant change the orientation,or the offsets:
    Code:
    00004000  30 00 50 00 36 00 42 00 31 00 32 00 30 00 30 00  0.P.6.B.1.2.0.0.
    00004010  30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  0...............

    a word of warning to anyone who wants to translate a different MID,be extremely careful plugging things into the command,as screwing it up can have consequences,as show very clearly a few posts up.

    what variant does your mid fit? ill add it to the 2nd post.