Related
I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.
Hey Dude,
I figured I would get to you before the wolves do lol you'll probably get a better response to your questions in the "General" section. To answer you directly there is already rooted versions of this OTA such as (shameless plug) both my Roms Redemptive rEVOlution (Evo hybrid) and Redemption Rom.
OK. Thanks.
RuLEoF2 said:
OK. Thanks.
Click to expand...
Click to collapse
Not a problem enjoy Rom hunting.
RuLEoF2 said:
I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.
Click to expand...
Click to collapse
I've been hitting Cancel on that update message for the last 2 weeks. Today I read about it a bit, and finally just gave in and ran the update. I don't know if it actually updated, but the message is gone, it says my system is up to date, and I still have S-OFF/root. FWIW.
jrocket said:
I've been hitting Cancel on that update message for the last 2 weeks. Today I read about it a bit, and finally just gave in and ran the update. I don't know if it actually updated, but the message is gone, it says my system is up to date, and I still have S-OFF/root. FWIW.
Click to expand...
Click to collapse
you can edit the build prop to make it stop search the skyraider thread i think its in there.
ACD168 said:
you can edit the build prop to make it stop search the skyraider thread i think its in there.
Click to expand...
Click to collapse
I saw that, thanks. I wanted the update, I just couldn't find any solid answers on whether it disabled root or not. It sounded like it disabled root but left S-OFF alone, so I did ran the update, thinking I could root it again later. But now I still have root, so I don't know if the update was actually applied or not.
I'm not worried either way, it was just an experience relevant to the OP's question.
jrocket said:
I saw that, thanks. I wanted the update, I just couldn't find any solid answers on whether it disabled root or not. It sounded like it disabled root but left S-OFF alone, so I did ran the update, thinking I could root it again later. But now I still have root, so I don't know if the update was actually applied or not.
I'm not worried either way, it was just an experience relevant to the OP's question.
Click to expand...
Click to collapse
Go into Settings/About Phone and see what firmware version you have, if it's 26 your updated, if it's still 21, it didn't update.
If you don't know if it's updated, it's prolly not. You would've known as it would've rebooted and then had run the update. If you don't recall any of that, your not updated.
Like was posted previously, you'd be better off finding which ROM has the update and then just flash that, be sure to do a backup 1st and foremost in case you screw up, you can always flash back to what you had and start over.
The only way that update will take is if you have stock with just root and no changes, I did this initially though and you will loose root, which is why I recommend you backup before trying, this way you don't have to root over again.
Edit build.prop. Here is the configuration you'll need to change to stop the OTA updates. This will also help save your battery if it frequently tries to download on 3G.
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys
RuLEoF2 said:
I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
Click to expand...
Click to collapse
If you want to stay put on the version you have now, not accept the update, not be bothered by it again, then following bsdbytes's info for editing the build.prop is what you need to do.
If you want to accept and the NOV OTA update and still have clockworkmod recovery and root after... see -> http://solo.dc3.com/dinc/ (If you have an SLCD incredible, be carefull of which CWM Recovery version you use).
RuLEoF2 said:
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.
Click to expand...
Click to collapse
The current Unrevoked3 (ver 3.21) does not work to root the Nov OTA, nor install a custom recovery. There were tweets about an update coming, but delays due to thanksgiving, finals, etc. I haven't seen an ETA posted yet.
joelcableguy said:
Go into Settings/About Phone and see what firmware version you have, if it's 26 your updated, if it's still 21, it didn't update.
If you don't know if it's updated, it's prolly not. You would've known as it would've rebooted and then had run the update. If you don't recall any of that, your not updated.
The only way that update will take is if you have stock with just root and no changes, I did this initially though and you will loose root, which is why I recommend you backup before trying, this way you don't have to root over again.
Click to expand...
Click to collapse
thanks for the info. you're right, it didn't update, i'm still at 21. when i clicked update a window came up saying it was going to reboot, but it never did. must be due to change i had on the device.
KidJoe said:
If you want to stay put on the version you have now, not accept the update, not be bothered by it again, then following bsdbytes's info for editing the build.prop is what you need to do.
If you want to accept and the NOV OTA update and still have clockworkmod recovery and root after... see -> LINK (If you have an SLCD incredible, be carefull of which CWM Recovery version you use).
Click to expand...
Click to collapse
thanks for that link - i'll try to go through that when i get a chance.
So I am running the stock rom but have root access. the update pops up every 5 minutes to remind me to install it. I let it install and about 3 second in i get a yeild sign with an exclamation point in it. and the phone stops there. I waited for about 3 hours and nothing happened. Anybody know what I need to do here? I used Galaxy Nexus root toolkit v1.3 to root my phone. BTW i am with verizon
For as far as i now you cant update a rooted device. i sugest unrooting an try to update agian.
reply
yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had.
nvm i think im going to trade the phone
So no one has an answer on this?
jordi97 said:
For as far as i now you cant update a rooted device. i sugest unrooting an try to update agian.
Click to expand...
Click to collapse
Yes you can. You can't update a phone with CWM recovery though.
Sent from my Galaxy Nexus using xda premium
Correct a rooted phone can update but not with any custom recovery. You need to flash back to the factory stock recovery.
Sent from a phone...
OK so looks like everyone is here was incorrect. The 4.04 rooted update is here in the XDA forums all i needed to do was flash it and the new antenna and everything is working fine now. here are the links.
4.04 http://forum.xda-developers.com/showthread.php?t=1631796
radio http://forum.xda-developers.com/showthread.php?t=1630438
Thank you Brandon for helping me out with this.
There are no stupid questions only stupid answers.
Sdalton19 said:
OK so looks like everyone is here was incorrect. The 4.04 rooted update is here in the XDA forums all i needed to do was flash it and the new antenna and everything is working fine now. here are the links.
4.04 http://forum.xda-developers.com/showthread.php?t=1631796
radio http://forum.xda-developers.com/showthread.php?t=1630438
Thank you Brandon for helping me out with this.
There are no stupid questions only stupid answers.
Click to expand...
Click to collapse
Your right, stupid answers, that's not an ota update you did. That was pulled from a phone which was updated and packaged into a flashable file to use on a rooted device. But a carrier ota update as your device was asking you to update will not work without stock recovery.
Sent from a phone...
Isn't that exactly what i asked for second post in? Point is if you knew that, why didn't you say so? Look there's nothing wrong with being wrong every once in a while but be graceful about it. And if your going to give advice make sure you fully read the question and offer decent advice. You were saying there was no way to update it without unrooting and flashing back to stock. That was after I asked "yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had." Is that not exactly what I asked for????
Sdalton19 said:
Isn't that exactly what i asked for second post in? Point is if you knew that, why didn't you say so? Look there's nothing wrong with being wrong every once in a while but be graceful about it. And if your going to give advice make sure you fully read the question and offer decent advice. You were saying there was no way to update it without unrooting and flashing back to stock. That was after I asked "yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had." Is that not exactly what I asked for????
Click to expand...
Click to collapse
Well, you are right that there are a lot of partially right and partially wrong answers in this thread. But what are you saying is not exactly right either.
1) There is a difference between updating your existing build (like what you had asked to do in the first post) and flashing an entirely new build.
2) There is a difference between running a stock ROM (like what you were running before) and running a ROM that looks like it's stock, but is not (like what you are running now).
3) Root has NO impact whatsoever on your ability to install OTA updates on your stock ROM.
4) An OTA update will NOT install with a stock recovery UNLESS you are using the stock recovery version that came with the build you are using. (It seems like a lot of toolkits are flashing non-matching stock recoveries).
5) An OTA update file can EASILY be installed if you have CWM installed. See here.
6) Your phrase "unrooting and flashing back to stock" is silly, as flashing back to stock replaces your ROM, so why would you need to "unroot" your current ROM only to flash a stock ROM overtop? You don't root a device - you root an Android OS build. The phrase "root my device" does not make any sense.
So I have a Verizon Pixel XL that has been unlocked, TWRP alpha installed, and rooted....
How shall I update my build? Should I even update the build?
My goal is to have the latest update running on my system (manually flashing or OTA I don't care) with an unlocked rooted Pixel XL that can broadcast wifi natively.
I have everthing down except the update piece. Any advice?
You have TWRP and root? How is that working? I was reading that SuperSu needs an update to work with it. Also many people who have taken the OTA (or even flash full system image) are getting stuck in the bouncing balls boot loop. I would hold off on updating. No real major changes as of yet.
Twrp is working fine but I have nothing to flash to test...????
networx2002 said:
Twrp is working fine but I have nothing to flash to test...????
Click to expand...
Click to collapse
Yeah that is what I'm hinting at.... There is no updated ROM to work with TWRP yet that is updated to the latest Google Build
Root is working. I have twrp alpha 2. Root and elementalx 8 all installed. Although, im getting my daydream headset tomm. And when you install the app it tells you to check for updates. It says I have one. But if you look at the OTA updates NDE63 is the newest. Which im on. So I dn at this point. I guess i'll just roll with it for now. The dev that made purenexus that I ran on my nexus 6. Says hes working on it already and gets his on the 21st. So i'll just stick with what I have for now. I'm sure we'll see roms pretty soon
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
s1dest3pnate said:
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
Click to expand...
Click to collapse
jreink01 said:
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
Click to expand...
Click to collapse
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
DeathSentinels said:
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
Click to expand...
Click to collapse
If you edit the flash-all.bat file and take out the -w near the end you wont flash user data. So you can skip restoring your cloud backup and apps. Backup just to be safe though.
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
jreink01 said:
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
Click to expand...
Click to collapse
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
TonikJDK said:
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
Click to expand...
Click to collapse
OK, thanks, that's good to know. When I lose root, will that mess with any of my apps that need root to work like titanium backup? Or will I just need to grant it user privileges again? I have never done this particular process before so I am a little weiry. Do you know of a step by step guide to do this? Sorry but I would feel more comfortable that way. Thanks for all you help and feedback, it's been years since I last went through the rooting, flashing process so, I guess I am being extra cautious. I have/am learning by the feedback you have given me.
Sent from my Pixel XL using Tapatalk
I am rooted with TWRP RC1
i never sideloaded an OTA before, alway applied factory images. Too lazy, but tired of all the rework.
i folllowed,
https://9to5google.com/2016/12/05/how-to-sideload-android-7-1-1-nmf26o-onto-the-pixel/
no data loss.
just had to use fastboot to reinstall TWRP and reflash SUPERSU.
All is well.
If I choose to side load it, do I root and install TWRP the same way I did when I first did this, with ADB on my windows PC? And side loading will work with a new operating system (when it comes out) along with the monthly security updates? I just checked and my latest security update is from January. If I updated March's update, would that automatically have the February one with it?
---------- Post added at 02:10 AM ---------- Previous post was at 02:02 AM ----------
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
jreink01 said:
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
Click to expand...
Click to collapse
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
TonikJDK said:
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
Click to expand...
Click to collapse
Yes, I am in the beta program, that's why I am on this version. So, I'm assuming the beta's don't get updates then? I have turned off automatic updates since I'm rooted. Would you recommend I turn that back on or no? If I'm correct, I can't take a OTA since I'm rooted so I was correct in turning off automatic updates then? I will probably stay on this version since the difference is improvement and bug fixes. So, when 7.1.2 rolls out to everyone, then I would assume that that version would show up on the Google page then?
Sent from my Pixel XL using Tapatalk
Just ordered a new Nexus 5x a few days ago should be here soon. It'll probably still have Marshmallow on it. Should I only flash custom ROMs. Immediately to avoid bootloop issues u have been hearing about? I'm confused because it seems that the OTA or preview edition was causing this not custom ROMs.
To me, it depends what you want to do with your device.
For me, I downloaded the latest 6.X and flashed manually. Relocked the BL and enrolled in Android beta program. Then let the OTA 7.1.1 come down to upgrade the device so I continue to get updates, including upgrade to production release down the road.
mikeprius said:
Just ordered a new Nexus 5x a few days ago should be here soon. It'll probably still have Marshmallow on it. Should I only flash custom ROMs. Immediately to avoid bootloop issues u have been hearing about? I'm confused because it seems that the OTA or preview edition was causing this not custom ROMs.
Click to expand...
Click to collapse
More signs point to hardware failure rather than the update. I think it was just coincidence that 7.0 came out when phones were getting close to 1 year old. I've been running my replacement from last month on 7.1 beta and it's just fine.
Sent from my Nexus 5X using Tapatalk
Ezekial said:
To me, it depends what you want to do with your device.
For me, I downloaded the latest 6.X and flashed manually. Relocked the BL and enrolled in Android beta program. Then let the OTA 7.1.1 come down to upgrade the device so I continue to get updates, including upgrade to production release down the road.
Click to expand...
Click to collapse
So you have just been flashing new images manually? For me I don't care about the newest version I sill am using Marshmallow on my Nexus 6. I prefer customization so I'm going to unlock, TWRP, custom ROM etc........ I just want to potentially avoid any of the bootloop issues I have been hearing about.
It sounds like there was never a definitive conclusion as to why it was happening only with Nougat
mikeprius said:
So you have just been flashing new images manually? For me I don't care about the newest version I sill am using Marshmallow on my Nexus 6. I prefer customization so I'm going to unlock, TWRP, custom ROM etc........ I just want to potentially avoid any of the bootloop issues I have been hearing about.
It sounds like there was never a definitive conclusion as to why it was happening only with Nougat
Click to expand...
Click to collapse
Gotcha. I have only had my 5x for just over a month so not the most knowledgeable. My take is largely the same as the other guy, failures are from hardware or just bloat from long term use.
I start with the latest 6 and considered staying on it for root, xPosed, etc. I have always ran this way for years. But it is super annoying not having Android pay and a few other things. I sucked it up and decided to try not rooting or even unlocking BL. There are things I miss but I am staying locked down for now. The primary issue I have is for tethering, which I cannot do. The rest I have surprisingly been able to do without.
Flash away
Hey mate, you will not have issues flashing what ever you like, issues are caused by hardware failures ( unavoidable ) or just not following instructions correctly. I flash factory images, beta etc, and custom ROMs. Never have issues. Flash like crazy. It's just a phone and almost all of them can be fixed, if something goes wrong.
P.s. You gotta try the 7.1.1 beta. Its has potential.
Hi. I own a moto g5 xt1670, stock nougat with some security patch I believe. I'd like to stay on nougat for a while, so I guess I must root, then freeze the updater app because it's turning pretty annoying. The question is...can I install Oreo Ota with the device rooted in case I want in the future?
I'm not planning to install roms, so I prefer to stay on locked BL.
Many thanks.
no
mortadelax said:
Hi. I own a moto g5 xt1670, stock nougat with some security patch I believe. I'd like to stay on nougat for a while, so I guess I must root, then freeze the updater app because it's turning pretty annoying. The question is...can I install Oreo Ota with the device rooted in case I want in the future?
I'm not planning to install roms, so I prefer to stay on locked BL.
Many thanks.
Click to expand...
Click to collapse
Well to start with you need to unlock your bootloader if you want to root your device
And otas can only be installed on a totally unmodified device so you would need to flash stock firmware via fastboot (and lock the bootloader to make sure the images are totally unmodified) before any ota is attempted to installed
Thanks both of you for the reply!
So, let's say I'm not interested in Oreo Ota, how can I stop the upgrade spam notification? I guess I must unlock BL, then root, then freeze the updater app. Is that correct? In case I want Oreo in the future I guess I can install some rom...
Does this make sense? I've read bad reviews about oreo and battery drain. This is my mother's phone. I don't want any possible problem. Nougat is just fine, and works well.
Thanks a lot. I'll be waiting for your reply.
mortadelax said:
Thanks both of you for the reply!
So, let's say I'm not interested in Oreo Ota, how can I stop the upgrade spam notification? I guess I must unlock BL, then root, then freeze the updater app. Is that correct? In case I want Oreo in the future I guess I can install some rom...
Does this make sense? I've read bad reviews about oreo and battery drain. This is my mother's phone. I don't want any possible problem. Nougat is just fine, and works well.
Thanks a lot. I'll be waiting for your reply.
Click to expand...
Click to collapse
Force stopping system update app (you need to show system apps in app list) will temporarily remove the notification until restart or the app starts again
And as far as I'm aware there's nothing wrong with oreo - Always makes me laugh when people say they have read something but provide no source or context