So I had my Verizon HTC One M8 rooted and that was enough for my needs. I didn't mess with it further.
Well then Verizon started pestering me with update notices for... what was it? 4.4.3? Anyways, I got sick of them and hit "OK" next thing I know my phones in a 1 to 2hr upgrade cycle with no warning. I was on call for my job! Then, when it came back all my root apps were disabled... you know the story.
So the only option to re-root it was sunshine.
Now I'm getting pestered with the same notices again to go to 4.4.4
They are really bad. I can't even unlock the phone. They are in your face and obnoxious. I can't get rid of them. I don't want to let Verizon make my phone even worse. Any advice that doesn't leave me shelling out $25? Can I call Verizon and pitch a fit? I DO NOT WANT THIS.
You can install a custom ROM and those popups are blocked automatically. I recommend the new Clean Rom
---------- Post added at 12:35 PM ---------- Previous post was at 12:34 PM ----------
thewagdy said:
You can install a custom ROM and those popups are blocked automatically. I recommend the new Clean Rom
Click to expand...
Click to collapse
It is mostly stock and should be exactly what you need.
thewagdy said:
You can install a custom ROM and those popups are blocked automatically. I recommend the new Clean Rom
---------- Post added at 12:35 PM ---------- Previous post was at 12:34 PM ----------
It is mostly stock and should be exactly what you need.
Click to expand...
Click to collapse
I cannot install a rom. I lost Root with the last update and do not have S-off. I didn't even know what S-off was until that update. It's extremely irritating to have to keep up on this nonsense just to own a smartphone.
Sunshine should have given you S-OFF. Also, you should be able to run Sunshine in the same phone again without paying again.
charliemopps said:
I cannot install a rom. I lost Root with the last update and do not have S-off. I didn't even know what S-off was until that update. It's extremely irritating to have to keep up on this nonsense just to own a smartphone.
Click to expand...
Click to collapse
If you used Sunshine on 4.4.3 you are S-off and bootloader unlocked. If you currently have root you flashed a custom recovery and then SU, right?
So you have everything in place to just flash a rom and be done with it.
Scrosler's CleanROM is just like stock, but de-bloated of most of the VZW and some of the HTC bloatware.
If you want pure stock flash his stock rooted 4.4.3 rom. Nothing changed to the original firmware except it's rooted and the SD write protection removed.
No, I did not use sunshine.
It was the only option, I did not do it. I'm poor.
I was hoping there was some option to gain root without it. If not, I'm just screwed.
I am s-off and on Viper ROM and I am being pestered with the update as well. It even downloaded it for me without me knowing. Then it forced me to select a time to install it so I had to pick 12am so I have to figure out how to dodge this nonsense, i am waiting for the newe Viper to update to 4.4.4
LibertyMonger said:
I am s-off and on Viper ROM and I am being pestered with the update as well. It even downloaded it for me without me knowing. Then it forced me to select a time to install it so I had to pick 12am so I have to figure out how to dodge this nonsense, i am waiting for the newe Viper to update to 4.4.4
Click to expand...
Click to collapse
Just flash this until the next update where that nag will be removed.
No more nags...
if you're still on 4.4. 3 use weak sauce to temporarilyroot then use a root explorer and delete your OTA updater files or rename them. and I'm not positive of this but from what I thought I understood it depends on your hardware version whether or not firewater will work and that is the free s off version.this is my first HTC device alsobut I am a root user so that is what I look for in the only way to have permanent forever root on an htc is to S OFF when you first get the devicethen it doesn't really matter what happens after that you can always flash su to get root on any new update after you flashing your recovery..
and just FYI no none of this is necessary just to own a smartphone only if you're trying to be smarter than your smartphone then in that case I guess you have to work for it ie free hotspot or IE ad blocker ect. and everybody here already understand those types of benefits involve maintenance and your own research and time especially with the latest devices. sorry is it just me butI had already read most of the m8 forum by the time my MA got here I researched very thirdly on which phone I even wanted to get which ushered me capability and S OFF or permanent root before I even purchased the phone and already knew the wrist before I even took it to the computer for root for the first time. good luck ..bTW if you do get temporary root and want to move or rename or delete the update file that you downloaded so it will not actually go through it is in. /cache/fuma . just search how to disable your OTA updater per the firmware you are on with and do while you are running your temp root.
charliemopps said:
They are really bad. I can't even unlock the phone. They are in your face and obnoxious. I can't get rid of them. I don't want to let Verizon make my phone even worse. Any advice that doesn't leave me shelling out $25? Can I call Verizon and pitch a fit? I DO NOT WANT THIS.
Click to expand...
Click to collapse
It sounds like smartphones may not be for you, get a old dinosaur phone and you won't have to "deal" with updates.
What do you think pitching a fit to a CS rep will do? They don't have some magic button to stop your phone from receiving updates.
Either take the time and learn more about flashing and rooting and do it yourself or pay the people that have taken the time to figure out how and ask thoughtful questions to other people and get help along the way.
Advice: Sell your phone on Swappa and get something that's already flashed with cyanogen, or accept the update and suffer through the horrible indignity of allowing your phone to be updated to 4.4.4 and getting the stock flashlight that should have been there already.
I see a lot of similar questions, but am getting yes and no answers.
Background+Rant: after spending yesterday bashing my head against knox, i managed to get my new sm-g900p from oem 5.0 back to stock 4.4.2, towel-rooted successfully (keeping 0x0). Good, but not enough. without a real recovery to make a backup, samsung is actually putting me at more risk than ever at turning my phone into a brick (security my ***). plus the slow/ugly stock rom hurts my head after seeing what Android should be. They act like making a rewarding process dangerous is going to stop this entire community! Anyway enough ranting from a non-dev.
what i need to know is since i have NOT sent knox into lockdown mode(0x1), can i get knox out of the Bootloader? from what i understand, you can disable the knox apps using superSU, titanium, or a command prompt, but this will not effect the flash counter (not eliminating the risk of permanent 0x1). we flash bootloaders all the time with our recoveries, firmwares, and roms. If knox has not activated (ie blocking root, apps, etc) how is this bootloader different?
http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html seems hopeful as it involves extracting the firmware to linux, removing the knox code, repacking and reflashing. sounds like something even i could do, but would feel more comfortable downloading from a real developer.
Hopes and thoughts to go along with my disappointment and concerns?
3rdsurfer said:
I see a lot of similar questions, but am getting yes and no answers.
Background+Rant: after spending yesterday bashing my head against knox, i managed to get my new sm-g900p from oem 5.0 back to stock 4.4.2, towel-rooted successfully (keeping 0x0). Good, but not enough. without a real recovery to make a backup, samsung is actually putting me at more risk than ever at turning my phone into a brick (security my ***). plus the slow/ugly stock rom hurts my head after seeing what Android should be. They act like making a rewarding process dangerous is going to stop this entire community! Anyway enough ranting from a non-dev.
what i need to know is since i have NOT sent knox into lockdown mode(0x1), can i get knox out of the Bootloader? from what i understand, you can disable the knox apps using superSU, titanium, or a command prompt, but this will not effect the flash counter (not eliminating the risk of permanent 0x1). we flash bootloaders all the time with our recoveries, firmwares, and roms. If knox has not activated (ie blocking root, apps, etc) how is this bootloader different?
http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html seems hopeful as it involves extracting the firmware to linux, removing the knox code, repacking and reflashing. sounds like something even i could do, but would feel more comfortable downloading from a real developer.
Hopes and thoughts to go along with my disappointment and concerns?
Click to expand...
Click to collapse
I did a little reading on the xda thread that links to but other than it being done just because it can, I don't see the real usefulness in the exercise of removing knox from a stock bootloader.
As you already pointed out, getting anywhere with a stock rom is pretty much pointless without two things:
1. Root
2. Custom Recovery
First of all, lets face it, there is only so much you can do with a stock odexed rom. Secondly, I personally dont understand the need to keep the knox bit untripped. Even if you remove knox from the bootloader, once custom recovery is installed, I'm pretty sure you're going to trip the bit anyway.
He even states so in the thread here:
http://forum.xda-developers.com/showpost.php?p=51828541&postcount=102
---------- Post added at 02:25 PM ---------- Previous post was at 02:17 PM ----------
And FYI, no one to my knowledge has ever hard bricked a Sprint Galaxy S5 phone. The only real issue at the moment is once you flash the OD3 Lollipop firmware or newer (currently OF6 I think) or take the OTA update, flashing any firmware older than OD3 is blocked.
So I'm going back to stock from TEKXodus with a SkyHigh kernel as I have decided to sell my N5 and go back to the Note 4. There just isn't enough development for the N5, and that's not to take away from the devs that have put their time and effort in, but I just finally accepted that CM13 and/or AOSP ROMs will never be coming to the N5. So I'm selling my 5, and have come to see that there aren't many Android phone rooting/ROMming people in my area. EVERYONE has this Apple-induced fear of buying a rooted phone. I guess I get it since you never know how experienced the previous owner was. I'd be pissed if I bought a new paperweight for $500 too. Lol. BUt my questions are, if I go back to stock COK5, will my Knox counter still be 0 x 1 and the settings page say "custom" on firmware? Assuming I use Odin, will a stock COK5 .tar file also flash a stock kernel and recovery as well or will I still have TWRP? I have looked for the answers to these everywhere but haven't had any luck. Some help here would be great if anyone has experience with this. Any other tips would help too. Thanks guys, it's been fun, see you back on the Note 4.
Just odin to stock. Then factory reset.
Knox will still be tripped, but they'd have to boot into recovery to check.
You will have stock kernel and recovery.
No it won't say custom anymore.
Also samsung pay won't work after root.
Android_Monsters said:
Just odin to stock. Then factory reset.
Knox will still be tripped, but they'd have to boot into recovery to check.
You will have stock kernel and recovery.
No it won't say custom anymore.
Click to expand...
Click to collapse
You will also have a wake lock caused by tripping Knox if you are on the stock kernel.
Also don't forget Samsung Pay. Personally that might be grounds for an unhappy customer because it is one of the features.
Also for the op, the Note 5 has a dedicated cm dev working on Cm13 for the S6 and Note 5.
Sent from my SM-N920T using Tapatalk
I'm considering jumping to the S7. Is there a reliable, working root yet?
reliable yes
working yes
some issues yes
issues can be remedied for most people
sacnotsack said:
reliable yes
working yes
some issues yes
issues can be remedied for most people
Click to expand...
Click to collapse
What kind of issues? I'm getting mine tomorrow and I would like to root pretty much right away. I've been through the threads and didn't see much as far as issues.
metalfan78 said:
What kind of issues? I'm getting mine tomorrow and I would like to root pretty much right away. I've been through the threads and didn't see much as far as issues.
Click to expand...
Click to collapse
overheating, lag, extreme batter drain, but these can be fixed by setting the cpu governor to on-demand or interactive. those were the only issues I personally experienced, but was easily fixed.
occasionally I will have bad lag, but after a reboot all is well. speaking of boots....boot time is horrendous.
Well, the lag is what I'm trying to get rid of, which is what I'm currently getting with my LG G5. So, I guess switching to the S7 won't make much difference.
Sent from my LG-H830 using Tapatalk
Sounds fixable. I think I'll go stock for a day or so then root it.
I have read that if you freeze the bloat, that helps with battery and lag issues as well.
So, from what I've read, it has to do with the modified boot.img. I really just want to restore all my stuff from titanium backup
Maybe rooting isn't even worth it right now. Unless I root, restore, then flash stock boot.img, if possible.
metalfan78 said:
So, from what I've read, it has to do with the modified boot.img. I really just want to restore all my stuff from titanium backup
Maybe rooting isn't even worth it right now. Unless I root, restore, then flash stock boot.img, if possible.
Click to expand...
Click to collapse
Not really worth it... there are some workarounds. But, you will never get rid of the lag. Stay on stock until there is either a new root method or unlocked bootloader.
EDIT: Echoe Rom is out for the SMG930T and SMG935T !!!!!! No lag at all
Thats what I plan on doing for now
metalfan78 said:
Thats what I plan on doing for now
Click to expand...
Click to collapse
Flash the U firmware. Removes the bloat.
Is the bloat the only cause of the lag?
metalfan78 said:
Is the bloat the only cause of the lag?
Click to expand...
Click to collapse
No. The eng boot will cause a little lag and more battery drain than compared to stock.
lvpre said:
No. The eng boot will cause a little lag and more battery drain than compared to stock.
Click to expand...
Click to collapse
Ok, that's what I was reading. I think I'll wait it out a bit. I've had the phone for 24 hrs and that's the longest I've gone without rooting in like 7 years, lol.
https://drive.google.com/open?id=0B0yzuMcMjykeV0wwYnVmbmp0SnM
download this it will help with the CPU , lag , wifi not saving, battery drain, can log in to snapchat, debloat,.. etc
You'll brick your s7
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.
boobteg2 said:
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.
Click to expand...
Click to collapse
The US models are able to be rooted. You are not well informed if you believe otherwise. I highly doubt you "bricked" your phone, probably just a boot loop or stuck at a screen. it can be fixed.
The engineering boot is how we are able to obtain root. There are a ton of details on how it works, so I am not going to go into details.
please don't post misinformation, it only confuses the ones trying to learn.
-sent from my Rooted and stable Tmo S7
sacnotsack said:
The US models are able to be rooted. You are not well informed if you believe otherwise. I highly doubt you "bricked" your phone, probably just a boot loop or stuck at a screen. it can be fixed.
The engineering boot is how we are able to obtain root. There are a ton of details on how it works, so I am not going to go into details.
please don't post misinformation, it out lyrics confuses the ones trying to learn.
-sent from my Rooted and stable Tmo S7
Click to expand...
Click to collapse
You are right... there are working root methods... that works flawlessly with a few tweaks... In regards to the bricking, The firmware I've had the most issues with is PG1 but it is a simple fix, just disable or block security updates with titanium backup ... or alternatively you can install Echoe Rom which debloats, deodex's and deknox's. I've had zero issues with this rom. No bricks no boot loops and no lag. I hope this helps
boobteg2 said:
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.
Click to expand...
Click to collapse
It may not be the prettiest root, but it is a working root none-the-less. Other than the eng boot lag issues (which can be mitigated mostly through things like Govtuner, etc.), all apps that require root permissions work fine as intended. Bootloops can be avoided by disabling security policy services. Other than the random reboot every now and again, I'm running strong since the day root came out.
boobteg2 said:
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.
Click to expand...
Click to collapse
Wow talk about uninformed. I've been running a rooted Galaxy S7 for just about a month now. I had rooted even earlier then that but I didn't know about the security policy updating. Yeah, security caught up but it didn't brick the phone. Just reflash the stock files and everything is fine. Now that I've been able to freeze the security update policy I haven't had a problem.