[how to]change your MID without the eng bootloader

scotty1223 · Oct 20, 2013

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

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

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

-AT&T,developer,google play MID:

________________________________________________________________________________________
-t mobile MID:

________________________________________________________________________________________
-HTC_Europe MID:

________________________________________________________________________________________

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=2477792
change lock status flag(lock/unlock bootloader): http://forum.xda-developers.com/showthread.php?t=2475914

scotty1223 · Oct 20, 2013

i dont think im going to add any more MIDs in the above post,as i dont think many(any?) will be flip flopping to something other than those 3. it could be dnagerous to try and convert m7_ul to m7_u or m7_wlv

if you need to change to something different let me know,and i can put it here,so all the comands are in one place. this post is for reference only.

for HTC_Europe international m7_ul PN0710000

Code:

echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384

for m7_u PN0711000

Code:

echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384

for other gsm international m7_ul PN0714000

Code:

echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x34\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384

for verizon,m7_wlv PN0731000

Code:

echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384

*please note that neither sprint nor vzw devices can be converted to gsm or vice versa

for sprint, m7_wls PN0720000

Code:

echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384

*please note that neither sprint nor vzw devices can be converted to gsm or vice versa

for htc one dual sim PN0751000

Code:

echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x35\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384

electronical · Oct 20, 2013

@scotty1223

My MID is currently: PN0711000 and i want to change it to: PN0710000
Can you add the correct command line in adb shell?

Nerekan · Oct 20, 2013

Great!
Please make for MID: PN0710000.

zaphodbeeb · Oct 20, 2013

Kudos 2 u man. Another really useful post. I would appreciate the code for PN0710000 also as I am currently planning on converting to the google edition, but would like to know the code to revert back to the above if I need to return to HTC at sometime. Much more convienient (and less risky) than using eng boot method to change.

ervius · Oct 20, 2013

Nerekan said:
Great!
Please make for MID: PN0710000.

I think this is the command for "PN0710000"

Code:

echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384

but wait scotty1223 to confirm my theory.....
see U!

scotty1223 · Oct 20, 2013

electronical said:
@scotty1223

My MID is currently: PN0711000 and i want to change it to: PN0710000
Can you add the correct command line in adb shell?

zaphodbeeb said:
Kudos 2 u man. Another really useful post. I would appreciate the code for PN0710000 also as I am currently planning on converting to the google edition, but would like to know the code to revert back to the above if I need to return to HTC at sometime. Much more convienient (and less risky) than using eng boot method to change.

what model/variant do you guys have? if this is another variant of m7_u,let me know if you run into any snags or issues with the conversion to google play,wich is an m7_ul. id really appreciate reports of success or failure for OTAs.

id like to convert my dads m7_u(PN0711000) to HTC__001 and PN0712000 so he could recieve european updated. not sure if OTAs will catch some other flag since the m7_u has no provisions for LTE.

feel free to post here or pm me anything you learn while converting,and if you intend to OTA or not

ervius said:
I think this is the command for "PN0710000"

Code:

echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384

but wait scotty1223 to confirm my theory.....
see U!

looks fine- x30 = 0 so just need to replace the 31,wich obviously = 1

zaphodbeeb · Oct 20, 2013

I have a m7_ul.

scotty1223 · Oct 20, 2013

zaphodbeeb said:
I have a m7_ul.

and are PN0711000?

edit:

i see,you are international. outside the us m7_ul is the PN710000. had some MID confusion,lol.. move along,nothing to see here

ngagephone · Oct 20, 2013

OK I have a uk HTC one my current mid is PN0710000

I would like the gpe MID is this the att developer edition you have listed on the first page?

Edit also guessing you need root?

scotty1223 · Oct 21, 2013

ngagephone said:
OK I have a uk HTC one my current mid is PN0710000

I would like the gpe MID is this the att developer edition you have listed on the first page?

Edit also guessing you need root?

correct,to the best of my knowledge,the GPE shares PN0712000 along with dev edition,att,and canadian variants.

yes,you need root and s-off.

ngagephone · Oct 21, 2013

Thank you

frankcck · Oct 24, 2013

Just clarify,
If I have an US T-mobile One, I wanna convert to International version as I can get the x.xx.401.xx OTA, I have to change my CID to HTC_001 and MID to PN0710000. Is this correct?

Sent from my HTC ViperOne

scotty1223 · Oct 25, 2013

tommy0411 said:
Just clarify,
If I have an US T-mobile One, I wanna convert to International version as I can get the x.xx.401.xx OTA, I have to change my CID to HTC_001 and MID to PN0710000. Is this correct?

Sent from my HTC ViperOne

correct

io53 · Oct 25, 2013

That's one neat hack. Thank you for this!

Sent from my HTC One using Tapatalk

scotty1223 · Oct 25, 2013

io53 said:
That's one neat hack. Thank you for this!

Sent from my HTC One using Tapatalk

glad it was helpful. basically the same idea as hex editing p4 to change cid with evita and ville,so its not a new concept. all i did was locate the mid and apply the same idea

io53 · Nov 1, 2013

Is the MID on the same place in the GE bootloaders?

Sent from my HTC One using Tapatalk

scotty1223 · Nov 1, 2013

io53 said:
Is the MID on the same place in the GE bootloaders?

Sent from my HTC One using Tapatalk

The mid is not located in the bootloader,it's in p6. I'm fairly certain the mid is in the same location,but I've not checked it. You're welcome to dump it and we can verify.

Sent from my HTC One VX using Tapatalk

papubhai · Nov 9, 2013

Change MID to 710000 from 714000 (S-off)

scotty1223 said:
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

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

-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:

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,developer,google play MID:

enter the following:

adb shell

Code:

[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 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 PN0712000 for modelid

fastboot reboot

________________________________________________________________________________________
-t mobile MID:

enter the following:

adb shell

Code:

[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 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 PN0713000 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:
http://forum.xda-developers.com/showthread.php?t=2477792
http://forum.xda-developers.com/showthread.php?t=2475914&highlight=+how+to+lock+unlock

Hi,

I'm on Hboot 1.55 and I'm s-off MID =714000 and CID =11111111. Please guide me to change the MID to 710000 as i need OTA from CID HTC__001. Urgent help would be very welcomed...Many many thanks.. Eng method fails with remote parsing error (error 24)

---------- Post added at 03:08 PM ---------- Previous post was at 03:07 PM ----------

Hi,

I'm on Hboot 1.55 and I'm s-off MID =714000 and CID =11111111. Please guide me to change the MID to 710000 as i need OTA from CID HTC__001. Urgent help would be very welcomed...Many many thanks.. Eng method fails with remote parsing error (error 24)

scotty1223 · Nov 9, 2013

papubhai said:
Hi,

I'm on Hboot 1.55 and I'm s-off MID =714000 and CID =11111111. Please guide me to change the MID to 710000 as i need OTA from CID HTC__001. Urgent help would be very welcomed...Many many thanks.. Eng method fails with remote parsing error

you just enter the adb command in the second post for 710000. if you need more guidance than what the OP states,you maybe not should do this.

im not sure you should do this,anyway. there is likely a reason the eng method failed. what variant is 714000?

if you are m7_ul it should be ok to switch to 710000.but if you are something else(m7_u,m7_wls,etc) it may not be safe to convert to that cid/mid

[how to]change your MID without the eng bootloader

Inactive Recognized Contributor

Inactive Recognized Contributor

Senior Member

Member

Senior Member

Retired Recognized Developer

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Similar threads

Top Liked Posts