I just got the update msg and i am afraid to update because if i do i may lose the Root and ect ha?!
I'm pretty sure you don't have the OneUI 2.5 update. Maybe the OneUI 2.1 but definitely not the 2.5 one. Even the S10/Note10 don't have it yet and we're after them. Also if you're rooted you shouldn't receive OTA updates at all. Can you attach a screenshot so it's clearer what you got?
This is what i got. May be it is or some security + software update
That was last months update.
The August update is ETH1
Ohh!!! Ok i thought it's the new one ??* if i update this i will lost root and may be boot loop?
I still think that if you're rooted you shouldn't have received this though. You sure you're rooted? Check with this app please just in case: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck
Yes. Rooted and using all rooted apps in here
Related
Has anyone else received this update?
Not here.
Los Angeles, CA
lol figures once i get root an update starts rolling out, it probably enables wifi n like they released for the EVO today.
1.22.605.2 is the software version i have (rooted)
It adds 3G Mobile hotspot and fixes the signal issue, im in a pickle now though lol. cant remove superuser
Not exactly a pickle - just don't do the upgrade, wait for someone else to take the OTA download and make it root-safe.
where did you confirm this info as to what the update offers?
I guess i am confused, what would happen if we did the update with our rooted phones?
Nothing. Because with rooted phones you won't see the OTA Update...but if you were to manually upgrade without it being root proofed....you'd loose root.
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
giantcrazy said:
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
Click to expand...
Click to collapse
Incredible OTA Update 1.65.605.2
I'm confused to, so if you are rooted, you won't see this update? or you will see it and if you do it, you lose root? I have the stock rom, which is what I thought disabled your OTA's is this an incorrect thinking?
giantcrazy said:
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
Click to expand...
Click to collapse
The name of this post is Incredible OTA Update 1.65.605.2 so even though we are at 1.22.605.2 that is not 1.65.605.2
Thats the thing, i was rooted and did get the OTA update notifications, hit accept for the update by mistake. And the only reason why i confirmed that info is because i have it on my inc.
P.S sorry lol made a type in the title of the post, its 1.35.605.2
So if you updated as root, did you lose your Root? It is not guaranteed that you would loose it, just likely is all. I feel like they released it to break our Root, and nothing more... but maybe they fixed a few issues too... we have the same screen grounding issue the EVO had, and the recent update fixed theirs... but who knows...
EDIT: Posted an article to an outdated update. Oops...
so i assume you lost root?
Yes i did.
I haven't seen it yet. <-- OHIO
have you tried redoing root? did you loose recovery?
I havent tried redoing the root process again, but how is that going to work? isn't the root process based off of the original software? the baseband is different as well.
Haven't seen it yet either <-- Rhode Island
Didn't find any information on it either. Was their a "more info" link included with yours? as with other OTA updates. Changelog, etc.?
Better question would be, do you have a screen shot of your About Phone page (baseband, software version, etc.)
somebody who gets the update needs to upload the file so a dev can do something with it.
Hi,
I have a rooted I9295, after the last ota update (2 weeks ago) i noticed that my wifi stopped working and i get an annoying message "Prevention Information". I think the update failed on the radio part which is causing this.
I'm currently on android 4.2.2 with baseband version MF5 and ML3 buildnumber.
can anyone point to a fix ?
thx !
Rexxen said:
Hi,
I have a rooted I9295, after the last ota update (2 weeks ago) i noticed that my wifi stopped working and i get an annoying message "Prevention Information". I think the update failed on the radio part which is causing this.
I'm currently on android 4.2.2 with baseband version MF5 and ML3 buildnumber.
can anyone point to a fix ?
thx !
Click to expand...
Click to collapse
I'm not sure if this is the right modem, but it could be. Hopefully somebody else will reply with a proper solution.
The latest OTA update was for 4.3. Looks like you didn't update at all, but the process borked something up on your phone. Maybe a factory reset will fix your phone. Yeah, major pain, but had you gotten the 4.3 update you'd really be screwed since going back would not be an option and you would have lost root.
Miami_Son said:
The latest OTA update was for 4.3. Looks like you didn't update at all, but the process borked something up on your phone. Maybe a factory reset will fix your phone. Yeah, major pain, but had you gotten the 4.3 update you'd really be screwed since going back would not be an option and you would have lost root.
Click to expand...
Click to collapse
Unfortunately we're not so lucky in Europe, still no 4.3 update.
The latest OTA update we had here added some more Samsung bloatware and a nice message warning you to close the flappy charge port after charging.
I had a rooted 4.2.2, and i think that caused the problem.
Going to try to update the radio with Odin.
Rexxen said:
Unfortunately we're not so lucky in Europe, still no 4.3 update.
The latest OTA update we had here added some more Samsung bloatware and a nice message warning you to close the flappy charge port after charging.
I had a rooted 4.2.2, and i think that caused the problem.
Going to try to update the radio with Odin.
Click to expand...
Click to collapse
Did this work out for you? I'm having the same issue.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
So i ended up doing this:
First i flashed the entire phone (since i couldn't find just the modem)
http://honai-android.blogspot.nl/2014/01/how-to-update-galaxy-s4-active-i9295.html
After that i rooted the phone again
http://androidxda.com/root-samsung-galaxy-s4-active-gt-i9295
And that fixed the issues.
Everything works fine again, and i didn't loose any data in the process.
So, I have a rooted G4 with Tmo, however I have been receiving an alert to update my device for the last few days, but am not sure what to do. The alert isn't going away and its annoying. What can I do?
Download titanium backup and freeze update app.
What's the update app, what if it isn't visible in tb?
XDDavie said:
So, I have a rooted G4 with Tmo, however I have been receiving an alert to update my device for the last few days, but am not sure what to do. The alert isn't going away and its annoying. What can I do?
Click to expand...
Click to collapse
In TiBu:
Freeze -
com.tmobile.pr.adapt
In Root Explorer -
system/pri-app/
LGUpdateCenter.apk changed to
LGUpdateCenter.apk.bak
system/app/LTDDM/
LTDDM.apk changed to
LTDDM.apk.bak
You should probably figure out how to apply the update because it makes the phone 1000000% better. You can root it again after you update it or just update it using a rooted image and save some time.
willshep said:
You should probably figure out how to apply the update because it makes the phone 1000000% better. You can root it again after you update it or just update it using a rooted image and save some time.
Click to expand...
Click to collapse
Agreed.
After updating to 10N, you can then block future OTA Updates via my previous post.
I updated to 10N using this method. Works great:
http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-rooted-rom-t3188858
so the update you have been receiving was or is for 10n? if so then just flash the 10n xtreme rom from micromod and you will be all set for it includes tweaks and no more ota surprises too
The update isn't working for me. I used the "Low Effort Root," and I may have made a half-hearted attempt at blocking OTA, but I keep getting prompted for the update.
Accepting it causes the phone to to reboot and try to install, but then it just says "Error" and hangs. After a few minutes, it reboots, and I am still at H81110h.
Any ideas? I like the idea of low effort, and not flashing another ROM. I would rather just take the update, and re-root if needed.
Hello all, I have a Nexus 6 and I'm using it on Verizon's network. I have yet to receive the Android 7.0 OTA update. Should I have gotten this already or is there something possibly wrong with my situation? I've searched online and it seems like I should have gotten the update already. I appreciate any help.
You should have had it by now (unless you have modified your phone in any way that might interfere with the OTA process)
Your best bet would be to sideload the OTA from https://developers.google.com/android/ota
Yeah, it's a bone stock Nexus 6. I got it from Amazon around this time last year, and I received the 6.0.1 OTA update and I receive the android security patch updates. Just no update to 7.0.
When my Australian carrier delays updates I used to change my SIM to a foreign one (cambodia, vietnam, thailand, or whatever) and the update used to immediately appear. The SIM doesn't even need to be active.
Now that Google publish the OTA files, it's easier just to sideload it.
Anyway, try a different SIM (t-mobile or whatever you can find locally) and see if it appears (you need to reboot). Otherwise, Verizon only just approved the update a few days ago so might take a while to roll out to you.
I think that there are a lot of N6 (mine is on T-mobile) out there that have not seen an OTA. I got the 6.01 November secuity patch last week. Was expecting 7.0.
I went ahead and did a sideload of the OTA 7.0. This won't break any future OTA updates, will it?
xdatastic said:
When my Australian carrier delays updates I used to change my SIM to a foreign one (cambodia, vietnam, thailand, or whatever) and the update used to immediately appear. The SIM doesn't even need to be active.
Now that Google publish the OTA files, it's easier just to sideload it.
Anyway, try a different SIM (t-mobile or whatever you can find locally) and see if it appears (you need to reboot). Otherwise, Verizon only just approved the update a few days ago so might take a while to roll out to you.
Click to expand...
Click to collapse
Ah.. I'm kind out of the loop these days, but I thought the Nexus devices got their updates straight from the Google. So I figured the carrier had nothing to do with how or when you got your updates.
russ4h said:
Ah.. I'm kind out of the loop these days, but I thought the Nexus devices got their updates straight from the Google. So I figured the carrier had nothing to do with how or when you got your updates.
Click to expand...
Click to collapse
The updates come from Google, but some carriers in some countries require an approval process (it's the same for Apple iphone, but is done more seamlessly and under NDA). Here in Australia, any devices sold by a carrier must go thru an approval process to make sure the software doesn't violate any compliance regulations (such as ability for emergency calling when no sim is present). Once Google get the go-ahead, they push the update to the phone with the relevant sim card in (or in some cases the IMEI). This can sometimes (dependant on current software version) be bypassed by changing the sim to one that doesnt require approval or has already been approved. Bear in mind however, you may get a software build not intended for your carrier.
Here's verizon's update info from a few days ago:
https://www.verizonwireless.com/support/google-nexus-6-update/
xdatastic said:
The updates come from Google, but some carriers in some countries require an approval process (it's the same for Apple iphone, but is done more seamlessly and under NDA). Here in Australia, any devices sold by a carrier must go thru an approval process to make sure the software doesn't violate any compliance regulations (such as ability for emergency calling when no sim is present). Once Google get the go-ahead, they push the update to the phone with the relevant sim card in (or in some cases the IMEI). This can sometimes (dependant on current software version) be bypassed by changing the sim to one that doesnt require approval or has already been approved. Bear in mind however, you may get a software build not intended for your carrier.
Here's verizon's update info from a few days ago:
https://www.verizonwireless.com/support/google-nexus-6-update/
Click to expand...
Click to collapse
Hey, thanks! I guess I just needed to wait a little while longer haha. I just finished the sideload and everything seems to be working well. Do you know if the sideload process somehow breaks future OTA updates?
russ4h said:
Hey, thanks! I guess I just needed to wait a little while longer haha. I just finished the sideload and everything seems to be working well. Do you know if the sideload process somehow breaks future OTA updates?
Click to expand...
Click to collapse
Nope, the sideload doesn't break future OTA updates (however it theoretically could if you flashed a build not intended for your carrier, however usually Google just send a 'Full OTA' which a large download to your device to get it back on the correct build).
Enjoy.
I was offered 7.0 and it took rooted
So ive been rooted since u bought the phone when it came it in 2014 and have sideloaded any updates and i received the 7.0 notice OTA and i figuredbid just see if it would update. It did and then i list root , wh?? Im green with Android but i struggke through it to get ehat i need done so im sorry if this is a noob question.
Nexus 6
Was the 59 build first series.
I was rooted with SuoerSU.
tbared said:
So ive been rooted since u bought the phone when it came it in 2014 and have sideloaded any updates and i received the 7.0 notice OTA and i figuredbid just see if it would update. It did and then i list root , wh?? Im green with Android but i struggke through it to get ehat i need done so im sorry if this is a noob question.
Nexus 6
Was the 59 build first series.
I was rooted with SuoerSU.
Click to expand...
Click to collapse
I always lose root when flashing an image or installing an OTA update. It is normal for that to happen. You just need to root your phone again by installing SuperSU . The latest version is SuperSU v2.78 SR5 and can be found here.
I joined (then left) the Beta program so i can get a stable release of 7.0 Nougat a little over a month ago. Good so far but what I'm concerned about is security patches. Ever since I got on Nougat, my N6 no longer gets OTA security patches. I'm still on the October security patch. Anyone know what's going on?
Regardless, even with a mod'd phone, I got the 7.0 nag 2 weeks ago - which spurred me to wipe everything and flash it with NRT.
alryder said:
I always lose root when flashing an image or installing an OTA update. It is normal for that to happen. You just need to root your phone again by installing SuperSU . The latest version is SuperSU v2.78 SR5 and can be found here.
Click to expand...
Click to collapse
Thanks as soon as i have some time i will reinstall and flas..
As of today my Moto X4 A1 shows the latest security update as April 1, 2019 and the update check says it is up to date. Can anyone confirm this is accurate?
UPDATE: I have received the security update for May 1, 2019.
Mine is the same unfortunately. Seems like google doesn’t keep up as well with Android One devices
Sent from my iPhone using Tapatalk
Mine is trying to update to May 1 today but is failing because I'm rooted. Does anyone know where to find the update on my phone so I can sideload after going back to stock?
LankiCat said:
Mine is trying to update to May 1 today but is failing because I'm rooted. Does anyone know where to find the update on my phone so I can sideload after going back to stock?
Click to expand...
Click to collapse
If you flash back to stock, you should the be able to take the OTA update. I have XT1900-1. Not sure how to get the OTA file off the phone to flash it manually though.