CARRIER BLOCK UPDATE

[NCqTee]

Yep a no for me lol

[novares]

Funny, I am working on the same thing.
But different angle.
I am planning to desquise my note 7 with my existing devices.
I need to check if Market Helper still works.
So I don't get stupid notifications from Google Play that this or that app is not compatible with this device.

There is newer version that I have; link below.
Must create new Gmail/Google account first like from PC
Anyhow there are threads on xda "how to"
I have about 6 galaxy devices all from T-mobile. All legit
Link: edited
Just checked the link. The name of dev is the same
But link was rubbish.
Sorry for posting without checking.
App icon was the same so I took a bite.
Will look for legit link.

I just saw this now. Let me know how your progress fairs. Perhaps we can combine methods or team up. I like all of these efforts, this community makes me happy. Good job guys.

[rudolf.hohenfelse]

short summary of findings today:

it seems impossible to find a common flash approach for all n7 models/variants.

nobody knows why, but samsung created a bunch of different n7's. this goes far beyond 2nd source idea. they have developers gone craisy or they tried something completely new to proof (we will never know what it was because of the recall).

e.g. we found differences with the F model sold in the same region (under the hood there is a hidden 'black' and a hidden 'white' version with exactly same HW and SW revision). you cant't get rid of this kind of factory-branding, even when you flash a custom kernel/rom - the difference is still there after flashing. this is really weird and has never been observerd on any device before the n7.

what we have learned from today: we have to set focus on our friends from AU and CA to support them first - a common approach to all n7 versions/variants seems not feasable at the moment.

[rudolf.hohenfelse]

Rudolf thanks for the quick response. Can you make video on how to self generate as i dont want to brick the n7. Maybe if anything a personal step by step tut by you would be best imo.

Well, as @aztek already said: Generating a valid IMEI is only the first step. Now we need a safe way to flash the IMEI to n7. Then we need to proof it in the wild with an device already blocked by carrier. So please be patient...

[Elbegev]

I can try on mine, I'm from New Zealand and was among the first to have mine blocked

[novares]

Rudolf thanks for the quick response. Can you make video on how to self generate as i dont want to brick the n7. Maybe if anything a personal step by step tut by you would be best imo.

Well, as @aztek already said: Generating a valid IMEI is only the first step. Now we need a safe way to flash the IMEI to n7. Then we need to proof it in the wild with an device already blocked by carrier. So please be patient...

Currently just the Support Assistant team has been working on the IMEI changing portion of this. Alliance++ has been working on the IMEI # issue (validation, swapping, etc...). Good R&D so far on that end.

Later tonight I'll be putting a guide together for my Alliance++ team to attempt to do it to their devices as well for testing. (those who have Windows 7 computers, as it seems this method is only fairing well on Win7 so far). Those amongst Alliance++ people, let me know who can help test later.

[edit] Rudolf, keep in mind, when we are searching for IMEI #'s encoded in the hex file, if our IMEI number appears as (example): 7 49 37 68 30 68 39 50 30 the conversion of the IMEI needs to be equivalent to: 7A 94 73 86 03 86 93 05 03 (example again)

This is how the IMEI# is hidden within the backup file.

[novares]

I can try on mine, I'm from New Zealand and was among the first to have mine blocked

THIS would be the only non Alliance++ member I'd consider for testing this not fully authenticated method yet, as he actually has his phone disabled.

@Elbegev: Do you have your SIM card still and another phone you're using (obviously), as well as an active service on your line which would propagate signal should we test on your disabled phone?

[michael.kalaitzakis]

I have a 930F Australian edition here I'm willing to do some testing if u need to guys keep up the good work!

[kojak2424]

Yep a no for me lol

It does have to be paid off first. I bought mine outright therefore I was able to unlock it.

[NCqTee]

Az, you know I'm here if needed

Sent from my flaming hot Note 7 via Tapatalk!

We are the ALLIANCE!!!!

[COBRAED2003]

Hey guys/gals! Brand new to the forum and super awesome so far. I just took care of that pesky 60% battery charge on my Note 7 using your amazing tutorials! Thank you so much. Please, keep up all of the great work.

I love my Note and do not want to give it up at all. I am looking forward to seeing if this great community can come up with some way for us to bock off the upcoming Note killer that will be released here soon.

Thanks again for everything!

[population96]

Just signed up to the forums, glad to see other like minded people who also will not let go of this awesome phone! Like Kojak, I also have access to OPUS, I'm an AT&T corporate store employee. Let me know if there is anything I can do to help. I was looking to try and find a way to use my Nexus 6P IMEI on the Note to prevent any bricking updates or blacklisting, and found this forum while googling. But I might be beat, because my phone got the APK1 firmware update before I could catch it

[capoceo]

Rudolf thanks for the quick response. Can you make video on how to self generate as i dont want to brick the n7. Maybe if anything a personal step by step tut by you would be best imo.

Well, as @aztek already said: Generating a valid IMEI is only the first step. Now we need a safe way to flash the IMEI to n7. Then we need to proof it in the wild with an device already blocked by carrier. So please be patient...

Currently just the Support Assistant team has been working on the IMEI changing portion of this. Alliance++ has been working on the IMEI # issue (validation, swapping, etc...). Good R&D so far on that end.

Later tonight I'll be putting a guide together for my Alliance++ team to attempt to do it to their devices as well for testing. (those who have Windows 7 computers, as it seems this method is only fairing well on Win7 so far). Those amongst Alliance++ people, let me know who can help test later.

[edit] Rudolf, keep in mind, when we are searching for IMEI #'s encoded in the hex file, if our IMEI number appears as (example): 7 49 37 68 30 68 39 50 30 the conversion of the IMEI needs to be equivalent to: 7A 94 73 86 03 86 93 05 03 (example again)

This is how the IMEI# is hidden within the backup file.

Samtung obviously has most likely used a scrambling coding when trying to use common hex tools when it comes to changing or modification. As i have no software paid tools like samtung tool pro chimeratool or hardware like SPT riff furious gold volcono z3x mircal box octoplus atf box sigma key gcpro key Asansam Samsung Micro UART nspro box just to name a few i feel if anyone has such access to these things they may have a certain advantage to experiment. I experimented with the imei of a verizon s7 edge and messed up. The imei shows but now its got a status of blocked and shows as no service which blows. Got any help for me? Possible to copy my fiance's imei to it and have it running again or do i need a new imei via cert flash or remotely serviced? Good thing i decided to do testing on the s7 before on the n7 id be even more upset than i am now without the calm.

[CleanSC]

In for updates on this.

And I echo the thanks for the tuts on here. I was referred over from MizSxxyBych on xda. Thanks so much for that!! I was able to bring my phone back.

Curious as to how this convo progresses.

[NCqTee]

In for updates on this.

And I echo the thanks for the tuts on here. I was referred over from MizSxxyBych on xda. Thanks so much for that!! I was able to bring my phone back.

Curious as to how this convo progresses.

Heyyy that's me! Welcome!!!!