[how to] change your MID without an eng bootloader

[dave.michael]

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







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

I realized its because my OS isn't rooted. It would have worked on my Mac, but the OS simply isn't rooted to allow me to get the elevated prompt.

Sent from my HTC One_M8 using Tapatalk

 

[yourunlikegus]

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

Sorry to say, but I have changed my CID to developer version. I think I have the original saved on my PC somewhere but right now it is out of commission and I am waiting on a few parts. I will check once the parts come in and I reassamble everything.

 

[craig0r]

Rogers MID

FYI, here's the command to get the Rogers MID of 0P6B16000 back:

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

Follow the steps in the OP, of course, but use this command.

 

[kirdroid]

@Scotty - Isn't the model id of Google play edition 0P6B17000? How do I change it to that model id?

From Anandtech review article where it lists different models.


NM80P6B100 EMEA
NM80P6B120 AT&T
NM80P6B130 T-Mobile
NM80P6B200 Verizon
NM80P6B700 Sprint
NM80P6B160 Canada
NM80P6B170 Google Play Edition

Sent from my HTC One_M8 using Tapatalk

 

[scotty1223]

@Scotty - Isn't the model id of Google play edition 0P6B17000? How do I change it to that model id?

From Anandtech review article where it lists different models.


NM80P6B100 EMEA
NM80P6B120 AT&T
NM80P6B130 T-Mobile
NM80P6B200 Verizon
NM80P6B700 Sprint
NM80P6B160 Canada
NM80P6B170 Google Play Edition

Sent from my HTC One_M8 using Tapatalk

That may be. For some reason no one has stepped forward in this thread or my getvar all requests thread with a getvar all from an actual gpe phone. The assumption that the gpe shared a mid with att,unlocked and dev edition was based on the mid shared by those models on m7. Do you know someone with a real gpe that can verify?

assuming the GPE to have a mid of 0P6B17000,the code would be this:

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

as soon as we can confirm ill add the info to the OP

Sent from my HTC PG09410 using Tapatalk 2

 

[kirdroid]

Thanks. I'm 100% sure that GPE model id is not the same. AT&T, Developer and unlocked versions are the same SKU but GPE is a different SKU and model.

I'm going to change my model id to 0P6B17000. Thanks for the instructions

Sent from my HTC One_M8 using Tapatalk

 

[sari94]

I do not have S-off .I need help in getting my M8 the S-off with CID HTC__J15!
who can help?

 

[exad]

I've converted my Telus device to gpe using the ruu zip. Haven't changed the MID and I have been getting OTA updates... Is changing the mid really necessary for some?

Sent from my HTC One_M8 using xda app-developers app

 

[scotty1223]

I've converted my Telus device to gpe using the ruu zip. Haven't changed the MID and I have been getting OTA updates... Is changing the mid really necessary for some?

Sent from my HTC One_M8 using xda app-developers app

Your mid may have allready been the same,or the gpe updates may for some reason not be as strict in their requirements.

If you're getting gpe otas with an incorrect cid/mid this is an exception,not a rule,as an ota typically checks them and will fail if one is not correct.

If you're supercid,that may be bypassing the mid check,but accepting otas while supercid is not something I'd recomend.

As such,if you want to fully convert to another variant,the safest way IMO is to change the cid and mid to the correct values.

Sent from my HTC PG09410 using Tapatalk 2

 

[exad]

I don't see why accepting otas with supercid and soff would be a problem. If I was s-on I could understand.

Sent from my HTC One_M8 using XDA Free mobile app

 

[scotty1223]

I don't see why accepting otas with supercid and soff would be a problem. If I was s-on I could understand.

Sent from my HTC One_M8 using XDA Free mobile app

They were bricks off evita and Ville when folks tried to OTA on SuperCID, and we never really did figure out why.

Running an ruu is one thing, but accepting an OTA is another. Is easy enough to change cid and mid, that I personally would not risk it.

 

[exad]

Only s-on phones bricked but I suppose I can understand your caution never the less. Also, it was both RUUs and OTAs so if you're going to be cautious about one, I'd be cautious about the other too.

 

[scotty1223]

Only s-on phones bricked but I suppose I can understand your caution never the less. Also, it was both RUUs and OTAs so if you're going to be cautious about one, I'd be cautious about the other too.

There were s off bricks as well. There were also lots of folks who did it with no issue. I do not remember any incidents while using an ruu.

May have been a really odd fluke, and could be perfectly safe now. But like I said, we never did figure out why.

Folks look to the threads here for solid advice. As such, I use an extreme amount of caution as to what I recommend is safe. If it caused even one brick, I don't want to be responsible for it

Sent from my HTC One VX using Tapatalk

 

[exad]

I'll cross my fingers and hope not to brick. Never saw an S-off brick from ota or RUU personally and I lived on the evita forums and Irc for quite some time. I remember seeing you there as well from time to time. Maybe you caught something I didn't. *shrugs*

And I agree, accurate information is most helpful.

 

[mehmetolgungun]

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:

this process,in your cmd window,should look something like this:

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

enter the following:

adb shell

su (if needed to get a # prompt)

[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

________________________________________________________________________________________
-t mobile MID:

enter the following:

adb shell

su (if needed to get a # prompt)

[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)

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

c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
root@m7:/ # [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)
root@m7:/ # [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://xdaforums.com/showthread.php?t=2708565
change lock status flag(lock/unlock bootloader): http://xdaforums.com/showthread.php?t=2708571

Hi, Could you please post the verizon mid? I changed it to developer edition and I cant change it back now.

 

[scotty1223]

Hi, Could you please post the verizon mid? I changed it to developer edition and I cant change it back now.

added to the second post.

in the future,please do not quote the OP in its entirety when responding to things in the forums. its un-neccessary and makes it extremely dificult to find the actual comment/question when reading email notifications. we know what the OP says. theres no reason to quote it.

 

[cronojay]

I am on viper one for t-mobile us and trying to go to developer ed. I get this error. Any ideas

ViperOne@/# echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
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
00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384 <
/dev/block/mmcblk0p5: write error: No space left on device
1+0 records in
0+0 records out
0 bytes transferred in 0.002 secs (0 bytes/sec)
1|ViperOne@/#

 

[russellvone]

I am on viper one for t-mobile us and trying to go to developer ed. I get this error. Any ideas

ViperOne@/# echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
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
00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384 <
/dev/block/mmcblk0p5: write error: No space left on device
1+0 records in
0+0 records out
0 bytes transferred in 0.002 secs (0 bytes/sec)
1|ViperOne@/#

could you copy and paste

ALL of the command from start to finish?

it looks like you copy and pasted the command twice??? before you hit enter?



Sent from my HTC6525LVW using Tapatalk

 

[cronojay]

Here it is from start to finish

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\windows\system32>cd C:\Users\jkrizman\Downloads\adb

C:\Users\jkrizman\Downloads\adb>adb devices
List of devices attached
xxxxxxxxxxxxxxxxx device


C:\Users\jkrizman\Downloads\adb>adb shell
ViperOne@/# su
su
ViperOne@/# echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
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
00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384 <
/dev/block/mmcblk0p5: write error: No space left on device
1+0 records in
0+0 records out
0 bytes transferred in 0.001 secs (0 bytes/sec)
1|ViperOne@/#

 

[russellvone]

yah, um you've posted the "echo ne bla bla bla"

twice before hitting enter

Sent from my HTC6525LVW using Tapatalk