I have a converted to dev retail Note 4. Still running the stock rom and on oscar_kernel_v0.2. This evening I got notice of a security update from verizon. My feeling is not to take the update, but that's because I'm not sure. Is it safe to take the update or not?
Sent from my N910V converted to dev.
I would stay away. Verizon is evil and you will regret taking that update. If you have custom kernel then you must have custom recovery. With both those things being custom the update won't work anyway. Will probably get you in bootloop.
Sent from my Unlocked/Rooted SM-N910V using XDA-Developers mobile app
Google issues a monthly security update for Android. For Nexus devices, it's OK to take these updates.
For devices like ours that took a year and a half to root, I'd stay away no matter how much it nags.
Many custom ROMs disable such warnings.
Use Titanium to freeze sdm.apk and you will not get the OTA notification any longer
Related
If I root my samsung fascinate... am I able to continuously update to the newer version of Android? Or does it require additional assistance from the good people of XDA? thank you in advance
Most likely will either not accept update or will lose root upon update.
That's what happened last time.
Sent from my SCH-I500 using XDA App
so if new updates from google android comes out, even if I root the phone i can't just go and download the new version?
If all you do is install apparently that require root access, you should be fine. You'll just lose root access, and have to re-root afterward. If, however, you remove factory apps like Bing, or do any other OS modifications like the lag fix, there's a much bigger chance that the official updates will either fail, or cause problems. In that case, you either need to revert to stock before updating, or rely on xda developers to roll out customized versions of the updates that you can apply with your modifications in place.
Sent from my SCH-I500 using XDA App
So, the "official update" from say verizon will not work as well if I remove all the bloat ware... however, a rooted phone will be able to take in updates from Google ANdroid...like 2.3 or 3.3 etc... with no issues?
Perhaps to clarify a little further, I wish to purchase the Fascinate and root it. In the future, as new Android versions come out, I would rather take the official Android versions by Google instead of the updates by Verizon. Much like the Tmobile G1, is this possible once rooted?
I understand this is rather a long post so I appreciate all the help. Thank you.
There are no Google updates vs. OEM updates released through the carriers. All updates are carrier-released, regardless of the source (OEM OR Google), and are model-specific, largely due to OEM OS customizations and differing hardware. The only phones that get pure Google updates OTA (somebody correct me if I'm wrong) are the ones that are released with a 100% stock Android ROM from the factory.
The only OTA updates you will get for the Fascinate will be from Verizon, and will require a stock ROM, and most likely will need all original apps in place. If you want the pure Google updates, you will need to install a custom ROM with those updates.
Sent from my SCH-I500 using XDA App
Oh, and just to clarify, if you install a custom ROM that gives you pure stock Android, you will have to rely on the developer of that ROM to release updated versions that include the latest updates from Google. There are no OTA updates for custom ROMs, as they are not supported by Google, your carrier, or the phone manufacturer.
Sent from my SCH-I500 using XDA App
The only phone that truly gets untouched virgin updates would be the Nexus One, and even then the drivers are added by HTC.
The Moto Droid I guess would be the next one to also, but its been so long since I used a purely stock version that I remember if Moto adds apps at Verizon's request.
All carriers request what features/bloatware to install/not install. They send said requests to OEM, which turns around and incorporates the requests, and adds their custom branding/widgets/etc to send back to the carrier for testing. The carrier then has its own internal testing to verify requests and make sure no new prevalent bugs pop up. No one at Verizon (or any carrier really) actually does any coding of any kind.
What the OEM's receive from Google may be what you consider a "pure ROM" with "hooks" built in so that the various OEM's can add their custom homescreen, bloatware, brand specific widgets, etc. But, with the source being released most likely what happens is that this job now falls upon the OEM's themselves to write in their own "hooks", as Google just pumps out strictly OS generic builds into the ASOP.
In which case, either Sammy or Moto or whoever pulls that and fixes whatever issues, or they have internal builds going (which is more likely) that they tinker with to fix issues.
I believe Moto does this as evidenced by the lettering of the builds. Seems like they go through builds nightly when they are working on an update for a phone. I wouldn't be surprised if Sammy was the same way.
Sorry to make this post so long. Hope this helps.
So, a phone has to be "rooted" to allow full control over the phone. In this mode, I am allowed to make changes to the phone such as downloading ROMS that imitates the basic stock version of say the Froyo 2.2 In the future if a new version arrives, I can expect the upgrade from either Verizon (which I will have to unroot) or hope that the good people of XDA find ways to put new version of the Android in to my already rooted phone.
So, if I have a android phone and if the hardware is popular enough, people will continue finding ways to put new Android versions on the rooted phones through ROM. I hope I am understanding this matter correctly...
If that is the case, I now will go search in the threads for a way to root the Fascinate and find a ROM that lets me have the stock version of Android. I am very satisfied with the great people on this thread and I am very thankful for your responses and patience. Thank you very much.
Yes. You've got it down for the most part. If you root there are methods to unroot that will allow you to download the ota update. But with any luck the devs will get the froyo build long before it gets officially released and will be properly rooted by then.
Sent from my SCH-I500 using XDA App
Well I am on the horrible MF3 that requires the safestrap recovery to flash any compatible file. So I am not on a custom ROM I am only rooted.
I recently saw the notification that the new 4.3 update is ready to download .
My question is if I update will it still update and just take the root away? Or will I have to unroot and then upgrade?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
VeryCoolAlan said:
Well I am on the horrible MF3 that requires the safestrap recovery to flash any compatible file. So I am not on a custom ROM I am only rooted.
I recently saw the notification that the new 4.3 update is ready to download .
My question is if I update will it still update and just take the root away? Or will I have to unroot and then upgrade?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am still waiting on an answer for this also. I do know that it has been confirmed working to retain root when upgrading to 4.3 using "survival mode" in SuperSU. I purchased SuperSU Pro and enabled "survival mode". Then I defrosted the AT&T software updater (had it frozen previously to avoid the update) and Let the update to 4.3 download. I tried this twice and both times the 4.3 update failed to install at 25%. Maybe because I had previously uninstalled some of the AT&T BS apps. So I think I wasted $2.50 for SuperSU Pro. I have searched the forum and there are many people talking about having upgraded and retained root via this method, but nobody seems to want to clarify the steps of the process.
Some I am guessing maybe if you haven't removed any of the bloatware from your phone, you can use survival mode in SuperSU to retain root and take the 4.3 OTA update as normal. If you try it, let me know your mileage.
If I had any idea about MF3 and the locked bootloader I never would have gotten this phone. I hated iOS 7 and decided to come over to Android thinking modification would be much easier on the platform. With carriers locking bootloaders now, it's actually WORSE than having to wait for a jailbreak for an iOS version.
I accidently ota to mk2 from mf3 and re rooted with the mj6 method on att s4
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
jsgates said:
I am still waiting on an answer for this also. I do know that it has been confirmed working to retain root when upgrading to 4.3 using "survival mode" in SuperSU. I purchased SuperSU Pro and enabled "survival mode". Then I defrosted the AT&T software updater (had it frozen previously to avoid the update) and Let the update to 4.3 download. I tried this twice and both times the 4.3 update failed to install at 25%. Maybe because I had previously uninstalled some of the AT&T BS apps. So I think I wasted $2.50 for SuperSU Pro. I have searched the forum and there are many people talking about having upgraded and retained root via this method, but nobody seems to want to clarify the steps of the process.
Some I am guessing maybe if you haven't removed any of the bloatware from your phone, you can use survival mode in SuperSU to retain root and take the 4.3 OTA update as normal. If you try it, let me know your mileage.
If I had any idea about MF3 and the locked bootloader I never would have gotten this phone. I hated iOS 7 and decided to come over to Android thinking modification would be much easier on the platform. With carriers locking bootloaders now, it's actually WORSE than having to wait for a jailbreak for an iOS version.
Click to expand...
Click to collapse
Take a chill pill bro. This phone is still better than an iPhone. There is a safe root method now so no need to use survival mode just have to find a way to get to 4.3 which is all over the discussion boards.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Figuring that the stock one is so locked down, is it possible to take new features of an ota of the regular s5 and flash it to a dev edition one without messing up root? Things like updated boot, going from 4.4.x to 4.5, etc?
I recall but never fully understood that was the problem with the s4, they never sent out ota update for the dev edition....
Just debating getting an s5 dev edition, but don't want to be stuck with original firmware/software
Sent from my SM-G900V using Tapatalk
808phoneaddict said:
Figuring that the stock one is so locked down, is it possible to take new features of an ota of the regular s5 and flash it to a dev edition one without messing up root? Things like updated boot, going from 4.4.x to 4.5, etc?
I recall but never fully understood that was the problem with the s4, they never sent out ota update for the dev edition....
Just debating getting an s5 dev edition, but don't want to be stuck with original firmware/software
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
I believe you can upgrade from 4.4 to 4.5 but have to flash a unlocked bootloader like one from t-mobile or a international version. From what I gather from the Note 3 thread that's pretty much how they do it.
Well I know the s4 dev edition's problem was that they wouldn't update firmware for it, stuff like the boot (I forget which other things weren't able to get updated since they weren't sending out otas), which left the device with only it's original firmware
Sent from my SM-G900V using Tapatalk
You'll be able to do some stuff. Consider how cm releases updated firmware even though the carrier doesn't make a release. It's tough but possible.
Sent from my SM-N900V using Tapatalk
Let me start off by saying i appreciate all the developers who put in the hard work to make root and such possible. I could not imagine the frustration they go through.
So my question is about the future of this phones development, I feel like as of December 31 2016 that the chances of root are only for those with builds with/under pd8 (as far as I'm aware) (I am running PK1) everyone above pd8 build is SoL. So my question, is there any chance we will see full root for those of us on the newer builds? Also with the talks of the Nougat update around the corner will root be harder to achieve seeing as its new firmware and developers haven't had much time digging into it? My reason for wanting root is to have xposed running, viper4android and be able to debloat it. Forgive my ignorance but does it feel like the s7e development is stuck? I feel like maybe I would get a better experience if I traded in s7e for a device that has more stable development. I'm sorry if I offended anyone, if anything I just want to be informed.
isaac970 said:
Let me start off by saying i appreciate all the developers who put in the hard work to make root and such possible. I could not imagine the frustration they go through.
So my question is about the future of this phones development, I feel like as of December 31 2016 that the chances of root are only for those with builds with/under pd8 (as far as I'm aware) (I am running PK1) everyone above pd8 build is SoL. So my question, is there any chance we will see full root for those of us on the newer builds? Also with the talks of the Nougat update around the corner will root be harder to achieve seeing as its new firmware and developers haven't had much time digging into it? My reason for wanting root is to have xposed running, viper4android and be able to debloat it. Forgive my ignorance but does it feel like the s7e development is stuck? I feel like maybe I would get a better experience if I traded in s7e for a device that has more stable development. I'm sorry if I offended anyone, if anything I just want to be informed.
Click to expand...
Click to collapse
Nothing sure what kind of answer you're looking for that you wouldn't already know.
We only have root due to an engineering kernel.
Android 7 requires a different kernel. So we can't use it.
So unless we get a leaked engineering kernel for Android 7 then we will have to see if we can unlock the bootloader or discover some other kind of exploit. But I'm sure you already knew all of that.
The s7 is pretty much dead, are only hope is that a dev finds an exploit and capitalizes or an inside man leaks a file for Nougat.
AceDaMack said:
The s7 is pretty much dead, are only hope is that a dev finds an exploit and capitalizes or an inside man leaks a file for Nougat.
Click to expand...
Click to collapse
I just got CM14 (Nougat) on my Note 4, it made it into a whole new device way better than the laggy S7Edge. Here's hope that Nougat has some exploit and we can root it. CM14 is so smooth.
Root is supposed to work thru pk1 with eng kernel. When I update to official 7.x I am going to leave bootloader as is so I can still root.
I am not impressed that much with the new rom and hate the user interface, so I may go back to rooted 6.0 until if and when 7.x is rooted.
Sent from my SM-G935T using XDA-Developers mobile app
gaww said:
Root is supposed to work thru pk1 with eng kernel. When I update to official 7.x I am going to leave bootloader as is so I can still root.
I am not impressed that much with the new rom and hate the user interface, so I may go back to rooted 6.0 until if and when 7.x is rooted.
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
you may not be able to bootup android 7 with a MM bootloader. I ran into this problem in the past with my older notes. I couldn't get MM to work on a LP bootloader. It would awesome if someone could pull out the Beta nougat BL so we could revert it ends up being a problem.
black96ss said:
you may not be able to bootup android 7 with a MM bootloader. I ran into this problem in the past with my older notes. I couldn't get MM to work on a LP bootloader. It would awesome if someone could pull out the Beta nougat BL so we could revert it ends up being a problem.
Click to expand...
Click to collapse
Before I went back to stock to get the beta on the second phase, I went to stock Verizon and flashed their beta.
I was able to revert to stock tmo pk1, so am hoping that will be possible with the official 7.0 also, as that bootloader in rootable.
Sent from my SM-G935T using XDA-Developers Legacy app
gaww said:
Before I went back to stock to get the beta on the second phase, I went to stock Verizon and flashed their beta.
I was able to revert to stock tmo pk1, so am hoping that will be possible with the official 7.0 also, as that bootloader in rootable.
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
it was also BETA so they purposely could let you revert back if you didn't like the bugs ons BETA. that's why I said would be awesome if someone could pull the BETA boatloader so you have best of both worlds(pending on if they the official update wont boot up with a MM BL)
black96ss said:
it was also BETA so they purposely could let you revert back if you didn't like the bugs ons BETA. that's why I said would be awesome if someone could pull the BETA boatloader so you have best of both worlds(pending on if they the official update wont boot up with a MM BL)
Click to expand...
Click to collapse
If we can't revert back to a bootable mm and that us no sign of a rootable nouget, I may just kiss thus device good by and get a 935f.
Chen has multiboot working on it plus, he has a 7.0 Rom with Wi-Fi calling working. I may have to give up some tmo network features, but given that they have no plans to get the higher speed frequencies where I live, there is not much that I will be loosing out on.
Sent from my SM-G935T using XDA-Developers Legacy app
gaww said:
If we can't revert back to a bootable mm and that us no sign of a rootable nouget, I may just kiss thus device good by and get a 935f.
Chen has multiboot working on it plus, he has a 7.0 Rom with Wi-Fi calling working. I may have to give up some tmo network features, but given that they have no plans to get the higher speed frequencies where I live, there is not much that I will be loosing out on.
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I was thinking the same thing, what all features would you lose? obviously t mobile bloat and wifi calling. what LTE bands would we lose?
black96ss said:
I was thinking the same thing, what all features would you lose? obviously t mobile bloat and wifi calling. what LTE bands would we lose?
Click to expand...
Click to collapse
Would not loose WiFi calling - it is working in Chen's 935f ROM. I think we loose band 12 and possibly another, bit not sure.
The best way would be to ask him - but am going to search his threads before I ask.
Hi,
My Nexus 6P is on android 6.0.1 and after reading all the problems with Nougat, I would better stay on marshmallow.
However, my security patch is from April 2016.
I am rooted with stock 6.0.1 MHC19Q.
Would like to know if I can update only the security update and if so, how to do this ?
Sent from my Nexus 6P using xda premium
Lior84 said:
Hi,
My Nexus 6P is on android 6.0.1 and after reading all the problems with Nougat, I would better stay on marshmallow. However, my security patch is from April 2016. I am rooted with stock 6.0.1 MHC19Q.
Would like to know if I can update only the security update and if so, how to do this ?
Click to expand...
Click to collapse
I respect your decision to stay with MM, but I think it is misguided. There are many improvements that come with installing N, including the security updates. Security updates are part of the OS update and are not available separately. If you want the benefits of the latest security updates, you have to install 7.1.2.
Right now I'm on latest stock rooted with franco kernel and there are no issues. Except there's no xposed support.
But updating to nougat comes with no issues, so u should try, make a backup and flash.
I'm afraid to update because of brick possibility. From what I read, many users that updated, had a brick.
Sent from my Nexus 6P using xda premium
Lior84 said:
I'm afraid to update because of brick possibility. From what I read, many users that updated, had a brick.
Sent from my Nexus 6P using xda premium
Click to expand...
Click to collapse
Nah, don't be afraid, I'm flashing everything with twrp, factory images too. No issues.
If by brick issue you are talking about the boot loop of death that's a hardware issue and it happens while you are on Marshmallow, Nougat or a custom Rom. If you are talking about something else as long as your bootloader is unlocked and OEM Unlock is enabled in developer options you should be able to recover in the unlikely event of a flash going bad. Whether to flash or not is a tradeoff. You get the latest features and security updates on Nougat but you can't use Xposed (if that's actually important to you) and you will almost certainly get worse battery life on the latest versions of Nougat than you are getting on Marshmallow. Google has goosed the stock kernel settings lately resulting in worse battery life and the operating system and screen using more battery than previously. The only way to avoid that and stay up to date is to flash a custom kernel or flash a custom Rom.
I have bootloader unlocked from the first day of the phone. I really like this model (except for the camera that responds slower than the nexus 5 one) and would like to use it at least one more year. Really worry about the hard brick and because of its, staying till now on stock 6.0.1.
With N5, I flashed many roms, but in this one, I stayed one year on a single rom that came on it.
Sent from my Nexus 6P using xda premium
Lior84 said:
I have bootloader unlocked from the first day of the phone. I really like this model (except for the camera that responds slower than the nexus 5 one) and would like to use it at least one more year. Really worry about the hard brick and because of its, staying till now on stock 6.0.1.
With N5, I flashed many roms, but in this one, I stayed one year on a single rom that came on it.
Click to expand...
Click to collapse
The bootloop issue has nothing to do with the os update. It is because of dodgy hardware. It can happen from a damaged and degraded battery. Updating to nougat doesn't cause the issue.