CARRIER BLOCK UPDATE

[novares]

once we generate an imei, how do we change it on our phone? Is there an app or developer code we have to enter ?

Read back and catch up. All of this is addressed.

We're still working on testing that. We've changed the IMEI # but then service cuts out upon doing so. So, we're still testing multiple methods including possible methods to root snapdragon roms on all carriers.

Working as best we can and there's no guarantees. This update everyone worries about will be OTA, which means if you have updates DISABLED you should not be affected by the carrier brick. In the mean time, we're looking into methods that can make things like this easier to prevent in the future.

[ronnie.koh]

once we generate an imei, how do we change it on our phone? Is there an app or developer code we have to enter ?

Read back and catch up. All of this is addressed.

We're still working on testing that. We've changed the IMEI # but then service cuts out upon doing so. So, we're still testing multiple methods including possible methods to root snapdragon roms on all carriers.

Working as best we can and there's no guarantees. This update everyone worries about will be OTA, which means if you have updates DISABLED you should not be affected by the carrier brick. In the mean time, we're looking into methods that can make things like this easier to prevent in the future.

Hiya. The imei block will be OTA? Does this mean that the disabler actions taken that have stopped the battery limitation will also stop the imei block?

Sent from my SM-N930F using Tapatalk

[beowulf381]

once we generate an imei, how do we change it on our phone? Is there an app or developer code we have to enter ?

Read back and catch up. All of this is addressed.

We're still working on testing that. We've changed the IMEI # but then service cuts out upon doing so. So, we're still testing multiple methods including possible methods to root snapdragon roms on all carriers.

Working as best we can and there's no guarantees. This update everyone worries about will be OTA, which means if you have updates DISABLED you should not be affected by the carrier brick. In the mean time, we're looking into methods that can make things like this easier to prevent in the future.

Hiya. The imei block will be OTA? Does this mean that the disabler actions taken that have stopped the battery limitation will also stop the imei block?

Sent from my SM-N930F using Tapatalk

Of course not. Disabling packages just prevents the bricking updates as in Canada (which will kill wifi, radio and bluetooth) or the US (which will kill any further charging). But stopping those will help most users as this is time critical stuff. The IMEI block can't be stopped this way. The development and testing for keeping save from this is in progress.

[novares]

once we generate an imei, how do we change it on our phone? Is there an app or developer code we have to enter ?

Read back and catch up. All of this is addressed.

We're still working on testing that. We've changed the IMEI # but then service cuts out upon doing so. So, we're still testing multiple methods including possible methods to root snapdragon roms on all carriers.

Working as best we can and there's no guarantees. This update everyone worries about will be OTA, which means if you have updates DISABLED you should not be affected by the carrier brick. In the mean time, we're looking into methods that can make things like this easier to prevent in the future.

Hiya. The imei block will be OTA? Does this mean that the disabler actions taken that have stopped the battery limitation will also stop the imei block?

Sent from my SM-N930F using Tapatalk

@ronnie.koh: No, IMEI blacklists are not in the form of an update. The update that's going to release to "render Note 7 devices useless and disable wi-fi" yadda yadda will be OTA. Can't be done if OTA updates are literally disabled from the core.

IMEI blacklist is done by either the carrier or overall hardware blacklist databases. Once they're blacklisted they're EXTREMELY hard to have removed (the proper way).

[edit] Yes @beowulf381, exactly. Seems we both answered at the same time. Thank you for clarifying for him.

@marcel.ames: Please read back a few pages and you'll catch up to where we are at.

@population96: Interesting. My device is registered through AT&T as well. You should PM me, I may have some questions. Being a corporate AT&T employee yourself, do you have any information to provide us with about potential IMEI# blacklist or will AT&T just focus on OTA updates attempting to render the phone useless?

@Elbegev: Did NZ blacklist IMEI# or just send out update to null phone?

[ronnie.koh]

Read back and catch up. All of this is addressed.

We're still working on testing that. We've changed the IMEI # but then service cuts out upon doing so. So, we're still testing multiple methods including possible methods to root snapdragon roms on all carriers.

Working as best we can and there's no guarantees. This update everyone worries about will be OTA, which means if you have updates DISABLED you should not be affected by the carrier brick. In the mean time, we're looking into methods that can make things like this easier to prevent in the future.

Hiya. The imei block will be OTA? Does this mean that the disabler actions taken that have stopped the battery limitation will also stop the imei block?

Sent from my SM-N930F using Tapatalk

@ronnie.koh: No, IMEI blacklists are not in the form of an update. The update that's going to release to "render Note 7 devices useless and disable wi-fi" yadda yadda will be OTA. Can't be done if OTA updates are literally disabled from the core.

IMEI blacklist is done by either the carrier or overall hardware blacklist databases. Once they're blacklisted they're EXTREMELY hard to have removed (the proper way).

[edit] Yes @beowulf381, exactly. Seems we both answered at the same time. Thank you for clarifying for him.

@marcel.ames: Please read back a few pages and you'll catch up to where we are at.

@population96: Interesting. My device is registered through AT&T as well. You should PM me, I may have some questions. Being a corporate AT&T employee yourself, do you have any information to provide us with about potential IMEI# blacklist or will AT&T just focus on OTA updates attempting to render the phone useless?

@Elbegev: Did NZ blacklist IMEI# or just send out update to null phone?

Thanks for clarifying guys. Tbh I was extremely surprised when I read that 'what we are all worried about' was OTA. I had assumed that this worry was the imei block.

Fingers crossed on a remedy..

Sent from my SM-N930F using Tapatalk

[thomas.bernal]

Read back and catch up. All of this is addressed.

We're still working on testing that. We've changed the IMEI # but then service cuts out upon doing so. So, we're still testing multiple methods including possible methods to root snapdragon roms on all carriers.

Working as best we can and there's no guarantees. This update everyone worries about will be OTA, which means if you have updates DISABLED you should not be affected by the carrier brick. In the mean time, we're looking into methods that can make things like this easier to prevent in the future.

Hiya. The imei block will be OTA? Does this mean that the disabler actions taken that have stopped the battery limitation will also stop the imei block?

Sent from my SM-N930F using Tapatalk

@ronnie.koh: No, IMEI blacklists are not in the form of an update. The update that's going to release to "render Note 7 devices useless and disable wi-fi" yadda yadda will be OTA. Can't be done if OTA updates are literally disabled from the core.

IMEI blacklist is done by either the carrier or overall hardware blacklist databases. Once they're blacklisted they're EXTREMELY hard to have removed (the proper way).

[edit] Yes @beowulf381, exactly. Seems we both answered at the same time. Thank you for clarifying for him.

@marcel.ames: Please read back a few pages and you'll catch up to where we are at.

@population96: Interesting. My device is registered through AT&T as well. You should PM me, I may have some questions. Being a corporate AT&T employee yourself, do you have any information to provide us with about potential IMEI# blacklist or will AT&T just focus on OTA updates attempting to render the phone useless?

@Elbegev: Did NZ blacklist IMEI# or just send out update to null phone?

"Can't be done if OTA updates are literally disabled from the core."
How do you do this? I thought I had blocked updates and one morning my phone was updating.

[beowulf381]

Hiya. The imei block will be OTA? Does this mean that the disabler actions taken that have stopped the battery limitation will also stop the imei block?

Sent from my SM-N930F using Tapatalk

@ronnie.koh: No, IMEI blacklists are not in the form of an update. The update that's going to release to "render Note 7 devices useless and disable wi-fi" yadda yadda will be OTA. Can't be done if OTA updates are literally disabled from the core.

IMEI blacklist is done by either the carrier or overall hardware blacklist databases. Once they're blacklisted they're EXTREMELY hard to have removed (the proper way).

[edit] Yes @beowulf381, exactly. Seems we both answered at the same time. Thank you for clarifying for him.

@marcel.ames: Please read back a few pages and you'll catch up to where we are at.

@population96: Interesting. My device is registered through AT&T as well. You should PM me, I may have some questions. Being a corporate AT&T employee yourself, do you have any information to provide us with about potential IMEI# blacklist or will AT&T just focus on OTA updates attempting to render the phone useless?

@Elbegev: Did NZ blacklist IMEI# or just send out update to null phone?

"Can't be done if OTA updates are literally disabled from the core."
How do you do this? I thought I had blocked updates and one morning my phone was updating.

Maybe you missed one of the packages: Here is what i have blocked:

com.policydm
com.sec.android.soagent
com.wssyncmldm
com.sec.spp.push
com.sec.android.app.samsungapps
com.samsung.knox.appsupdateagent
com.samsung.firmware.sensorhub
com.samsung.android.firmware.tsp

Especially the last 2 are most important if they exist on your device.

Depending on your model / provider not all of the packages are installed.
Plus, it can be that there are some more for you, e.g. provider specific apk's.
Look for att, sprint, t-mobile etc.

As a second line of defense i use a firewall too:

https://play.google.com/store/apps/deta ... ewall.beta

You can monitor which app/package wants to access internet. Then you can decide if you allow or deny. I personally start with deny access for the whole part of system apps beginning with: AASAservice, Android System... It's just a large amount what is blocked at once, but my devices are working fine and all the update packages are included to have no internet access, just in case...

[Fatwoman]

I am testing, can anyone give me an IMEI of NOTE 7s phone preferably not from AT&T. Verizon is best. We only have 2 days!

@keith.horn
@TeresaDusel
@MightyJoeTYoung
@Demosthenes

[flexxx228]

Why not at&t? Are we the sacrificial lambs? :'(

[MasKScarin]

I am testing, can anyone give me an IMEI of NOTE 7s phone preferably not from AT&T. Verizon is best. We only have 2 days!

@keith.horn
@TeresaDusel
@MightyJoeTYoung
@Demosthenes

Would 2 Canadian IMEI's be of any use to you?

[novares]

I am testing, can anyone give me an IMEI of NOTE 7s phone preferably not from AT&T. Verizon is best. We only have 2 days!

@keith.horn
@TeresaDusel
@MightyJoeTYoung
@Demosthenes

Would 2 Canadian IMEI's be of any use to you?

You guys are the ones getting bricked. So, I don't think so. I was just assuming if I tried with Verizon (the only carrier to not say they'd brick phones), perhaps it would have been good for tests. I did use a Verizon IMEI # from a note 7.

I'll post my findings and methods shortly. I'm at a stopping point between all the other work I need to get done and testing and developing this.

We were able to extract the IMEI #, change it, put it back on the phone and disrupt service temporarily until it came back on with the new IMEI#. However, since we aren't editing the build_prop file which displays the IMEI # to the OS, it doesnt show up as changed. I believe it's only changing in the non-volatile memory of where it's stored: /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001

So, perhaps once I post my methods other users can develop them further.

[EDIT] DISCLAIMER: *OBVIOUSLY* this entire thread is based on learning experiences as changing IMEI #'s is illegal. I do not condone or promote this. Everything documented here is for users to learn, not break the law.

[capoceo]

We were able to extract the IMEI #, change it, put it back on the phone and disrupt service temporarily until it came back on with the new IMEI#. However, since we aren't editing the build_prop file which displays the IMEI # to the OS, it doesnt show up as changed. I believe it's only changing in the non-volatile memory of where it's stored: /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001

So, perhaps once I post my methods other users can develop them further.

[EDIT] DISCLAIMER: *OBVIOUSLY* this entire thread is based on learning experiences as changing IMEI #'s is illegal. I do not condone or promote this. Everything documented here is for users to learn, not break the law.

Are you flashing the imei remotely using one of those boxes or is the uart cable being used? I mentioned on here i did what you did using 2 s7 edges and the imei on one got a blocked lost status. In other words in what form is the imei in a backup efs form using a app help creating it like something from xposed or titanium backup?

[novares]

We were able to extract the IMEI #, change it, put it back on the phone and disrupt service temporarily until it came back on with the new IMEI#. However, since we aren't editing the build_prop file which displays the IMEI # to the OS, it doesnt show up as changed. I believe it's only changing in the non-volatile memory of where it's stored: /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001

So, perhaps once I post my methods other users can develop them further.

[EDIT] DISCLAIMER: *OBVIOUSLY* this entire thread is based on learning experiences as changing IMEI #'s is illegal. I do not condone or promote this. Everything documented here is for users to learn, not break the law.

Are you flashing the imei remotely using one of those boxes or is the uart cable being used? I mentioned on here i did what you did using 2 s7 edges and the imei on one got a blocked lost status. In other words in what form is the imei in a backup efs form using a app help creating it like something from xposed or titanium backup?

I'll be posting my findings shortly, but no not using uart cable. I don't want to open the the phone up. If that was the case uart cable would be ezpz. But, since this phone is glued shut to retain its IP68 water resistant rating, that proves to be a bit harder.

What we've learned with the Note 7 is apparently you need to use an IMEI # of another Note 7. If you have a (US) Verizon Note 7 and you trade IMEI#'s with someone on an International Carrier- it should work just fine. Random IMEI#'s cannot be used for the Note 7. Considering S7 and Note 7 have the same exact logic boards, swapping them may or may not work but no normal user is going to be doing that.

No, Xposed is used for rooted devices. We are doing this the 'unrooted' way. Or at least trying and no we aren't using efs backup files. I'll post shortly.

[novares]

Please follow new developing topic: viewtopic.php?f=3&t=145