Changing CID/MID via android-info.txt - AT&T HTC One (M8)

With no computer I'm somewhat very limited to changing anything concerning CID/MID...As a matter of fact, I don't think you can change CID without fastboot commands, so in order to change my CID from superCID to GOOGL001. I have edited the android-info.txt of RUU 2.12.1700.1 to only include CID: GOOGL001.
Also, there are plenty of MID changing tools available. Jball was kind enough to find me one. Unfortunately, the aroma script was made for the M7. I did find one though, but it didn't include the GPE MID 0P6B1700. I edited the android-info.txt to include only 0P6B1700..
recap: I currently have RUU 2.12.1700.1 with an edited android-info.txt that contains only 1 CID (that being GOOGL001) and 1 MID (that being 0P6B17000).
Let's hope this works because after a month of being unable to change cid. I hope I can

@jxcorex28
I'm hoping it works for you to

It didn't...CID is still 11111111 and mid is still 0P6B12000...I gave up

Related

CID Bricked Shooter (CDMA)

Here is what I did:
Months ago trying to install ICS (VM leak) went to s-off on my Sprint EVO 3D y changed my CID to super CID (111111) then thinking that the original CID of the phone was HTC__001 (following an EVO 3D GSM tutorial) changed it and went back to S-ON and stock but with the wrong CID (HTC__001) then when y tried to use my phone and update it to Sprint ICS but the phone won't even load the OS, it shows the screen where I can see my HBOOT by the way is 1.5 and go to fastboot but it says security warning etc... I do can install CWM and 4ext that means I can lock and relock fastboot oem then I tried to install several roms stock inculded but still doesn't boot to the OS even I tried to install stock RUU zip and EXE but since I'm with wrong CID the phone displays Wrong CID I don't know if installing a RUU for the CID HTC__001 makes sense but anyway when I try to install it says signature fail and since installing the RUU for Bricking or corrupting the HBOOT is imposible, I can't get in to QHSUSB_DLOAD to try any method like HTC Unbricking Project, Ultimate Recovery Tool 2.3 RC1, HBOOT Downgrade Toolkit Live CD or Juopunutbear S-OFF......
So achieving S-OFF it's imposible for my or I'm missing any other method for S-OFF and go back to the SPCS_001 CID? or there is another way to change the CID on S-ON considering that fastboot oem writecid fails on S-ON I even tried modifying the mmcblk0p4 file with an hex editor and it failed
Another way would be using a RUU with the android-info file changed to accept my HTC__001 CID even my hardware is CDMA (shooter) but signed for S-ON
Or another way is somehow corrupting the HBOOT without installing a RUU
So being S-ON with the wrong CID (HTC__001) with warning security and HBOOT 1.5 and no ROM can boot I think my phone is really death
Is there something missing I can do to make it work again or I have a really expensive brick??
anyone help??? please
Deleted
Wikd said:
Deleted
Click to expand...
Click to collapse
didn't worked for me, I don't have the exact error that shows, I'm not at home now trying to post you the error later....
any other ideas?? another method for s-off or maybe change the CID

[Q] Wrong CID and S-OFF

Here is what I did:
Months ago trying to install ICS (VM leak) went to s-off on my Sprint EVO 3D y changed my CID to super CID (111111) then thinking that the original CID of the phone was HTC__001 (following an EVO 3D GSM tutorial) changed it and went back to S-ON and stock but with the wrong CID (HTC__001) then when y tried to use my phone and update it to Sprint ICS but the phone won't even load the OS, it shows the screen where I can see my HBOOT by the way is 1.5 and go to fastboot but it says security warning etc... I do can install CWM and 4ext that means I can lock and relock fastboot oem then I tried to install several roms stock inculded but still doesn't boot to the OS even I tried to install stock RUU zip and EXE but since I'm with wrong CID the phone displays Wrong CID I don't know if installing a RUU for the CID HTC__001 makes sense but anyway when I try to install it says signature fail and since installing the RUU for Bricking or corrupting the HBOOT is imposible, I can't get in to QHSUSB_DLOAD to try any method like HTC Unbricking Project, Ultimate Recovery Tool 2.3 RC1, HBOOT Downgrade Toolkit Live CD or Juopunutbear S-OFF......
So achieving S-OFF it's imposible for my or I'm missing any other method for S-OFF and go back to the SPCS_001 CID? or there is another way to change the CID on S-ON considering that fastboot oem writecid fails on S-ON I even tried modifying the mmcblk0p4 file with an hex editor and it failed
Another way would be using a RUU with the android-info file changed to accept my HTC__001 CID even my hardware is CDMA (shooter) but signed for S-ON
Or another way is somehow corrupting the HBOOT without installing a RUU
So being S-ON with the wrong CID (HTC__001) with warning security and HBOOT 1.5 and no ROM can boot I think my phone is really death
Is there something missing I can do to make it work again or I have a really expensive brick??
anyone help??? please

big problem

Here is what I did:
Months ago trying to install ICS (VM leak) went to s-off on my Sprint EVO 3D y changed my CID to super CID (111111) then thinking that the original CID of the phone was HTC__001 (following an EVO 3D GSM tutorial) changed it and went back to S-ON and stock but with the wrong CID (HTC__001) then when y tried to use my phone and update it to Sprint ICS but the phone won't even load the OS, it shows the screen where I can see my HBOOT by the way is 1.5 and go to fastboot but it says security warning etc... I do can install CWM and 4ext that means I can lock and relock fastboot oem then I tried to install several roms stock inculded but still doesn't boot to the OS even I tried to install stock RUU zip and EXE but since I'm with wrong CID the phone displays Wrong CID I don't know if installing a RUU for the CID HTC__001 makes sense but anyway when I try to install it says signature fail and since installing the RUU for Bricking or corrupting the HBOOT is imposible, I can't get in to QHSUSB_DLOAD to try any method like HTC Unbricking Project, Ultimate Recovery Tool 2.3 RC1, HBOOT Downgrade Toolkit Live CD or Juopunutbear S-OFF......
So achieving S-OFF it's imposible for my or I'm missing any other method for S-OFF and go back to the SPCS_001 CID? or there is another way to change the CID on S-ON considering that fastboot oem writecid fails on S-ON I even tried modifying the mmcblk0p4 file with an hex editor and it failed
Another way would be using a RUU with the android-info file changed to accept my HTC__001 CID even my hardware is CDMA (shooter) but signed for S-ON
Or another way is somehow corrupting the HBOOT without installing a RUU
So being S-ON with the wrong CID (HTC__001) with warning security and HBOOT 1.5 and no ROM can boot I think my phone is really death
Is there something missing I can do to make it work again or I have a really expensive brick??
anyone help???
really sorry to hear about your problem.
i think you might get some quicker replies tho if you were to post this in the Q&A section so people will know your asking for help.
best of luck in fixing your phone!

AT&T and Developer Edition RUU - how to convert to Developer Edition

Update 12/23/2015 >> See my signature below for Android M
Thanks to @Jonny We now have the AT&T RUU
M9_ATT_Cingular_US_1.32.502.9
https://www.androidfilehost.com/?fid=95916177934556955
Code:
modelid: 0PJA11000
cidnum: CWS__001
mainver: 1.32.502.9
~Update~ Now the New Official Android Lollipop 5.1 RUU.exe is out for AT&T 2.11.502.18
http://www.htc.com/us/support/htc-one-m9-att/news/
~Update~10-26-15
Thanks @krazyace35 - This is the rom.zip pulled from the 2.11.502.18 RUU >>
https://www.androidfilehost.com/?fid=24052804347847327 or http://1drv.ms/1kIro4b
and the Full RUU.exe is here >>
http://dl3.htc.com.s3.amazonaws.com...51_SENSE70_ATT_MR_Cingular_US_2.11.502.18.exe
Thanks to @krazyace35 the 2.6.502.18 OTA and stock recovery are posted here >> http://forum.xda-developers.com/att-one-m9/general/2-6-502-18-ota-t3187078
and the older 1.32.502.31 is here
http://dl3.htc.com/application/RUU_...21_62.05.50320G_F_release_426950_signed_2.exe
I have pulled the Rom.zip from the 1.32.502.31 RUU for you it's here >> https://www.androidfilehost.com/?fid=96042739161891969
flash with htc_fastboot >> https://www.androidfilehost.com/?fid=96042739161891970
Code:
modelid: 0PJA11000
cidnum: CWS__001
mainver: 1.32.502.31
aareport:1
btype:1
And thanks To @jcase we now have S-OFF
SunShine S-Off v3.1 for the HTC One M9
http://theroot.ninja/
With S-OFF we can now convert the AT&T phones to Developer Edition
The Developer Edition does not have any of the AT&T Bloatware in it and the phone are the same hardware
all that's needed is a simple CID change and flash the Developer Edition RUU.
You could also convert to International but it will require a MID change that I'll post here ...
Great news @scotty1223 has posted the simple way to change your MID
just a small update... mid change thru adb has become obsolete. you can
fastboot oem writemid xxxxxxxxx in download mode on an s off device. eng bootloader no longer needed
@Mutasek24 has confirmed
Click to expand...
Click to collapse
So to convert your Mid to International WWE the command would be
fastboot oem writemid 0PJA10000
and to AT&T / Developer Edition would be
fastboot oem writemid 0PJA11000
To convert to Developer Edition, you phone will need to be unlocked at htcdev.com with TWRP 2.8.6.4 Beta Flashed in Download mode (Black bootloader screen) Please read this before flashing TWRP And Rooted with SuperSU Flashed in TWRP.
Once your unlocked and Rooted and S-OFF you can change your CID to the Developer Edition
All fastboot commands will take place in Download Mode / not in the normal white bootloader screen
fastboot oem writecid BS_US001
or
fastboot oem writecid BS_US002
followed by fastboot reboot-bootloader
Both will work for flashing the RUU.
For Super CID use
fastboot oem writecid 11111111
fastboot reboot-bootloader
At this point your ready to backup all your stuff and flash the Developer Edition RUU
I advise you copy the entire internal sdcard of the phone to your PC before flashing the RUU
also use google / and HTC backup to save your phones contacts, app's and SMS, Call history ..etc
Here are the Developer Edition RUU's we have so far (to flash these please rename them to RUU.zip to simplify the commands)
Code:
modelid: 0PJA11000
cidnum: BS_US001
cidnum: BS_US002
This is the one the phone shipped with ( this should receive an OTA update as soon as you flash it)
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32.617.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426167_signed.zip
and this is the 2nd Software / with Camera, overheating Fix (use this one)
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32.617.30_Radio_01.01_U11440221_62.05.50320G_F_release_427069_signed.zip
Also here's the Android Lollipop 5.1 - 2.11.617.15 RUU.EXE direct from HTC >> http://www.htc.com/us/support/htc-one-m9/news/
And the Rom.zip pulled from the RUU >> https://www.androidfilehost.com/?fid=24052804347772812
New 8/30/15 - Developer Edition RUU 2.11.617.15 RUU_HIMA_UL_L51_SENSE70_ATT_MR_NA_Gen_Unlock_2.11.617.15_Radio_01.01_U11440601_76.03.50611G_F_release_445910_signed_2.Rom.zip
M9_stock-system_2.11.617.15_TWRP_nandroid.rar >> Thanks @nkk71
And here's the OTA >> OTA_HIMA_UL_L51_SENSE70_ATT_MR_NA_Gen_Unlock_2.11.617.15-2.8.617.4_release_445912.zip
If you have problems with the normal fastboot flashing any RUU you'll have to use the htc_fastboot pulled from the RUU.EXE
you can download it here >> https://www.androidfilehost.com/?fid=96039337900114016 >> Thanks go to @Sneakyghost for sharing
Note their is a newer htc_fastboot here >> https://www.androidfilehost.com/?fid=24052804347775783 that seems to fix the old one only flashing the first 300mb of the system.img
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip
htc_fastboot flash zip RUU.zip <this may not be needed it might restart on it's own>
htc_fastboot reboot
You can also use the 0PJAIMG.ZIP method
rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
If you need to go back to AT&T software just change your CID back to CWS__001 and Flash the AT&T RUU and you'll be back to Stock
I'll post more later on going back to complete stock.
Some other useful files
Recovery flashable Radios here >> https://www.androidfilehost.com/?w=files&flid=32827
Developer Edition Stock Recovery's
Developer Edition 1.32.617.30 Firmware without red text
1.32.502.9_Stock_recovery_signed.img
1.32.502.9_radio.img
ATT_HIMA_1.32.502.31.Stock.recovery_signed.img
ATT_HIMA_1.32.502.31.radio.img
fastboot-mac.zip
I don't think SuperCID is an option anymore. I did this last night and it would not let me OTA update as long as I had 1111111 as my CID. Only upon changing it to BS_US001 would it allow the OTA update to boot to recovery and apply itself.
XperiaNexus333 said:
I don't think SuperCID is an option anymore. I did this last night and it would not let me OTA update as long as I had 1111111 as my CID. Only upon changing it to BS_US001 would it allow the OTA update to boot to recovery and apply itself.
Click to expand...
Click to collapse
Yeah I think the M8 was the same way ... SuperCID may still be useful for something but not for OTA
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
fastboot oem writecid 11111111
You can change back to any desired CID after a successful firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
Click to expand...
Click to collapse
clsA said:
Thanks to @Jonny We now have the AT&T RUU
M9_ATT_Cingular_US_1.32.502.9
Is this the firmware for att that is supposed to be released this coming week? The one with the big camera fix (supposedly) that tmobile just got?
Click to expand...
Click to collapse
brittoking said:
Is this the firmware for att that is supposed to be released this coming week? The one with the big camera fix (supposedly) that tmobile just got?
Click to expand...
Click to collapse
No this is the software on the phone now (before the update) ... it's for going back to Stock
clsA said:
brittoking said:
No this is the software on the phone now (before the update) ... it's for going back to Stock
Click to expand...
Click to collapse
Thank you for the quick reply! So waiting is the only option right now for the camera fix on an att model. Appreciate the help.
Click to expand...
Click to collapse
brittoking said:
Thank you for the quick reply! So waiting is the only option right now for the camera fix on an att model. Appreciate the help.
Click to expand...
Click to collapse
convert to developer edition .. that's what the thread is all about
my modelid is 0PJA11000
but my mid 0PJA10000
will it recive ota´s?
or i must change mid, and if i must change it, how can i do it???
thx
overon37 said:
my modelid is 0PJA11000
but my mid 0PJA10000
will it recive ota´s?
or i must change mid, and if i must change it, how can i do it???
thx
Click to expand...
Click to collapse
MID = modelid, their the same thing ... where are you seeing 2 different ?
I'll post links / Instructions for changing the MID when they become available.
with this app
https://play.google.com/store/apps/details?id=org.tritonsoft.cidgetter&hl=es
i can see that my modelid this, but when from download mode with fastboot oem readmid i get the other ¿? not the same number
AND now, with a factory reset i have only 18G free,not 21G
edit: nvm I didn't read everything
K.AuthoR said:
edit: nvm I didn't read everything
Click to expand...
Click to collapse
The AT&T RUU is at the top of the post
Yep, I'm downloading now. I am curious though, what's the difference between the two CID's for the developer editions?
For the purpose of if we ever have to use insurance / warranty, is there a way to get the bootloader header to show "Locked" again instead of "Relocked?" On the M8, revone had a tag that would mark it as locked (./revone -l) and then you could use "fastboot oem writesecureflag 3" to put S-On back. I'm assuming the S-On command still works here, I'm just wondering about putting Locked back instead of Relocked.
Do we have to manually enter AT&T apns or anything else once we convert to Dev Edition? This is my first GSM phone (had Sprint for last 13 years) and have never had opportunity to do this conversion.
Anything else we need to do? I heard dev edition also doesn't have VoLTE working?
clsA said:
Thanks to @Jonny We now have the AT&T RUU
M9_ATT_Cingular_US_1.32.502.9
https://www.androidfilehost.com/?fid=95916177934556955
Code:
modelid: 0PJA11000
cidnum: CWS__001
mainver: 1.32.502.9
And thanks To @jcase we now have S-OFF
SunShine S-Off v3.1 for the HTC One M9
http://theroot.ninja/
With S-OFF we can now convert the AT&T phones to Developer Edition
The Developer Edition does not have any of the AT&T Bloatware in it and the phone are the same hardware
all that's needed is a simple CID change and flash the Developer Edition RUU.
You could also convert to International but it will require a MID change that I'll post here ASAP
To convert to Developer Edition, you phone will need to be unlocked at htcdev.com with TWRP 2.8.6.4 Beta Flashed in Download mode (Black bootloader screen) Please read this before flashing TWRP And Rooted with SuperSU Flashed in TWRP.
Once your unlocked and Rooted and S-OFF you can change your CID to the Developer Edition
All fastboot commands will take place in Download Mode / not in the normal white bootloader screen
fastboot oem writecid BS_US001
or
fastboot oem writecid BS_US002
followed by fastboot reboot-bootloader
Both will work for flashing the RUU.
For Super CID use
fastboot oem writecid 11111111
fastboot reboot-bootloader
At this point your ready to backup all your stuff and flash the Developer Edition RUU
I advise you copy the entire internal sdcard of the phone to your PC before flashing the RUU
also use google / and HTC backup to save your phones contacts, app's and SMS, Call history ..etc
Here are the 2 Developer Edition RUU's we have so far (to flash these please rename them to RUU.zip to simplify the commands)
Code:
modelid: 0PJA11000
cidnum: BS_US001
cidnum: BS_US002
This is the one the phone shipped with
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32.617.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426167_signed.zip
and this is the Current Software / with Camera, overheating Fix (use this one)
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32.617.30_Radio_01.01_U11440221_62.05.50320G_F_release_427069_signed.zip
If you have problems with the normal fastboot flashing any RUU you'll have to use the htc_fastboot pulled from the RUU.EXE
you can download it here >> https://www.androidfilehost.com/?fid=96039337900114016 >> Thanks go to @Sneakyghost for sharing
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip
htc_fastboot flash zip RUU.zip <this may not be needed it might restart on it's own>
htc_fastboot reboot
If you need to go back to AT&T software just change your CID back to CWS__001 and Flash the AT&T RUU and you'll be back to Stock
I'll post more later on going back to complete stock.
Some other useful AT&T files
1.32.502.9_Stock_recovery_signed.img
1.32.502.9_radio.img
Click to expand...
Click to collapse
how can i clean files before do it all this work, because now i have only 18G free, not 21G
overon37 said:
how can i clean files before do it all this work, because now i have only 18G free, not 21G
Click to expand...
Click to collapse
Flashing any of these RUU's will wipe your phone. Backup to your PC first
I had to use HTC
_fastboot, but glad to be on the dev edition again....
Android The Greek said:
I had to use HTC
_fastboot, but glad to be on the dev edition again....
Click to expand...
Click to collapse
Did you have to do any manual edits to get everything working on AT&T or did you just change CID and flash the RUU?
The dev edition software asks what carrier you are on during the setup, so my guess is that it would install the correct APNs. When I was using the DE Rom, it worked perfectly with AT&T. I'm hoping the RUU works the same. On a side note, I also had to use the HTC_fastboot.
Is it safe to root and flash the Dev edition 1.32.617.6 from ATT 1.32.502.9 since there is a difference in firmware? Am I better off waiting until the firmware OTA hits for ATT and then trying?

Flashing M8_UL RUU to M8_UL_CA

Hi folks,
I have M8_UL_CA S-OFF and I was wondering if I can flash M8_UL Europe roms to avoid bloatware?
"ROM" and "RUU" are two very different things; so please take care before using the terms interchangeably.
You should be able to run a Euro RUU. But you should be specific as to which RUU you want to flash (file name, source, etc.).
You will likely also need to change CID and MID in order to run the RUU, depending on what RUU exactly.

Categories

Resources