• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Am I the only one who has this cid and firmware?

nethoinkz

Newbie
So I'm wondering if I'm the only one who has CID ACG__001 and build 1.33.510.8? There seem to be no RUU nor are there any sign of ota coming soon for me. I'm starting to regret switching carrier to nTelos, and I'm in a 2yr contract too.
frown.gif


HTC One m9
Android 5.0.2
Build 1.33.510.8
CID ACG__001
Carrier nTelos
 
True. I'm on twrp and I have no idea how to get back to my stock recovery (to take OTA when it comes) since there are no resources for my device. I did a twrp read only mode backup when I was still at full stock but I don't know if that included my stock recovery. I'm thinking I could just flash another firmware and edit CID but I'm worried I'd lose my carrier (phone stuff). Also I didn't know I'd have to pay 25$ to s-off just to flash a firmware. :( This is my first htc device. :|
I really like my sexy phone though although it gets hot and battery life is awful.
 
Which network does this MVNO use?(guessing Sprint OR VZW based off the scant info I'm finding......)
 
Pretty sure that you can just nandroid restore the stock rom matching that OS level that you did, and then fastboot flash the stock recovery from another CID but matching the same revision level of the stated stock software level, and the OTA will work for you.

Then, reinstall TWRP and press on.

I know that I've helped others do that with the M8 and they came out just fine.

Not sure what would prevent that working on the M9.
 
Which network does this MVNO use?(guessing Sprint OR VZW based off the scant info I'm finding......)
I have no idea.

Pretty sure that you can just nandroid restore the stock rom matching that OS level that you did, and then fastboot flash the stock recovery from another CID but matching the same revision level of the stated stock software level, and the OTA will work for you.

Then, reinstall TWRP and press on.

I know that I've helped others do that with the M8 and they came out just fine.

Not sure what would prevent that working on the M9.
I thought you couldn't flash stuff from another CID? Wouldn't it give me an error or no?
 
Pretty sure that you can just nandroid restore the stock rom matching that OS level that you did, and then fastboot flash the stock recovery from another CID but matching the same revision level of the stated stock software level, and the OTA will work for you.

Then, reinstall TWRP and press on.

I know that I've helped others do that with the M8 and they came out just fine.

Not sure what would prevent that working on the M9.

I know it's a device from 3 generations ago, but this also worked on the One X.
 
I thought you couldn't flash stuff from another CID? Wouldn't it give me an error or no?
A lot of stuff you can't - but there's a whole lot also that simply doesn't matter, it's standardized.

HTC is not customizing each and every one of literally hundreds of software components for each CID - it's not necessary and it would be a terrible design if it were.

If you get the matching recovery (in general) with your stock nandroid backup together - and the flag at the top of your bootloader screen stops saying TAMPERED or CUSTOMIZED - however it's worded on the M9 - then the system is happy and the OTA ought to work just fine.

Hmmm... Don't recall, going by memory - but I don't think that you even need to relock the bootloader.

And if so, that's definitely no big deal, you can lock and unlock that all you want.

I've never seen an HTC OTA ever care that the bootloader was relocked, highly doubt that all of the rules suddenly changed for the M9.

Doing other isn't in HTC's support interests.
 
A lot of stuff you can't - but there's a whole lot also that simply doesn't matter, it's standardized.

HTC is not customizing each and every one of literally hundreds of software components for each CID - it's not necessary and it would be a terrible design if it were.

If you get the matching recovery (in general) with your stock nandroid backup together - and the flag at the top of your bootloader screen stops saying TAMPERED or CUSTOMIZED - however it's worded on the M9 - then the system is happy and the OTA ought to work just fine.

Hmmm... Don't recall, going by memory - but I don't think that you even need to relock the bootloader.

And if so, that's definitely no big deal, you can lock and unlock that all you want.

I've never seen an HTC OTA ever care that the bootloader was relocked, highly doubt that all of the rules suddenly changed for the M9.

Doing other isn't in HTC's support interests.

Awesome, I would definitely try this out when my OTA comes.

Another question though, if I s-off and maybe flash the dev edition firmware(?) will I lose my carrier stuff like calling/texting? Thanks again for everyone replying in this thread.
 
Unless there were issues with the ROM you were flashing, you'd still be able to call/text no problem (if that's what you're asking)?

You may need to setup your APN's again, but that should be relatively easy.
 
Unless there were issues with the ROM you were flashing, you'd still be able to call/text no problem (if that's what you're asking)?

You may need to setup your APN's again, but that should be relatively easy.
To setup my APN would I need to contact my carrier for some details? Also, won't I be breaking anything from my 2 year contract that way or by unlocking my phone?
 
Which network does this MVNO use?(guessing Sprint OR VZW based off the scant info I'm finding......)
I have no idea.
Until you know the answer to this, APN is the least of your worries.

If this is a CDMA phone and you flash the developer GSM firmware - without an RUU to fall back on to fix - you could easily end up with a phone that you can't use on your carrier.

Now, seriously - what's the push for updating the firmware right now?

I'm feeling like we're talking about details but not the real issue ok.

If all you want is to flash a new rom, your best bet is to find one that others are already using that work on your network.

So let's see -

https://en.wikipedia.org/wiki/NTelos

CDMA PCS - if it's like other CDMA phones, I'll bet you don't have APN entries in your settings.

You might want to try a rom for Sprint or Verizon as @KOLIO suggests.

Or - customize your rom yourself by adding Xposed components and debloating, a little bit at a time.

Either path - keep those nandroid backups going ok.
 
Last edited:
Until you know the answer to this, APN is the least of your worries.

If this is a CDMA phone and you flash the developer GSM firmware - without an RUU to fall back on to fix - you could easily end up with a phone that you can't use on your carrier.

Now, seriously - what's the push for updating the firmware right now?

I'm feeling like we're talking about details but not the real issue ok.

If all you want is to flash a new rom, your best bet is to find one that others are already using that work on your network.

So let's see -

https://en.wikipedia.org/wiki/NTelos

CDMA PCS - if it's like other CDMA phones, I'll bet you don't have APN entries in your settings.

You might want to try a rom for Sprint or Verizon as @KOLIO suggests.

Or - customize your rom yourself by adding Xposed components and debloating, a little bit at a time.

Either path - keep those nandroid backups going ok.

Well I'm just asking for stuff that I might encounter along the way. Haha. Yes this is a CDMA phone and yes there is no APN settings. And no I would rather not flash a rom because I'd like to use just xpose for now. (suggest me a module for sense!)
Anyway, my real concern is the latest firmware and android 5.1. Because I heard they fixed some stuff and I would like my phone to be in the best condition. :) No rush though, I'm just bummed cause nTelos is taking too much of their time. And the fact that there are no resources for my CID anywhere. :\
 
Hey. I tried to install a leedroid awhile ago. I tried international but I had no signal. I then tried sprint and I have signal but no data. I restored back to stock to find clues on how can I get data.
I found this on ##data# and att.mvno took my attention and discovered it is at&t(?).
So does this mean I should've flashed at&t instead?

edit: Actually nevermind. at&t doesn't work as well. I give up.
 

Attachments

  • Screenshot_2015-08-07-03-00-44.png
    Screenshot_2015-08-07-03-00-44.png
    43.8 KB · Views: 136
Last edited:
Back
Top Bottom