Modified firmwares to save your note 7! No package disabler required! - Note 7 Guides, News, & Discussion

Follow my instructions very carefully and you you're note 7 is in the clear!!
https://drive.google.com/file/d/0Bw6tEApjkJtRODdGdElYTU45TGc/view?usp=drivesdk AT&T
https://drive.google.com/file/d/0Bw6tEApjkJtRMWhnT20xSHJubVk/view?usp=drivesdk SPRINT
https://drive.google.com/file/d/0Bw6tEApjkJtReVQ1UHdkZmlOQ3M/view?usp=drivesdk TMOBILE
https://drive.google.com/file/d/0Bw6tEApjkJtRMXNIakU3eWtINEk/view?usp=drivesdk VERIZON

---

I am assuming you have to be on the PH1 or lesser version in order for this to work? Your walk through for verizon README says nothing about what your phone should currently be on. There were many users who were unable to downgrade from PHE version (green battery, root block update).
Anyone with a verizon phone want to try this out? =]
EDIT- GOing through some of the files, is this in fact the PHE update modified? If so, there should also be a warning that this will remove root for anyone that had it or did I miss something and the PHE version is now rootable?

---

I apologize I should have been more clear, this is not for anyone who has the original gray battery, rootable firmware, this is mainly for green batterys that have lost their PACKAGE disabler, so far the firmware takes the splash screen out and the update notification, follow rest of instructions to never worry about forced update to death firmware.....if you have root no obstacle is big to overcome for the sheer capability of being able to write systems files....

---

oook, so this is in fact for PHE firmwares, just modifies the system apks with the ones you provided and removes the update/flash screen.
---------- Post added at 12:25 PM ---------- Previous post was at 12:20 PM ----------
My next question would be, since the apps crash out, is it safe to say that something will still be calling for them in the background? Would this cause battery drain, wake locks etc?

---

Well I say green battery update because it also works on the tmobile AP14 firmware, also it hasn't been tested on VERIZON note 7 but I'm confident that the files will flash because they are signed and they are not images which seem to be the only partitions that don't flash due to an encrypted signature of the bootloader. So when u you install a system app on itself it more accurately corrupts the app and it ceased to function, which is literally what the note7alliances shield app v2 does. I know this because after I stated on their website that installing system apps on top of themselves disables them, they came out with shield v2 the next day and then banned me. Suspicious, but I'm not accusing anyone of anything lol. To answer your question, anytime an app calls on the corrupted app u get a failed app splash message so don't do this corruption to any other app other than the system update apps

---

Thanks for the post ?
Proud owner of the Samsung Galaxy Note 7 ?. Take that Samsung ???.

---

I am glad ro hear that there are some workarounds for people who have been victims of the capping firmwares, I am lucky, I am using my green batt icon note 7, charging 100%, as here in Mexico no capping or blocking are being made, I use an always floating batt temp indicator, and it never goes above 4 or 5 degrees above ambiental temperature, I have been using my note 7 for 6 months now!

---

Anything available for the Canadian variant? W8 model.

---

Hi everyone. Just curious. I have a Verizon note 7 with green battery icon, working great with package disabler. Since its unlocked I'm using Simple Mobile which uses T-Mobile's network. My question is can I flash the T-Mobile modified firmware here on a Verizon variant to avoid the issues that the Verizon firmware is creating when using T-mobile? I'm assuming it will run smoother this but will the phone safely accept it? Or stick with the Verizon firmware for the Verizon variant?

---

Good work, but stop with the v2 nonsense
akiraO1 said:
Well I say green battery update because it also works on the tmobile AP14 firmware, also it hasn't been tested on VERIZON note 7 but I'm confident that the files will flash because they are signed and they are not images which seem to be the only partitions that don't flash due to an encrypted signature of the bootloader. So when u you install a system app on itself it more accurately corrupts the app and it ceased to function, which is literally what the note7alliances shield app v2 does. I know this because after I stated on their website that installing system apps on top of themselves disables them, they came out with shield v2 the next day and then banned me. Suspicious, but I'm not accusing anyone of anything lol. To answer your question, anytime an app calls on the corrupted app u get a failed app splash message so don't do this corruption to any other app other than the system update apps
Click to expand...
Click to collapse
First let me say, good job. Having another method to protect Note 7 users is always a plus and for that I say good job.
I might try this out, and if solid recommend it for users.
Now that part that has been bothering me. Your timeline about you being banned and the Alliance v2 App.
Here you say one day after you told the Alliance that installing system apps on top of themselves you were banned and v2 was released.
On the rebels site you said a week (this screenshot is before you said that and then got in the fight with the one dude and the thread was deleted)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Either way I wish I was that fast of a developer in the conditions I was in. (yes I am the developer of the Alliance Shield v1, v2 and v3).
Shield v2 took a little over two weeks to develop because at the time I was in the desert of California for two months. I am in the Army and my unit was there training. There are plenty of Facebook posts in the Alliance group about my conditions, one bar 3g tethered to a laptop in the back of a truck in a metal box.
Has it ever occurred to you that you though about/discovered the same idea we already had? It is possible, but to say that it was your idea, with no proof is what makes us mad.
Either timeline you want, one day or one week this screenshot from the Shield v2 Repo will prove that we had the idea before you told us as it was in development for 15 days before it was released.
We called this method the Solid Explorer method because that is the name of the App we were using to extract and install the APK's. We are digging for posts but we think we first started talking about it on December 3rd. Once v1 was blocked by Samsung we sprung into action on v2 using that method as it does not depend on Samsung
I don't want this to take away from your work, it is good work. Just tone down the the whole Alliance stole my idea talk. If that is how you felt, you should have contacted us, we are very nice to work with when you approach us. When you go behind our back saying we stole your idea is when we get upset.
EDIT: found it Nov 28 the Solid Explorer method was posted by a Mod for our site
https://note7alliance.com/viewtopic.php?f=19&t=30&p=51&hilit=Solid+Explorer#p51

---

The links in the first post no longer work. @akiraO1 can you please repost these?
Thanks!

---

Ill get right on It