I just got my phone rooted last week. Couple of questions, If I upgrade, I lose my root status, correct?
And how do I remove the service which causes the update notification to appear (it's the "Software update ready to install -- Android 6.0 Marshmallow" messaging) I'd just like to remove it if I can't upgrade without losing root. I just don't know the name of the service to remove.
If you do an OTA Update then you will lose root status. As far as removing services go I think there are two that you want to disable: SDM and one that has firmware update or something in the name.
Personally I would recommend installing PaulPizz or JasmineROM. PaulPizz already has those packages disabled.
shadeau said:
If you do an OTA Update then you will lose root status. As far as removing services go I think there are two that you want to disable: SDM and one that has firmware update or something in the name.
Personally I would recommend installing PaulPizz or JasmineROM. PaulPizz already has those packages disabled.
Click to expand...
Click to collapse
I have Jasmine and love it but I still get that nuisance message of the update. Any ideas?
---------- Post added at 08:08 PM ---------- Previous post was at 07:54 PM ----------
sportytony said:
I have Jasmine and love it but I still get that nuisance message of the update. Any ideas?
Click to expand...
Click to collapse
I think I found it. TB has 2 system update files, I froze them both and rebooted. no more nuisance message
Related
Hi, i just did root the device and when i went to update the software it says that operating system on my device has been modified are you guys experiencing the same thing?
wisnia99 said:
Hi, i just did root the device and when i went to update the software it says that operating system on my device has been modified are you guys experiencing the same thing?
Click to expand...
Click to collapse
That is part of the KNOX system. Rooting trips it. So Now your phone has been permanently marked in its hardware as tampered. Any system that checks it integrity will now fail it. You will never be able to get OTA updates now. Also if your employer uses KNOX on their servers you will not be able to use this phone to connect to their servers for email now. That is the purpose of KNOX to assure network providers that the phone is stock and not tampered with.
Even if you try to unroot it the KNOX flag will still be tripped. This was an issue on the NOTE 3 as well. Once the KNOX flag is tripped it cannot be reset as it is in the hardware.
Thanks for the explanation i really dont care for tripping Knox as long as i can update trough Keis or wait for new roms
You can use the Wanam Xposed module to fake your system status and still get System Updates. Thats what I did.
TheCrzy1 said:
You can use the Wanam Xposed module to fake your system status and still get System Updates. Thats what I did.
Click to expand...
Click to collapse
So if they do any firmware or radio updates wouldn't it break the root?
I ran into the problem on note 3 if u Odin back to stock u can get updates depending on devs if they have a new root method or not I generally never updated till I found I method to reroot
wisnia99 said:
Thanks for the explanation i really dont care for tripping Knox as long as i can update trough Keis or wait for new roms
Click to expand...
Click to collapse
You can still use Odin to flash roms if needed, or the wanam trick....
I installed wanam and set my status to official but the OTA system update still fails with the message my phone has been modified. I have galaxy tools installed with native tether enabled if that matters. What should i do to enable the update?
---------- Post added at 01:17 PM ---------- Previous post was at 12:30 PM ----------
The OTA Still errored with a "device has been modified" or some such. I ran triangle away and saw my binary status was 'custom'. I checked the triangle away 'auto reset at boot and that fixed my binary status. Now i well retry the update and rpt back.
---------- Post added at 02:05 PM ---------- Previous post was at 01:17 PM ----------
With my sprint note 4 wanam doesnt help nor triangle away although binary, flash and counter all look good in T Away
cknicker said:
I installed wanam and set my status to official but the OTA system update still fails with the message my phone has been modified. I have galaxy tools installed with native tether enabled if that matters. What should i do to enable the update?
---------- Post added at 01:17 PM ---------- Previous post was at 12:30 PM ----------
The OTA Still errored with a "device has been modified" or some such. I ran triangle away and saw my binary status was 'custom'. I checked the triangle away 'auto reset at boot and that fixed my binary status. Now i well retry the update and rpt back.
---------- Post added at 02:05 PM ---------- Previous post was at 01:17 PM ----------
With my sprint note 4 wanam doesnt help nor triangle away although binary, flash and counter all look good in T Away
Click to expand...
Click to collapse
Well, if you are rooted and have custom recovery you can't get updates, "ota's" you will have to wait for a dev to come up with a flashable update. Being on 4.4.4 no reason to worry... You are up to date.
Oh, btw, forget about triangle away... It no longer serves any purpose for us...
On stock unrooted you still get OTA. Even with Knox tripped. If you have a custom recovery and root dont take the ota if you are promoted. It will brick your phone and you will have to Odin back to stock anyway.
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
Prompted not promoted lol
Real_JESRadio said:
On stock unrooted you still get OTA. Even with Knox tripped. If you have a custom recovery and root dont take the ota if you are promoted. It will brick your phone and you will have to Odin back to stock anyway.
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
Prompted not promoted lol
Click to expand...
Click to collapse
In 'about device it now says my phone is up to date. My version numbers are below. Do they show my phone was really updated?
Baseband version
N910PVPU1ANIE
Kernel version
3.10.0-2774708
[email protected] #1
Wed Sep 17 19:19:02 KST 2014
Build number
KTU84P.N910PVPU1ANIE
SE for Android status
Enforcing
SEPF_SM-N910P_4.4.4_A019
Wed Sep 17 19:19:33 2014
Real_JESRadio said:
On stock unrooted you still get OTA. Even with Knox tripped. If you have a custom recovery and root dont take the ota if you are promoted. It will brick your phone and you will have to Odin back to stock anyway.
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
Prompted not promoted lol
Click to expand...
Click to collapse
Interesting. I came from the S3. Trying to take an ota wouldn't brick the phone but it would stop any future notifications of updates. We were fortunate to have a lot great devs there.
Btw, if you can still Odin the phone is not bricked. Bricked is dead...
jhill110 said:
Interesting. I came from the S3. Trying to take an ota wouldn't brick the phone but it would stop any future notifications of updates. We were fortunate to have a lot great devs there.
Btw, if you can still Odin the phone is not bricked. Bricked is dead...
Click to expand...
Click to collapse
Came from the S3 myself as well. Definitely a lot of active development until after SlimKat 7.0 and then that fell apart just in time for getting the Note 4. The numbers 4 and 3 i am starting to despise.
Slimteam, when i was keeping up with them, stated something about Android 5.0.
Maybe well get a surprise and see SlimPop for the Note 4. Slimpop isnt as euphonious as it looks to the eye...
On Topic: i wasnt able to update after rooting either as the phone is currently already UTD.
jhill110 said:
Interesting. I came from the S3. Trying to take an ota wouldn't brick the phone but it would stop any future notifications of updates. We were fortunate to have a lot great devs there.
Btw, if you can still Odin the phone is not bricked. Bricked is dead...
Click to expand...
Click to collapse
I mean soft bricked. And I should have elaborated, if you have a custom recovery you will soft brick taking an OTA update. Yes, some ROMs eliminate the OTA capability but some stock based ROMs will still get a notification.
---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------
cknicker said:
In 'about device it now says my phone is up to date. My version numbers are below. Do they show my phone was really updated?
Baseband version
N910PVPU1ANIE
Kernel version
3.10.0-2774708
[email protected] #1
Wed Sep 17 19:19:02 KST 2014
Build number
KTU84P.N910PVPU1ANIE
SE for Android status
Enforcing
SEPF_SM-N910P_4.4.4_A019
Wed Sep 17 19:19:33 2014
Click to expand...
Click to collapse
That is the latest update. A new one is coming soon. But you should be on the latest with that build.
Deleted.
So then i am rooted with TWRP recovery and still can load OTA updates? What happened to Knox?
Simple. Go to the download screen and see what the status says. Google it
Does anyone know what is in this latest update do I need it if so where can I get it in a flashable format that works with a rooted phone
My GS3 used to be rooted, but I had to install MDM/Airwatch on it for testing at work, so I unrooted it. The unroot was successful and MDM didn't complain, and it's pretty picky. That was a few months ago.
Now Sprint or Samsung is pushing an update to the phone (I don't know exactly what it is) but when I try to run the update, it reboots and extracts then gets an error complaining that /system/priv-app/GoogleServicesFramework.apk has unexpected contents.
I tried doing the update through Kies and it fails with an error saying that the phone was disconnected, even though it wasn't. I even set the phone to not sleep and no screenlock just so the connection would stay alive, but get the same error.
I did a factory reset but that didn't help. It seems like there's a problem with that APK but I don't know what to do about it.
So I just reimaged my wife's S3 with an unrooted image I'd previously downloaded. Everything seems fine but when I try to apply this same update, it gets the exact same error!
Do I need to reimage these phones with something different to get the updates working?
Philomorph said:
My GS3 used to be rooted, but I had to install MDM/Airwatch on it for testing at work, so I unrooted it. The unroot was successful and MDM didn't complain, and it's pretty picky. That was a few months ago.
Now Sprint or Samsung is pushing an update to the phone (I don't know exactly what it is) but when I try to run the update, it reboots and extracts then gets an error complaining that /system/priv-app/GoogleServicesFramework.apk has unexpected contents.
I tried doing the update through Kies and it fails with an error saying that the phone was disconnected, even though it wasn't. I even set the phone to not sleep and no screenlock just so the connection would stay alive, but get the same error.
I did a factory reset but that didn't help. It seems like there's a problem with that APK but I don't know what to do about it.
Click to expand...
Click to collapse
Philomorph said:
So I just reimaged my wife's S3 with an unrooted image I'd previously downloaded. Everything seems fine but when I try to apply this same update, it gets the exact same error!
Do I need to reimage these phones with something different to get the updates working?
Click to expand...
Click to collapse
in order to completely unroot your phone and hers is to Odin the stock tar...and since the both of you are on Sprint you can take the NJ2 tar...which is the Update that you are trying to install
Thanks, I'll give this a try! Do you think this is going to be a problem going forward though, where I can't get OTA updates anymore? The ROM I used put me on ND8 and is called:
L710VPUCND8_L710SPRCND8_L710VPUCND8_HOME.tar.md5
I'm not 100% sure where I downloaded it from, but I think it was from the link in this thread: http://forum.xda-developers.com/showthread.php?t=2738533
Philomorph said:
Thanks, I'll give this a try! Do you think this is going to be a problem going forward though, where I can't get OTA updates anymore? The ROM I used put me on ND8 and is called:
L710VPUCND8_L710SPRCND8_L710VPUCND8_HOME.tar.md5
I'm not 100% sure where I downloaded it from, but I think it was from the link in this thread: http://forum.xda-developers.com/showthread.php?t=2738533
Click to expand...
Click to collapse
Well ND8 and NJ2 are both 4.4.2 just NJ2 is a security update on top of ND8 and it will break root via Towel Root but the other 2 methods will still work
Doh wish I'd seen this before posting my own. Same exact problem here.
Where does one get the NJ2 tar? And will I be able to update after that? Otherwise how can we fix it so we can run updates and not have to wipe our phones every time?
---------- Post added at 04:05 PM ---------- Previous post was at 03:24 PM ----------
Guessing this is it? http://forum.xda-developers.com/gal.../stock-l710vpudnj2-pc-odin-flashable-t3007847
dtseiler said:
Doh wish I'd seen this before posting my own. Same exact problem here.
Where does one get the NJ2 tar? And will I be able to update after that? Otherwise how can we fix it so we can run updates and not have to wipe our phones every time?
---------- Post added at 04:05 PM ---------- Previous post was at 03:24 PM ----------
Guessing this is it? http://forum.xda-developers.com/gal.../stock-l710vpudnj2-pc-odin-flashable-t3007847
Click to expand...
Click to collapse
NJ2 is the update....
6th_Hokage said:
NJ2 is the update....
Click to expand...
Click to collapse
Right. I've gone ahead and applied it manually and it seems fine for now. But I'd like to be able to just apply them from OTA like a pleb without having to download **** and run Odin.
dtseiler said:
Right. I've gone ahead and applied it manually and it seems fine for now. But I'd like to be able to just apply them from OTA like a pleb without having to download **** and run Odin.
Click to expand...
Click to collapse
only sure way to OTA is to be completely stock including recovery...
6th_Hokage said:
only sure way to OTA is to be completely stock including recovery...
Click to expand...
Click to collapse
I've confirmed that I have the stock android recovery as well.
This new update is garbage, greatly reduced my battery life, wifi off, cloud sync off, minimal apps installed.
How do I rollback update?
Thru companion app im going to do the same...
---------- Post added at 06:38 PM ---------- Previous post was at 05:54 PM ----------
After trying it out it seems like Sony updated the companion app with 5.1 aswell. From here im not sure how to roll back.
sony pc companion says: Sony Update Engine doesn't have software available for your phone
any solution?
My guess would be that you would have to find the 5.02 image file on the forums and flash it through ADB.
I'm not sure you can.
If fact if you could I suspect OTA would update without asking you.... The update before the last one did for me.. I had it on charge looked over to it and it was rebooting after installing the update. No warning, No questions... just did it.
So I wondered this at the last update--from v4 to v5--and after much research, AndroidWear is very much like any Android rom on a phone or tablet. Officially, going backwards in an update is impossible using the stock recovery because each OTA only allows for an update from x version to y version and will error if you try to update from w version. The only way to get backwards is to unlock the bootloader, replace the recovery with something like TWRP and flash an old image. Among many problems that you might experience though is that OTAs are not system images in that they sometimes they only update specific partitions. In short, you run the risk of bricking your watch, just as you could with a phone or tablet.
If you can live with it, keep it. If you can't, start doing your research.
Isn't there a repacked stock rom in development forum? It gets flashed via twrp
Is there a way to block updates from getting pushed to the watch?
As title says reverted back to 13b, trying top keep phone from going to MM, what processes do I disable to make that happen?
Can you not use Ota rootkeeper?
want no OTA when rooted here https://youtu.be/yuxGsiGq3io
if you not rooted and dont wont the OTA here https://youtu.be/c_yxHYE7ogk
---------- Post added at 01:53 AM ---------- Previous post was at 01:49 AM ----------
Tex_Norseman said:
As title says reverted back to 13b, trying top keep phone from going to MM, what processes do I disable to make that happen?
Click to expand...
Click to collapse
i ment to quote your message so sorry for a repeat
want no OTA when rooted here https://youtu.be/yuxGsiGq3io
if you not rooted and dont wont the OTA here https://youtu.be/c_yxHYE7ogk
enjoy
So I am having the issue posted in my pics. I am not part of beta. I am Verizon on September patch. Never touched my sim since I got device. Bootloader is unlocked but that shouldn't matter. Anyway if someone can help me figure out according to the screenshots why I can't update it would be greatly appreciated.
aaronpw0621 said:
So I am having the issue posted in my pics. I am not part of beta. I am Verizon on September patch. Never touched my sim since I got device. Bootloader is unlocked but that shouldn't matter. Anyway if someone can help me figure out according to the screenshots why I can't update it would be greatly appreciated.
Click to expand...
Click to collapse
I got the same problem as well. I'm on Verizon and haven't found a fix.
I've got a Google Play Pixel XL on Verizon, no problem with update. Full stock locked bootloader.
Sent from my BTV-W09 using Tapatalk
I don't understand how you got the OTA so quick. Even with Google saying last month that doing a check for update manually should now get you OTAs instantly, it's not working on my stock bootloader unlocked XL.
Same here.. got the OTA October Android 8.0 Oreo Security Patch without a hiccup... I also have a locked bootloader as well on Verizon Pixel XL version. Really wish these bootloaders could be unlocked but that's another topic that has been saturated to death... lol.
Damn that sucks for you guys that aren't getting it instantly. Checking for update seems to work for me. But try clearing your Google play services app and then see if it will let you download the update you guys.
alobear said:
Damn that sucks for you guys that aren't getting it instantly. Checking for update seems to work for me. But try clearing your Google play services app and then see if it will let you download the update you guys.
Click to expand...
Click to collapse
No need, hes going to brake GPServices and get bunch of force closes.
The check for updates now works on demand when you press it. This has already been confirmed by bunch of folks, and even myself when i did on my wife's phone.
aaronpw0621 said:
So I am having the issue posted in my pics. I am not part of beta. I am Verizon on September patch. Never touched my sim since I got device. Bootloader is unlocked but that shouldn't matter. Anyway if someone can help me figure out according to the screenshots why I can't update it would be greatly appreciated.
Click to expand...
Click to collapse
I just did the manual way of flashing the ota. All good now.
lucky_strike33 said:
I just did the manual way of flashing the ota. All good now.
Click to expand...
Click to collapse
Wish I could. I am out of town working till the weekend.
Google Pixel XL unlocked bootloader and update failing to install. Showing me update size of 50.6 MB.
Will try and patch manually.
I have a Verizon Pixel XL on T-Mobile and i got the October 5th patch yesterday without issue. It took a while for only 64.5mb, but it took it. I did have 1 random reboot this morning though.... BTW, like i said, i took the update with a TMO SIM and still have gray OEM Unlocking
I had the same error. I disabled Block This! and it installed without problems.
Sent from my Pixel XL using Tapatalk
Still waiting for my OTA Oct 5 update. I am complete stock, locked bootloader (never unlocked or rooted). Damn Check for update button not working for me.
So I tried flashing the September patch to both slots manually and taking the OTA but it failed still. So I went ahead and manually flashed the October patch.
I am wondering if it has to do with me upping to Unlimited Data plan on Verizon.
I just checked for an OTA update manually and nothing showed up. I'm still on September patch. Google edition, locked bootloader and not rooted.
westside80 said:
I just checked for an OTA update manually and nothing showed up. I'm still on September patch. Google edition, locked bootloader and not rooted.
Click to expand...
Click to collapse
We're you part of the Beta Program? If so that can be a reason why. You will have to unenroll your device
lucky_strike33 said:
I just did the manual way of flashing the ota. All good now.
Click to expand...
Click to collapse
Hi, can you please share the steps to manual flashing the update i am on stock, rooted SU, september. Thank you.
veskostoev said:
Hi, can you please share the steps to manual flashing the update i am on stock, rooted SU, september. Thank you.
Click to expand...
Click to collapse
Go to Google ota and download October. You can flash the ota through twrp. Flash as you would a rom. That's it.
aaronpw0621 said:
We're you part of the Beta Program? If so that can be a reason why. You will have to unenroll your device
Click to expand...
Click to collapse
I bought the phone off eBay so I'm not sure if it was enrolled but I doubt it was. I guess I could check to make sure.
---------- Post added at 04:51 PM ---------- Previous post was at 04:48 PM ----------
aaronpw0621 said:
We're you part of the Beta Program? If so that can be a reason why. You will have to unenroll your device
Click to expand...
Click to collapse
It was enrolled in the beta program. I just checked. I unenrolled it but since I'm already on the stable build it didn't send me an OTA so I won't have to wipe the phone. I'll go check for an update again and see what happens now that I unenrolled the phone.
westside80 said:
I bought the phone off eBay so I'm not sure if it was enrolled but I doubt it was. I guess I could check to make sure.
---------- Post added at 04:51 PM ---------- Previous post was at 04:48 PM ----------
It was enrolled in the beta program. I just checked. I unenrolled it but since I'm already on the stable build it didn't send me an OTA so I won't have to wipe the phone. I'll go check for an update again and see what happens now that I unenrolled the phone.
Click to expand...
Click to collapse
I didn't think about the beta program - that would sort of make since as to the cause of not getting latest October OTA. Please let us know if you get it now when you do a manual check for update.