I tried to flashing a new firmware into my sensation this morning, but it not succeed http://forum.xda-developers.com/showthread.php?t=1412618
because the firmware didnt support my CID no. After that i tried to put my CID(T-MOB101) into the android-info.txt, but when i finished flashing, my Hboot upgrade to 1.20 with a *** LOCKED *** message, when i try to re-flash the PG58IMG.img file again, the screen shows cid error and the radio was not been upgrade as well.
I tried to change my CID to 11111111, but it not working, when i ran getvar cid it keep showing cid: T-MOB101
but the phone can be boot normally, i'm currently using RHD 4.1.7
HELP HELP HELP
I had a similar problem, which was fixed by doing a superCID.
What's the problem you're having with doing that?
Sent from my HTC Sensation XE with Beats Audio using xda premium
The cid for t-mobile is T-MOB010 NOT T-MOB101 try that it should help
ok people need to start reading and actually looking the thread,
there is a a warning RIGHT there when adding cid..
If your CID or MID is not supported by default, do this: (you do it at your own risk)
Click to expand...
Click to collapse
and not only that if your superCID there is no need to add
Code:
Firmware from 3.12.401.2/102 RUU
--- MD5 checksum: 9F6DAE6198D735CFCB9C06D35111720B *PG58IMG.zip ---
Supported devices:
--- CID's added by users requests are marked with green color ---
[COLOR="Red"]cidnum: 11111111[/COLOR]
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__044
cidnum: HTC__038
cidnum: VODAP203
its all there in plain sight!
just superCID then flash and everything so go just fine
and reason why its error out and your still getting the same is once hboot updated you lost all fastboot commands, you would have to htcdev unlock to get basic fastboot commands, or find a way to set hboot back or edit the info text again
ilostchild said:
ok people need to start reading and actually looking the thread,
there is a a warning RIGHT there when adding cid..
and not only that if your superCID there is no need to add
Code:
Firmware from 3.12.401.2/102 RUU
--- MD5 checksum: 9F6DAE6198D735CFCB9C06D35111720B *PG58IMG.zip ---
Supported devices:
--- CID's added by users requests are marked with green color ---
[COLOR="Red"]cidnum: 11111111[/COLOR]
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__044
cidnum: HTC__038
cidnum: VODAP203
its all there in plain sight!
just superCID then flash and everything so go just fine
and reason why its error out and your still getting the same is once hboot updated you lost all fastboot commands, you would have to htcdev unlock to get basic fastboot commands, or find a way to set hboot back or edit the info text again
Click to expand...
Click to collapse
um.. how can i do that?
after all the failed, i try to run the CID change command but it not working, maybe as @ilostchild said, My phone lost all command
The only CID locator app I've found is called the "CID Getter" and has a cupcake as an icon. Problem is when I use it, it gives me a CID number that doesnt match even the same format as what I've seen listed for others. The CID number I get is T-MOB010 but the formats I am seeing on line are:
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
So my guess is the app I downloaded isn't getting my proper CID number? Any advice or help?
Thanks!
That is your proper cid. T-Mobile hasn't finished their jb yet and is still beta testing. That is why they aren't in that list yet... Only a select few international HTC cids are.
Those HTC CIDs are for unbranded people. E.g HTC__001 is Unbranded Worldwide. CIDs are 8 digits.
Sent from my HTC One S using Tapatalk 2
I had been flashing this splash screen for some time and I just finally took the plunge to Neo's rom and therefore lollipop. However, with the changes to the MMCBLKs I wanted to double-check that my splash screen zip file was still safe to flash. It contains a splash1.img file which presumable contains the image that is known to be of the correct resolution. It also contains an android-info.txt file which I'm questioning. Here are its contents:
modelid: PN0710000
modelid: PN0711000
modelid: PN0712000
modelid: PN0713000
modelid: PN0714000
modelid: 0P6B20000
modelid: PN071****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
cidnum: VZW__001
mainver: 3.62.1700.1
btype:0
aareport:1
hbootpreupdate:3
I see that my verizon cid is there and I've heard of the mainver needing to match your phone for a file to flash so I wonder if I need to edit that to match whatever the lollipop firmware mainver is ( can look that up). I don't know what btype, aareport, and hbootpreupdate are but I'm concerned that it might flash a splash screen to the wrong partition. Can anyone tell me if this is still safe to flash on lollipop firmware or if it requires editing? Thanks.
Bump
Hi,
How do I Know when the RUU is to the single or dual sim ? For example this one: RUU_OCEAN_WHL_N71_SENSE90GP_NA_Gen_Unlock_1.16.617.6
My device is single-sim:
mid: 2PZC10000
cid: VODAP110
And I want to convert to:
modelid: 2PZC50000
cidnum: BS_US001
So I can have pt-br and and that RUU, Can I do this with s-off?
OTA file https://androidfilehost.com/?fid=6006931924117929460
To update from v1.24.401.12 to v1.24.401.14
Magisk patched boot image to flash in download mode https://androidfilehost.com/?fid=6006931924117929459
This is the latest Oreo version!
modelid: 2Q4D10000
cidnum: HTC__001
cidnum: HTC__034
cidnum: HTC__J15
cidnum: HTC__A07
cidnum: HTC__002
cidnum: HTC__M27
mainver: 1.24.401.14
hbootpreupdate:1
nohardreset: 1
any changes happend ??
what bugs did this update fix